M4A to WAV: When and Why
to Convert Apple Audio

Why Convert M4A to WAV?

M4A works well for listening — it's compact, sounds good, and plays on every Apple device. But when you move beyond playback into editing, production, or distribution, you'll encounter situations where WAV is required or strongly preferred.

Audio editing and DAW compatibility

Most professional digital audio workstations — Pro Tools, Logic Pro, Ableton Live, Reaper, Audacity — handle WAV natively as their primary format. While many modern DAWs can import M4A, some workflows break down with compressed audio:

• Waveform editing: WAV displays sample-accurate waveforms immediately. M4A must be decoded first, and some editors create temporary WAV copies behind the scenes anyway.
• Plugin processing: audio plugins operate on PCM data. Starting with WAV eliminates the decode step, reducing CPU overhead in large sessions with 50–100+ tracks.
• Non-destructive editing: WAV supports precise sample-level cuts. M4A's frame-based structure can introduce tiny gaps or encoder padding at edit points.

Video production

WAV is the universal audio format for video editing. Premiere Pro, DaVinci Resolve, Final Cut Pro, and After Effects all treat WAV as the standard timeline audio format. When you import audio for a video project, WAV ensures frame-accurate sync and avoids the overhead of real-time AAC decoding during preview playback.

CD burning

The Red Book CD-Audio standard requires 16-bit, 44.1 kHz PCM audio. WAV is PCM in a container — it's exactly what CD burning software needs. While some burning apps can accept M4A and decode on the fly, providing WAV eliminates a potential source of errors and ensures the disc matches your intended quality.

Professional tool requirements

Broadcast, podcast hosting platforms, and sound design libraries often mandate WAV submissions. Professional contexts value WAV's simplicity, universal compatibility, and the guarantee that no lossy compression has been applied (assuming a lossless source). If your submission guidelines say "WAV only," there's no workaround.

Hardware compatibility

Some older or specialized hardware — standalone CD players, certain DJ controllers, church sound systems, medical dictation devices — cannot decode M4A (AAC). WAV, being uncompressed PCM, is readable by virtually every device that plays digital audio.

The Important Caveat: Lossy Is Irreversible

This is the single most important thing to understand about M4A-to-WAV conversion. Lossy compression is a one-way street. When the AAC encoder created your M4A file, it permanently discarded audio data that it deemed inaudible based on psychoacoustic models. That data is gone — no conversion tool, no software, and no AI upscaler can bring it back.

Converting AAC M4A to WAV is like printing a JPEG photo at poster size: the pixels don't become sharper. The poster is bigger, but the image quality is exactly what the JPEG contained.

This means converting M4A (AAC) to WAV makes sense only when you need the format, not when you want better quality. If your DAW requires WAV, convert. If you're hoping for audiophile sound from an iTunes purchase, you won't get it — the AAC encoding already set the quality ceiling.

The exception: M4A with ALAC

Here's where it gets interesting. M4A is a container — it can hold two very different codecs:

• AAC (Advanced Audio Coding): lossy. Used by iTunes Store purchases, Apple Music downloads (unless you have lossless enabled), and Voice Memos.
• ALAC (Apple Lossless Audio Codec): lossless. Used by Apple Music Lossless tier and CD rips made with Apple's lossless setting.

If your M4A contains ALAC, converting to WAV preserves every single sample perfectly. No data is lost because ALAC, like FLAC, is mathematically lossless — it compresses without discarding anything. In this case, the WAV output is bit-for-bit identical to what was originally recorded.

How to Tell AAC vs ALAC in Your M4A Files

The file extension .m4a doesn't tell you which codec is inside. You need to check the actual audio stream. Here are the most reliable methods:

Using ffprobe (command line)

Run ffprobe yourfile.m4a and look for the codec name in the output:

• AAC: you'll see Audio: aac with a bitrate (e.g., 256 kbps)
• ALAC: you'll see Audio: alac with a much higher bitrate (typically 800–1,400 kbps)

Using MediaInfo

Open the file in MediaInfo (free, available on all platforms). The "Audio" section shows the codec as either AAC LC (lossy) or ALAC (lossless).

Quick rules of thumb

Bit Depth Options When Converting

When converting M4A to WAV, you'll choose a bit depth. The right choice depends on your source material:

• 16-bit (recommended for most users): the CD standard. If your M4A source is AAC (lossy), 16-bit WAV is the logical choice — the source audio doesn't have more than 16-bit resolution to begin with. AAC typically works with audio equivalent to 16-bit quality, so storing it in 24-bit WAV just wastes space.
• 24-bit: choose this only if your M4A source is ALAC from a hi-res recording (24-bit/48 kHz or higher). In this case, 24-bit WAV preserves the full resolution of the original recording. If the source is standard ALAC from a CD rip (16-bit/44.1 kHz), 16-bit WAV is sufficient.

File Size Comparison

WAV files are dramatically larger than M4A because they store audio uncompressed. Here's what to expect:

A typical 4-minute song goes from ~7.5 MB as M4A to ~40 MB as 16-bit WAV — over 5× larger. For a 60-minute album, that's the difference between ~112 MB and over 600 MB. Make sure you have the storage space before batch-converting a large music library.

The size increase is identical whether your M4A source is AAC or ALAC — WAV output size depends only on duration, sample rate, bit depth, and channel count, not on the source codec.

Alternative: Convert to FLAC Instead

Before committing to WAV, consider whether FLAC (Free Lossless Audio Codec) might be the better choice for your situation.

FLAC advantages over WAV

• 40–60% smaller: FLAC uses lossless compression, so a 40 MB WAV file typically becomes 16–24 MB as FLAC — with zero quality loss.
• Rich metadata: FLAC supports album art, artist/title/album tags, track numbers, and custom fields. WAV metadata support is limited and inconsistent across software.
• Error detection: FLAC includes MD5 checksums for integrity verification. WAV has no built-in error detection.
• Wide compatibility: supported by VLC, foobar2000, Winamp, most Android players, many car stereos, and all major streaming platforms for upload.

When WAV is still the right choice

• DAW requirements: some DAWs (especially older versions of Pro Tools) work best with WAV.
• CD burning: Red Book audio CD requires PCM — WAV is the native format.
• Legacy hardware: devices that can't decode FLAC.
• Broadcast submission: many broadcast standards mandate WAV specifically.
• Maximum compatibility: WAV is understood by literally every audio tool ever made.

If your goal is archiving or general lossless storage, FLAC saves significant disk space while preserving identical audio quality. If your goal is editing in a DAW, burning a CD, or meeting a specific format requirement, WAV is the right tool for the job.