F4V to OGV Converter

F4V or OGV: Two Formats That Both Lost Their Platform

F4V and OGV are, in a sense, the same story told twice. F4V was Adobe's answer to "Flash Video needs to hold H.264", and it lived and died with Flash Player, which Adobe shut down on 31 December 2020. OGV was the free-software web's answer to "video needs a patent-unencumbered container", and it lost that argument to WebM and MP4. Converting one to the other is therefore rarely about reach — it is about feeding a specific toolchain that wants Ogg.

Read the comparison first. If your actual goal is "make this old Flash video play somewhere", OGV is not the target you want.

F4V vs OGV Side by Side

The ftyp f4v line is worth dwelling on because it surprises people: an .f4v file is structurally an MP4. We checked the first bytes of one and the brand box reads literally ftyp f4v . That is why so many players open F4V files without complaint even though Flash is long dead — they recognise the ISO base media structure and ignore the unfamiliar brand.

How to Convert F4V to OGV

1. Upload Your F4V File: Drag the .f4v onto the page or click "+ Add Files". Several files can be queued and each is converted independently with the same settings.
2. Choose the Video Codec: Open Advanced Options. Video Codec offers VP8, which is preselected, and Theora. This choice changes which quality controls actually do anything — see the table below before you decide.
3. Choose the Audio Codec and Compression: Audio Codec offers Vorbis (preselected), Opus, FLAC and Speex; all four mux into Ogg alongside the video. File Compression opens on Quality Preset ("Very High (Recommended)"), with Specific file size, Constant Bitrate, Variable Bitrate, Constant Quality and Constraint Quality also available.
4. Set Resolution or Trim, then Convert: Video resolution offers Keep original, Resolution Percentage, Preset Resolutions or an exact Width x Height; Trim can export one Start time / Duration range. Click Convert and download the .ogv. No sign-up, no watermark.

VP8 or Theora: the Control Surface Is Different

This is the decision that actually changes your output, and it is not obvious from the dropdown.

If you want a slider you can actually feel, pick Theora and use Constant Quality. On our 5-second test clip the Theora slider spanned 141 KB at position 0 up to 1.97 MB at position 10, with the default 7 landing at 1.13 MB — a real, monotonic quality control. If you want the better codec, keep VP8 and drive it with the Quality Preset or one of the bitrate modes instead; on the same clip, presets corresponding to roughly 1.3×, 0.9× and 0.4× of the source video bitrate produced 752 KB, 519 KB and 280 KB.

One thing to watch on the default path: the recommended "Very High" preset asks the encoder for about 132% of the source's own video bitrate, so a straight conversion at defaults will usually produce a larger file than the F4V you started with. Our 594 KB source came back as 752 KB. If you want it smaller, step the preset down or set an explicit bitrate.

Frequently Asked Questions

Will the .ogv play in Chrome, Firefox or Safari?

No, and it is worth being blunt about it because "Ogg is the open web format" is a claim with a 2010 expiry date. Chromium removed Theora decoding in version 123 and Chrome had already disabled it by default in 120; Firefox disabled it by default in 126; Safari never shipped it at all. Choosing VP8 instead does not rescue you — browsers decode VP8 inside WebM, not inside Ogg, so an .ogv carrying VP8 is not a delivery path either. If the goal is a page that plays the video, convert to F4V to WebM for VP8/VP9 in the container browsers actually accept, or F4V to MP4 for the widest reach.

Why is my OGV bigger than the F4V I started with?

Because the default preset is not a neutral pass-through. "Very High (Recommended)" asks for roughly 132% of the source's own video bitrate, on the reasoning that a re-encode needs headroom to avoid visibly degrading the picture. Combine that with VP8 being a less efficient codec than the H.264 your F4V almost certainly contained, and growth is the normal outcome rather than the surprising one. Step the preset down to High or Medium, or switch File Compression to Constant Bitrate or Specific file size and name the number you want.

The Constant Quality slider does nothing on VP8. Is that a bug?

It is a real limitation of the VP8 encoder rather than a slider that is merely mislabelled. libvpx does not implement a CRF mode the way x264 or libvpx-vp9 do, so when Constant Quality is selected with VP8 the encoder receives no quality target and no bitrate, and it falls back to its own built-in default — the same output whatever number the slider showed. Use Quality Preset or one of the bitrate modes with VP8, or switch the Video Codec to Theora where Constant Quality genuinely drives the encoder.

Does converting to OGV lose quality?

Yes, unavoidably. Your F4V holds H.264 that was already lossily compressed once; re-encoding it to VP8 or Theora decodes those pixels and compresses them again with a different codec, and generational loss is the result. There is no pass-through mode: the video stream is always re-encoded. Give the encoder headroom — a higher preset or an explicit bitrate at or above the source's — if the output is going to be edited or converted again later.

Which audio codec should I use inside the Ogg file?

Vorbis is preselected and is the safest choice, because anything that reads Ogg video reads Vorbis. Opus is technically much better per bit and is the modern Xiph recommendation; pick it if you control the playback side. FLAC keeps the audio unchanged in quality but roughly doubles or triples the audio's contribution to file size — our test clip grew from 520 KB with Vorbis to 810 KB with FLAC on the same video settings. Speex is a narrowband speech codec and will destroy music; only use it for voice recordings where size matters more than fidelity.

Will interlaced source video be deinterlaced?

No. There is no deinterlacing anywhere in the pipeline, so if your F4V somehow contains interlaced material the comb artefacts on moving edges are re-encoded into the output as they are. Flash-era F4V is nearly always progressive so this rarely bites here, but if your source came from a broadcast capture that was wrapped in F4V rather than encoded for the web, deinterlace it locally first.

Can I keep the original frame size, or should I scale down?

Keep original is the default and is usually right — F4V material is mostly 480p to 720p already, and upscaling nothing gains you nothing. Scaling down is the most reliable way to cut the file size when the codec choice has painted you into a corner: halving both dimensions quarters the pixel count and the bitrate needed to encode it cleanly. Video resolution offers Resolution Percentage, Preset Resolutions, Width, Height and an exact Width x Height.

Why does OGV still exist if nothing plays it?

Because the container and the codecs are unencumbered by the patent licensing that surrounds H.264 and HEVC, and that matters to a specific set of users: Wikimedia and Wikipedia have historically standardised on Ogg and WebM for exactly this reason, some Linux distributions ship Ogg-only media stacks by policy, and academic and archival projects sometimes mandate formats with no licensing attached. Those are real use cases, and they are why this conversion is here. They are just not the same as "put a video on a web page".

What happens to my F4V after the conversion?

It is uploaded over an encrypted connection, converted on our servers, and both the upload and the .ogv output are deleted automatically after a few hours. There is no sign-up, no watermark, and files are never shared or made public. The F4V on your own machine is untouched. Since the output is often larger than the input, the practical limit on a long clip is upload and download time over your connection rather than anything about the conversion itself.