Why won't my Mac play WMA files?

macOS does not include a Windows Media Audio decoder. Apple never licensed the codec stack from Microsoft, and the third-party Flip4Mac plugin that used to bridge the gap was discontinued in 2018 and does not work on macOS Catalina or later. QuickTime Player, the Music app, and AirPlay all return 'document could not be opened' or play silently when handed a .wma file. The fix is to convert WMA to a macOS-native format like MP3 or AAC first, which you can do in a browser, with command-line FFmpeg, or with VLC.

Can I convert DRM-protected WMA files to MP3?

No. WMA files purchased from old Microsoft Media DRM stores (PlaysForSure, MSN Music, Yahoo Music Unlimited, early Zune Marketplace) are encrypted and require a license server that Microsoft has shut down. The audio cannot be decoded without that license, and no converter can bypass the DRM legally or reliably. You can identify protected files by running 'ffmpeg -i file.wma' and looking for 'DRM protected' in the output. Unprotected WMA — files you ripped yourself or downloaded from non-DRM sources — converts cleanly.

What bitrate should I use when converting WMA to MP3?

Match the source quality. Most WMA files were ripped at 128 or 192 kbps, so converting to MP3 192 kbps preserves the audible quality without inflating file size. Going higher than the source bitrate cannot recover detail the WMA encoder already discarded. For WMA Lossless files, MP3 320 kbps is the highest practical lossy target, or convert to FLAC to keep lossless quality. For spoken-word WMA recordings, MP3 96-128 kbps mono is sufficient and saves significant disk space.

Is FFmpeg or AudioUtils faster for large WMA libraries?

Command-line FFmpeg with GNU Parallel is faster for libraries over a few dozen files because it saturates every CPU core in parallel. On an M2 Mac, FFmpeg processes WMA at roughly 15-25x realtime per core, so a 500-song library completes in 30-60 minutes using all 8 cores. AudioUtils in the browser handles single-file or small-batch conversion comfortably and wins for a one-off file because there is no install step. The crossover is around 30 files.

Will the artist, album, and track number tags survive WMA to MP3 conversion?

Yes, in most cases. WMA stores metadata in an ASF metadata block that FFmpeg automatically maps to ID3v2 tags in the output MP3. Artist, album, title, track number, year, genre, and album art all transfer. AudioUtils and VLC do the same mapping. If tags do not transfer, add the '-map_metadata 0' flag to FFmpeg explicitly. The one edge case is custom WMP rating values, which use a Microsoft-specific scale that does not have a direct ID3 equivalent and may be dropped.

How to Convert WMA to MP3 on Mac (Step-by-Step Guide)

WMA (Windows Media Audio) was Microsoft's answer to MP3 in the early 2000s, and a lot of legacy Windows-ripped music libraries still contain it. On a Mac, that creates an immediate problem: macOS does not decode WMA natively. QuickTime Player, the Music app, and AirPlay all silently refuse the format. This guide covers every working method to convert WMA to MP3 on a Mac in 2026, plus the one type of WMA file you cannot convert.

Why macOS Doesn't Play WMA Natively

Microsoft never licensed the Windows Media codec stack to Apple. The old Flip4Mac plugin from Telestream that brought WMA support to QuickTime was discontinued in 2018 and is incompatible with macOS Catalina and later (no 32-bit support, no notarization). That left a gap that Apple has never filled — every modern Mac, including M-series Apple Silicon machines on macOS Sonoma and Sequoia, ships without a WMA decoder.

The result is that double-clicking a .wma file produces 'The document could not be opened' or it opens silently with no audio. The fix is to convert to MP3, AAC, or another macOS-native format first.

Method 1: Convert WMA to MP3 in the Browser (Easiest)

AudioUtils' WMA to MP3 converter handles WMA in WebAssembly FFmpeg. The codec runs inside the browser tab — no Flip4Mac, no install, no Microsoft components needed. Workflow:

1. Open Safari, Chrome, or Firefox on your Mac. 2. Navigate to the WMA to MP3 tool URL. 3. Drag the .wma file onto the drop zone. The file is read into browser memory, never uploaded. 4. Choose 192 kbps CBR (recommended for music) or 128 kbps (voice). Sample rate stays at 44.1 kHz. 5. Click Convert. A 4-minute song finishes in 5-10 seconds on Apple Silicon, slightly slower on older Intel Macs. 6. Save the MP3. It plays in QuickTime, the Music app, AirPods, HomePod, and every other macOS audio surface.

Privacy advantage: your library never leaves the Mac. Important if the WMA files are unreleased recordings, archived voicemail, or anything you do not want sitting on a third-party server.

Method 2: ffmpeg via Homebrew (Best for Batches)

