Initializing... drag & drop files here
Supports: MKV
MKV (Matroska) is an open consumer container; MXF (Material Exchange Format) is SMPTE's professional broadcast wrapper. You almost never want this conversion unless a specific system downstream — an Avid-era edit suite, a broadcast ingest, or a playout server — refuses anything but MXF. The honest short answer: if you just need a file that plays and edits everywhere, stay on MKV or convert MKV to MP4; reach for MXF only when a delivery spec or ingest system names it.
| Property | MKV (source) | MXF (output) |
|---|---|---|
| Full name | Matroska Video | Material Exchange Format |
| Standard / origin | Open format, announced Dec 2002 (EBML-based) | SMPTE 377M / ST 377-1, first published 2004 |
| Designed for | Consumer playback, ripping, archiving | Broadcast, post-production, professional interchange |
| Video codec here | Source (often H.264 / H.265 / AV1) | Re-encoded to MPEG-2 by default; H.264, H.265, MPEG-1 selectable |
| Audio here | Source (AAC, AC3, FLAC, Opus, etc.) | Uncompressed PCM, 16-bit Little Endian |
| Subtitles & chapters | Carried natively, multiple tracks | Not carried across — MXF is not a subtitle/chapter container |
| Timecode & structured metadata | Limited | Designed for it (continuous timecode, rich metadata) |
| Layout / patterns | n/a | OP1a, OP-Atom and others define the file layout |
| Plays in consumer apps | Widely (VLC, browsers via WebM lineage) | Rarely without pro tooling |
.mkv onto the page or click "Add Files" to browse. You can queue several clips and they convert with the same settings.No — and this is the most common misunderstanding. MXF is a container standard (SMPTE 377M / ST 377-1); it standardizes how picture, sound, timecode, and metadata are wrapped, not whether the video inside meets a broadcaster's bar. A facility's delivery specification — for example a UK DPP-style AS-11 profile — dictates the exact codec, bitrate, resolution, frame rate, and audio layout it will accept. This tool produces a valid MXF, but a consumer MKV that started at a modest bitrate stays at that bitrate inside the MXF. Always conform to the spec the recipient actually published rather than assuming the container alone qualifies the file.
Yes — this is a re-encode, not a lossless rewrap. MKV almost always already holds compressed video (commonly H.264, H.265, or AV1), and producing the MXF means decoding that and re-compressing once, which is one lossy generation. By default the target is MPEG-2, an older codec than H.264/H.265, so you're also stepping a generation back in compression efficiency — expect a larger file for the same picture quality. To minimize visible loss, keep "Video resolution" on "Keep original" and choose a high Quality Preset or a generous bitrate rather than squeezing to a small "Specific file size."
By default the video is encoded as MPEG-2, the codec most broadly expected inside professional MXF workflows, and the audio is written as uncompressed PCM (16-bit Little Endian) — which matches how broadcast and camera MXF typically store sound, as linear PCM rather than a compressed codec. In "Show All Options" you can instead pick H.264, H.265, or MPEG-1 for the video. MXF itself is codec-agnostic, so the wrapper accepts several, but your ingest or playout server usually accepts only one or two — choose the one your destination documents.
They are not carried across. MKV is a rich consumer container that holds multiple subtitle tracks, chapter markers, and several audio languages; MXF is a professional interchange wrapper and is not a subtitle or chapter container in the way Matroska is. If you rely on embedded subtitles or chapter points, extract or burn them in before converting, or keep an MKV/MP4 copy alongside the MXF. Multiple audio tracks may also be folded down rather than preserved as separate selectable streams, so check the output before relying on it.
For almost everyone, MP4 is the right answer — it's smaller, plays and scrubs cleanly across current editors and devices, and keeps modern codecs without a backward step to MPEG-2. Choose MXF only when something downstream specifically requires it: a broadcast ingest, a playout server, or an Avid-era NLE workflow whose pipeline names the format. There's no quality or compatibility benefit to MXF outside a workflow that mandates it. If you later need the file back in a consumer container, convert MXF to MKV does the reverse.
Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, and your files are never shared or made public. In our testing, MPEG-2-in-MXF output is noticeably larger than the H.264 MKV that went in, so with a long source the practical thing to watch is upload size and time rather than anything on the output side.