Convert M4A to WAV
FFmpeg Online — Run FFmpegin Your Browser
Convert your M4A file to WAV right in your browser. Nothing is uploaded, nothing is installed, and your files never leave your device.
Convert, compress, trim, and process video & audio locally. Files never leave your device. No signup. The real FFmpeg.- 100% private — nothing is uploaded
- Free, no account
- Real FFmpeg — any command runs
Convert M4A to WAV — tool
Loading the tool…
What this does
This tool converts M4A files to WAV in your browser. It runs the real FFmpeg, compiled to WebAssembly, right inside your browser — nothing is installed, no account is needed, and your files are never uploaded to a server. Add a M4A file, press Run, and download the WAV — the output matches what you would get from FFmpeg on the command line.
About the formats
M4A is AAC audio in an MP4 file — what Apple Music and Voice Memos use.
The result is uncompressed 16-bit PCM WAV.
The FFmpeg command
This is the exact command the tool runs for you. Copy it to run the same conversion with FFmpeg on your own machine.
ffmpeg -i input.m4a -vn -c:a pcm_s16le output.wav Same commands. No limits.
Test in your browser free — run at scale on Rendi's FFmpeg API. n8n, Zapier & Make integrations.





Frequently asked
Is it really private?
Yes. FFmpeg runs entirely in your browser via WebAssembly. Your files are never uploaded, streamed, or seen by any server — including ours.
What's the file size limit?
Around 2 GB, and it's a browser limit rather than ours. WebAssembly can only address so much memory, so the whole job has to fit in the tab. Lightweight operations that copy streams instead of re-encoding (trimming, remuxing, stripping the audio track) work on files right up near that ceiling, because the file is read in place instead of being copied into memory. Full re-encodes need room for the input, the output, and working memory at once, so their practical ceiling is lower — lower still on phones. For anything bigger, the exact same command runs with no size limit on the Rendi API.
Does it work on my phone?
Yes. It's a web page, so it opens in Safari or Chrome on a phone the same way it does on a laptop: nothing to install, and your files still never leave the device. The layout is built for touch, and the Run button stays pinned to the bottom of the screen while you work. What changes on a phone is memory — there's much less of it, so the size limits are halved: the tool stops at files over about 1 GB, and it refuses re-encodes over 500 MB instead of letting the tab crash mid-run. Trimming, remuxing and extracting audio stay cheap, so those are the jobs a phone handles best. For a long video or a heavy encode, send the same command to the Rendi API; that works from a phone just as well.