Convert WAV to M4A — Free Online Tool
Convert WAV audio files to M4A format using AAC encoding, shrinking large uncompressed PCM audio into a compact, iTunes-compatible file without sacrificing perceptible quality. This tool runs entirely in your browser — no uploads, no servers, just instant WAV-to-M4A conversion powered by FFmpeg.wasm.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your WAV file here
or click to browse
Free — no uploads, no signups. Your files never leave your browser.
Settings
Note: Browser-based encoding uses approximate quality targets. For precise CRF compression, copy the FFmpeg command above and run it on your desktop.
Estimated output:
Conversion Complete!
DownloadHow It Works
WAV files typically contain raw, uncompressed PCM audio (most commonly 16-bit signed little-endian, or pcm_s16le), which means every sample is stored without any compression — resulting in large file sizes. During this conversion, FFmpeg decodes the raw PCM audio stream and re-encodes it using the AAC (Advanced Audio Coding) codec at 128kbps, then wraps the result in an MPEG-4 audio container (.m4a). This is a lossy transcoding process: the audio is mathematically compressed by discarding frequencies that are statistically less perceptible to human hearing. The -vn flag ensures no video stream is accidentally written to the output, which is important because some WAV files can carry metadata that FFmpeg might otherwise try to handle as a video stream. The result is a file typically 85–95% smaller than the original WAV, optimized for playback on Apple devices, iTunes, streaming platforms, and most modern media players.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg program, the open-source multimedia processing engine that handles decoding the WAV input and encoding the M4A output. In this browser tool, FFmpeg runs as a WebAssembly binary (FFmpeg.wasm) without any server involvement. |
-i input.wav
|
Specifies the input file — your WAV source audio. FFmpeg auto-detects the WAV container and the internal PCM codec (typically pcm_s16le), then prepares the raw audio samples for re-encoding into AAC. |
-c:a aac
|
Tells FFmpeg to encode the audio stream using the AAC (Advanced Audio Coding) codec, which is the standard lossy audio format for M4A files and the native codec for Apple iTunes, Apple Music, and iOS/macOS media playback. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second, a widely accepted balance between file size and audio quality for music and voice content. Increasing this to 192k or 256k improves fidelity; decreasing to 96k or 64k further reduces file size at the cost of quality. |
-vn
|
Explicitly disables any video stream in the output, ensuring a clean audio-only M4A file. This is a required flag for M4A output and acts as a safeguard in case FFmpeg detects embedded artwork or metadata in the WAV source that it might otherwise attempt to mux as a video stream. |
output.m4a
|
Defines the output filename and container format. The .m4a extension signals to FFmpeg to wrap the AAC-encoded audio in an MPEG-4 audio container, producing a file compatible with iTunes, Apple devices, and most modern media players. |
Common Use Cases
- Preparing finished music recordings or mixes exported from a DAW as WAV for distribution on iTunes, Apple Music, or podcast platforms that expect AAC-encoded M4A files.
- Reducing the storage footprint of large WAV archives — such as voice memo collections or field recordings — while keeping them playable on iPhones and iPads without format conversion on-device.
- Converting WAV audio exported from video editing software (like Final Cut Pro or DaVinci Resolve) into M4A for use in Apple-ecosystem projects where AAC is the native audio format.
- Sending audio files over email or messaging apps where WAV file sizes (often 50–200MB for a few minutes) exceed attachment limits, by compressing them to much smaller M4A files.
- Producing audiobook chapters or podcast episodes from uncompressed WAV recordings, taking advantage of M4A's native chapter support for chapter-marked delivery to podcast apps.
- Converting WAV samples or sound effects from audio libraries into M4A for use in iOS or macOS app development, where AAC is the preferred and hardware-accelerated audio format.
Frequently Asked Questions
Yes — this conversion is lossy. Your WAV file contains uncompressed PCM audio, and encoding it to AAC at 128kbps discards some audio data that the codec deems perceptually insignificant. For most music, podcasts, and voice recordings, the difference is inaudible to most listeners. However, if you plan to re-edit or further process the audio after conversion, it's best to keep the original WAV and only produce the M4A as a final delivery format, since repeated lossy re-encoding degrades quality further.
WAV files store audio as raw, uncompressed PCM samples — a 3-minute stereo WAV at CD quality (44.1kHz, 16-bit) is roughly 30MB. AAC at 128kbps compresses audio using perceptual coding, discarding frequencies the human ear is least sensitive to, and stores only what's needed to reconstruct a convincing approximation. The same 3-minute track encoded as AAC in an M4A container typically comes out around 2.9MB — about a 10:1 reduction. The -b:a 128k flag in the FFmpeg command directly controls this tradeoff between file size and audio fidelity.
M4A can also contain lossless audio using the FLAC codec, but this tool uses AAC by default, which is lossy. WAV can carry uncompressed audio up to 32-bit float and high sample rates like 96kHz or 192kHz, preserving every sample perfectly. When converting to AAC in M4A, that extended dynamic range and resolution is traded for compression efficiency. If you need to preserve the full lossless quality in an M4A container, you would need to change the codec to FLAC using -c:a flac in the FFmpeg command.
It depends on whether your WAV file contains metadata tags. WAV supports metadata via INFO chunks or ID3 tags, but support is inconsistent across applications. FFmpeg will attempt to map any recognized WAV metadata to the equivalent iTunes-style tags in the M4A container (such as title, artist, and album). However, artwork embedded in WAV is often not transferred. You may want to verify and re-embed metadata after conversion using a tag editor like MusicBrainz Picard or iTunes itself.
The -b:a 128k flag sets the AAC encoding bitrate. You can change 128k to any supported value: 64k for smaller files with noticeable quality loss (suitable for voice), 192k or 256k for higher fidelity music, or 320k for the highest quality AAC. For example, to encode at 256kbps you would run: ffmpeg -i input.wav -c:a aac -b:a 256k -vn output.m4a. Note that AAC at 256k is generally considered transparent (indistinguishable from the source) for most listeners.
The single-file command shown here processes one file at a time, but on your desktop you can use a shell loop to batch process. On Linux or macOS, run: for f in *.wav; do ffmpeg -i "$f" -c:a aac -b:a 128k -vn "${f%.wav}.m4a"; done. On Windows Command Prompt, use: for %f in (*.wav) do ffmpeg -i "%f" -c:a aac -b:a 128k -vn "%~nf.m4a". This is one reason the tool displays the raw FFmpeg command — files over 1GB or large batch jobs are better handled locally.
Technical Notes
WAV is one of the few formats that can contain a wide variety of audio codecs beyond PCM, including ADPCM, A-law, mu-law, and even compressed formats like FLAC — but the vast majority of WAV files encountered in practice use pcm_s16le (16-bit signed little-endian PCM), which is what this tool is optimized for. The AAC encoder used here is FFmpeg's native aac encoder, which produces compliant MPEG-4 AAC-LC (Low Complexity) audio — the most universally supported AAC profile across Apple devices, Android, web browsers, and streaming platforms. The -vn flag is included as a safeguard because FFmpeg may attempt to pass through non-audio streams if present in the source container. M4A is technically an MPEG-4 Part 14 container (.mp4) with an audio-only restriction signaled by the file extension; it supports iTunes-style metadata atoms (including artwork, lyrics, and gapless playback markers) and chapter markers, though chapter data cannot be sourced from a WAV input. One known limitation: if your WAV file was recorded at a sample rate higher than 48kHz (e.g., 96kHz or 192kHz used in high-resolution audio production), FFmpeg's AAC encoder will accept these rates but the perceptual benefit over 44.1kHz or 48kHz is negligible in a lossy format. For files larger than 1GB — common with long-form uncompressed recordings at high sample rates — the displayed FFmpeg command is the recommended route, as browser-based processing of very large files may be constrained by available system memory.