What Is WMA? Windows Media Audio Explained
WMA is Microsoft's audio codec from 1999, abandoned by Apple, mobile, and even Microsoft itself. Learn the profile family, the DRM history, and how to convert.
The Short Answer
WMA — Windows Media Audio — is Microsoft's family of audio codecs introduced in 1999 as part of Windows Media Format. It was Microsoft's bid for the post-MP3 era: a proprietary, more efficient lossy codec tightly integrated with Windows Media Player, Internet Explorer, and the Windows DRM stack. WMA powered a decade of CD-rip libraries, PlaysForSure music stores, the original Zune ecosystem, and a lot of streaming radio in the 2000s.
By 2026 the format is effectively abandoned. Microsoft itself has stopped pushing it. Apple Music, Spotify, YouTube, and every modern streaming service ignore it. Most mobile devices reject it. Yet hundreds of millions of WMA files still exist — sitting in old Windows Media Player libraries, backup hard drives, and CDs ripped between 2002 and 2012. If you have inherited a music collection from that era, those files are probably WMA.
A Brief History
Microsoft launched WMA 1.0 in April 1999, integrated into Windows Media Player 6.4 and the Windows Media Audio and Video 4 codec pack. The pitch was direct: at half the bitrate, WMA would deliver MP3-equivalent quality. That was roughly true for early MP3 encoders — Microsoft's listening tests in 1999 showed WMA at 64 kbps matching MP3 at 128 kbps. The MP3 encoder community caught up rapidly with LAME, but the WMA marketing claim stuck.
Versions followed quickly:
- WMA 1 (1999) — initial release.
- WMA 2 / 7 (2000) — improved quality and the WMP 7 launch.
- WMA 8 (2001) — bundled with Windows XP / WMP 8. The version most legacy libraries actually use.
- WMA 9 (2003) — substantial codec overhaul, introduction of WMA Pro, WMA Lossless, and WMA Voice as separate profiles.
- WMA 9.2 / 10 — minor tuning, mostly for HDDVD/BD use.
- WMA 9.2 Voice — last meaningful update around 2006.
The format peaked roughly 2003–2007. PlaysForSure (Microsoft's DRM-licensed music ecosystem with Napster, MSN Music, Yahoo! Music Unlimited, Walmart Music, and dozens of others) ran on WMA. The original Microsoft Zune (2006) used WMA as its native format. Then iTunes and the iPod won the ecosystem war, Microsoft killed PlaysForSure in 2008 and replaced it with Zune Music Pass (still WMA), and then killed Zune in 2012. Groove Music (formerly Xbox Music) replaced Zune and migrated to non-DRM formats. The WMA codec is still bundled in Windows 11 — Media Player Legacy and the modern Media Player both decode it — but Microsoft no longer encodes new content into it for any consumer-facing service.
The Profile Family
WMA is not one codec but four:
WMA Standard — the original lossy transform codec. Modified discrete cosine transform (MDCT) with psychoacoustic modeling, similar in concept to AAC and Vorbis. Bitrates from 5 kbps to 384 kbps; sample rates up to 48 kHz; mono and stereo only. This is what 99% of '.wma' files in the wild actually are. Quality is broadly competitive with mid-era MP3 LAME — better than the worst MP3 encoders at low bitrates, roughly equivalent to LAME -V2 at typical settings.
WMA Pro — released with WMA 9 in 2003. Supports up to 24-bit/96 kHz audio and up to 7.1 surround. Bitrates 128 kbps to 768 kbps. Better quality than WMA Standard at every setting and competitive with HE-AAC for similar bitrates. Almost no consumer software wrote WMA Pro — it was designed for HD DVD, Blu-ray's secondary audio tracks, and digital cinema, none of which were mass markets.
WMA Lossless — introduced with WMA 9. Bit-for-bit reversible compression up to 24-bit/96 kHz, comparable in concept to FLAC. Compression ratios slightly worse than FLAC. Largely ignored in favor of FLAC and ALAC; WMA Lossless never escaped the Windows ecosystem.
WMA Voice — narrowband speech codec, 8–22 kbps, 8 kHz / 16 kHz sample rates only. Used in some Windows Mobile voice recorders, some podcast publishing tools in the 2003–2008 era, and Skype's older Windows clients. Functionally obsolete now that Opus exists.
When you see a '.wma' file the rule of thumb is "Standard unless proven otherwise" — Pro and Lossless are uncommon, and Voice files almost always have a different extension or context.
The Container and File Structure
WMA files use Microsoft's Advanced Systems Format (ASF) as their container — the same container that holds WMV video. ASF is a packetized, indexed, optionally encrypted container designed for streaming over networks. A '.wma' file consists of a Header Object (with metadata, codec configuration, and DRM data), a Data Object (the audio packets), and an Index Object (for fast seeking). ASF was Microsoft's answer to RealMedia and QuickTime — designed for the streaming era, but also built so Microsoft could revoke playback rights remotely via DRM, which became a feature nobody wanted.
The ASF metadata model is reasonably capable: ID3-like tags, multiple bitrate stitching ("MBR" — different bitrate streams in one file for adaptive streaming), and arbitrary key/value attributes. Cover art embedding works. Tag editors like Mp3tag handle WMA metadata fine.
The Licensing and DRM History
WMA's DRM story is the format's most consequential legacy. Microsoft built Windows Media DRM into WMA from version 7 onwards. A protected '.wma' file (often called WMRMv1, v2, or v10 depending on era) embeds an encrypted content key and references a licensing server. To play the file, Windows Media Player contacted Microsoft's license server, verified the user's purchase or subscription, and obtained a per-machine decryption key.
This worked when the servers were running. Two events showed why DRM tied to a single vendor's online infrastructure is fundamentally fragile:
- MSN Music shutdown (2008) — Microsoft told customers it would deactivate license issuance for MSN Music purchases. After enormous backlash they extended the license server until 2011, but the message was clear: when Microsoft retires a service, the music users "bought" stops being playable.
- Yahoo! Music Unlimited shutdown (2008) — Yahoo's WMA-based service shut down with 30 days' notice. Subscribers were given Rhapsody credit; their downloaded WMA files became unplayable.
Today the original WMRM license servers are gone. DRM-protected WMA files from Napster (pre-Rhapsody), the original MSN Music store, Yahoo! Unlimited, Walmart Music Downloads, and the original Zune Marketplace are now effectively bricked: Windows can decode the codec, but it cannot acquire a license to decrypt the audio. Recovery is essentially impossible without the original license — analog reamping (playing the file in a DRM-aware environment that still works, capturing the analog out) is the last-resort method for genuinely irreplaceable files.
If you have a '.wma' file that refuses to convert with the message "this file is protected" or similar, that is the cause. Unprotected WMA (the much more common case — anything ripped from your own CDs by Windows Media Player) converts trivially.
WMA Quality, Honestly
Microsoft's "WMA at 64 kbps equals MP3 at 128 kbps" marketing claim was true in 1999, against Fraunhofer's reference MP3 encoder. Modern blind testing tells a different story:
- WMA Standard at 64 kbps — usable for speech, audibly compromised on music. Both MP3 (LAME -V8) and AAC (HE-AAC v2) are clearly better.
- WMA Standard at 96 kbps — acceptable for casual music listening. Roughly equivalent to MP3 LAME -V6, a bit behind AAC LC at 96 kbps.
- WMA Standard at 128 kbps — competitive with MP3 LAME -V4 / 128 kbps CBR. AAC at the same bitrate is generally better.
- WMA Standard at 192 kbps — close to transparent for most listeners, equivalent in practice to MP3 at the same bitrate.
- WMA Standard at 320 kbps — the maximum stereo bitrate. Hard to fault on most material, but not lossless.
WMA Pro is genuinely better than WMA Standard at every setting and competitive with modern AAC and Vorbis. The trouble is that almost no playback software outside Windows handles Pro correctly — it tends to fall back to silent or stuttered playback rather than transcoding.
Why WMA Files Exist in 2026 Libraries
Three sources account for nearly all the WMA files real users encounter:
1. CDs ripped with Windows Media Player. Between WMP 9 (2003) and WMP 12 (2009), the default rip format was WMA. Millions of Windows users built their entire music libraries this way without changing the setting. 2. Built-in Windows voice recorders. The Sound Recorder utility on Windows XP / Vista / 7 wrote WMA Voice files by default, and many a doctor's dictation, lecture recording, and audio note from that era is still on a hard drive somewhere as a '.wma'. 3. Downloads from defunct stores or podcasts. A few open podcasts published WMA enclosures, and a few audiobook publishers used WMA for early downloadable audiobooks. Most of these are now of historical interest only.
If you are converting a library, the realistic plan is: identify whether your files are protected (right-click → Properties → Details → look for any "Content protection" entry), convert the unprotected ones to MP3 or FLAC, and accept that the protected ones are likely lost.
Compatibility Reality
WMA playback in 2026:
- Windows — Media Player Legacy and the modern Media Player decode all WMA profiles. VLC, foobar2000, MusicBee handle it.
- macOS — no native support since Flip4Mac was discontinued. VLC plays unprotected WMA. iTunes/Music does not.
- iOS / iPadOS — no native support. VLC plays unprotected WMA via its own decoders.
- Android — most stock players reject WMA. VLC, MX Player, and Poweramp handle it.
- Linux — VLC and most multimedia frameworks support unprotected WMA via ffmpeg.
- Hardware — older Windows-aligned car stereos and home receivers often play WMA Standard. Modern ones rarely do. Bluetooth speakers do not understand WMA at the wire level.
- Streaming services — none accept WMA uploads. iTunes Match, Apple Music library upload, and YouTube Music all require non-WMA sources.
Conversion Strategy
For unprotected WMA — which is the vast majority of files — conversion is straightforward:
- WMA → MP3 — the universal compatibility move. The WMA to MP3 converter handles this in your browser. Use 192 kbps or 256 kbps to minimize transcoding artifacts; both formats are lossy, so each conversion compounds quality loss slightly. Detail: WMA to MP3 guide.
- WMA → WAV — when you need an editable, uncompressed working file. The WMA to WAV converter decodes the WMA and writes raw PCM. The audio will sound identical to the WMA source — converting to WAV does not recover the quality lost during WMA's original encoding.
- WMA → OGG — for game audio pipelines or open-format archives. The WMA to OGG converter covers this.
- WMA → FLAC — only meaningful if the source is WMA Lossless, in which case the audio quality is preserved exactly. For lossy WMA Standard, transcoding to FLAC yields a bigger file with the same lossy artifacts as the source.
- WMA on Mac — see the convert WMA to MP3 on Mac walkthrough for browser-based and CLI options.
For protected WMA, the realistic options are: locate the original purchase receipt and re-download from the issuing service if it still exists (most do not); play the file in a DRM-licensed environment that still works (a Windows 7 or 10 install activated against the original license, if you have one) and capture the audio via virtual loopback; or accept the loss. Browser-based converters cannot strip Microsoft's DRM, and tools that claim to are usually selling broken or malicious software.
Should You Use WMA Today?
For new audio: no. Every reason to choose WMA in 2003 is gone. MP3 has wider playback compatibility. AAC has better quality at every bitrate. FLAC has lossless compression with better metadata. Opus crushes WMA on every objective measure. There is no remaining advantage WMA holds — even Microsoft's own modern apps prefer non-WMA formats.
For existing files: convert them. The What is MP3 explainer covers the format you are most likely converting to. The format-explainer index covers everything else.
WMA was a competent codec at the wrong moment in history, with a licensing model that turned its biggest advantage — tight Windows integration — into a liability. Two decades later it is mostly a migration problem rather than a working format.