What is the difference between FLV and F4V?

Both are Adobe video formats, but their internal structures are different. FLV is Flash's own proprietary container format and can carry Sorenson Spark, VP6 or H.264. F4V is the container Adobe later developed on the basis of the MP4 standard; in other words F4V is actually much closer to MP4. Confusion arises because some download tools mistakenly save F4V files with an .flv extension. If your file will not open, it is worth checking its real format.

Why do FLV files look so low quality?

The reason is not the container itself but the conditions of the era. FLV was designed for streaming over internet connections with narrow bandwidth; videos were usually encoded at low resolutions such as 320x240 or 480x360 and at low bitrates. In other words, the quality loss happened when the file was first produced, not during conversion. Converting that recording to MP4 does not improve the picture, it only makes it openable.

Will my FLV files become completely unopenable one day?

Becoming completely unopenable is not expected in the near term, because open source tools such as VLC and FFmpeg maintain FLV support. But the direction is clear: no new device, browser or application is adding FLV support, and the existing support only diminishes over time. If there are FLV recordings in your archive that you care about, moving them to MP4 without waiting is a reasonable archiving decision.

If there is H.264 inside, why does FLV still cause problems?

Because the problem is not the picture itself but the container wrapped around it. Your device's chip can decode H.264 without any trouble, but the player software first has to be able to open the FLV container and pull the data out of it. Most modern players contain no FLV parser at all, so they reject the file without recognising it. That is why with files of this kind the conversion is not a quality operation, it is simply a change of packaging.

What Is FLV? Why This Format Was Abandoned Entirely After Flash

The standard of an era: how FLV came about

When you visit a video site today, the video opens directly in the browser's own player. That is a much more recent state of affairs than you might think. For most of the 2000s browsers could not play video on their own; a plugin sat in between, and that plugin was almost always Adobe Flash Player.

Flash had its own container for carrying video: FLV, that is, Flash Video. It was a lightweight format, designed for the internet infrastructure of the time and optimised for streaming. The first years of video sharing sites were built entirely on this format. So an old FLV file in your hands is really a relic from the earliest period of internet video.

FLV is a container, not a codec

This distinction is the key to understanding FLV. The container is the outer layer that holds video and audio data together and stores the timing information between them. The codec determines which algorithm that data was compressed with. FLV is a container; what is inside varies from file to file.

Over the history of the FLV container the following codecs were carried inside it:

Sorenson Spark: the video codec of the earliest period. Weak compression, low quality, but light enough to run on the hardware of the day.
VP6: the next generation. It gave noticeably better picture than Sorenson and was widely used for a long time.
H.264: supported in Flash's final years. The codec still used everywhere today.

On the audio side you see MP3, Nellymoser, which was designed for speech, and in the later period AAC.

This variety produces a practical consequence: two FLV files can look identical from the outside and yet be completely different inside. One may carry data compatible with today's standards while the other is compressed with an algorithm abandoned twenty years ago.

Why did FLV work in its day?

FLV's success came not from technical elegance but from solving the right problem at the right moment.

A streaming-friendly structure. An FLV file consists of small data packets lined up one after another. The player does not need to download the whole file; it can start playback the moment the first packets arrive. In an era when connections were slow, that was a decisive advantage.

One plugin, every browser. Flash Player was installed on almost every computer in those years. For a content producer that meant never having to think about browser compatibility.

Lightness. The container itself added very little overhead; on narrow bandwidth every kilobyte mattered.

So why did it disappear entirely?

FLV's end was really Flash's end. But that end came not from one cause but from several developments piling on top of each other.

Browsers started playing video themselves. Once built-in video support was added to the HTML standard, the need for a plugin disappeared. Browsers built that native support on MP4 and WEBM — FLV never featured on that list at all.

Mobile devices never accepted Flash. iOS never supported Flash Player. As the weight of internet traffic shifted to phones, Flash-based video was necessarily pushed aside.

Security problems. Flash Player was associated with serious security vulnerabilities for years. That accelerated the move away from the plugin by organisations and browser makers alike.

Adobe pulled the plug. When support for Flash Player was formally ended, the only infrastructure keeping FLV alive disappeared as well. The format died without leaving an owner behind it.

What does this history mean for the file you have?

We arrive at this practical conclusion: FLV has no future, but the data inside it can still be rescued.

If your file belongs to Flash's final period and has H.264 video with AAC audio inside, moving to MP4 is only a container change. The picture data stays bit for bit the same, the compression algorithm never runs, and there is no quality loss. This operation is called a remux and it is fast.

If your file is older and has VP6 or Sorenson Spark inside, the situation is different. The MP4 container does not carry those codecs, so the picture has to be re-encoded to H.264. That is a genuine compression operation and, to be honest about it, a certain amount of quality loss occurs. On a source that is already low quality that loss can be even more irritating, because it means compression is being applied for a second time. Re-encoding also takes time; on long files the operation can run for minutes.

If you do not know which case you are in, that is not a problem — our FLV to MP4 conversion tool reads the codec inside and picks the lossless path where possible.

The real lesson to take from FLV

FLV's story is more than the story of a single format. What determines whether a format survives is not its technical superiority but the durability of the ecosystem behind it. FLV did its job well in its own era; what killed it was not bad design but the disappearance of the single platform it depended on.

That is why it makes sense to ask this question when archiving: how many different tools will be able to open this format ten years from now? MP4 is the safest answer to that question today — because it leans not on a single company but on a broad standard and on the support of almost every hardware manufacturer.

In summary

FLV was the video container of the Flash era, and when that era ended it went with it. The container itself is not supported today, but the data it carries inside is still usable. With late-era files, moving to MP4 is a lossless change of box; with early-era files it is a rescue operation performed with a certain amount of loss. In both cases there is no advantage whatsoever in staying with FLV; moving the file is the only way to genuinely keep it.