How to Convert WAV to AAC

A WAV stores audio uncompressed: every sample of the waveform, exactly as recorded, with nothing thrown away.^[1] That gives perfect fidelity and enormous files, often around ten megabytes per minute of stereo. It is the right format for recording and editing, but a poor fit for a phone, a music library, or anything you want to send over a network.

Converting WAV to AAC compresses that audio into a small file using a lossy codec designed to sound transparent. AAC, Advanced Audio Coding, is the default in the Apple ecosystem and is supported almost everywhere, so this is the standard way to take a studio-grade recording and make it practical to carry and share.^[3] Because your starting point is uncompressed, this is close to the best-case scenario for a lossy encode: the encoder receives the full, undamaged waveform and only has to make one clean set of decisions.

Uncompressed to compressed

The key point is that this conversion goes from lossless to lossy. A WAV keeps everything; AAC deliberately throws some of it away. AAC works by discarding parts of the sound that human hearing is least likely to notice, then packing what remains far more tightly than a WAV ever could. The result is typically a small fraction of the original size, often around a tenth or less, with a difference from the source that most people cannot hear at a sensible bitrate.

AAC is a modern codec and generally sounds better than older MP3 at the same bitrate, which is a large part of why it became the standard for streaming and Apple devices. Moving your WAV to AAC keeps the listening experience essentially the same for most people while making the file small enough to live comfortably on a phone or stream over a mobile connection. The one thing to hold onto is that the discarded detail is gone for good, so the AAC is a copy for use, not a replacement for your master.

Two formats, two philosophies

WAV and AAC embody opposite ideas about what an audio file should be. WAV is a container built on Microsoft's Resource Interchange File Format. Inside it, a short header records the sample rate, bit depth, and channel count, and a data chunk holds the raw PCM samples one after another, exactly as they were captured.^[2] There is no encoding step between the numbers and the file, which makes WAV trivial to read and edit but impossible to shrink without changing the format. Its whole design goal is fidelity and simplicity, not size.

AAC takes the opposite stance: its entire purpose is to represent audio in as few bits as possible while sounding the same to a human listener. It is a perceptual codec, meaning it is built around a model of human hearing rather than around preserving the literal waveform. It was standardized as part of the MPEG family and adopted as the default audio codec for the MPEG-4 world, the iTunes Store, and a long list of streaming services, which is why it is so ubiquitous on modern hardware.^[4] Converting between the two is therefore not a simple repackaging like some format changes; it is a genuine transformation from a literal record of the sound into a compact perceptual approximation of it.

How AAC encoding works

Understanding the encode explains why bitrate is the control that matters. The AAC encoder takes the PCM samples from the WAV and processes them in short overlapping windows. For each window it applies a modified discrete cosine transform, converting the slice of waveform from the time domain into a set of frequency coefficients. It then consults a psychoacoustic model, which predicts what the ear will and will not perceive: it identifies frequencies masked by louder nearby tones, and ranges where hearing is naturally insensitive, and marks those as candidates for coarse treatment.

Armed with that model, the encoder quantizes the frequency coefficients, spending many bits where the ear is sensitive and few or none where it is not. This quantization is exactly where data is discarded and where all the quality loss happens. Finally the quantized data is entropy-coded and written into the AAC bitstream. The bitrate you choose sets the overall budget for this process: a higher bitrate lets the encoder quantize less aggressively and keep more detail, while a lower one forces harder choices and eventually audible artifacts. Everything about tuning an AAC comes down to giving that budget the right size for the material.

Why AAC over MP3

AAC was designed as a direct successor to MP3 and improves on it in several concrete ways: a higher-resolution filter bank, better handling of sharp transients, and more flexible stereo coding. In practice that means AAC usually sounds slightly better than MP3 at the same bitrate, or equally good at a lower one, so you can often step down a notch and save space with no perceived loss. It is also the native format across Apple Music, iPhones, iPads, and many car systems, which makes it the path of least resistance if that is where your audio will live. Choose MP3 instead only when you specifically need to feed an old player or a tool that accepts nothing else.

Convert WAV to AAC, step by step

1. Open the converter and add your WAV

   Open the FileFormer audio converter and drop your WAV in. The conversion runs on your device, so the recording is never uploaded.

2. Choose AAC as the output

   Select AAC. Your uncompressed audio will be re-encoded into a compact, lossy AAC file.

3. Pick a bitrate

   Set the bitrate to match your needs: 256 kbps for excellent, near-transparent quality, or 128 kbps for the smallest file that still sounds fine on most gear.

4. Convert and download

   Export the AAC and listen back. If you hear anything you do not like, convert again from the WAV at a higher bitrate.

Choosing a bitrate

Bitrate is the single control that decides both the size and the sound of your AAC. The higher it is, the more of the original detail survives and the larger the file. The relationship is close to linear and easy to reason about: bitrate is literally the number of kilobits used per second of audio, so a 256 kbps file is twice the size of a 128 kbps one of the same length, and a rough estimate of the final size is the bitrate multiplied by the duration. A four-minute song at 256 kbps lands around seven or eight megabytes, against roughly forty megabytes for the same track as a WAV. That order-of-magnitude saving, with almost no audible cost, is the whole reason this conversion is so common. These are sensible starting points.

Real-world scenarios and settings

The right bitrate depends on both the content and where the AAC will be heard. A few common cases:

AAC, M4A, and the container question

A common source of confusion is the difference between the AAC codec and the file that carries it. AAC audio is most often stored inside an MP4-family container, and when a file holds only AAC audio it usually carries the .m4a extension, while a raw AAC stream sometimes uses .aac. All of these hold the same underlying AAC audio; only the wrapper differs. So if your converter produces an .m4a file when you asked for AAC, that is entirely normal and expected, and the file will play anywhere AAC is supported. There is nothing to fix, and no quality difference between the wrappers.

When to keep the WAV

Because AAC is lossy, keep the WAV if you are still recording, mixing, or mastering. Each time you edit and re-export a lossy file you lose a little more, so your working master should stay in WAV, or in a lossless format like FLAC if you want the same fidelity in less space. Make the AAC only when the audio is finished and you want a copy to listen to or distribute. Think of the AAC as the print and the WAV as the negative: you make prints freely, but you never throw away the negative.

If you specifically need the smallest, most universally recognized music file rather than the best-sounding one, converting to MP3 is another common route, though AAC generally sounds better byte for byte. If you want an open, royalty-free format for a game or open-source project, WAV to OGG is the better fit. For archiving, leave the WAV alone.

Common mistakes to avoid

A few recurring errors turn an easy conversion into a disappointing one. The first is converting from an already-compressed source when the WAV is available. Taking an old MP3, decoding it, and re-encoding it as AAC stacks the AAC's loss on top of the MP3's, and the compounded artifacts can be clearly worse than either format alone. Since the whole point of starting from a WAV is that the encoder gets clean input, feeding it anything lossier throws that advantage away.

The second is chasing an unnecessarily high bitrate. Because AAC is efficient, 256 kbps is already transparent for almost everyone, and pushing much higher mostly inflates the file without a benefit anyone can hear. If size is not a concern at all, the honest answer is to keep the lossless WAV or a FLAC rather than a very large AAC that is still lossy. The third mistake is deleting the WAV once the AAC exists. The AAC is a one-way, lossy derivative, so if you discard the master you can never regenerate a higher-quality or different-format version from full-quality source again. Keep the WAV (or a FLAC of it), and treat every AAC as a copy you can remake at will.