How to Convert M4A to WAV

An M4A file is a container, usually holding audio that was compressed with AAC. That means the sound inside it has already been through lossy compression: some detail was discarded when the file was first made, and it is not coming back. A WAV file, by contrast, stores raw uncompressed audio samples with nothing thrown away.

Converting M4A to WAV therefore does not add quality. It decodes the compressed AAC audio back into plain samples and writes them out uncompressed. You end up with a much larger file that sounds exactly like the M4A did, no better. Knowing that up front keeps your expectations honest and points you to the one situation where this conversion is genuinely the right move. This guide walks through what an M4A really contains, what happens step by step during decoding, why the resulting file balloons in size, and how to pick sample rate and bit depth so the WAV drops cleanly into whatever tool needs it.

What an M4A actually holds

Most M4A files carry AAC audio, the same codec used by Apple Music downloads, iTunes purchases, and voice memos. M4A is not a codec at all; it is a file name given to audio-only content stored in the MPEG-4 container, the same ISO base media format that underpins the MP4 you use for video.^[1] Inside that container, the audio is almost always Advanced Audio Coding, and less often Apple Lossless (ALAC). AAC is efficient: it keeps files small by permanently removing sound the encoder judges you will not notice, using a perceptual model of human hearing to decide what can be discarded.^[2] That trade is fine for listening, but it means an AAC-based M4A is a finished, lossy product. Nothing you do to it later can recover the discarded information.

WAV is the opposite philosophy. Defined by Microsoft and IBM as a RIFF-based format, it writes every sample as it is, uncompressed linear PCM, which is why WAV files are big and why they are the standard working format for editing, mastering, and hardware that cannot decode AAC on its own.^[3] A WAV file is essentially a short header describing the audio (its sample rate, bit depth, and channel count) followed by a long, raw block of the samples themselves, one after another with no compression scheme in between.

M4A and WAV: two opposite philosophies

The two formats represent the two fundamental strategies for storing digital audio. M4A, carrying AAC, is a perceptual, lossy format: it starts from the raw waveform, transforms short windows of it into the frequency domain, and then spends bits only where the ear is sensitive, throwing away detail that a psychoacoustic model predicts you cannot hear. The result is a file often one tenth the size of the original at a quality most listeners cannot distinguish. This is why AAC became the default for streaming and downloads.

WAV takes the opposite stance: store everything, compress nothing. It holds pulse-code-modulated samples exactly as they came off the analog-to-digital converter, so there is no encoding model, no quality setting, and no perceptual guesswork. That makes WAV the natural interchange format between audio tools, because every editor, every operating system, and most embedded devices can read raw PCM without needing a codec.^[4] The cost is size and the fact that WAV alone offers no way to shrink a file. When you convert M4A to WAV, you are moving from the compact, finished world of perceptual coding into the bulky, editable world of raw samples, and every consequence of the conversion flows from that single shift.

How the conversion works under the hood

The conversion is a decode, not a re-encode, and understanding the pipeline explains why it neither improves nor further degrades the audio. First the converter parses the MPEG-4 container, locating the audio track and reading its metadata: how many channels, what sample rate, and which codec produced the stream. Then it decodes the AAC frames back into linear PCM samples. AAC decoding reverses the encoder's work as faithfully as it can, reconstructing a waveform from the stored frequency-domain data, but it can only rebuild what the encoder kept. Whatever the perceptual model discarded stays gone; the decoder simply produces the best approximation the compressed data allows.

Finally the converter writes those PCM samples into a WAV wrapper, prepending the RIFF header that describes the format and then dumping the sample block verbatim. Because this final step is lossless (it just copies samples into a new container) the WAV is an exact record of what the AAC decoder produced. No quality is added, because there is nothing to add back, and no quality is lost, because raw PCM storage discards nothing. The audio you hear from the WAV is bit-for-bit the same audio the M4A would have played.

Why convert to WAV at all

