M4A to WAV: How to Convert and Why

M4A files are everywhere on Apple devices and in many cross-platform audio workflows. Every iPhone voice memo is an M4A. iTunes purchases are M4A. Recordings made in GarageBand export as M4A by default. Apple Music offline downloads are M4A. The format works fine for playback, but it hits a wall the moment you need to edit the audio, process it with plugins, import it into a DAW or video editor, or hand it off to a system that expects uncompressed PCM. That is why every audio professional ends up converting M4A to WAV at some point.

This guide explains the format relationship, every legitimate reason to convert, the quality limitations you cannot escape, the file size math, the exact workflow on Windows and Mac, podcast-specific guidance, batch conversion tips, troubleshooting for the common issues, and a fast browser-based way to do the conversion without uploading your files anywhere.

What Is M4A?

M4A is not a codec — it is a container format. Specifically, it is an MPEG-4 container (the same type used for .mp4 video files) that holds audio only. The audio inside is almost always AAC (Advanced Audio Coding), which is a lossy compression codec. In rare cases an M4A file contains Apple Lossless (ALAC) audio, but unless you ripped a CD into iTunes with Apple Lossless explicitly enabled, your M4A is AAC.

So when someone says \"M4A file,\" they mean: an MPEG-4 container wrapping AAC-encoded audio. The .m4a extension was introduced by Apple to distinguish audio-only MPEG-4 files from video-carrying .mp4 files. Renaming an .mp4 file to .m4a has no effect on the contents — only the system hint about what's inside.

AAC inside M4A is typically encoded at:

• Voice memos on iPhone: 32–128 kbps, mono or stereo, 44.1 kHz
• iTunes purchases: 256 kbps AAC, stereo, 44.1 kHz
• Apple Music downloads (offline): 256 kbps AAC
• GarageBand exports: variable, typically 128–256 kbps
• Logic Pro exports: AAC up to 320 kbps or Apple Lossless if selected

What Is WAV?

WAV (Waveform Audio File Format) is an uncompressed audio format. It stores raw PCM (Pulse Code Modulation) samples — no codec, no compression, no data discarded. Every sample from the original recording survives intact.

WAV files are large, but they are universally accepted by audio software, video editors, and broadcast systems. WAV is the lingua franca of professional audio. The format was developed jointly by IBM and Microsoft in 1991 and has been a stable standard ever since, which is why ancient industrial systems and brand-new mastering plugins both speak WAV without any negotiation.

Reasons to Convert M4A to WAV

Working in a DAW. Digital audio workstations such as Logic Pro, Ableton Live, Reaper, Pro Tools, and FL Studio all work natively with WAV. While most DAWs technically accept M4A, working with uncompressed WAV eliminates decompression overhead, avoids any codec compatibility issues, and lets you scrub and edit without latency from on-the-fly decoding. For a clean, trouble-free session, WAV is always the right starting point. Pro Tools in particular has historically been picky about non-WAV imports.

Video editing. If you are importing an M4A voice memo or recording into a video editing project, WAV at 48 kHz is the standard format. Premiere Pro, DaVinci Resolve, and Final Cut Pro all handle WAV without any preprocessing. M4A imports sometimes trigger transcoding steps that slow down the timeline, and some plugins refuse to operate on AAC sources directly.

Archiving voice memos. iPhone voice memos are M4A files in your iCloud. Converting them to WAV creates a lossless container copy (at the AAC quality ceiling) stored in a universally readable format that does not depend on Apple's ecosystem. If you ever need to share an interview, a lecture recording, or a legal deposition with someone outside the Apple world, having a WAV copy in your archive is much safer than only the M4A.

Software compatibility. Some older audio software, industrial systems, telephony equipment, broadcast automation, and embedded devices do not support M4A. WAV is a 30-year-old format with essentially universal support — if a device plays digital audio at all, it almost certainly plays WAV.

Processing with plugins. When you apply noise reduction, EQ, dynamic range compression, or normalization to an M4A file, some processing chains are cleaner when working with PCM data rather than decompressing AAC mid-chain. Some specialized restoration software (iZotope RX, Adobe Audition Spectral) explicitly recommends a WAV source for best results.

Forensic and transcription work. Legal and law-enforcement workflows for evidence handling typically require WAV. So do many transcription services and accuracy-critical speech-to-text pipelines.

The Critical Quality Caveat

This is the most important thing to understand: converting M4A to WAV does not improve audio quality.

The AAC codec inside your M4A file is lossy. It discarded audio data when the original encoding happened — frequencies it judged inaudible, low-amplitude content masked by louder sounds, certain stereo information. That data is permanently gone. Converting to WAV creates a larger file — a lossless container — but the content inside is the decoded AAC audio, not a restored original.

