Initializing... drag & drop files here
Supports: MPG, MPEG
MXF is the wrapper broadcast and post-production systems expect: a vendor-neutral container defined by SMPTE 377M that carries picture, sound and metadata in one file. This converter re-encodes an MPEG program stream into an MXF file labelled with the OP1a operational pattern (SMPTE 378M) — the single self-contained layout playout servers and NLEs treat as one clip — with MPEG-2 or H.264 video and PCM audio. It is a genuine transcode, not a rewrap, and the output is all-intra, which has consequences for file size worth understanding before you start.
.mpeg or .mpg file onto the page, or click "+ Add Files". Several clips can be queued and wrapped with the same settings..mxf. Files upload over an encrypted connection, are processed on our servers and are deleted automatically after a few hours — no sign-up, no watermark.| Property | Value |
|---|---|
| Container | MXF, SMPTE 377M |
| Operational pattern | OP1a (SMPTE 378M) — one self-contained file |
| Video codecs offered | MPEG-2 (preselected) or H.264 |
| Video codecs not offered | AVC-Intra, DNxHD/DNxHR, JPEG 2000 — MXF carries them, this tool does not write them |
| Audio essence | PCM 16-bit little-endian, uncompressed |
| Audio sample rate | 48 kHz only — that is what the MXF mapping here implements |
| GOP structure | Forced to 1: every frame is an I-frame |
| Resolution | Source resolution unless you change it |
The MXF muxer has strict limits on how far a frame may be offset from its reference, so this pipeline sets the GOP to 1 — every frame is coded on its own, with no prediction from its neighbours. That is exactly what broadcast and edit-friendly formats do, and it is also why the output is bigger than the source.
How much bigger depends entirely on the footage. Encoding 10-second 720x480 MPEG-2 test clips at a matched quantizer, we measured the all-intra encode at about 7x the long-GOP encode on a largely static pattern (4.2 MB against 0.6 MB) and about 1.7x on constantly moving content (8.8 MB against 5.1 MB). Static, talking-head and locked-off material pays the biggest penalty because long-GOP coding gets almost everything from prediction, and intra coding gets none of it. Budget accordingly: an MXF that preserves the look of a DVD-rate source will not be DVD-sized.
| Mode | On MPEG-2 (default) | On H.264 |
|---|---|---|
| Quality Preset | Scales the source bitrate — "Very High" targets about 1.32x the measured source rate | Resolves to an x264 CRF, tightened on small frames |
| Constant Bitrate / Variable Bitrate | Applied directly, then raised if it falls below the MPEG-2 minimum for the frame size | Applied directly |
| Specific file size | Converted to a bitrate for you | Converted to a bitrate for you |
| Constant Quality | The CRF number is not used — MPEG-2 has no CRF mode, so the encoder falls back to the minimum bitrate for the resolution | Real CRF, 0-51 |
| Constraint Quality | Same fallback as Constant Quality | CRF plus a max-bitrate ceiling |
The practical rule: on the default MPEG-2 codec, drive size with the Quality Preset or a bitrate mode, not with the Constant Quality slider. MPEG-2 also enforces a floor — roughly 0.10 to 0.18 bits per pixel at 30 fps and never less than 2 Mbps — so asking for a very small MXF from a large frame quietly gets you the floor instead.
If a delivery spec names AVC-Intra 100, DNxHD 120 or JPEG 2000, this converter cannot produce it — those essences exist in MXF but are not on offer here, and a broadcast transcoder or your NLE's export module is the right place to make them. If the goal is simply a file people can watch, MXF is the wrong container entirely: MPEG to MP4 or MPEG to MOV will play anywhere, and MXF to MP4 goes the other way if you have been handed an MXF already.
OP1a — the file carries the OP1a operational-pattern label, which we confirmed by reading the operational-pattern key back out of a file this converter produced. OP1a stores all essence in one self-contained file, which is what Adobe Premiere Pro, DaVinci Resolve and most playout servers expect. OP-Atom (SMPTE 390M), the other pattern you will hear about, splits each stream into its own file and is what Avid generates for its own media; if your workflow specifically wants OP-Atom, transcode after import rather than expecting it here.
Because the output is all-intra. Every frame is coded independently rather than predicted from its neighbours, which is why edit and broadcast formats use it and why they are large. In our own measurements on 720x480 test clips at a matched quantizer, all-intra ran about 1.7x the long-GOP size on constantly moving content and about 7x on largely static content. PCM audio adds to it too, since it is uncompressed.
No. The Video Codec list on this page has exactly two entries: MPEG-2 and H.264. MXF as a format can wrap AVC-Intra, DNxHD/DNxHR, JPEG 2000, DV and more, but this converter does not write them. If a spec sheet requires one of those, use a dedicated broadcast transcoder.
PCM 16-bit little-endian — the only entry in the Audio Codec list, so your MPEG's MPEG-Audio soundtrack is decoded and rewrapped as uncompressed PCM. Note that this MXF audio mapping implements 48 kHz only. DVD-sourced MPEG-2 is normally already 48 kHz, but MPEG-1 and Video CD material is often 44.1 kHz, and those files will not wrap.
No. There is no deinterlacing step anywhere in the pipeline, so an interlaced source stays interlaced and its field structure travels into the MXF as-is. For broadcast delivery that is usually what you want; if you need progressive output, deinterlace in your NLE after import.
No — MXF is a wrapper, not a quality upgrade, and no re-encode recovers detail the MPEG source discarded. What you gain is a container that professional tools ingest cleanly, with per-frame access and uncompressed audio. Keeping the codec on MPEG-2 keeps the encode inside the same codec family, which limits how much the second generation costs you.
Adobe Premiere Pro, DaVinci Resolve, Avid Media Composer and broadcast ingest and playout systems all read MXF; consumer players like Windows Media Player and QuickTime Player generally do not. Avid in particular is fussy about which codecs it will edit natively, so expect to consolidate or transcode inside Media Composer after import.
Yes. It is uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours along with the MXF we generate. Nothing is shared or made public, there is no sign-up and no watermark. Since MXF output is larger than the input, remember that the download can take longer than the upload did.