Convert WAV to M4A

The most common misunderstanding about this pair is that M4A is a quality level. It is not; it is Apple’s file extension for an MPEG-4 container carrying sound and no pictures. The same container can hold AAC, which throws audio away to get small, or ALAC, which does not. The extension alone tells you nothing about which.

This converter writes AAC. That is the right default because AAC is what Apple’s own ecosystem produces and what every application that asks for an M4A is expecting to find, and because a lossless M4A is a large file people usually did not mean to make. If lossless is genuinely what you are after, convert the WAV to FLAC instead and keep the M4A for delivery.

Apple applications will generally play a WAV and then behave oddly around it — it imports without tags, sorts badly, syncs as an unusually large item, and in a music library it looks like a mistake next to everything else. The friction is not that WAV is unsupported; it is that nothing in the ecosystem is designed around a 40 MB song with no artist field.

Converting to M4A resolves that in one step. The file lands at a size the rest of the library shares, carries the metadata fields the interface expects to populate, and behaves like every other item next to it. That is a workflow fix rather than an audio one, and it is the honest reason most people make this conversion.

AAC was standardised in 1997 as the deliberate successor to MP3, with a longer transform window, better handling of transients and no obligation to stay compatible with a 1993 decoder. The practical result is that AAC at a given bitrate sounds like MP3 at a somewhat higher one, and the advantage widens as the bitrate falls.

At 256 kbps the two are hard to separate on most material. At 128 kbps the difference is easy to hear on cymbals, applause and reverb tails, which are the sounds a codec finds hardest. If your WAV is speech, neither codec will struggle at any sensible setting and the choice is purely about what the destination accepts.

The control offers small, balanced and high rather than a number of kilobits, because the right number is different for every codec and nobody should have to know that AAC at 160 is roughly MP3 at 192. The band is resolved into a bitrate by the encoder itself.

Balanced is the correct answer for almost every WAV that is going into a music library, and the small setting is a reasonable one for speech — an interview or narration survives it intact. Take the high band when the M4A will be edited, re-encoded or used as a delivery master, because every additional encode after this one starts from whatever this one produced.

A WAV is a first encode, and that is the advantage you have here that most people converting to M4A do not. Every artefact in the result will have been introduced exactly once, by an encoder working from complete information.

The corollary is worth planning around. If you need an M4A for the library, an MP3 for a car and a small version for a website, make all three from this WAV rather than making the small one from the M4A. Each conversion between two lossy formats compounds what the previous one discarded, and the WAV is the only copy that still holds everything.

A great many WAVs are stereo files carrying one microphone duplicated across both channels — the standard output of a phone, a conference tool or a single-source interview rig. Encoding that as stereo spends the bitrate saying the same thing twice.

AAC handles this better than older codecs do, because it stores what the channels have in common once rather than encoding two near-identical signals, so the waste is smaller than the arithmetic suggests. It is still waste. Where the source is genuinely one voice, the small band produces a file that sounds the same as the balanced one and is roughly half the size.

Chrome, Edge and Safari expose an AAC encoder through WebCodecs, so on those browsers the conversion uses the same encoder the operating system already uses and downloads nothing extra. Firefox has no AAC encoder at all, and there a WebAssembly build is fetched the first time you convert to an AAC target.

That fallback is loaded per format pair rather than per page, which is why converting a WAV to FLAC on this site downloads none of it. It also means the first M4A conversion in a Firefox session is slower to start than the second, and nothing after that is.

Every file dropped here is capped at 100 MB, and WAV is the format most likely to meet that ceiling because its size follows only its length: 176,400 bytes a second at CD quality, about 10 MB a minute, regardless of content. That works out at a little under ten minutes of stereo per file.

It is a generous cap for a song and a tight one for a lecture. If the WAV is longer, split it in an editor before converting, or convert with a desktop tool — the limitation is the browser tab holding the whole file in memory, not a plan you can upgrade.

Drop a whole folder and each WAV becomes its own M4A, returned together as a ZIP, up to a hundred files at a time. Nothing is uploaded, so the batch waits in no queue and costs no bandwidth.

It does cost processor time, and AAC encoding is fast enough that a folder of songs finishes in the time it takes to read this. A folder of hour-long recordings is a different proposition, and those will be over the per-file ceiling anyway.