Convert M4A to WAV

M4A is a container and the registry lists two codecs inside it: AAC and ALAC. Which one you have decides whether this conversion is a compatibility step or an archival one, and it is the single most useful minute you can spend before converting anything.

Size answers it immediately. A four-minute AAC M4A is four to eight megabytes; the same track as Apple Lossless is twenty to thirty. On a Mac, Command-I on the file names the codec outright; in the Music app, adding a Kind column shows "Apple Lossless audio file" against "AAC audio file". If it is ALAC, the WAV you get is bit-for-bit the audio that went into the encoder, and this page's warnings about not restoring anything simply do not apply to you.

For the usual case — AAC — the honest statement is that decoding to WAV restores nothing. AAC works by permanently discarding parts of the recording the ear is least likely to notice. Those parts are not compressed, not hidden and not recoverable; they are absent. Writing the surviving samples out uncompressed produces a file five to ten times larger that sounds precisely the same, because it contains precisely the same audio.

That does not make the conversion pointless. It makes the reason for it something other than quality — and the real reasons are good ones, which the next two sections are about. It only becomes a mistake when someone converts an entire library to WAV in the belief that they are upgrading it, and deletes the M4As afterwards.

Some hosts refuse M4A outright. Many hardware samplers, grooveboxes, field recorders and DJ controllers read PCM off a card and contain no AAC decoder at all — the file is not rejected so much as invisible. Where a DAW does import an M4A, a good number of them quietly write a WAV into the project folder on import, which is this conversion happening without being asked for.

The other reason is behaviour rather than compatibility. A compressed file has to be decoded before it can be played, scrubbed or waveform-drawn, and a session with forty compressed clips in it is doing that work continuously. Uncompressed audio can be read straight off the disk at the byte offset the playhead is at, which is why scrubbing is instant and why studio workflows have used WAV since 1991 without seriously considering an alternative.

The second good reason is generational. Every time audio is exported back to a lossy format it is compressed again, and the losses accumulate — a clip that has been through five edit-and-export cycles as AAC is audibly worse than one that has been through one.

Working in WAV breaks that chain. Convert once, do the trimming, the level matching, the fades and the processing on uncompressed audio, and encode once at the end to whatever the delivery format is. The source is no better than it was, but it stops getting worse with each pass, which over a project of any length is the difference that shows.

Sixteen-bit stereo PCM at 44,100 Hz is 1,411 kilobits per second, which is 10.1 megabytes per minute. A four-minute track is about 40 MB, a 45-minute rehearsal recording is around 455 MB, and a two-hour interview is a little over 1.2 gigabytes. WAV offers no quality control because there is nothing to trade; that is what makes it a working format.

The 100 MB per-file ceiling here is the practical limit, and it corresponds to roughly ten minutes of stereo audio. For longer material, FLAC is the sensible target: it is lossless in exactly the same sense, typically compresses to half the size, and every audio editor made in the last fifteen years reads it. Reach for WAV specifically when a piece of software or hardware insists on it.

WAV metadata lives in a RIFF INFO chunk, and it is much smaller than what an M4A carries. Title, artist, album, track number, genre, date and comment map across. Album artist, disc number, description and lyrics have no INFO equivalent and are dropped, and so is embedded cover art — there is no picture field in the chunk at all.

There is a second, sharper limit worth knowing: RIFF INFO values are ISO 8859-1, so a title containing Japanese, Cyrillic, Greek or Devanagari characters cannot be represented and is left out rather than written as nonsense. For a session file none of this matters. For a music library it matters a great deal, and it is the strongest argument for FLAC over WAV as an archival target.

The registry records M4A as supporting up to 48 channels and WAV up to 18, so most surround material passes through intact — a 5.1 film soundtrack extracted as M4A converts to a six-channel WAV rather than being folded down, which is the outcome anyone doing post-production work wants.

The channel order is the thing to check on arrival. WAV files carry channel assignments in an extension chunk that not every program reads, and a six-channel file imported into a host that assumes a different order will put the centre channel somewhere unhelpful. Play the first few seconds through your monitoring before you build anything on top of it.

AAC encoders add priming samples at the start of a file and padding at the end, because the encoder works in blocks and a recording rarely ends on a block boundary. The M4A records how many samples to skip, so a player trims them and you never hear them.

That instruction has no home in a WAV, so the padding is written out as audio — typically a few dozen milliseconds of near-silence at each end. It is invisible in ordinary listening and it matters in two places: a sample that must trigger instantly, and material that has to line up against picture or against another take. Both are fixed by trimming to the first transient in the editor, which is a ten-second job once you know to look for it.

Every other audio target on this site needs an encoder, and two of them need a WebAssembly package downloaded before they can run. WAV needs neither. Your device already contains an AAC decoder — it is the one that plays the M4A when you double-click it — and a WAV is a RIFF header wrapped around the samples that come out of it, which is arithmetic rather than compression.

So this is the fastest conversion in the audio set and the one with the smallest footprint, and the file never leaves the tab. That is worth something concrete when the material is a client's unreleased stems, a rough vocal or a recording made under an agreement about where it may be stored. Open the network tab and convert something: you will see the page and the advertising that funds it, and nothing carrying your audio.