MXF to ASF Converter

Convert MXF to ASF: What This Tutorial Covers

MXF is SMPTE's professional interchange wrapper — the file XDCAM decks, P2 cards, Avid systems and broadcast archives hand to one another. ASF is Microsoft's Advanced Systems Format, the container behind Windows Media: .wmv and .wma are ASF files with different extensions and different payloads inside. Converting one to the other is almost always about getting broadcast material into a Windows-only pipeline — a Windows Media Services archive, a signage player, an embedded kiosk, or a case-management system that indexes ASF and nothing else.

This tutorial covers the codec pairing the page produces by default, which is not the one most people assume, and the three properties of professional essence — multiple audio tracks, non-square pixels and interlacing — that decide whether the result looks right.

How to Convert MXF to ASF

1. Upload Your MXF File: Drag the .mxf onto the page or click "Add Files" to browse. Several clips can be queued and every file in the batch is converted with the same settings.
2. Check Video Codec and Audio Codec: Open Advanced Options. Video Codec opens on H.264 — not on a Windows Media codec — and Audio Codec opens on WMA v2. WMV 1, WMV 2, MPEG-2, MPEG-4, Xvid, DivX, MJPEG and others are also in the video list if a legacy decoder needs them.
3. Set File Compression and Video resolution: File Compression opens on Quality Preset at "Very High (Recommended)". Specific file size, Constant Bitrate, Variable Bitrate, Constant Quality and Constraint Quality are the alternatives. Video resolution opens on "Keep original"; Resolution Percentage, Preset Resolutions, Width, Height and Width x Height are all available, and Trim takes a Start time and Duration.
4. Convert and Download: Click Convert and save the .asf. Files are uploaded over an encrypted connection, converted on our servers and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public.

Walk-through: The Codec Pair You Actually Get

The instinct on a Windows Media page is to assume a Windows Media video codec. That is not what happens here. The page pre-selects H.264 video with WMA v2 audio, which is a legal and well-supported combination inside ASF and the right default for anything running on a machine built in the last fifteen years — H.264 has been decoded in silicon by every mainstream GPU since around 2010, while WMV 9 has not been a priority for anyone in a long time.

Where that default is wrong is at the old end. A pre-2010 Windows build, a stripped-down embedded image or a set-top signage box may ship the legacy WMV decoder and nothing newer. Switch Video Codec to WMV 2 in that case, and know what changes when you do:

• H.264 gives you a rate-control panel whose CRF field runs 16 to 51 and opens at 23 — the familiar x264 scale, where lower is better.
• WMV 1 and WMV 2 are quantiser-driven codecs. The same field re-ranges to a 1-31 qscale and opens at 5, which is a sensible value on that scale rather than a placeholder. What goes wrong is typing 23 out of x264 habit: on a 1-31 scale that sits near the bottom of the quality range, not in the middle of it. Stay in the low single digits, or use Constraint Quality and set a Max bitrate ceiling instead.

The audio side is less negotiable. WMA v2 is what Windows Media Player and its Windows 11 "Legacy" replacement decode without any codec pack, and it is what an ASF parser expects to find. The list also offers AAC, AC3, MP3, MP2, FLAC, Vorbis, Speex, DTS, EAC3, WMA v1 and several PCM widths; those write, but they are outside what ASF tooling normally expects, so treat any of them as a bet on the specific player you are targeting.

MXF and ASF Compared

What Survives the Conversion and What Does Not

Common Errors and How to Fix Them

• "The wrong audio track came out" — there is no track picker on this page. A master carrying two discrete mono stems and one stereo pair gives you the stereo pair, because the encoder's automatic selection takes the stream with the highest channel count. Isolate the track you need in your NLE and export it before converting.
• "My 16:9 footage came out squashed" — SD and HD broadcast MXF is frequently anamorphic (1440x1080 or 720x576 flagged widescreen). Leaving Video resolution on "Keep original" passes the stored pixel aspect through, but any resize normalises pixels to square and throws that flag away. If you must resize, use Width x Height and type the display geometry you want.
• "Comb lines through everything that moves" — the master is interlaced, which is normal for 1080i and 576i broadcast. Nothing here deinterlaces, so the field structure is encoded as it stands. Deinterlace on export from your editor.
• "The picture fell apart after I set the quality number to 23" — you switched to WMV 1 or WMV 2, where that field is a 1-31 quantiser and lower is better. Use a low single-digit value.
• "An old kiosk will not play it" — it probably has no H.264 decoder. Re-convert with Video Codec set to WMV 2.
• "The colours look washed out" — an S-Log, HLG or PQ master getting a plain colour conversion. Grade to Rec. 709 and re-export the MXF first.
• "The file will not open on a Mac or a phone" — expected. macOS, iOS and Android ship no ASF decoder; VLC is the reliable cross-platform reader. For anything outside Windows, MXF to MP4 is the right target.

When This Doesn't Work

