Convert MXF to MPEG — Free Online Tool
Convert MXF broadcast files to MPEG format by re-encoding the video stream to MPEG-2 and the audio to MP2 — the same codec pairing used in DVD and broadcast MPEG-2 Program Streams. Ideal for moving professional production footage into a legacy-compatible format for broadcast playout, archival, or DVD authoring workflows.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your MXF file here
or click to browse
Free — no uploads, no signups. Your files never leave your browser.
Settings
Note: Browser-based encoding uses approximate quality targets. For precise CRF compression, copy the FFmpeg command above and run it on your desktop.
Estimated output:
Conversion Complete!
DownloadHow It Works
MXF is a professional wrapper format commonly used in broadcast and post-production, often containing MPEG-2, H.264, or DV video alongside PCM audio. Converting to MPEG involves full re-encoding: the video stream is transcoded to MPEG-2 video using the mpeg2video encoder, and the audio — which in MXF is typically uncompressed PCM (16-bit or 24-bit) — is encoded to MP2 (MPEG-1 Audio Layer II), the traditional audio format for broadcast MPEG-2 streams. The resulting .mpeg file is a raw MPEG Program Stream, which drops MXF-specific metadata such as timecodes, clip names, and multi-track audio assignments, retaining only the primary video and first audio pair.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg application. When run via this browser tool, FFmpeg.wasm executes the same command logic inside a WebAssembly sandbox — no data leaves your machine. |
-i input.mxf
|
Specifies the input MXF file. FFmpeg will demux the MXF container, identifying the wrapped video codec (which may be H.264, MPEG-2, or MJPEG) and the audio codec (typically PCM 16-bit or 24-bit), and make each stream available for transcoding. |
-c:v mpeg2video
|
Tells FFmpeg to encode the output video stream using the MPEG-2 video encoder. Regardless of what video codec was inside the MXF (H.264, MPEG-2, MJPEG), the video will be fully decoded and re-encoded as MPEG-2 Part 2, which is the standard for DVD-Video and broadcast MPEG-2 Program Streams. |
-c:a mp2
|
Encodes the output audio as MP2 (MPEG-1 Audio Layer II), transcoding from the MXF's typically uncompressed PCM audio. MP2 is the standard audio codec for broadcast MPEG-2 and DVD-Video, and is the expected audio format for strict MPEG Program Stream decoders. |
-q:v 2
|
Sets the MPEG-2 video quality using a quantizer scale from 1 (best quality, largest file) to 31 (lowest quality, smallest file). A value of 2 is near-maximum quality, appropriate for broadcast or archival use where preserving detail from the MXF source is the priority. |
-b:a 192k
|
Sets the MP2 audio bitrate to 192 kbps, which is the standard bitrate for broadcast MP2 audio and matches the audio quality level commonly used in DVB and DVD-Video production. |
output.mpeg
|
Defines the output filename and triggers FFmpeg to write a raw MPEG Program Stream (.mpeg). The .mpeg extension signals FFmpeg to use the MPEG-PS muxer, which packages the MPEG-2 video and MP2 audio into a standard Program Stream container. |
Common Use Cases
- Preparing broadcast-ready MXF footage from a camera or ingest system for playout on legacy broadcast servers that accept MPEG-2 Program Streams
- Converting MXF rushes from a professional camcorder (e.g., Sony XDCAM or Panasonic P2) into MPEG-2 for DVD authoring in tools like Adobe Encore or DVD Architect
- Archiving finished broadcast segments from an MXF-based NLE timeline into a self-contained MPEG file for long-term storage on systems without MXF support
- Delivering edited content to a client or broadcaster whose ingest system requires MPEG-2 video with MP2 audio rather than MXF-wrapped H.264
- Creating a lower-complexity MPEG-2 proxy from an MXF master file for use in older editing or review systems that cannot decode modern MXF codecs
- Extracting a broadcast-compatible MPEG-2 stream from MXF material for integration into MPEG-TS multiplexers used in digital TV transmission pipelines
Frequently Asked Questions
No. MXF is specifically designed to carry rich metadata including SMPTE timecodes, clip UMIDs, reel names, and production notes. The MPEG Program Stream format (.mpeg) has no equivalent metadata container, so all of this information is lost during conversion. If preserving timecode or production metadata is important, keep the original MXF file as your master and treat the MPEG output as a delivery or distribution copy only.
MPEG Program Streams support only a single stereo or mono audio stream, so FFmpeg will map the first detected audio track from the MXF file and encode it to MP2. Additional audio tracks — such as a second language mix, isolated music track, or a separate dialogue stem — will be dropped. If you need a specific audio track other than the first, you can modify the command to add -map 0:a:1 (or the appropriate track index) before the output filename to select a different audio stream.
The -q:v parameter controls the quantizer scale for MPEG-2 encoding, where 1 is the highest possible quality and 31 is the lowest. A value of 2 is near-maximum quality, producing large file sizes but preserving as much detail from the MXF source as possible. For broadcast or archival use this is appropriate, but if you need smaller files for web delivery or review purposes, increasing this value to 5–8 will significantly reduce file size with only a modest visible quality drop at typical broadcast resolutions.
This depends heavily on what codec was used inside the MXF wrapper. If the MXF contained uncompressed or lightly compressed video (such as PCM video or high-bitrate XDCAM), the MPEG-2 output at -q:v 2 will likely be significantly smaller. If the MXF contained highly compressed H.264 (AVC-Intra), the MPEG-2 output may actually be larger, because MPEG-2 is generally less efficient than H.264 at equivalent perceptual quality. The PCM-to-MP2 audio transcoding will always result in a smaller audio track.
Yes. The -b:a 192k flag sets the MP2 audio bitrate to 192 kbps, which is standard for broadcast MPEG-2. You can increase this to 256k or 320k for higher fidelity, or reduce it to 128k to save space. You can also swap MP2 for MP3 audio by replacing -c:a mp2 with -c:a libmp3lame, though note that some strict MPEG-2 broadcast decoders expect MP2 audio specifically and may not handle MP3 correctly in a Program Stream.
On Linux or macOS, you can run a shell loop: for f in *.mxf; do ffmpeg -i "$f" -c:v mpeg2video -c:a mp2 -q:v 2 -b:a 192k "${f%.mxf}.mpeg"; done. On Windows Command Prompt, use: for %f in (*.mxf) do ffmpeg -i "%f" -c:v mpeg2video -c:a mp2 -q:v 2 -b:a 192k "%~nf.mpeg". This applies the same encoding parameters to every MXF file in the current directory. The in-browser tool processes one file at a time, so the FFmpeg command is particularly valuable for bulk workflows.
Technical Notes
MXF to MPEG conversion involves two encoding stages that both introduce lossy compression. On the video side, the mpeg2video encoder produces MPEG-2 Part 2 video, which uses discrete cosine transform (DCT) compression with I, P, and B frames — the same fundamental codec used in DVD-Video and DVB broadcast. MPEG-2 is significantly less efficient than H.264, so if your MXF source was encoded in H.264 (common in XDCAM EX or AVC-Intra MXF files), transcoding to MPEG-2 is a generation loss: you are decoding a compressed stream and re-compressing it in a less efficient codec. On the audio side, PCM audio from MXF (typically 16-bit or 24-bit at 48 kHz, the broadcast standard) is encoded to MP2 at 192 kbps. MP2 was designed specifically for broadcast use and is the mandated audio format in DVB and DVD-Video standards, making it appropriate for this output type. The output is a raw MPEG-1 System / MPEG-2 Program Stream, not a Transport Stream (.ts) — if you need a Transport Stream for DVB or HLS use, you would need to add -f mpegts to the command. The .mpeg container does not support subtitles, chapter markers, or the kind of structural metadata (UMIDs, essence descriptors) that MXF is built around, so this output format is strictly a delivery or compatibility format rather than an archival one.