F4V to TS Converter

F4V to TS Converter

An .f4v file is Adobe's Flash MP4 container — an ISO base media file (MPEG-4 Part 12) with Flash-specific metadata, introduced so Flash Player could carry H.264 video and AAC audio properly. Support arrived with Flash Player 9 Update 3 on December 3, 2007, and F4V existed precisely because the older FLV structure ran into limits when streaming H.264 or AAC. A .ts file is an MPEG-2 Transport Stream, standardised as ISO/IEC 13818-1 and ITU-T H.222.0, and it is what broadcast, IPTV and HLS segments are built on.

There is a neat symmetry to this conversion. F4V was the container Adobe built to stream modern codecs over the web; the transport stream is what took over that job once Flash was gone. Your file already holds the codecs a transport stream wants — the work is repackaging it into a format that current streaming stacks read.

F4V Format at a Glance

TS Format at a Glance

How to Convert F4V to TS

1. Upload Your F4V File: Drag the .f4v onto the page or click "+ Add Files". Batch uploads convert with a single set of settings.
2. Leave Video Codec and Audio Codec Alone: Both open on the values your F4V almost certainly already contains — H.264 and AAC — which is also the pairing HLS and modern transport-stream players expect. Change them only for legacy broadcast equipment, where MPEG-2 video with MP2 audio is the period-correct choice.
3. Pick a File Compression Mode: The panel opens on Quality Preset at "Very High (Recommended)". Constant Bitrate, Variable Bitrate, Specific file size, Constant Quality and Constraint Quality are all available and all behave normally on an H.264 target — Constant Quality exposes a CRF slider that opens at 23.
4. Set Resolution or Trim, Then Convert: Video resolution opens on Keep original, which is what you want when the source is already H.264 at a sensible size. Trim opens on "Unchanged" and takes a Time Range. Click Convert to download the .ts. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark.

The Codecs Match, but This Is Still a Re-encode

It is tempting to think of F4V to TS as a pure repackage, because an F4V holding H.264 and AAC contains exactly what a transport stream is happy to carry. The containers really are the only thing that differs at the format level.

The conversion is still a fresh encode. The video is decoded and compressed again rather than copied across packet boundaries, so the output takes one generation of loss, and that is worth planning for: keep Video resolution on "Keep original", choose a high Quality Preset or a generous bitrate, and do the conversion once from your original file rather than chaining it through other formats first. Expect the output to be somewhat larger than the input at default settings — in our testing a 10-second 1280x720 F4V of 2.02 MB produced a 2.75 MB transport stream, the difference being the encoder's default quality target plus the transport stream's per-packet header overhead.

Frequently Asked Questions

Is F4V the same as FLV?

No, and the difference is exactly why F4V exists. FLV is Adobe's older Flash Video container, built around Sorenson Spark and VP6 video with Nellymoser or ADPCM audio. F4V is a completely different structure — an ISO base media file, the same family as MP4 — created because FLV's layout ran into functional limits when carrying H.264 and AAC. F4V deliberately does not support the FLV-era codecs at all. If your file is a .flv, this page is not the right one for it.

Is F4V just a renamed MP4?

Very nearly, but not exactly. Both are ISO base media files with the same ftyp, moov and mdat structure, and the video and audio essence inside is stored the same way. What differs is the metadata: F4V carries Flash-specific metadata formats that plain MP4 does not. Many players open a .f4v by sniffing the container and ignoring the extension, which is why renaming sometimes appears to work — but the metadata differences are real and a strict parser can tell them apart.

Why is the transport stream bigger than my F4V?

Two reasons, and both are expected. The encode is fresh rather than copied, so the encoder spends bits according to its own quality target rather than matching the source's bitrate — at the default settings that usually lands a little above where the source sat. On top of that, a transport stream adds a 4-byte header to every 184 bytes of payload and interleaves program tables at intervals, which is a few percent of pure overhead. If size matters, raise the CRF value under Constant Quality or set a Specific file size.

Can I concatenate several converted TS files into one?

Yes, and it is one of the format's real advantages. Because a transport stream is a run of self-contained 188-byte packets rather than a single indexed file, clips encoded with matching codec, resolution and frame rate can be joined end to end and play as one continuous stream. Convert each F4V with identical settings so the streams line up — mismatched resolutions or frame rates will make players stumble at the joins.

Does the TS keep the metadata from my F4V?

Almost none of it. F4V stores Flash-oriented metadata in its moov structure — cue points, custom fields, and the descriptive data Flash tooling wrote — and a transport stream has no equivalent place to put any of that. What crosses over is the picture and the sound. If the metadata is important to your workflow, record it separately before converting, or keep the original F4V alongside the transport stream.

Which codec should I choose for older broadcast hardware?

MPEG-2 video with MP2 audio. That is the original DVB and ATSC payload and the only combination receivers from that generation decode. Two things to expect: the file gets considerably larger, because MPEG-2 needs several times the bitrate of H.264 for comparable detail, and the quality-based sliders stop behaving as labelled — on an MPEG-2 target a Constant Quality or Constraint Quality value is converted internally into a bitrate figure. Use Constant Bitrate or Variable Bitrate when you need to hit a number on that path.

Should I be converting to TS, or to MP4?

MP4 unless something downstream requires a transport stream. Given that your F4V already holds H.264 and AAC, F4V to MP4 produces a file that plays on essentially every device and app with less packet overhead than a .ts carries — it is the natural destination for Flash-era video. Choose TS when the destination is a segmenting pipeline, an IPTV or broadcast chain, or a workflow that appends clips into one stream. For a container that also handles multiple audio tracks and chapters, F4V to MKV is the middle ground.

What opens a .ts file after conversion?

VLC reads transport streams on Windows, macOS and Linux without extra components, and broadcast, editing and segmenting tools consume them natively since that is the format they were designed for. Consumer players and browsers are less reliable with .ts — the format is a delivery and transport one rather than a sharing one. If a player refuses the file, first confirm it supports the H.264-in-TS pairing this page produces by default.

Can I still play the original F4V?

Not in a browser. Adobe ended Flash Player support on December 31, 2020 and began blocking Flash content on January 12, 2021, so the runtime F4V was designed for is gone. The good news is that F4V's contents are ordinary H.264 and AAC in an ISO base media container, so VLC and most desktop players open .f4v files directly without any Flash component. That is also why converting them is straightforward — the codecs inside never went anywhere, only the player did.

How are my files handled?

Your .f4v is uploaded over an encrypted connection, converted on our servers, and both it and the transport stream are deleted automatically a few hours later. Files are never shared or made public and no account is required. Flash-era video is usually modest in size, so the whole round trip is generally quick.