.mxf describes a family rather than a single format. The extension covers several operational patterns wrapped around many different video essences, so whether a given file converts depends entirely on what is inside it. Growing or partial captures pulled off a card mid-record, vendor-specific variants and unusual essence types can decode imperfectly or be refused. The reliable fix is to re-export a flat OP-1a master from your editor and convert that. Avid and P2 OP-Atom media is the other common case: it splits each essence track into its own file, so pointing this page at an audio companion gives you a file with no picture in it.

And it is worth checking whether ASF is genuinely what you need. If the destination is a Windows tool that expects the .wmv spelling, MXF to WMV writes the same container under that extension. If the destination is anything modern, MXF to MP4 is smaller, plays everywhere, and skips the compatibility conversation entirely.

Frequently Asked Questions

Is ASF the same thing as WMV?

They are the same container. Microsoft's format defines an object layout keyed by GUIDs; .wmv names an ASF file holding Windows Media Video, .wma names one holding Windows Media Audio, and .asf is the generic spelling used when the content does not fit either naming convention. The same parsers read all three and only the extension and MIME type differ. If a downstream tool matches on .wmv specifically, use MXF to WMV rather than renaming by hand.

Why is the default video codec H.264 rather than a Windows Media codec?

Because it is the better file for almost every current destination. ASF is a container, not a codec, and it carries H.264 perfectly well — Windows Media Player and Player Legacy both decode it, and hardware decode has been standard on Intel and AMD graphics since roughly 2010. WMV 2 is the fallback for genuinely old targets: a pre-2010 Windows build, an embedded image, or a signage box that shipped with the legacy decoder and never got another. Choose it deliberately rather than by default, because it costs you picture quality per megabyte.

My MXF has eight audio tracks. Which one ends up in the ASF?

The one with the most channels, with ties broken toward the lowest stream index. There is no track picker on this page and no explicit stream mapping in the pipeline, so the encoder's automatic selection rule decides. On a typical deliverable carrying a stereo mix plus several discrete mono stems, the stereo pair wins and the mono tracks are dropped. If a specific microphone, language or stem matters, isolate it in your NLE and export before converting — a container change cannot choose for you.

Will the timecode and reel name survive?

No. Broadcast MXF carries a metadata layer that ASF has nowhere to store: start timecode, reel and tape names, essence descriptors, sometimes captions and structural metadata. None of it is written into the output. Keep the original MXF as your conform master and treat the ASF as a delivery or review copy, not a replacement for the file it came from.

Can the converter deinterlace my 1080i master?

No — there is no deinterlacing filter anywhere in this pipeline, under any codec or preset. An interlaced master is encoded with its field structure intact, so the horizontal combing on moving subjects is written straight into the ASF and shows up on progressive displays. That is the honest answer rather than a hidden setting you have missed. Deinterlace on export from your editor, or accept the combing if the file is only going to a player that handles interlaced content properly.

Why is my ASF larger than I expected?

Because Quality Preset is a quality target rather than a size target. On the H.264 codec this page opens with, the preset resolves to a CRF value: "Very High" is CRF 18 at 1080p, stepping to 16 at standard-definition frame sizes and 20 at UHD. CRF 18 is close to visually lossless, and a broadcast master is exactly the kind of material — grainy, detailed, frequently all-intra — that a near-transparent setting spends a great many bits on. Drop to High or Medium, which are CRF 20 and CRF 23 at 1080p and shift by the same resolution step, or switch File Compression to Specific file size and name the number you need. One thing to watch: if you also switch Video Codec to WMV 1 or WMV 2, the preset stops being a CRF at all and instead multiplies the master's own bitrate — 1.32x on the "Very High" rung — which on a high-bitrate master is a worse outcome still.

Does the conversion keep the anamorphic flag on my 1440x1080 master?

Only if you leave Video resolution on "Keep original". We converted a 720x576 MXF flagged 16:9 with no resize and the output kept its 64:45 pixel aspect and 16:9 display aspect intact. Any resize, including a percentage or a height preset, normalises pixels to square and discards the flag, which is what makes widescreen SD material come out narrow. When you do need to resize anamorphic footage, use Width x Height and type the display geometry directly.

Is ASF still worth targeting in a modern workflow?

Inside Windows-only estates, yes. Windows Media Player Legacy still ships as an optional feature in Windows 11, Windows Media Services-era archives are still in use, and plenty of embedded Windows kiosks and signage players expect ASF or WMV as their only guaranteed video path. Outside that, no — Microsoft's own guidance points new code away from the legacy Windows Media Format APIs, and MP4 plays on every platform without a conversation. For anything general-purpose use MXF to MP4.

How large a file can I send, and what happens to it afterwards?

There is no fixed per-file cap; the practical limit is upload size and connection speed, and a broadcast master runs to many gigabytes before the conversion even starts. If you only need part of a long clip, trimming it first with trim MXF or the video cutter is far quicker than sending the whole master. Everything you upload travels over an encrypted connection, is converted on our servers, and both the upload and the output are deleted automatically after a few hours — no sign-up, no watermark, never shared or made public.