Convert MXF to AIFF — Free Online Tool
Convert MXF broadcast media files to AIFF audio, extracting the PCM audio streams into Apple's uncompressed lossless format. This tool uses FFmpeg.wasm in your browser to remux PCM audio from professional MXF containers directly into AIFF using the pcm_s16be codec — preserving full audio fidelity without re-encoding.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your MXF 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
MXF files used in broadcast and post-production typically carry audio encoded as PCM (pcm_s16le or pcm_s24le) alongside video streams. During this conversion, FFmpeg discards the video track entirely and transcodes the audio from PCM little-endian (as stored in MXF) to PCM big-endian (pcm_s16be), which is what AIFF requires. The byte-order swap between little-endian and big-endian is the primary transformation — the raw 16-bit sample values themselves are preserved at full quality, making this effectively a lossless remux of the audio content. No lossy compression is applied at any stage.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg tool, which runs entirely in your browser via WebAssembly (FFmpeg.wasm) — no files leave your device during this conversion. |
-i input.mxf
|
Specifies the input MXF file. FFmpeg reads the MXF container and demuxes its internal streams — in this case identifying the PCM audio track and any video tracks present in the broadcast file. |
-c:a pcm_s16be
|
Sets the audio codec to PCM signed 16-bit big-endian, which is the encoding AIFF requires. This converts the MXF's typical little-endian PCM audio to the big-endian byte order that Apple's AIFF format mandates, while preserving all 16-bit sample values losslessly. |
output.aiff
|
Defines the output filename and container. The .aiff extension tells FFmpeg to wrap the pcm_s16be audio stream in an AIFF container — a format natively supported by macOS, Logic Pro, Final Cut Pro, and most professional audio applications on Apple platforms. |
Common Use Cases
- Extracting clean dialogue or music stems from a broadcast MXF master for use in an Apple Logic Pro or GarageBand session, which natively work with AIFF files on macOS.
- Delivering isolated audio tracks from an MXF news package or documentary to an audio post-production studio that requires AIFF format for their Pro Tools workflow.
- Archiving the uncompressed audio layer of a broadcast MXF recording to AIFF for long-term preservation in a macOS-based media asset management system.
- Pulling a stereo mix-down from an MXF camera original (e.g., from an ARRI, Sony Venice, or Panasonic VariCam) to create an audio reference file for music synchronization review.
- Converting broadcast MXF audio to AIFF so it can be imported into Final Cut Pro X or other Apple NLE tools without carrying the full MXF container overhead.
- Extracting PCM audio from an MXF file received from a broadcast playout server to deliver to a client who requires high-quality, uncompressed audio in a universally readable format.
Frequently Asked Questions
No audio quality is lost in this conversion, provided your MXF file contains 16-bit PCM audio (pcm_s16le), which is the most common case in broadcast MXF files. FFmpeg performs a byte-order swap from little-endian to big-endian to produce pcm_s16be for AIFF — this is a mathematically lossless transformation. The actual sample values are identical; only their byte arrangement in memory changes. If your MXF source contains 24-bit audio (pcm_s24le), note that the default command outputs 16-bit AIFF, so you may want to specify -c:a pcm_s24be to preserve the full 24-bit depth.
The video stream is completely discarded. AIFF is a pure audio format with no container support for video, so FFmpeg automatically drops all video tracks when the output format is AIFF. You do not need to add a -vn flag to suppress video — FFmpeg handles this automatically based on the output container's capabilities. Only the first audio track is extracted by default.
By default, FFmpeg selects the first audio stream from the MXF file. MXF files from broadcast environments often carry multiple discrete audio channels or tracks (e.g., a stereo mix plus individual mono channels). AIFF does not support multiple audio tracks in a single file. If you need a specific audio stream other than the first, you can modify the FFmpeg command to add -map 0:a:1 (for the second audio stream) or -map 0:a:2 (for the third), and so on, before the output filename.
The default command uses pcm_s16be, which is 16-bit. If your MXF was recorded at 24-bit (common on professional broadcast cameras and field recorders), replace -c:a pcm_s16be with -c:a pcm_s24be in the command to output 24-bit AIFF. The full command would be: ffmpeg -i input.mxf -c:a pcm_s24be output.aiff. This ensures the full dynamic range of the original recording is preserved in the AIFF file.
No — AIFF has very limited metadata support compared to MXF. MXF is a metadata-rich format designed for broadcast workflows, capable of storing SMPTE timecode, clip names, reel IDs, and production metadata. AIFF supports only basic ID3-style tags (title, artist, etc.), so the broadcast-specific metadata embedded in the MXF source will not transfer to the output file. If preserving timecode or production metadata is critical, consider keeping the original MXF file alongside the extracted AIFF.
You can batch process files using a shell loop. On Linux or macOS, run: for f in *.mxf; do ffmpeg -i "$f" -c:a pcm_s16be "${f%.mxf}.aiff"; done. On Windows Command Prompt, use: for %f in (*.mxf) do ffmpeg -i "%f" -c:a pcm_s16be "%~nf.aiff". This applies the same pcm_s16be conversion to every MXF file in the current directory and outputs a matching AIFF file for each. This is especially useful for processing large batches of broadcast files that exceed the 1GB browser limit.
Technical Notes
MXF (Material Exchange Format) is a SMPTE-standardized wrapper used across broadcast and professional production environments. Its audio payloads are almost universally stored as uncompressed PCM — most commonly pcm_s16le (16-bit signed little-endian) or pcm_s24le (24-bit signed little-endian) at 48kHz, the broadcast standard sample rate. AIFF (Audio Interchange File Format), developed by Apple, stores PCM in big-endian byte order, which is why FFmpeg applies a byte-swap transformation even though no lossy compression occurs. The output file size will be roughly equivalent to just the audio portion of the source MXF — video data is stripped, so a large MXF master will produce a significantly smaller AIFF. AIFF supports sample rates up to 192kHz and bit depths up to 32-bit float (pcm_f32be) or 64-bit float (pcm_f64be), making it well-suited for high-resolution professional audio. One known limitation: AIFF does not support multiple audio tracks in a single file, unlike MXF which can carry 8, 16, or more discrete audio channels as separate streams. Users working with multi-track MXF audio should extract each stream individually using the -map flag. Additionally, MXF files containing AAC audio (less common but possible) will require a full decode-and-re-encode cycle to PCM, which is handled transparently by FFmpeg but represents a decode of the lossy source.