AV1 to ASF Converter

Convert AV1 to ASF: What This Tutorial Covers

AV1 is AOMedia's modern royalty-free video codec; ASF is Microsoft's Advanced Systems Format, the container behind Windows Media. This guide walks the conversion end to end and spends most of its time on the one setting that decides whether your .asf opens in the Windows Media tooling you are targeting — because the output does not default to the codec most people assume. Read the walk-through before you convert; re-running it afterwards is the slow way to learn this.

How to Convert AV1 to ASF

1. Upload Your AV1 File: Drag and drop your .av1 file onto the page, or click "+ Add Files" to browse. Batch upload is supported — queue several clips and convert them all with one set of settings.
2. Pick a Compression Method: Under File Compression the default is Quality Preset → Very High (Recommended). Drop it toward Medium or Low for a smaller file, or switch to Specific file size, Constant Bitrate, Variable Bitrate, Constant Quality, or Constraint Quality when a downstream system dictates the numbers.
3. Set the Video Codec, Resolution, and Trim: Open the advanced options to reach Video Codec (defaults to H.264 here — see the walk-through), Audio Codec (defaults to WMA v2), Video resolution (defaults to Keep original), and Trim, where Time Range exports just a start-plus-duration segment.
4. Convert and Download: Click Convert. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public.

Walk-through: Picking the Codec That Actually Plays

ASF is deliberately codec-agnostic. Microsoft's own description is that an ASF file's streams "can be in any compressed or uncompressed format" — the container defines objects, packets, and indexes, not the compression inside them. That flexibility is exactly what trips people up here, because a valid .asf can hold video that your target software has never heard of.

On this page the Video Codec dropdown defaults to H.264 and the Audio Codec dropdown to WMA v2. That pairing is modern and efficient, and it opens in VLC, MPC-HC, and anything else built on FFmpeg — but H.264-inside-ASF is not what a classic Windows Media Player build or an old Windows Media Server was written to expect.

• You need genuine Windows Media compatibility. Change Video Codec to WMV 2 (Windows Media Video 8) and leave Audio Codec on WMA v2. That is the codec pairing the .wmv/.asf ecosystem was built around, and it is what an old player looks for.
• You just need an .asf extension for a modern player. Leave the defaults. H.264 in ASF is smaller at the same quality than WMV 2 and plays anywhere FFmpeg-based demuxing exists.
• You wanted to keep AV1 itself. The dropdown does list AV1, but almost nothing in the Windows Media world can decode AV1 in an ASF wrapper, so this combination gives you the compatibility problems of ASF with none of its compatibility benefit. If you want to stay on AV1, keep the file as it is.

One thing no setting can change: this is always a re-encode. AV1 and the codecs ASF carries are unrelated, so the picture is decoded and re-compressed from scratch — there is no stream-copy or rewrap path. Because AV1 is a far more efficient codec than H.264 or WMV 2, the ASF you get back is normally larger than the AV1 you started with, at best equal in quality. That is the direction of travel here, and it is the price of compatibility.

What the ASF Options Actually Offer

AV1 vs ASF at a Glance

Common Errors and How to Fix Them

• "Audio plays but the video is black in Windows Media Player" — you left Video Codec on the default H.264. Re-convert with WMV 2.
• "My iPhone, browser, or QuickTime won't open the .asf" — expected. ASF support outside the Windows ecosystem is thin. For portable playback use AV1 to MP4.
• "The output is bigger than my AV1 source" — also expected, and unavoidable when re-encoding to an older codec. Lower the Quality Preset, or use Specific file size to cap the result.
• "The converted file has no sound" — a raw .av1 bitstream has no audio track to begin with, so there is nothing for the WMA v2 encoder to work with. Check whether your source actually carries audio.
• "Conversion is taking a long time" — the wait is upload time plus a full re-encode. Use Trim → Time Range to convert only the part you need, or downscale under Video resolution.

When This Doesn't Work

ASF earns its place in exactly one situation: something Windows-only refuses to accept anything else — a Windows Media Server playlist, an archival pipeline built on the Windows Media Format SDK, or in-house software that filters on the .asf extension. Even Microsoft has moved on: its documentation labels the Windows Media Format 11 SDK a legacy feature, superseded by the Source Reader and Sink Writer APIs in Media Foundation, and recommends that new code use those instead. If your goal is playback, sharing, or editing rather than feeding a legacy Windows workflow, convert to AV1 to MP4 and skip ASF entirely. If you specifically need a .wmv rather than a .asf — same container, Windows Media naming — use AV1 to WMV.

Frequently Asked Questions

Which codecs does the ASF output use by default?

Video defaults to H.264 and audio to WMA v2. That surprises people who expect Windows Media Video, and it matters: H.264 in an ASF wrapper plays in VLC, MPC-HC, and other FFmpeg-based players, but a classic Windows Media Player build may show audio with no picture. For genuine legacy compatibility, open the advanced options and set Video Codec to WMV 2 before converting.

Why would I convert AV1 to ASF instead of MP4?

Only for a Windows-specific requirement. ASF is the container Windows Media was built on, so a Windows Media Server, an old Windows Media Format SDK pipeline, or a line-of-business tool that hard-codes .asf may need it. For anything else — phones, browsers, editors, sharing — MP4 is better supported and smaller at the same quality, so use AV1 to MP4.

Will the ASF file be smaller than my AV1 file?

No. AV1 is a substantially more efficient codec than H.264, and dramatically more efficient than WMV 2, so re-encoding into ASF needs more bits to hold the same picture. Expect the .asf to be larger than the source at a high preset, or visibly softer if you force it smaller. You cannot recover compression efficiency by moving to an older codec.

Is the conversion lossless, or can I just rewrap the stream?

Neither — there is no rewrap. AV1 cannot be copied into ASF untouched, so the video is decoded and re-encoded to the codec you pick, which is a second lossy generation on top of whatever the AV1 encode already discarded. Keeping Quality Preset on Very High (Recommended) and Video resolution on Keep original is the way to keep that second generation invisible.

Will my ASF have sound?

Only if the source has an audio track. A bare .av1 file is a raw video bitstream — picture only — so a conversion from one produces a silent .asf no matter which audio codec is selected. Files exported from XConvert as AV1 are the exception: those are wrapped in a Matroska container and keep their audio track despite the .av1 name, and that audio is re-encoded to WMA v2 on the way into the ASF.

Will the .asf open in VLC as well as Windows Media Player?

VLC and MPC-HC open .asf regardless of the codec inside, because their demuxers are FFmpeg-based. Windows Media Player is the codec-sensitive one: with WMV 2 it plays on essentially any Windows build, while with the default H.264 payload behaviour varies by Windows version. QuickTime, iOS, and browsers do not open ASF at all.

What is actually inside an ASF file?

Microsoft describes ASF as an extensible format for storing and transmitting synchronised digital media streams. Internally it is a set of GUID-tagged objects: a required Header object holding file size, stream count, codec information, and metadata; a required Data object holding the stream packets; and an optional Index object of key-frame positions for seeking. One consequence of that design is robustness — a partially downloaded ASF is still readable as long as it has the Header object and at least one Data object.

Is ASF still maintained, or should I migrate off it?

Treat it as legacy. Microsoft's documentation marks the Windows Media Format 11 SDK — the toolkit behind ASF authoring — as a legacy feature superseded by the Source Reader and Sink Writer APIs, and strongly recommends new code use those instead. Existing .asf files still open on Windows 10 and 11, but for anything you want to keep or share, a modern container is the safer bet. To migrate files you already have, use ASF to MP4.