Convert MPEG to MXF — Free Online Tool
Convert MPEG files to MXF, the professional broadcast container used in post-production workflows. This tool re-encodes the MPEG-1/2 video stream into H.264 (libx264) and converts MP2/MP3 audio to uncompressed PCM, producing an MXF file ready for ingestion into broadcast editing systems like Avid or Adobe Premiere.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your MPEG 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
MPEG files typically carry MPEG-1 or MPEG-2 video with MP2 or MP3 audio — legacy compression standards designed for broadcast TV and DVD. Converting to MXF involves two re-encoding steps: the video is transcoded from MPEG-1/2 to H.264 using libx264, which delivers significantly better compression efficiency while maintaining visual quality at a CRF of 23. The audio is decoded from its lossy MP2/MP3 form and re-encoded as uncompressed PCM (16-bit little-endian), which is the standard for professional MXF workflows where audio fidelity must be preserved without further generational loss. The result is wrapped in the MXF OP1a container, which adds support for timecode, rich metadata, and multiple audio tracks — features absent from the original MPEG container.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg tool. In the browser version of this tool, FFmpeg runs locally via WebAssembly (FFmpeg.wasm), so no file data leaves your device. |
-i input.mpeg
|
Specifies the input MPEG file. FFmpeg will detect whether this is an MPEG-1 or MPEG-2 stream and demux the video and audio tracks accordingly before processing them. |
-c:v libx264
|
Transcodes the video from MPEG-1 or MPEG-2 to H.264 using the libx264 encoder. H.264 is the default video codec for MXF in this configuration, offering much better compression efficiency than MPEG-2 at comparable visual quality. |
-c:a pcm_s16le
|
Decodes the source MP2 or MP3 audio and re-encodes it as uncompressed 16-bit PCM (little-endian), the standard audio format for professional MXF files used in broadcast and NLE-based post-production workflows. |
-crf 23
|
Sets the Constant Rate Factor for the H.264 encoder to 23, which is the libx264 default and provides a good balance of visual quality and file size. Lower values (e.g., 18) increase quality and file size; higher values reduce both. |
-b:a 192k
|
Specifies a target audio bitrate of 192 kbps. Because the selected audio codec (pcm_s16le) is uncompressed, this flag has no practical effect in this command — PCM bitrate is fixed by sample rate and bit depth. It would apply if you switched to a compressed codec like AAC. |
output.mxf
|
Defines the output filename and tells FFmpeg to wrap the encoded H.264 video and PCM audio in an MXF container (OP1a), which supports the timecode, metadata, and multi-track audio features required by professional broadcast workflows. |
Common Use Cases
- Ingesting archival MPEG broadcast recordings into a professional NLE like Avid Media Composer or DaVinci Resolve, which prefer MXF for media management
- Preparing legacy MPEG footage from older broadcast cameras or capture cards for delivery to a television station or post-production house that requires MXF-wrapped media
- Migrating a library of DVD-sourced MPEG-2 files into an MXF-based media asset management (MAM) system for long-term archival with proper timecode and metadata support
- Converting MPEG files captured from satellite or cable broadcast streams into MXF for use in a broadcast playout server
- Wrapping older MPEG training or corporate video content in MXF so it can be re-edited within a broadcast-grade post-production pipeline without re-shooting
- Standardizing a mixed library of MPEG-1 and MPEG-2 files into a single MXF-based codec profile before color grading or re-mastering
Frequently Asked Questions
There will be some quality loss because the MPEG video is re-encoded from MPEG-1/2 into H.264 — this is a transcode, not a remux. At the default CRF of 23, H.264 typically delivers excellent visual quality that is indistinguishable from the source for most content, and often at a smaller file size than the original MPEG-2 stream. The audio conversion from MP2 or MP3 to PCM is actually an upgrade in terms of fidelity, as PCM is uncompressed and introduces no further audio degradation.
Professional MXF workflows — particularly those used in broadcast and Avid-based post-production — standardize on uncompressed PCM audio (pcm_s16le or pcm_s24le) because it eliminates any risk of generational loss when the file is re-exported or mixed. MP2 audio from the source MPEG is lossy, so keeping it compressed inside MXF would mean the audio has already been degraded once; re-encoding it to another lossy format would degrade it again. PCM acts as a clean slate for any downstream audio work.
Standard MPEG files do not carry formal timecode in the way professional formats do, so there is no timecode to transfer from the source. The MXF output will be created without embedded source timecode unless you explicitly add a timecode flag to the FFmpeg command (e.g., -timecode 00:00:00:00). If timecode is critical for your broadcast workflow, you should add it manually or let your NLE assign it on ingest.
The video quality is controlled by the -crf flag, which accepts values from 0 (lossless) to 51 (worst quality). The default of 23 is a good general-purpose setting. To improve quality — especially for archival purposes or when the source MPEG has high resolution — try lowering the CRF to 18 or 15 (e.g., -crf 18). Be aware that lower CRF values produce larger MXF files, so balance quality against storage requirements.
Yes. On Linux or macOS, you can use a shell loop: for f in *.mpeg; do ffmpeg -i "$f" -c:v libx264 -c:a pcm_s16le -crf 23 -b:a 192k "${f%.mpeg}.mxf"; done. On Windows Command Prompt, use: for %f in (*.mpeg) do ffmpeg -i "%f" -c:v libx264 -c:a pcm_s16le -crf 23 -b:a 192k "%~nf.mxf". This is especially useful for migrating large MPEG archives, and because the browser tool has a 1GB file limit, the desktop FFmpeg command is the recommended approach for batch processing.
Avid Media Composer works best with MXF files using MPEG-2 or DNxHD video codecs, so an MXF file with an H.264 video stream may have limited or no native support — you may need to transcode further using Avid's AMA or Media Creation tools. Adobe Premiere Pro handles H.264-in-MXF more readily. If Avid compatibility is your primary goal, consider changing the video codec to mpeg2video in the FFmpeg command (-c:v mpeg2video) to produce a more natively Avid-friendly MXF file.
Technical Notes
MPEG files use system stream or program stream containers (with extensions like .mpg, .mpeg, .m2v) and typically carry MPEG-2 video at bitrates between 2–15 Mbps alongside MP2 audio — specifications inherited from the DVD-Video and broadcast TV standards of the 1990s and 2000s. MXF (Material Exchange Format), standardized under SMPTE 377, is a professional wrapper designed for broadcast and post-production environments, supporting timecode, descriptive metadata, and multiple synchronized audio tracks. The conversion from MPEG-2 to H.264 inside MXF is a full transcode, meaning every frame is decoded and re-encoded; this is computationally intensive compared to a remux but necessary because MXF in this configuration does not default to MPEG-2 as its video codec (though mpeg2video is a supported option if needed). The -b:a 192k flag is technically ignored when the audio codec is pcm_s16le, since PCM is uncompressed and its bitrate is determined entirely by sample rate and bit depth — this flag would only take effect if a variable-bitrate audio codec like AAC were selected instead. One known limitation: MXF produced by FFmpeg uses OP1a operational pattern, which is broadly compatible but may not satisfy all broadcast facility specifications that require specific MXF flavors (e.g., XDCAM or IMF). Verify delivery requirements with the receiving facility before using this output in a regulated broadcast chain.