Why Windows Media Player will not play your M4A

A colleague or a phone sent them an .m4a and their default player refuses it. Microsoft's own forum answers recommend converting to WMA or installing a codec pack — advice that is either backwards or risky.

An .m4a is not really a format. It is a wrapper, and what sits inside it is almost always AAC audio in an MPEG-4 container. Windows Media Player Legacy — the classic player people still mean when they say Windows Media Player — has decoded plain AAC since Windows 7, so when it refuses your file the cause is usually one of four specific things: the audio inside is Apple Lossless rather than AAC, the file is really an .m4b, .m4r or a protected iTunes purchase wearing the wrong name, you are running an N edition of Windows with the media components stripped out, or the download never finished. If you only need to hear it now, drag the file into Microsoft Edge or open it in VLC. If something downstream is demanding MP3, convert it once in this tab and stop fighting the player.

What is actually inside an M4A

MPEG-4 defines one container and several extensions that all use it. Apple gave each purpose its own suffix, and Windows reads suffixes rather than contents, which is where most of this trouble starts.

Note the row that looks like a contradiction. Renaming .m4r to .m4a works because both extensions describe the same MPEG-4 container holding the same AAC stream, so nothing about the bytes has to change. Renaming that same file to .mp3 does not work, because MP3 is a different container and a different codec. That distinction is the whole subject of why renaming an M4A to MP3 does not convert it.

Find out which file you actually have

File Explorer will not tell you the codec. Three ways to see it that take under a minute:

• VLC: open the file and press Ctrl+J, or use Tools > Codec Information. The Codec line says MPEG AAC Audio (mp4a) or Apple Lossless (alac).
• This site's converter: drop the file on it and it reads the codec, the sample rate, the channel count and the duration before you choose anything. Nothing is sent anywhere to do that — the inspection happens in the page, in front of you.
• File Explorer, partially: right-click the file, choose Properties, then the Details tab. A bit rate of about 1,000 kbps or more on something described as M4A is the giveaway that you are holding ALAC, not AAC.

While you are in Explorer, turn on View > Show > File name extensions. Windows hides them by default, and a surprising share of "it will not play" files turn out to be called recording.m4a.dat or similar, because a webmail client added a suffix on the way down.

The N edition trap, and how to check in ten seconds

Windows N and KN editions are sold in Europe and Korea without Windows Media Player and without the media technologies that sit underneath it, which is why an ordinary AAC file can fail on an otherwise healthy machine.

Open Settings > System > About and read the Edition line. If it ends in N, that is your answer. The fix is Microsoft's own: Settings > System > Optional features > Add an optional feature, then search for Media Feature Pack and install it. Reboot afterwards. Nothing else on this page is needed if that was the cause.

On a normal edition of Windows 11 you may simply not have the old player installed. The modern Media Player app replaced Groove Music and is the default; Windows Media Player Legacy is now an optional feature in that same Optional features list. The two are separate programs with separate quirks, so it is worth trying the file in both before concluding anything.

Why the error message tells you nothing

Windows Media Player cannot play the file. The Player might not support the file type or might not support the codec that was used to compress the file.

That sentence covers every case in the table above and several that are not. It is the reason so much of the advice on forums is guesswork: the person answering has no more information than you do. The modern Media Player app is barely better, reporting only that the item was encoded in an unsupported format. Identify the file first, then act. Guessing costs more time than checking.

Play it without converting anything

If this is a one-off file and nothing else needs it, do not convert at all.

• Microsoft Edge or Chrome. Drag the .m4a onto an empty tab. Both browsers carry their own AAC decoder on Windows, so the file plays with a seek bar and a volume control and no installation. The file is opened from your disk by the browser; it does not travel anywhere.
• VLC. It ships its own decoders inside the application rather than registering them across the system, so it handles ALAC, .m4b, .m4r and raw .aac without changing how anything else on the machine behaves.
• The Media Player app. Right-click the file, choose Open with, and pick it. It often succeeds where the legacy player fails.

Convert it once, if the file has somewhere else to go

Playing it is enough if you only need to listen. Converting is the right call when the file has to work in a car stereo, a transcription service, a dictation tool or a submission form whose menu only names MP3. MP3 is the format with the fewest arguments left in it.

The M4A to MP3 converter here is FFmpeg compiled to WebAssembly and it runs inside the page, so the file never leaves your computer. Choose MP3, leave the bitrate at 192 kbps for music or drop to 96 kbps mono for speech, and save the result.

Two things to be straight about. This conversion cannot be a stream copy: AAC is not legal inside an MP3 file, so the audio must be decoded and encoded again, which takes processing time roughly proportional to the length of the recording rather than a fingersnap. And a second lossy encode cannot bring back detail the AAC encoder already discarded — at 192 kbps and above almost nobody can hear the difference on one pass, and asking for 320 kbps on a 128 kbps source only produces a larger file. The full comparison is in M4A vs MP3. If you have a folder of these rather than one file, the batch routes are in converting M4A to MP3 on Windows 11.

Why "convert it to WMA" is the wrong direction

Microsoft's own community answers have suggested converting the file to WMA, because WMA is what Windows Media Player was built around. It does work, and it is still a poor trade. WMA is lossy, so you pay the same re-encoding cost you would pay for MP3 and end up with a file that plays on Windows and very little else. Phones, car head units, browsers, podcast hosts and transcription services all take MP3; a good many of them have never taken WMA. Converting to WMA solves this afternoon and creates the same problem again the first time the file has to leave the machine. If anything, the traffic runs the other way, which is why there is a WMA to MP3 converter on this site and no MP3 to WMA one.

If nothing will open it, including the converter

At that point the file itself is usually the problem rather than the software.

1. Check the size. A file of 0 KB, or a few kilobytes where you expected several megabytes, is a truncated download. Ask the sender again, or fetch it from the original link rather than a mail preview.
2. Check for a second extension with file name extensions turned on. note.m4a.txt will not open as audio anywhere.
3. Check whether it is protected. An .m4p, or an audiobook bought before stores dropped their protection, cannot be decoded by this site or by any other converter. That protection is deliberate and there is no way round it here.
4. Try one more player. If VLC also says the stream cannot be read, the file is damaged and no amount of converting will change that.