MXF to FLV Converter

MXF to FLV Converter

This is a conversion between two containers that sit at opposite ends of the media world. MXF is SMPTE's professional broadcast and production wrapper, standardised as SMPTE ST 377-1, and it is what Sony XDCAM decks, Panasonic P2 cards, Avid systems and broadcast archives hand to each other. FLV is Flash Video — the container that carried most of the web's video for roughly a decade and then stopped, when Adobe ended support for Flash Player on 31 December 2020 and began blocking Flash content on 12 January 2021. Nothing plays FLV in a browser today. It remains a valid target for one honest reason: legacy media servers, older content-management systems and existing archives that were built around .flv and were never migrated. If that is not your situation, MXF to MP4 is what you actually want.

MXF at a Glance

FLV at a Glance

How to Convert MXF to FLV

1. Upload Your MXF File: Drag the .mxf onto the page or click "Add Files". Several clips can be queued and every one is converted with the same settings.
2. Choose the Video Codec and Audio Codec: Open Advanced Options. Video Codec opens on FLV (Sorenson Spark) and Audio Codec opens on AAC. Unless something downstream specifically demands the old codec, switch Video Codec to H.264 — the section below explains why.
3. Set File Compression and Video Resolution: File Compression opens on Quality Preset at "Very High"; Constraint Quality, Constant Bitrate and Specific file size are the alternatives here. Video resolution opens on "Keep original", and Trim takes a start time and duration if you only need a section.
4. Convert and Download: Click Convert. Files are uploaded over an encrypted connection, processed on our servers and deleted automatically after a few hours — no sign-up, no watermark, never shared.

Which Video Codec Belongs Inside the FLV

The FLV container will hold either the codec it was born with or H.264, and the gap between them is large. Sorenson Spark is a first-generation H.263 derivative designed for the bandwidth of the early 2000s; H.264 arrived years later and is the codec Flash itself adopted once it could. There is a hint about this in the conversion pipeline itself: when an FLV output is requested with no video codec named at all, H.264 is what it falls back to. The Sorenson Spark preselection on this page is a legacy-compatibility choice, not a quality one.

Pick Sorenson Spark only when the thing consuming the file genuinely cannot decode H.264 — a very old media server or an embedded player from the Flash 6 or 7 era. For anything newer, including modern software that merely reads .flv files, H.264 is the better encode by a wide margin.

One more control to know about: with Sorenson Spark selected, the numeric field labelled "CRF" under Constant Quality and Constraint Quality is not an x264-style CRF. It is an MPEG quantiser on a 1–31 scale where lower is better, it does not open on a considered value, and typing 23 out of H.264 habit puts you near the bottom of the range rather than in the middle. Try 3–5. Switch Video Codec to H.264 and that same field behaves the way you expect.

Frequently Asked Questions

Is it worth converting to FLV at all in 2026?

Only for a specific legacy target. Adobe ended Flash Player support on 31 December 2020 and started blocking Flash content on 12 January 2021, and no current browser plays FLV natively, so this is not a delivery format for anything public-facing. Where it still makes sense is a media server, ingest pipeline, digital-signage box or content-management system that was built around .flv and has not been migrated — those systems are often perfectly functional and simply expect that extension. For anything else, MXF to MP4 is the modern equivalent and plays everywhere.

How much worse is Sorenson Spark than H.264 in the same container?

Substantially, and we measured it rather than guessing. We encoded the same three-second 1280×720 clip into FLV twice, once with Sorenson Spark and once with H.264, tuned so the two outputs came out at almost the same size — about 1.51 MB and 1.46 MB respectively. Measured against the source, the Sorenson Spark encode scored around 37.5 dB PSNR and the slightly smaller H.264 encode around 41.8 dB. That is a large gap for the same container and the same byte budget. Unless a specific old player forces your hand, choose H.264.

My MXF has several audio tracks — which one ends up in the FLV?

The one with the most channels. There is no track picker on this page and the pipeline does not map streams explicitly, so the encoder's default rule decides: it takes the audio stream with the highest channel count, and where several tie it takes the lowest-numbered of them. On a broadcast master carrying two discrete mono tracks plus a stereo pair, the stereo pair wins and the mono tracks are dropped. If you need one particular mic, language or stem, export that track on its own from your editor before converting.

Why is there no Variable Bitrate option here when other video pages have one?

Because the codec FLV is built around does not support it. With Sorenson Spark selected, the available rate-control modes are Quality Preset, Constant Quality, Constraint Quality, Constant Bitrate and Specific file size — variable-bitrate encoding is simply not offered for this target. Constraint Quality is the most useful of what remains on a broadcast source, because it pairs a quality floor with a Max bitrate ceiling, which is exactly what an old streaming server usually needs.

Why did my FLV come out bigger than expected?

Quality Preset scales the source bitrate rather than setting an absolute one, and the rung the page opens on aims above the source rather than below it. MXF masters are deliberately high-bitrate — lightly compressed, frequently all-intra — so a preset that targets a multiple of that figure produces a large file. Drop the preset to Medium or lower, use "Specific file size" and name a number, or use Constraint Quality with a Max bitrate cap. Switching the codec to H.264 also helps enormously, for the reasons measured above.

Does the FLV keep my master's timecode and reel names?

No. Broadcast MXF carries a substantial metadata layer — start timecode, reel and tape identifiers, essence descriptors, sometimes captions — and FLV has nowhere to put most of it. Keep the MXF as your master if that information matters for conform or archive, and treat the FLV strictly as a delivery copy for the legacy system that needs it.

Can this deinterlace my 1080i broadcast master?

No. There is no deinterlacing stage anywhere in this pipeline, so an interlaced source is encoded with its field structure intact and combing stays visible on progressive playback. This bites harder on FLV than on most targets, because the legacy players that still read .flv are also the ones least likely to deinterlace on their own. Deinterlace when you export the MXF from your editor.

Why does one MXF convert and another one fail?

Because the extension describes a family rather than a format. MXF covers several operational patterns and a long list of possible video and audio essences, and vendor implementations diverged enough that Sony's and Panasonic's early camera files could not read each other. The files that fail are usually partial or still-growing captures taken from a card mid-record, vendor-specific variants, or unusual essence types — not files that are simply too large. Re-exporting a flat OP-1a MXF from your editor and converting that clears it up almost every time.

What happens to my file after it is converted?

It is uploaded over an encrypted connection, converted on our servers, and both the upload and the output are deleted automatically after a few hours. There is no sign-up, no watermark, and nothing is shared or made public. Because broadcast masters are large, the upload itself is usually the slowest part of the job — trimming the clip first with Video Cutter is the quickest way to shorten it when you only need a section.