Initializing... drag & drop files here
Supports: MPG, MPEG
This guide is for editors, broadcast engineers, and archivists who need a legacy MPG (an MPEG program stream, usually MPEG-2 video with MP2 audio) rewrapped or transcoded into MXF — the SMPTE-standardized container used for broadcast ingest, playout, and tapeless archiving. It walks through the conversion, explains which codec and operational pattern you actually get, and covers why a converted MXF sometimes still gets rejected so you know what to do next.
MXF is a wrapper, not a codec. It does not re-encode your MPG to a higher quality — it packages the "essence" (the actual compressed video and audio) together with timecode and metadata in a SMPTE-standard structure. Wrapping a consumer MPEG-2 program stream in MXF makes it readable by professional file-based systems; it does not recover quality the source never had.
What you choose in step 2 decides whether a downstream system accepts the file:
This converter outputs an OP1a MXF — a single, self-contained file with the video and audio interleaved together. OP1a is the operational pattern built for delivery, interchange, and archiving, and it is what most playout servers and NLEs other than Avid expect.
If your target is Avid Media Composer or a station that mandates a specific shim (AS-11, XDCAM, AVC-Intra OP-Atom), a generic MPG-to-MXF rewrap will not be enough — those workflows require a specific operational pattern, codec, and metadata that go beyond a container change. In that case, transcode inside the target NLE or use a tool built for that exact delivery spec. DRM-protected or corrupted MPG files cannot be converted. If you only need the file to be editable in common software rather than broadcast-ready, converting to MOV is often simpler than MXF.
No. MXF is a container that wraps your existing video and audio essence together with timecode and metadata — it does not re-encode to a higher quality. The picture is only as good as the source MPG, which is usually MPEG-2 at standard or early-HD resolution. MXF's value is interoperability with broadcast and post-production systems, not image enhancement.
By default the output carries MPEG-2 video with PCM (16-bit) audio — a close match to your MPG's original MPEG-2 essence and the Long-GOP stream most broadcast servers expect. You can switch the Video codec to H.264 in Advanced Options when the destination accepts it. In our testing, wrapping a standard-definition MPEG-2 MPG to an MPEG-2 MXF keeps the picture essentially identical to the source, because only the container and audio packaging change.
It outputs OP1a — a single self-contained file with video and audio interleaved. OP1a is the pattern designed for delivery, interchange, and archiving, and it is accepted by Adobe Premiere Pro, DaVinci Resolve, and most playout servers. Avid Media Composer is the notable exception: it requires OP-Atom, which stores each essence track in its own file.
Adobe Premiere Pro, DaVinci Resolve, Avid Media Composer, and Final Cut Pro all read MXF, and VLC plays it for preview. QuickTime Player and Windows Media Player do not support MXF natively, so an MXF that "won't open" on a consumer machine is usually a player limitation, not a broken file.
Keep your MPG (or a higher-quality master if you have one). MXF is a delivery and ingest format, not a smaller or better version of your video. If you later need a web-friendly file, use the MXF to MP4 converter, or convert the original MPG to MP4 directly for everyday playback and sharing.
Your MPG is uploaded over an encrypted connection, converted on our servers, and the output is returned to you. Files are deleted automatically a few hours after conversion — no sign-up, no watermark, and they are never shared or made public.