You can think of it like this: if someone gave you a photocopy of a photograph and you scanned it at high resolution, you would have a large, high-resolution scan of a photocopy. The original photograph quality is not restored, just preserved at the photocopy's level.

Converting M4A to WAV is still useful for all the workflow reasons above — it is just not a quality upgrade. The WAV file will be 10–20x larger than the M4A but will sound identical to the M4A. If you need higher quality than your M4A offers, you must go back to whatever produced the M4A and re-export from the original source.

File Size Math: How Much Bigger Is WAV?

A few concrete numbers so you can plan storage:

• 3-minute iPhone voice memo at 64 kbps AAC — M4A: 1.4 MB → WAV (16-bit, 44.1 kHz, mono): 16 MB. About 11× larger.
• 4-minute iTunes purchase at 256 kbps AAC — M4A: 7.7 MB → WAV (16-bit, 44.1 kHz, stereo): 42 MB. About 5.5× larger.
• 1-hour podcast interview at 128 kbps AAC — M4A: 56 MB → WAV (16-bit, 44.1 kHz, stereo): 605 MB. About 11× larger.
• 30-minute lecture at 96 kbps AAC mono — M4A: 21 MB → WAV (16-bit, 44.1 kHz, mono): 152 MB. About 7× larger.

WAV file size in MB is roughly: (sample rate in kHz × bit depth × channels × seconds) / 8 / 1024. CD-quality stereo WAV is about 10 MB per minute. That number is invariant — it does not matter what the source M4A bitrate was. The decoded WAV is whatever the destination sample-rate and bit-depth settings produce.

How to Convert M4A to WAV with AudioUtils

Converting M4A to WAV with AudioUtils takes a few seconds and happens entirely in your browser:

1. Open the M4A to WAV converter in AudioUtils 2. Drop your M4A file onto the converter (or click to browse) 3. The conversion runs locally in WebAssembly — no upload, no server 4. Click download to save your WAV file

Your file never leaves your device. This matters for voice memos that may contain personal conversations, legal discussions, medical notes, or anything else you would not want uploaded to an unknown server. There is no account required and no file size cap that forces you to register.

M4A to WAV on Windows

Windows has multiple workable paths for M4A to WAV, but most of the built-in tools are awkward.

• Windows Media Player (legacy) never officially supported saving as WAV from M4A. You can play the M4A but not export it.
• The new Windows 11 Media Player can play M4A files but does not include a "save as WAV" export option.
• Groove Music is deprecated and not a conversion tool.
• Audacity (free, open source) can import M4A on Windows but requires the optional FFmpeg library to be installed — Audacity does not bundle FFmpeg directly because of licensing, so you have to grab it and point Audacity at the DLL. Once configured, File → Open → File → Export As WAV.
• ffmpeg directly in PowerShell or CMD: `ffmpeg -i input.m4a output.wav`. Reliable and scriptable, but requires installing ffmpeg.
• AudioUtils in any browser — no install, no FFmpeg setup, no upload. Drag your M4A onto the M4A to WAV converter and click download. This is the path the Microsoft community thread should have linked, and it is why we built the tool.

If you are working with hundreds of files on Windows, ffmpeg in a PowerShell loop is unbeatable for scripted batch conversion. For one-off or occasional jobs, the browser tool is faster end-to-end because there is no setup phase.

M4A to WAV on Mac

Mac users have more options because Apple ships AAC and WAV codecs in Core Audio.

• GarageBand / Logic Pro: Import the M4A as an audio region, then File → Export → Bounce → choose WAV. This re-encodes at your project's sample rate, which is handy if you need 48 kHz for video.
• QuickTime Player: Open the M4A, then File → Export → Audio Only (sometimes via the "Audio" menu after Edit). QuickTime's WAV export is fine for one file but not great for batch.
• Music.app (formerly iTunes): Preferences → Files → Import Settings → set the encoder to WAV Encoder, then right-click the track → Convert → Create WAV Version. This creates a sibling file in your library.
• Terminal with afconvert (built-in): `afconvert -f WAVE -d LEI16@44100 -c 2 input.m4a output.wav`. afconvert is shipped with macOS so no install needed.
• AudioUtils in Safari, Chrome, or Firefox — no need to fire up GarageBand for a single conversion. Drag the file in, get a WAV back.

For Logic Pro users specifically: bouncing through a Logic project lets you adjust sample rate, bit depth, and apply a master fade if needed — handy when you are exporting voice memos for a podcast at a different sample rate than the recording.

M4A to WAV for Podcasting

Podcast workflows almost always end up needing WAV at some stage. The common pattern:

