Converting AAC to WAV decodes the lossy audio back into uncompressed PCM. Nothing about the sound changes (what the AAC contained is what the WAV will contain), but every audio editor, plugin, and piece of hardware will now accept the file without needing an AAC decoder.
Drag & drop audio files here, or browse
Drop your AAC files here
Zero quality change. WAV files are 10–15× larger than AAC, so disk usage goes up, but the audio is identical to whatever the AAC decoded to. No encoder involved in this direction.
WAV is universally supported. Every audio application and every device with audio playback handles it.
AAC is the successor the MPEG group designed to replace MP3. At 128 kbps it typically sounds as good as MP3 at 192 kbps. It's the default codec for YouTube audio, iTunes purchases, Apple Music, and nearly every streaming service that isn't using Opus or Vorbis.
WAV is Microsoft and IBM's uncompressed PCM container. A stereo CD-quality recording takes about 10 MB per minute. Because nothing is thrown away and nothing is compressed, WAV is the universal working format for recording, editing, and mastering in every major DAW.
No. AAC is lossy; detail the encoder discarded is gone forever. The WAV stores the decoded audio uncompressed.
Yes, for a given AAC file. The AAC decoder is deterministic, so decoding the same file always produces the same PCM output.
AAC is the successor the MPEG group designed to replace MP3. At 128 kbps it typically sounds as good as MP3 at 192 kbps. It's the default codec for YouTube audio, iTunes purchases, Apple Music, and nearly every streaming service that isn't using Opus or Vorbis.
WAV is Microsoft and IBM's uncompressed PCM container. A stereo CD-quality recording takes about 10 MB per minute. Because nothing is thrown away and nothing is compressed, WAV is the universal working format for recording, editing, and mastering in every major DAW.
Yes. The converter runs entirely in your browser using FFmpeg compiled to WebAssembly. Your audio files are never uploaded, never sent to a server, and never leave your device.
There's no hard limit, but because everything runs in your browser you're bounded by available memory. Files over about 2 GB total can get slow or hit browser memory limits. Process in smaller batches if you run into issues.