Initializing... drag & drop files here
Supports: MXF
This walk-through is for anyone who has a professional .mxf clip — from an ENG camera, an Avid or Premiere edit, or a station handoff — and needs it as a .flv because some un-migrated Flash-era system on the other end only ingests Flash Video. Be clear before you start: this is the wrong direction for almost everyone. You are taking a broadcast master and flattening it into a dead, Flash-era container, so do it only when a specific legacy player demands .flv. If your real goal is a file that plays everywhere, jump straight to MXF to MP4 instead.
.mxf clip onto the page, or click "+ Add Files" to browse. Batch upload is supported, so you can queue several clips and convert them with the same settings..flv file. No sign-up, no watermark.The two settings that actually matter for an MXF-to-FLV job are the Video Codec and how you control size, because the source is a high-bitrate broadcast essence (MPEG-2, XDCAM, AVC-Intra, or DNxHD/DNxHR) and the FLV container is a much smaller, simpler target. Everything here is a full, lossy-to-lossy re-encode — the picture inside the MXF is decoded and re-compressed from scratch — so no detail the original already discarded comes back, and a larger resolution preset only upscales without inventing new detail. Keep "Keep original" resolution and a high preset to avoid stacking second-generation loss on top.
.flv..flv natively anymore; open it in VLC, ffmpeg, or MPV, or feed it to the legacy Flash player it was made for. For browser playback, you need MXF to MP4 instead..flv has nowhere to store SMPTE timecode or descriptive metadata, so they are dropped. Keep the original MXF as your master if anything downstream relies on that structure.FLV is a dead web-delivery format: Flash Player reached end-of-life on December 31, 2020 and Adobe blocked Flash content from running on January 12, 2021, so no modern browser or site serves .flv anymore. If you are converting because you think it will help on the modern web, stop — it will not, and MXF to MP4 is the correct target. FLV is only the right answer when a specific un-migrated system (an old Flash-based web player, a vintage CMS, or legacy Articulate/Captivate courseware) refuses anything but .flv. And if your MXF is a damaged or partial card-offload that won't decode cleanly, no converter can repair the container — re-copy it from the source media first. If you later need the file back in a professional container, that is a separate job: FLV to MXF.
For almost everyone, MP4. MXF is a professional broadcast container — standardized as SMPTE ST 377-1 (Material Exchange Format), it wraps MPEG-2, XDCAM, AVC-Intra, or DNxHD video with SMPTE timecode, rich metadata, and multiple audio tracks. FLV throws all of that away and lands the video in a dead, Flash-era format that no browser plays natively. Convert to FLV only when a specific legacy Flash-based system genuinely requires the .flv extension. For a file that edits and plays everywhere, use MXF to MP4.
The Flash web-delivery workflow is dead, but the file itself is not unreadable. Adobe ended Flash Player support on December 31, 2020 and began blocking Flash content on January 12, 2021, so no browser plays .flv natively and no modern site serves it. The container itself still opens in VLC, ffmpeg, and MPV-class players, because those decoders never depended on the Flash plug-in. So an .flv is plain audio/video you can still play and re-convert — it just has no place left in a modern web stack.
By default, FLV (Sorenson Spark) for video — the original H.263-based codec every Flash Player from version 6 onward could decode — and AAC for audio, with MP3 also available under Audio Codec. If your downstream tool is newer, Flash Player 9 Update 3 (December 2007) added support for H.264 inside FLV, so you can switch Video Codec to H.264 for better quality at the same bitrate. We do not target On2 VP6 here; Sorenson Spark and H.264 cover the realistic compatibility range.
No, and that is an honest limit rather than a tool flaw. MXF to FLV is a full lossy-to-lossy re-encode: the MPEG-2, XDCAM, AVC-Intra, or DNxHD picture inside the MXF is decoded and re-compressed to Sorenson Spark or H.264 from scratch, so no detail the source already discarded can be regained. Selecting a larger resolution preset upscales the frame without inventing new detail. In our testing, a 1080p MPEG-2 MXF converted at the "Very High" preset produced a clean FLV that opened in VLC but required a dedicated player and looked softer than the MP4 we made from the same source at the same size.
They mostly do not survive. MXF stores SMPTE timecode, rich descriptive metadata, and ancillary data that broadcast playout and station automation depend on; an .flv has nowhere to keep them, so they are dropped. A broadcast MXF often carries several uncompressed PCM audio channels, but FLV is built around a single audio track, so the multiple tracks are typically flattened to the primary mix and the PCM is re-encoded to lossy AAC or MP3. If that structure matters, keep the original MXF and compress MXF instead of converting to a consumer codec.
Your MXF is uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after the conversion — no sign-up, no watermark, never shared or made public.