Convert MXF to MP4
MXF (Material Exchange Format) is the file format broadcast television and cinema production use for delivering finished video. If a broadcaster, editing house, or professional camera operator sends you a video, there's a good chance it's MXF. The picture data inside is usually one of several pro-grade codecs (XDCAM, AVC-Intra, DNxHD, or ProRes). Consumer devices refuse MXF entirely - iOS, Android, Chrome, Windows all skip it. Wave converts MXF to MP4 in your browser: sometimes with a fast wrapper swap (when the codec inside already fits MP4), sometimes with a real re-encode. It runs locally, which matters when your source is measured in gigabytes and you don't want it sitting on someone else's server.
What actually changes
MXF was designed to standardise interchange between broadcast systems - cameras, edit suites, playout servers, tape archives. What sits inside varies with the camera vendor: Sony XDCAM writes MPEG-2 long-GOP or XAVC (H.264), Panasonic P2 writes AVC-Intra (H.264 Intra), Canon C300 writes MPEG-2 or XAVC, ARRI Alexa writes ProRes. Audio is nearly always uncompressed PCM (24-bit, 48 kHz, sometimes multi-channel).
Wave inspects the payload and picks its path. AVC-Intra and XAVC (both H.264 profiles) re-mux into MP4 without touching the video pixels - the container header is rewritten, the raw NAL units are copied. MPEG-2 long-GOP, DNxHD, and ProRes need a re-encode because MP4 doesn't carry them broadly enough to be useful. Audio is normalised to AAC at 192 kbps regardless, since multi-channel PCM inside broadcast MXF is often 4-8 channels that consumer players won't handle cleanly. The re-encode runs through the browser's WebCodecs H.264 encoder when available (hardware-accelerated on most machines) and falls back to the wasm MPEG-4 encoder otherwise.
SMPTE standardized MXF in 2004 (SMPTE ST 377-1) to solve a real problem: broadcast, production, and archival tools all needed to interchange video with metadata (timecode, edit lists, colour space, camera settings, closed captions) without every vendor inventing its own wrapper. MXF is highly configurable - it defines operational patterns (OP-1a for a single self-contained file, OP-Atom for multi-file bundles) and multiple metadata sets, which is why an MXF from a Sony XDCAM camera looks different internally from an MXF from a Panasonic P2 card even though both are valid MXF.
Post-production workflows commonly use MXF-in-OP-1a for finished deliverables (BBC and NBCUniversal spec masters ship as OP-1a MXF, and many streaming platforms accept it as an alternative to ProRes-in-MOV). The file was engineered for interchange between professionals, not direct playback on a phone or in a browser. Wave's conversion produces the preview file you actually need when you have to send a clip to someone outside the edit bay.
Three steps.
-
01
Step 1
Drop your .mxf file onto the card.
-
02
Step 2
Wave inspects the payload - expect Fast copy for AVC-Intra / XAVC sources, Re-encode for XDCAM / DNxHD / ProRes.
-
03
Step 3
Convert. Big MXF files take a while; nothing gets uploaded while you wait.
Answers, specifically.
MXF files are huge. Will this even work in a browser?
Up to about 8 GB per file, yes. Wave streams the source through the WebAssembly engine chunk by chunk (via WORKERFS) instead of loading it wholesale into memory, so the practical limit is your browser's decoder headroom rather than the file size. A warning appears above 2 GB.
Does the multi-channel audio survive?
Yes. Wave converts the audio to AAC and keeps the channel count: a 5.1 AC-3 track becomes 5.1 AAC at 384 kbps, stereo becomes stereo at 192 kbps. Sources with more than six channels fold down to 5.1, the most AAC-LC carries. If the file has several audio tracks, every one of them is kept.
What about timecode?
MXF timecode metadata is preserved when it fits inside MP4's tmcd atom. Some post-production timecode formats have no MP4 equivalent and are dropped.
Why not just keep MXF for editing?
You should, if the target is an edit suite. This converter exists for the other case - sending an MXF clip to a producer or client who wants to preview it on a laptop or phone without installing broadcast tools.
AS-02 or AS-11 packages?
Wave converts individual MXF files. Multi-file MXF packages (AS-02 folders, AS-11 broadcast deliverables) need to be flattened to a single file first - most NLE export presets do this on request.
What is the difference between OP-1a and OP-Atom MXF?
OP-1a wraps a self-contained file with essence and metadata together (broadcast masters, XDCAM camera files). OP-Atom is a multi-file bundle where each track sits in its own MXF file (used by Avid MediaFiles). Wave reads OP-1a directly; OP-Atom bundles need to be flattened first with an Avid tool or an NLE re-export.
The MXF is 60 GB. Can Wave handle it?
Not in one file - Wave's per-file ceiling is 8 GB. For truly large MXF sources, a desktop ffmpeg install with a similar remux command handles it: 'ffmpeg -i huge.mxf -c copy -movflags +faststart output.mp4'. That runs on your machine's full memory rather than a browser's heap.
Are alpha channels in ProRes 4444 MXF preserved?
No. MP4 has no widely-supported alpha codec, so the re-encode composites against black. If you need alpha preservation, MXF or MOV with ProRes 4444 must stay in the professional pipeline; the H.264 MP4 exists for preview and delivery, not for further compositing.