How to convert M4A to MP3 on Windows 11

They have M4A files on a Windows machine and discovered the OS has no way to convert them. The results they find are affiliate blogs pushing paid desktop software. Often they have a folder of them, not one — the Microsoft forum keeps asking specifically about bulk.

Windows 11 has no audio converter in it. There is no Convert to MP3 in the File Explorer right-click menu. The new Media Player app plays your file and, on current builds, rips an audio CD, but it will not convert a file you already have. Clipchamp can pull the audio out of a video, and then hands it back as an M4A — the format you are trying to leave. So you need something else, and the free options are genuinely good: convert it in a browser tab with nothing installed, use VLC's Media > Convert / Save if you already have it, or install FFmpeg with one winget command and do an entire folder in a single line. All three are free, and none of them needs an account.

What none of them can do is get back what the AAC encoder inside the M4A already threw away. M4A to MP3 decodes one lossy format and re-compresses into another, so pick 192 kbps and stop worrying about it — see M4A vs MP3 if you want the detail.

The three routes, compared

Pick on the basis of how many files you have and whether you are allowed to install software on the machine.

Route 1: convert in the browser, nothing installed

The M4A to MP3 converter on this site runs FFmpeg compiled to WebAssembly inside the page. Your file is never sent anywhere — the encoder is in the tab, working on a file the browser reads off your own disk. That matters on a work laptop where you cannot install anything, and it matters if the recording is a client call or a medical appointment.

1. Open the converter and drag the .m4a onto it, or click to browse.
2. It reads the file's codec, length and bitrate first and tells you what it found.
3. Choose MP3, then a bitrate. 192 kbps is the default, and on a single pass most listeners cannot pick it out from the source. The ladder runs from 64 to 320, and if you ask for a higher bitrate than the M4A actually had, it says so — the extra bytes cannot put back detail the first encoder never kept.
4. Convert, then save the file where you want it.

Two honest caveats. The first visit downloads a 32 MB engine, which is cached for a year afterwards, so it is not the route to pick on a metered connection. And M4A to MP3 can never be a stream copy — the AAC inside has to be decoded and compressed again, which takes real processing time. Reckon on roughly a minute of work for every twenty-five minutes of audio, so a 90-minute meeting is a few minutes rather than a click.

Route 2: VLC's Convert / Save, step by step

VLC is on a lot of Windows machines already, and its converter is buried where nobody looks.

1. Open VLC and press Ctrl+R, or use Media > Convert / Save.
2. On the File tab click Add and pick your .m4a files.
3. Click the Convert / Save button at the bottom. It is a split button — click the words, not the arrow.
4. In Profile, choose Audio - MP3.
5. Click the settings icon beside the profile — its tooltip reads Edit selected profile — if you want to change the bitrate. The stock MP3 profile is 128 kbps unless you change it, which is lower than most people expect. The Audio codec tab is where the bitrate, channel count and sample rate live.
6. Under Destination, click Browse and type a filename that ends in .mp3.
7. Start. VLC shows progress on its own seek bar and plays nothing while it works.

The classic VLC mistake is the destination filename. VLC will not reliably add the extension for you, so if you type interview you can end up with a file that has no extension and that Windows will not associate with anything. Type the .mp3 yourself. The second mistake is leaving a video profile selected, which produces a file with a silent video track welded to it.

Doing a whole folder at once

This is the question the Microsoft community forums keep getting, and the answer depends on whether you will touch a command line.

Not VLC

VLC's Convert / Save dialog lets you add a dozen files, which makes it look like a batch tool. It is not a dependable one: the long-running complaint on VideoLAN's own forum is that a queue of inputs still points at a single destination, and people end up with one converted file rather than a dozen. Behaviour differs between builds, so if you try it, try it on two throwaway copies first and check that two files came out. For an actual folder, use one of the next two.

FFmpeg, one line

Windows 11 ships winget, so installing FFmpeg is one command in Terminal, then a restart of the terminal window so the new PATH is picked up:

