Converting M4A to WAV decodes the AAC audio inside the MP4 container to raw PCM samples. Every DAW, plugin, and piece of audio hardware reads WAV natively, so this is the standard first step for editing M4A recordings.
Drag & drop audio files here, or browse
Drop your M4A files here
No audio change in either direction. The WAV contains exactly what the M4A decoded to. File size grows 10–15× because nothing is compressed anymore.
WAV works on every audio device and every audio application ever built.
M4A is an MPEG-4 container that almost always holds AAC audio (though it can hold ALAC too). The payload is identical to what's inside an .aac file; the difference is that M4A carries proper tags, chapter markers, and cover art. iTunes, Apple Music, and iOS write M4A by default.
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.
Depends on your DAW. Logic, Pro Tools, Reaper, and Audacity all handle M4A natively. Older or more specialized tools may insist on WAV, hence this conversion.
No. M4A is lossy. The WAV stores whatever the AAC decoder produced, at the same perceived quality as the original M4A.
M4A is an MPEG-4 container that almost always holds AAC audio (though it can hold ALAC too). The payload is identical to what's inside an .aac file; the difference is that M4A carries proper tags, chapter markers, and cover art. iTunes, Apple Music, and iOS write M4A by default.
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.