Initializing... drag & drop files here
Supports: OGV
Almost everyone who lands here is moving between two formats that have both been left behind, and the useful question is not "how do I convert" but "which target should I be aiming at". Ogg Video is an open container from the Xiph project that current browsers no longer decode. F4V is Adobe's later Flash video format, and Adobe stopped supporting Flash Player on 31 December 2020 and began blocking Flash content from running on 12 January 2021.
So this page leads with a comparison rather than a how-to, because the honest answer for most visitors is that OGV to MP4 is the conversion they want. F4V is worth choosing in one narrow case, described below — and there is a structural quirk in the format that makes the decision less costly than it looks.
| Property | F4V | FLV | MP4 |
|---|---|---|---|
| Underlying structure | ISO base media (the MP4 family) | Adobe's own container, unrelated to ISO base media | ISO base media (ISO/IEC 14496-12) |
| File signature | ftyp box with major brand f4v |
The three ASCII bytes FLV |
ftyp box with major brand isom, mp42 or similar |
| Video written by this converter | H.264 | H.264 or older Flash codecs | H.264 |
| Audio written by this converter | AAC or MP3 | AAC or MP3 | AAC |
| Made for | Flash Player 9 Update 3 onward, and Adobe streaming servers | Flash Player, from the Sorenson/VP6 era onward | Everything |
| Plays in a browser today | No — nothing decodes it natively | No | Yes |
Renaming to .mp4 helps |
Usually yes — see below | No, the container is genuinely different | n/a |
The last row is the one worth knowing. We converted a test .ogv and read the container header of the result: the major brand is f4v and the compatible brands are f4v isom iso2 avc1. That is a real ISO base media file with a Flash-specific brand stamped on the front, so a player that inspects the boxes rather than the extension will normally handle it, and copying it to a .mp4 name is read as an ordinary MP4. FLV has no such escape hatch — its bytes begin FLV and nothing about it resembles an MP4.
.ogv onto the page or click "Add Files". Several files can be queued and converted with one set of settings..f4v. Files are uploaded over an encrypted connection, re-encoded on our servers, and deleted automatically after a few hours — no sign-up, no watermark.We ran a 640 × 360 Theora-and-Vorbis .ogv through this conversion and inspected the result:
| Property | Measured value |
|---|---|
| Container brand | ftyp box, major brand f4v , compatible f4v isom iso2 avc1 |
| Container family reported by probe tools | mov,mp4,m4a,3gp,3g2,mj2 — the MP4 family |
| Video stream | H.264, 640 × 360, matching the source frame size on Keep original |
| Audio stream | AAC, 48,000 Hz, stereo — the Vorbis track's own rate and layout preserved |
| Alternative audio | Selecting MP3 instead produced an MP3 stream in the same container without error |
Both streams are decoded and re-encoded on the way through; nothing is copied across untouched, so a second generation of lossy compression is applied to audio that Vorbis had already compressed and video that Theora had already compressed. On a Theora source that matters more than usual, because Theora is a weaker codec than H.264 and its artifacts are what the new encoder will be spending bits on preserving.
There is a real case for it, and it is narrow: you are feeding a system that was built around Adobe's video stack and never migrated — an on-premises Adobe Media Server, an old learning-management or digital-signage platform, a kiosk application, or an archive whose ingest rules name .f4v explicitly. Those systems still exist, they still work inside their own walls, and they will reject an .mp4 on the extension alone.
If that is not you, the target you want is MP4. It plays in every browser, on every phone, in every editor, and on television hardware, and it carries the same H.264 and AAC streams this page would have produced. OGV to MP4 is the same conversion with a container everything reads. If your destination is genuinely the older Flash container rather than the newer one, OGV to FLV writes that instead — but note that FLV is a different container, not a rebranded MP4, so the rename trick does not apply there.
Not natively in a browser, and not in Flash Player, which Adobe stopped supporting on 31 December 2020 and which has blocked Flash content from running since 12 January 2021. VLC, mpv and most desktop players will open the file anyway because they read the container structure rather than trusting the extension — and since the output is genuinely an ISO base media file with an f4v brand, most of them treat it as an MP4. Anything that insists on the .mp4 extension will accept a renamed copy.
They share a lineage and nothing else structurally. FLV is Adobe's original Flash Video container, with its own header and tag layout, and its bytes literally begin FLV. F4V is the later format Adobe introduced with Flash Player 9 Update 3, built on the ISO base media file format — the same skeleton as MP4 — with a Flash-specific brand. We checked both: our F4V output carries isom and avc1 among its compatible brands, while the FLV output shares nothing with it. That is why F4V renames to .mp4 and FLV does not.
Because it is the only one on the allow-list for this target. Each codec entry in the option set carries a list of output formats it may be used with, and F4V appears only on the H.264 entry's list, so the Video Codec group shows a single item. That is faithful to the format: F4V was introduced precisely to bring H.264 into the Flash ecosystem, replacing the Sorenson Spark and VP6 codecs that FLV had used.
AAC unless something downstream demands otherwise. It is the more efficient encoder — at any given bitrate it retains more of the original — and it is the audio codec F4V was designed around. MP3 exists on this page for compatibility with older Flash-era tooling that expected it. We confirmed that both choices produce a valid file; the difference is quality per byte, not whether it works.
No. This is a lossy re-encode of a lossy source, so the realistic outcome is "the same picture or slightly worse, in a different container". Theora is an older and weaker codec than H.264, which means the new encoder spends part of its bit budget faithfully reproducing Theora's own artifacts. Raising the quality setting reduces how much additional damage is done; it cannot recover detail Theora discarded when the .ogv was made.
Because current browsers no longer decode Theora, the codec Ogg Video normally carries. Chrome disabled it by default in version 120 and Chromium removed it in version 123; Firefox disabled it by default in version 126; Safari never shipped it. The file is not damaged — VLC and mpv still play .ogv perfectly, and this converter decodes it server-side without difficulty.
Yes. Switch Trim from Unchanged to the time range and enter a Start time and a Duration, either in seconds or as HH:MM:SS.sss. Only that window is decoded and re-encoded, which is also the quickest way to test a settings combination before committing to the whole file.
It is decoded and re-encoded to whichever codec you selected — F4V cannot hold Vorbis, so a re-encode was always going to happen. In our test the AAC output kept the source's 48,000 Hz stereo layout, so the channel arrangement and sample rate carried over even though the codec did not. Metadata in the Ogg comment block does not survive the container change.
Your .ogv is uploaded over an encrypted connection, decoded and re-encoded on our servers, and both the upload and the resulting .f4v are deleted automatically after a few hours. Files are never shared or made public, there is no watermark and no account is required. Since the work happens server-side, the practical constraint on a long clip is upload size and time rather than your own hardware.