For converting hundreds of WMA files at once, command-line FFmpeg on macOS is the most efficient option. Install Homebrew first if you do not have it (one line at brew.sh), then:

'brew install ffmpeg' — fetches a current FFmpeg build with WMA decode support
'ffmpeg -i input.wma -c:a libmp3lame -b:a 192k output.mp3' — single file
'for f in *.wma; do ffmpeg -i "$f" -c:a libmp3lame -b:a 192k "${f%.wma}.mp3"; done' — every WMA in the current folder

Run that loop in Terminal inside the directory containing your library and FFmpeg processes the files sequentially. On an M1 Mac, expect roughly 10-15x realtime — a 4-minute song finishes in under 20 seconds, and a 500-song library completes in 1-2 hours.

For parallel batch processing, GNU Parallel makes it faster: 'brew install parallel' then 'parallel ffmpeg -i {} -c:a libmp3lame -b:a 192k {.}.mp3 ::: *.wma' will saturate every CPU core.

Method 3: VLC's Convert/Save

VLC for Mac (free at videolan.org) decodes WMA and exports to MP3 through its Convert/Save dialog under the File menu. Steps:

1. File > Convert/Stream 2. Drag in the WMA file 3. Choose 'Audio - MP3' as the profile 4. Pick a destination 5. Save

VLC is slower than command-line FFmpeg but easier than installing Homebrew. It is also a good fallback when a particular WMA file refuses to decode in another tool, since VLC ships with an unusually permissive codec stack.

DRM-Protected WMA: The One You Cannot Convert

WMA files purchased from old Windows Media DRM stores (the original PlaysForSure ecosystem, MSN Music, Yahoo Music Unlimited, Zune Marketplace pre-2008) carry license-based DRM. The actual audio is encrypted and cannot be decoded without a Microsoft license server that no longer exists.

You can identify a DRM-protected WMA by inspecting the file in Finder Get Info — protected files typically show a 'license' or 'DRM' field. Or run 'ffmpeg -i file.wma' and look for 'is DRM protected' in the output. Converters cannot bypass this. The legal route is to repurchase the music from a current store (Apple Music, Amazon, Bandcamp) or stream from a service.

Unprotected WMA — files you ripped yourself with Windows Media Player or downloaded from non-DRM sources — converts cleanly with any of the methods above.

Recommended Bitrate

For ripped CDs originally encoded at WMA 128 or 192 kbps: convert to MP3 192 kbps. There is no quality benefit going higher than the source — you cannot recover detail that the original WMA encoder discarded — and 192 kbps MP3 is the floor where transcode artifacts become inaudible.

For WMA Lossless (.wma with the 'wmal' codec): convert to MP3 320 kbps if you want a single-format library, or convert to FLAC if you want to preserve lossless quality on the Mac side.

For voice recordings (interviews, lectures): MP3 96-128 kbps mono is fine.

Batch Workflow

If you have a large WMA library to migrate, the clean workflow is:

1. Sort by source: separate ripped CDs from purchased / DRM-encumbered files. 2. Test one file first to confirm decode works. 3. Use FFmpeg with GNU Parallel for the bulk conversion. 4. Verify metadata transferred (artist, album, track number) — WMA stores ID3-style tags that FFmpeg copies to MP3 ID3v2 by default. If not, add '-map_metadata 0' to force. 5. Spot-check a few output files for quality. 6. Archive the original WMA files to an external drive before deleting, in case any conversion failed silently.

For more on the WMA format itself, see what is WMA. For converting on Windows, see WMA to MP3 on Windows. For the broader WMA vs MP3 comparison, see MP3 vs WMA and WMA vs MP3 quality.

Verifying the Conversion

After converting a WMA library, spot-check the output before deleting originals:

1. Open the new MP3 in QuickTime or the Music app to confirm playback 2. Compare duration to the source WMA (should match exactly) 3. Listen for artifacts at the start and end of tracks — some buggy WMA files produce truncated MP3 output 4. Check that ID3v2 tags transferred (artist, album, title, track number, year) 5. Verify embedded album art still displays 6. Test a representative sample of the library, not just the first file

If any of these fail, re-run the conversion with a different tool. FFmpeg's WMA decoder, VLC's WMA decoder, and AudioUtils' WebAssembly FFmpeg all share most code but occasionally one handles a specific malformed WMA better than another.

Migrating from Windows to Mac

If you are switching from Windows to Mac and bringing a WMA library, the cleanest workflow is to convert all WMAs to MP3 320 kbps (or FLAC for lossless WMAs) on the Windows side first using a familiar tool, then transfer the converted files. This avoids the 'Mac cannot decode WMA' problem entirely and gives you a chance to clean up tags and folder structure during the migration.