Initializing... drag & drop files here
Supports: MXF
MXF is the container professional gear writes: standardised by SMPTE, built for interchange between cameras, edit suites, playout servers and archives, and openable by almost no ordinary software. MKV (Matroska) is an open container that plays in VLC, mpv, Plex and Kodi, holds essentially any codec, and carries multiple audio and subtitle tracks. The short answer: keep the MXF as your master if the footage still has grading, conform or delivery work ahead of it, and make an MKV when the job is watching, sharing or browsing an archive. Converting here is a full re-encode, so treat the MKV as a copy rather than a replacement.
| Property | MXF | MKV (Matroska) |
|---|---|---|
| Standard | SMPTE ST 377-1, current edition ST 377-1:2019 | Open specification maintained by the Matroska project |
| First released | 22 September 2004 | Open, continuously versioned specification rather than a dated release |
| Designed for | Interchange and mastering between professional systems | Playback and storage of anything, anywhere |
| Typical video essence | MPEG-2 long GOP at 25–35 Mbit/s (XDCAM HD), MPEG-2 422P@HL at 50 Mbit/s (XDCAM HD422), AVC-Intra, DNxHD/DNxHR | Whatever you encode into it; H.264 is what this page writes by default |
| Typical audio | Uncompressed PCM, mapped per SMPTE 382M, often on several discrete tracks | AAC by default here; PCM, FLAC, AC3, DTS, Opus and others are all selectable |
| Bitrate | Tens to hundreds of Mbit/s, sized for editing headroom | Whatever you choose; delivery-grade H.264 is typically an order of magnitude lower |
| Multiple audio tracks | Yes, and that is how broadcast audio is normally laid out | Yes, the container supports them — but this conversion writes one |
| Timecode and ancillary data | Carried natively (SMPTE timecode, descriptive metadata, VBI/ANC) | Not carried through this conversion |
| Operational patterns | OP1a (SMPTE 378M) self-contained, OP-Atom (SMPTE 390M) one essence per file | Not applicable — one self-contained file |
| Plays in VLC / Plex / Kodi | Usually not without professional decoders | Yes |
| Good as a master | Yes | Only if it was your original acquisition format |
.mxf onto the page or use "Add Files". Multiple clips can be queued and all convert with the same settings.| Attribute of the MXF | In the MKV |
|---|---|
| Picture | Re-encoded — H.264 by default, never copied through |
| Audio | Re-encoded to AAC by default; one stream, selected automatically |
| Additional audio tracks | Not carried — a single stream is written |
| SMPTE timecode | Not carried |
| Ancillary / VBI data, closed captions in ANC | Not carried |
| Interlacing | Preserved as-is, combing included — nothing deinterlaces |
| HDR transfer characteristics | Not tone-mapped; an HLG or PQ master can look washed out on SDR |
| Non-square pixel aspect | Normalised to square pixels without compensating geometry — set Width x Height |
| Frame rate and duration | Preserved unless you trim |
It is always a re-encode. There is no stream-copy path in this pipeline, so even though Matroska could happily hold the MXF's original essence, the picture is decoded and encoded again — H.264 unless you pick another codec. That is a deliberate trade: you get a file that plays everywhere, at the cost of one lossy generation. If keeping the exact original essence matters, keep the MXF.
Quality Preset at "Very High" or "Highest", with Video resolution left on "Keep original". On H.264 the presets map to a CRF chosen for the codec and then nudged by output resolution: at 1080p that is Highest → 17, Very High → 18, High → 20, Medium → 23, Low → 26, Very Low → 28, Lowest → 32, shifting up to ±2 as the output moves away from 1080p. If you would rather name the number, switch File Compression to Constant Quality and type a CRF — around 18 is visually lossless for most broadcast material.
No — one audio stream is written, and it is chosen for you. Our command builder emits no -map for MXF input, so ffmpeg's automatic stream selection applies: it takes "the stream with the most channels", and where streams tie, "the stream with the lowest index is chosen." We verified that on a three-stream MXF holding mono, mono and stereo essence, where the stereo pair was selected. Broadcast masters commonly carry the programme mix as two discrete mono tracks with a stereo reference alongside, so the result is not always the one you assumed. Bounce a stereo mixdown from your NLE first if the choice matters.
MKV when the destination is a computer, a media server or an archive — it is the more capable open container and the one VLC, mpv, Plex and Kodi are happiest with. MXF to MP4 when the destination is a phone, a smart TV, a social platform or anything with a hardware decoder and a narrow list of supported containers. The picture inside can be identical H.264 either way; you are choosing the wrapper, and MP4's wrapper is the one embedded devices recognise.
Yes. Set Audio Codec to FLAC for a compressed-but-lossless track, or to one of the PCM options to keep the samples uncompressed exactly as the MXF carried them. Matroska handles both without complaint, and it is a reasonable way to build a viewing copy that still holds mix-grade audio while the picture is compressed. Note this only applies to the single stream that gets selected — it does not bring the other tracks along.
It will look exactly as interlaced as the source, because nothing in this pipeline deinterlaces. The fields stay woven together and you will see comb artefacts on motion when the MKV is played on a progressive display. If the viewing copy needs to look clean, deinterlace in your NLE and export a progressive master first, then convert that. The same caution applies to HDR: there is no tone-mapping step, so an HLG or PQ master gets a plain colour conversion and can look flat on an SDR screen.
Because MXF is an interchange container carrying professional essence — XDCAM's MPEG-2 422P@HL, AVC-Intra, DNxHD and similar — and consumer builds frequently lack the demuxer, the decoders or both. That is precisely the problem this conversion solves: the decoding happens server-side on a build that carries those decoders, and what you download is a Matroska file with codecs VLC has shipped for years.
MXF profiles vary widely between vendors and generations. The reliable fix is to re-export the clip from your editor as self-contained OP1a — the single-file operational pattern defined alongside ST 377-1 as SMPTE 378M — and convert that. OP-Atom media, which Avid and Panasonic P2 write with one essence track per file, is the usual culprit: a single upload only sees the essence in the file you gave it. Truncated card offloads and interrupted recordings need repair in your NLE before any converter can help.
Your MXF uploads over an encrypted connection, converts on our servers and is deleted automatically after a few hours, along with the MKV. There is no sign-up, no watermark, and files are never shared or made public. Because broadcast masters run to many gigabytes, the practical limit is upload time on your connection rather than anything downstream — trim first if you only need part of the clip, and if you need to shrink an MKV afterwards the video compressor takes MKV directly.