Initializing... drag & drop files here
Supports: ASF
ASF (Advanced Systems Format) is Microsoft's container for Windows Media content, and .wma is not a different format — it is the same container carrying an audio-only payload. Microsoft states it plainly in the Windows Media Format documentation: "ASF is the container format for Windows Media Audio and Windows Media Video-based content. The extension wma or wmv is used to specify an ASF file that contains content encoded with the Windows Media Audio and/or Windows Media Video codecs." So converting .asf to .wma means one thing in practice: drop the video stream and write the sound back out as Windows Media Audio, under the extension that tells Windows the file is audio-only.
| Property | Value |
|---|---|
| Full name | Advanced Systems Format |
| Developer | Microsoft |
| Role | Extensible container for storing and streaming synchronized digital media |
| Specification | ASF Specification / Windows Media Format SDK |
| File structure | Header object + Data object (both required), plus an optional Index object; every object is keyed by a GUID |
| Typical payload | Windows Media Video + Windows Media Audio, but any compressed or uncompressed stream is allowed |
| Sibling extensions | .wmv (contains video), .wma (audio only) |
| Notable behaviour | A partially downloaded ASF still plays as long as the Header object and one Data object survived |
| Tooling status | The Windows Media Format 11 SDK is a legacy feature; Microsoft now points developers at Source Reader / Sink Writer |
| Best for | Legacy Windows Media streaming and archives |
| Property | Value |
|---|---|
| Full name | Windows Media Audio |
| Developer | Microsoft, first shipped in 1999 as an MP3 competitor |
| Container | ASF — a .wma file is an audio-only ASF file |
| Codec written here | WMA v2 (WMAV2) by default; WMA v1 (WMAV1) also selectable |
| Compression type | Lossy, psychoacoustic transform coding |
| Channel / rate ceiling | WMA Standard is a two-channel codec topping out at 48 kHz; multichannel and high-resolution audio require WMA Pro |
| Family members | WMA Standard, WMA Pro, WMA Lossless, WMA Voice — this converter outputs WMA Standard |
| Native playback | Windows and Windows Media Player; VLC and foobar2000 also decode it |
| Weak spots | Not natively supported by Apple's Music app, most phones, or mainstream browsers |
| Best for | A device or program that specifically demands .wma and refuses MP3 |
.asf onto the page or click "+ Add Files". Queue several files at once and they all run with the same settings..wma individually or as a ZIP. No sign-up, no watermark.For a file that plays outside the Windows ecosystem, ASF to MP3 or ASF to AAC is the better target; use ASF to MP4 if you want to keep the video track instead of discarding it.
Structurally, yes — they share one container. Microsoft defines ASF as the wrapper for Windows Media content and says the wma extension marks an ASF file whose payload is Windows Media Audio, while wmv marks one that also carries video. A file saved with the generic .asf extension can hold either, which is exactly why running a conversion is the reliable way to end up with a clean, audio-only .wma that Windows and its media apps treat as a music file rather than a video.
It re-encodes. Our server decodes the audio stream inside the ASF and runs it through a fresh Windows Media Audio encode rather than copying the compressed bytes across, so the result is not a bit-for-bit passthrough of the original. Because the source audio inside an ASF is usually already lossy WMA, that second encode discards a little more detail. Keep the loss minimal by matching or exceeding the source bitrate. If you do not need to stay in Windows Media format at all, ASF to MP3 avoids stacking WMA on top of WMA.
Leave it on WMA v2. That is the default here and the standard Windows Media Audio encoder — better quality per bitrate than the original 1999-era v1 codec, and understood by every modern Windows media stack. WMA v1 exists in the dropdown purely for compatibility with very old players or embedded software that predates v2 support. If you are not troubleshooting a specific ancient device, there is no reason to select it.
Pick by content, and work from the source. For spoken word, 64–96 kbps mono is plenty. For music, 128 kbps is the everyday choice and 192 kbps stays close to transparent for most listeners on typical gear. The arithmetic is simple if you need to predict size: bitrate multiplied by duration, so 192 kbps for a three-minute track is roughly 4.3 MB before container overhead. Going far above the source's original bitrate does not recover anything — it just makes the file bigger.
It is discarded. This conversion targets an audio-only container, so the Windows Media Video stream, along with any script commands, text streams, or other data streams the ASF carried, is dropped and only the audio is written out. If you actually want to keep the picture, convert to a video target instead — ASF to MP4 keeps both streams in a container that plays far more widely than ASF does.
Only sometimes. Native WMA decoding is essentially a Windows and Windows Media Player story. VLC and foobar2000 handle it on other platforms, and a good number of 2000s-era car head units and DLNA devices do too, but Apple's Music app, most phones, and mainstream browsers do not. Reserve .wma for the one device or application that specifically expects it; anything else is better served by ASF to MP3 or ASF to AAC.
No. The Audio Codec control offers WMA v1 and WMA v2, both of which are WMA Standard — a lossy, two-channel codec. WMA Pro (multichannel, higher sample rates) and WMA Lossless are separate encoders in the Windows Media family and are not written here. If you need a lossless archive of the audio from an ASF, target a lossless format instead: ASF to WAV gives you uncompressed PCM, and Audio to FLAC gives you compressed lossless with tagging.
Some older ASF and WMA files carry Windows Media DRM, which encrypts the media stream and ties playback to a licence bound to the original account or device. A converter cannot decode a protected stream, so the job fails or yields silence. That is a property of the DRM wrapper, not a limitation of the format or the tool. The only fix is to obtain an unprotected copy from the original source.
Files travel to us over an encrypted connection, are processed on our servers, and are deleted automatically a few hours after conversion. Nothing is shared or made public, there is no account to create, and no watermark is added. On a big batch, the practical constraint is how long the transfer takes rather than a per-file ceiling.