WAV is a thin container around uncompressed PCM samples, which is why a three minute song weighs thirty megabytes. M4A is an MPEG-4 container holding AAC audio, which is what a voice memo and a music store purchase both are. ffmpeg sits between the two, and this page says exactly what happens to a WAV file on the way to becoming an M4A one.
What runs when a WAV file becomes M4A
ffmpeg held to a single thread, on a machine we rent and watch. Your WAV file is uploaded once, ffmpeg runs once, the M4A comes back, and neither file is kept. WAV to M4A is one of the 3649 pairs that engine was probed on with a real file, which is why it has a page here and why the pairs the probe could not prove do not.
What survives from the WAV into the M4A
The running time and the channel layout. A stereo WAV comes back as a stereo M4A of the same length: this is a re-encode, not an edit, and nothing here normalises, trims or boosts the WAV.
The whole of the WAV, start to end. M4A is a lossy encoding, but it encodes all of the WAV rather than a shortened or quieter version of it, and the loudness you hear is the loudness you sent.
What WAV to M4A costs you
Exactness, once and for good. The WAV holds every sample; M4A keeps what its model believes you can hear and discards the rest. Going back from M4A to WAV later rebuilds the file size and none of the sound, which is the single most common misunderstanding about this pair.
Album art, where the WAV carried any. ffmpeg passes -vn on every audio target here, which counts an embedded cover as a video stream and drops it along with the film it was never part of. That is deliberate rather than careless: keeping it makes the mux fail outright on several audio containers, and hiding the choice would be lying by omission.
Any hope of M4A sounding better than the WAV. Nothing in this pass adds information, and a bitrate higher than the WAV deserved only makes a larger file of the same recording.
If a model is going to read the M4A
An M4A file is a waveform, and a language model reads text, so handing an assistant this M4A directly gets you nothing. The M4A becomes useful the moment somebody turns the sound into words, and that is a separate job with its own page here. WAV to M4A is the step before it: get the sound out of the WAV in a container the transcriber accepts, then hand the model a transcript instead of a file it cannot open.
Running WAV to M4A against the real engine with a real file, ffmpeg wrote 27,633 bytes of M4A in 0.2 seconds, machine otherwise idle. That is one WAV file on one day and not an average, which is why the number is given together with the file that produced it.
The WAV to M4A verdict was reached by ffprobe, meaning the container was actually demultiplexed, recognised under the right name, and carried at least one stream. Which check was used matters, because they do not all prove the same thing, and a status code of 200 proves nothing whatsoever about whether the M4A file has anything inside it.
The same WAV file, sent somewhere else
Other outputs the probe measured out of a WAV file, so the cost of choosing M4A can be read against something. Sizes do not compare across engines, because each family was probed with its own WAV witness file.
WAV to MP3: 24,468 bytes in 0.2 seconds, verified by ffprobe.
WAV to FLAC: 44,337 bytes in 0.1 seconds, verified by ffprobe.
WAV to OGG: 8,670 bytes in 0.1 seconds, verified by ffprobe.
WAV to OPUS: 27,591 bytes in 0.2 seconds, verified by ffprobe.
WAV to AAC: 27,219 bytes in 0.2 seconds, verified by ffprobe.
WAV to WMA: 54,944 bytes in 0.1 seconds, verified by ffprobe.
Other ways into M4A, and what they measured
Among the published routes into M4A, WAV is the number 15 largest output of the 16 measured. The witness files differ, so this ranks the probe run and not your document.
WEBM to M4A: 27,734 bytes in 0.2 seconds.
WMA to M4A: 27,998 bytes in 0.1 seconds.
WMV to M4A: 27,998 bytes in 0.1 seconds.
MP4 to M4A: 27,723 bytes in 0.2 seconds.
MP3 to M4A: 27,630 bytes in 0.2 seconds.
What we will not pretend about WAV to M4A
A WAV file over 150 MB is refused before the upload finishes rather than after it, so you do not wait for a rejection.
A WAV to M4A run that passes 240 seconds is killed, and the ffmpeg process is killed with it. A run left behind would sit on one of the machine's two cores until somebody noticed.
The WAV file behind the measurement on this page was a 3 second sine wave at 440 hertz, built by ffmpeg for the probe itself. That is why WAV to M4A came out at 0.2 seconds, and it is not what your file will do. The measurement proves the pair works and says almost nothing about how long yours will take.
WAV to M4A costs half a credit per conversion, whatever the length of the WAV. That is the same as an image or a document here, and it is a measurement rather than a gesture: an audio target on this engine is done in under two seconds, where a video target can take minutes.
A WAV longer than 60 minutes is refused before encoding. ffprobe measures the WAV first and answers with a refusal, rather than starting a job the 240 second guard would kill halfway to the M4A.
WAV to M4A waits at the audio door, which is 2 slots wide and gives up after 5 seconds rather than making you wait twenty times the length of the work. Until the 30th there was one door for everything, and a single video transcode starved every audio conversion for its whole duration: an M4A that needed less than a second was answered with a refusal after twenty.
Nothing here reads what is inside the WAV. No transcription, no scene detection, no summary: WAV to M4A is a container and codec operation, and the M4A says exactly what the WAV said, in a different wrapper. The sound is the whole payload.
One WAV file at a time, chosen in the browser. There is nothing else to set up and nothing else on offer.
WAV to M4A: what people ask
What actually converts my WAV file to M4A?
ffmpeg does it, held to a single thread, on a machine we rent and watch. Not a browser trick and not somebody else service: the WAV file is uploaded once, ffmpeg runs once, the M4A comes back, and neither file is kept afterwards.
How long does WAV to M4A take?
The probe measured 0.2 seconds for 27,633 bytes of M4A, on a 3 second file. An audio target scales far better than a video one: three minutes of source through this engine takes under a second, because only the sound is encoded. Past 240 seconds any run is stopped, and an audio one does not get close.
What do I lose going from WAV to M4A?
The one to know about first: Exactness, once and for good. The WAV holds every sample; M4A keeps what its model believes you can hear and discards the rest. Going back from M4A to WAV later rebuilds the file size and none of the sound, which is the single most common misunderstanding about this pair.
Will the M4A sound better than the WAV?
No. Nothing in this pass adds information to the WAV, so the M4A is at best an exact carry of what you sent and at worst one more lossy pass over it. Asking for a higher bitrate than the WAV deserved just makes a bigger file of the same recording.
Is WAV to M4A free?
There is a free allowance every month, and one WAV to M4A conversion costs half a credit against it however long the WAV runs. An audio target is charged per conversion and not per minute, because the engine encodes three minutes of sound in well under a second.