1. Record in M4A on iPhone (Voice Memos) or whatever your remote interview app produces (Riverside, Zencastr, SquadCast often deliver M4A or MP3). 2. Convert M4A to WAV at 48 kHz, 16-bit stereo — 48 kHz because that's the broadcast standard and what most podcast hosts and DAWs expect. 3. Edit in your DAW (Logic, Hindenburg, Reaper, Audition) without codec friction. 4. Master and export to MP3 (typically 128–192 kbps) for distribution to listeners and to WAV for an archive copy.

The reason podcasters care about the M4A-to-WAV step specifically is that working from compressed AAC source through aggressive EQ, compression, and noise gating can sometimes accentuate codec artifacts (a "swishing" sound around sibilants). Working from WAV avoids that completely. Even if the source quality ceiling is set by the original AAC encoding, the editing chain doesn't add new compression artifacts.

M4A to WAV vs M4A to MP3: Which Should You Choose?

The right choice depends on what you need the output file for:

Choose WAV when:

• You are importing into a DAW or video editor
• You need maximum software compatibility
• You are processing the audio further (EQ, noise reduction, normalization)
• You are archiving for long-term preservation
• You need 48 kHz or higher sample rates for broadcast

Choose MP3 when:

• You want a smaller file for sharing or uploading
• You need to email the file or send it via a messaging app
• You are distributing the audio for playback (not editing)
• Storage space is a concern
• The destination is a podcast feed, a website, or a phone

If you go the MP3 route, converting M4A to MP3 at 192–256 kbps gives you a compact file with quality that matches or exceeds the original M4A AAC encoding for most practical purposes. AudioUtils has a dedicated M4A to MP3 converter for that path.

Sample Rate and Bit Depth in the Output

When AudioUtils converts your M4A to WAV, it decodes the AAC audio and writes it as uncompressed PCM. The output sample rate matches the source — if your iPhone voice memo was recorded at 44.1 kHz, the WAV output will be 44.1 kHz.

If you need 48 kHz for a video project (the broadcast standard), you can resample inside your NLE or DAW during import. Resampling from 44.1 to 48 kHz introduces a negligible quality difference for content that has already passed through AAC encoding — there is no audible benefit to resampling at the WAV stage vs the DAW stage.

Bit depth in the output is typically 16-bit PCM, which is identical to CD quality and more than the AAC source actually carries audible information about. Higher bit depths (24-bit, 32-bit float) are useful when you are recording fresh content or working with masters that have a wide dynamic range — for a converted M4A, they only inflate file size without adding audible quality.

Batch Converting Multiple M4A Files

AudioUtils handles batch conversion in the browser — you can queue up multiple M4A files in one session and convert them sequentially. For very large batches (hundreds of files), a scripted ffmpeg loop is faster:

• macOS / Linux: `for f in *.m4a; do ffmpeg -i "$f" "\${f%.m4a}.wav"; done`
• Windows PowerShell: `Get-ChildItem *.m4a | ForEach-Object { ffmpeg -i $_.Name ($_.BaseName + ".wav") }`

Both require ffmpeg installed. The browser tool stays fully private (nothing leaves your machine) and requires zero setup, which is why it's the right choice for any non-script workflow.

Troubleshooting Common Issues

\"The WAV file won't open in my DAW.\" Check the sample rate. Some legacy DAWs choke on 48 kHz WAVs in a 44.1 kHz session, or vice versa. AudioUtils preserves the source sample rate; resample inside the DAW on import to match the session.

\"The file plays but the duration looks wrong.\" This is almost always a corrupted or partial M4A source — if the input is truncated, the WAV output will be truncated too. Re-export the source M4A from its origin (Voice Memos, GarageBand, etc.) and retry.

\"The audio sounds the same as the M4A — did the conversion work?\" Yes. It is supposed to sound the same. Converting M4A to WAV doesn't improve quality — it just gives you uncompressed PCM in a universally compatible container. See the quality caveat section above.

\"My WAV is huge.\" That is expected. A 10-minute stereo WAV at 44.1 kHz is around 100 MB. If you need smaller files, convert to MP3 or AAC after editing instead of distributing WAV.

\"Where do my files go after browser conversion?\" AudioUtils runs entirely client-side. Your file is read into browser memory, transcoded with FFmpeg compiled to WebAssembly, and written back to a local download. Nothing is uploaded to AudioUtils servers or anywhere else.

Summary

M4A files are Apple AAC audio in an MPEG-4 container. WAV is uncompressed PCM. Converting between them is straightforward and gives you a file that works cleanly in any audio or video software. The quality ceiling stays where the original AAC encoding set it — the conversion is about workflow compatibility, not audio restoration. Use AudioUtils to do it in seconds, with your files staying entirely on your device, no upload, no signup, no install. For batch jobs and scripting, ffmpeg in a terminal is the alternative. For one-off conversions, particularly on Windows where built-in tools are weak, the browser is faster than any other option.