winget install -e --id Gyan.FFmpeg

Close the terminal, open it again and run ffmpeg -version. If that comes back "not recognized", the package did not manage to set your PATH — a known and occasional failure — and you either sign out and back in, or add the bin folder holding ffmpeg.exe to PATH yourself. Then, in the folder holding the M4A files, from Command Prompt:

for %f in (*.m4a) do ffmpeg -i "%f" -c:a libmp3lame -q:a 2 "%~nf.mp3"

Or from PowerShell, which is what Terminal opens by default:

Get-ChildItem *.m4a | ForEach-Object { ffmpeg -i $_.FullName -c:a libmp3lame -q:a 2 "$($_.BaseName).mp3" }

-q:a 2 is LAME's VBR quality 2, which averages somewhere around 190 kbps and spends the bits where they are needed. Swap it for -b:a 192k if you specifically need a fixed bitrate — some older car head units and voice-transcription pipelines are happier with CBR. If you put the Command Prompt version into a .bat file, double the percent signs: %%f and %%~nf.

fre:ac or foobar2000

If you want batch conversion with a window rather than a prompt, fre:ac is free and open source and bundles the LAME encoder, so it converts a dropped folder without further setup. foobar2000 converts through a right-click on a selection, and needs its free encoder pack installed before MP3 appears as an output.

Route 3: the Media Player Legacy burn-and-rip trick

Windows 11 still carries the old player under Windows Media Player Legacy — search the Start menu, and if it is not there add it from Settings > System > Optional features. It cannot open an M4A and save it as an MP3. What it can do is burn an audio CD and rip one — the new Media Player app rips but does not burn — and for twenty years people have chained those two together:

1. Set the rip format first: Organize > Options > Rip Music, set Format to MP3 and push the audio quality slider up.
2. Drag the M4A files to the Burn tab, set the burn options to Audio CD, and burn them to a blank disc.
3. Put the disc back in and rip it from the Rip tab.

It works, and it is a bad idea. It needs an optical drive, a blank disc and the legacy player willing to play your M4A in the first place, and most machines sold since about 2015 have no drive at all. A disc holds about 80 minutes, so a folder becomes several discs. An audio CD is 44.1 kHz 16-bit stereo by definition, so anything the source had above that is resampled away. Every tag — title, artist, album — is thrown out at the burn and guessed back from an online database at the rip, or not guessed at all. The one thing it does not cost you is an extra lossy generation, since what sits on the disc is uncompressed: the chain is the same AAC-then-MP3 as any other route here. Use it only if the machine is locked down so hard that both the browser and an installer are off the table.

Why the paid desktop converters keep outranking this

Search for this and the first page is mostly affiliate reviews of paid desktop software that wraps the same open-source encoders you can get for nothing. That is not a conspiracy, it is just that a product with a commission attached can afford to buy content and a free command line cannot.

The free web converters have their own catch, which is that "free" has a shape rather than a price: a cap on how large a single file may be, a count of how many jobs you get in a day, and a queue that lengthens when the servers are busy. Those numbers get changed without notice, so do not trust a figure quoted in a blog post, including a figure quoted about a competitor. What free audio converters actually limit goes through the shapes. A converter that runs in your own tab has a different limit: nothing we impose, and a ceiling set by the browser's own address space, which tops out near 2 GB. Audio rarely gets close — three hours at 128 kbps is about 170 MB.

If Windows will not play the file at all

A separate problem with the same cause. If double-clicking the M4A gives you an error rather than sound, the fix is usually not a converter — Windows 11 decodes AAC perfectly well, and the culprit is the file association or the legacy player. That is covered in M4A will not play in Windows Media Player.

Two files genuinely will not convert, on any route on this page. An .m4p from the old iTunes Store carries DRM and will not open — not with these tools, and not with the paid ones that claim otherwise. And a zero-byte or truncated file, usually the result of an interrupted transfer or a cloud folder that never finished syncing, has nothing in it to convert; check the size in File Explorer before you blame the software.