The honest use case is compatibility and editing, not fidelity. Some audio editors, digital audio workstations, and older or embedded devices expect plain WAV and choke on M4A. Converting gives them a file they can read and process sample by sample. If you plan to cut, layer, or apply effects and then export to a delivery format anyway, working from a WAV avoids repeatedly decoding the same compressed source, and it prevents a subtle problem called generation loss, where re-encoding a lossy file each time you save slowly erodes quality. A WAV is a stable, lossless working copy that you can edit as many times as you like before exporting once at the end.

If your goal is just to play the audio, converting to WAV buys you nothing and costs you a lot of disk space. In that case, leave the M4A alone or, if you need broader playback support, convert to MP3 instead, which stays small.

Convert M4A to WAV, step by step

1. Open the converter and add your M4A

   Open the FileFormer audio converter and drop your M4A in. The file is processed on your own device and never uploaded.

2. Choose WAV as the output

   Select WAV. For most work, 44.1 kHz and 16-bit matches CD quality and is a safe default. Only raise these if a project explicitly requires it.

3. Convert and download

   Run the conversion and save the WAV. Expect the file to be several times larger than the M4A, because it is now uncompressed.

Sample rate and bit depth

WAV output has two settings worth understanding. Sample rate is how many audio snapshots are stored per second, and bit depth is how finely each snapshot is measured. Raising them above what the source contains does not recover lost quality; it only makes the file bigger.

Why the file grows so much

The most striking thing about the conversion is the size increase, and it is entirely predictable from arithmetic. Uncompressed PCM has a fixed data rate: sample rate multiplied by bit depth multiplied by channel count. Standard CD-quality stereo runs at 44,100 samples per second, sixteen bits each, across two channels, which works out to roughly 1.4 megabits per second, or about 10 megabytes per minute of audio.^[3] An AAC-based M4A of the same minute might occupy only 1 to 2 megabytes, because AAC typically compresses to a fraction of the raw size while sounding nearly identical.

That means a WAV is commonly five to ten times larger than the M4A it came from, and the ratio grows if you raise the sample rate or bit depth. There is no way around this: WAV stores every sample in full, so its size is a direct function of the audio's duration and format, not of how simple or complex the sound is. A minute of silence and a minute of a full orchestra produce WAV files of exactly the same size, which surprises people used to the way lossy formats shrink quiet passages.

Real-world scenarios and the right settings

The right output depends on why you need the WAV in the first place. A few common cases:

Common mistakes and fidelity limits

The single most common mistake is expecting a WAV to sound better than its M4A source. It cannot. Because the AAC data was already stripped of inaudible detail, decoding it to PCM recovers exactly what is there and nothing more. Choosing 24-bit or 96 kHz output does not restore lost quality; it only pads each already-final sample with extra precision it does not carry, producing a larger file that sounds identical.

The second mistake is resampling unnecessarily. If your M4A is 44.1 kHz and you export a 48 kHz WAV, the converter has to interpolate new samples, a process that can introduce tiny artifacts and always adds a processing step. Unless a target project demands a specific rate, keep the WAV at the source's native sample rate. The third pitfall is channel handling: if you collapse a stereo M4A to mono to save space, you permanently lose the stereo image, so only do it when the destination genuinely wants mono, such as a phone-line recording or a speech model.

WAV versus AIFF, FLAC, and MP3

WAV is not the only destination, and often not the best one. AIFF is Apple's uncompressed equivalent: it also stores raw PCM at the same size as WAV, differing mainly in byte order and metadata handling. If your workflow is entirely on macOS, AIFF is an equally valid target with no quality difference.

FLAC is the choice when you want a lossless file that is not enormous. FLAC compresses PCM without discarding a single sample, typically cutting the size by 40 to 60 percent, so a FLAC of the decoded audio is bit-for-bit identical to the WAV but far more storage-friendly. For archiving or moving lossless audio around, FLAC beats WAV on every axis except raw compatibility with very old tools. If you only need broad playback and small size, MP3 remains the universal option, though converting a lossy M4A to a lossy MP3 stacks one round of perceptual loss on another and is best avoided when a lossless path is available. The honest summary is that WAV earns its place specifically when a tool demands raw PCM; for storage, FLAC is smarter, and for casual playback, the original M4A is already fine.