Convert MXF to MP4
MXF is the Material Exchange Format used across broadcast and cinema - XDCAM, AVC-Intra, DNxHD, and ProRes-in-MXF are all common. Wave converts the streams locally, which matters when your source clip 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.
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?
Wave downmixes to stereo AAC by default. Multi-track passthrough is on the roadmap but not in the current build.
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.