WMA to MP3: rescue your Windows Media library
Your browser cannot decode WMA. Not Chrome, not Safari, not Firefox. The codec was never
licensed for the web, and at this point it never will be. So when you drop a .wma file into
mp3fy, it doesn’t pretend otherwise. The file’s row says plainly that this
device can’t read it and routes it to the cloud automatically. The row says so while the file uploads
over TLS, native ffmpeg converts it on our servers, and the upload is deleted the moment the
conversion finishes. A 4-minute track round-trips in about 15 seconds. That’s the whole answer.
The rest of this page is why you have these files, and how to rescue a few hundred of them at
once.
The format that was supposed to win
It’s 2001. You’ve just installed Windows XP, and Windows Media Player 8 is grinning at you from
the Start menu. You put a CD in the drive, press “Copy from CD”, and out come files ending in
.wma, not .mp3. That wasn’t an accident. Ripping to MP3 required a plugin that cost about
ten dollars, because Microsoft didn’t feel like paying Fraunhofer’s licensing fees on your
behalf. Ripping to WMA was free, one click, and the default.
The pitch was genuinely bold: Microsoft claimed WMA at 64 kbps sounded as good as MP3 at 128, so your hard drive (all six gigabytes of it) could hold twice the music. Millions of people took the deal without ever knowing a deal was on the table. They just pressed the shiny button.
Then October 2001 happened. The iPod shipped, it never played WMA, and it never would. iTunes ripped to MP3 and later AAC, every player that mattered followed Apple’s lead, and Microsoft’s answer (the Zune, plus a DRM ecosystem literally branded “PlaysForSure”) arrived late and left early. The Zune, in a detail almost too good to be true, didn’t support PlaysForSure either.
WMA never got a funeral. It just stopped being invited. Today an iPhone won’t play it, most editors won’t import it, and browsers never supported it at all. Your music is fine, though. It’s wearing the wrong container, and containers can be changed.
Rescue the whole library at once
Nobody converts two hundred albums one song at a time. Do it in a single pass:
- Open the converter and press Add folder. Point it at the old
My Musicdirectory: the whole tree, subfolders and all. - Everything queues. WMA rows head to the cloud on their own; anything your browser can decode (stray MP3s, WAVs) converts on-device and never leaves your machine. Cloud jobs run a few at a time per person: a rate cap, never a size cap. There’s no limit on file count, size, or duration.
- Wait. Progress is live per file, and tags carry over: artist, album, title, the track numbers you fixed by hand in 2004.
- Press Download all. Every finished file streams into a single ZIP as it completes.
Converted files don’t sit around. Each output expires one hour after you first download it, or 24 hours after conversion, whichever comes first. Grab the ZIP, spot-check a few tracks, done. For the longer walkthrough, see batch-converting a folder.
The DRM files, frankly
Some of your WMA files aren’t rips. They’re purchases (from MSN Music, Napster 2.0, Walmart, Yahoo Music Unlimited), and those came wrapped in Windows Media DRM. Here’s the part most converter sites won’t say out loud: no legitimate tool can convert them. Not mp3fy, not anything else. The license servers those files phone home to were switched off years ago; when MSN Music wound down, Microsoft’s parting advice to customers was to burn their purchases to CD while they still could. The right to play those files died with the stores that sold them.
Any converter claiming to handle “protected” WMA is either stripping DRM, which is legally murky at best, or lying about what it does. mp3fy does neither. A protected file fails with a protection error, and that’s the correct behavior, not a bug.
The good news: CDs you ripped yourself aren’t DRM’d, and for most libraries that’s nearly everything. Those convert without complaint.
The other relics in the same drawer
The XP era left more than WMA behind. RealAudio files (.ra and .rm,
from the age of buffering) are equally undecodable in a browser, and ASF
is essentially WMA’s container wearing a trench coat. mp3fy handles both through exactly the
same automatic cloud path: TLS up, native ffmpeg, delete on finish, same fifteen seconds a
track. One rainy afternoon clears the whole drawer.
Frequently asked
Is uploading my files to the cloud safe?
As safe as we know how to make it. Files travel over TLS, are converted by native ffmpeg, and the upload is deleted the moment conversion finishes: not on a nightly cleanup job, immediately. Output expires an hour after first download and 24 hours regardless. No accounts, no cost, nothing retained; details in the privacy policy. For every format a browser can decode, mp3fy converts on-device and nothing uploads at all. WMA is one of the few where the cloud is the only road.
What MP3 bitrate should I pick for old WMA rips?
Match the source, don’t inflate it. A 128 kbps WMA rip holds 128 kbps of information; encoding it at 320 makes the file bigger, not better. For era-typical rips, 192 kbps is a comfortable ceiling. The full reasoning is in which MP3 bitrate to use.