Convert M4V to WAV

Nobody converts to WAV in order to listen. The file is many times larger than the M4V’s soundtrack and sounds no different; it exists because something downstream has said, explicitly or by refusing everything else, that it wants uncompressed PCM. With an Apple source that is usually one of four destinations: a DAW, Audacity, a podcast edit assembled from a filmed talk, or a speech model.

All four are doing further work on the samples, and all four would rather start from something that has not been through a second lossy encoder. That is the honest case for this pair — not that the audio gets better, but that nothing else is taken away between here and the finished cut.

There is no resampler anywhere in this path. The conversion decodes the AAC and writes the samples out at the rate they came in at, so the WAV inherits the M4V’s rate exactly rather than being normalised to anything.

On Apple-sourced material that matters more than usual, because the sources split. Files from the iTunes era and much music-derived material are 44.1 kHz; cameras, screen recordings and Final Cut exports are almost always 48 kHz. Drop a 44.1 kHz WAV into a session running at 48 and it either plays fast and sharp or gets resampled by whatever conversion the host does quietly. Look at the rate in the import dialogue before the edit rather than after it.

The WAV is 16-bit PCM in a RIFF WAVE container — the format Microsoft published in 1991 and the one every audio tool reads without argument. Sixteen bits is the depth that matches what came in: the source was lossy AAC decoded to floating point, and storing more precision would preserve the decoder’s own rounding rather than any part of the recording.

Sessions that specify 24-bit are specifying it for recording, where the extra headroom protects against clipping a signal that has not been captured yet. Importing a 16-bit file into a 24-bit session is routine and costs nothing; a host promotes it on load. What would cost something is converting up here and pretending the extra bits carry information.

An M4V is a delivery encode. It came out of Final Cut, Compressor, iMovie or a course platform’s exporter, which means somewhere upstream there was a timeline with the original audio still sitting on it, uncompressed and untouched.

Going back for that beats anything this page can do. The audio in the M4V has already been through one lossy pass, and no amount of PCM afterwards recovers it. Use this conversion when the M4V is genuinely all there is — a file somebody sent you, a download, an archive of a project that no longer opens — and go to the project when the project is still there.

A WAV as written here holds exactly one audio track. Whichever track the M4V lists first is the one that comes out, and every other one is discarded without a warning. On a phone recording that is a non-issue; on Apple-delivered video it is a live risk, because a distributed film, a bilingual course or a conference recording frequently has more than one.

VLC will tell you what is in the file in a few seconds — its Audio menu lists the tracks by name and language. That is worth doing before an hour-long conversion, because discovering the wrong track after the edit has begun is expensive in a way discovering it beforehand is not.

QuickTime Player can export audio from a video on its own, and what it writes is an M4A: the same AAC, in a smaller container, still compressed. For putting a talk on a phone that is the better route and it needs no browser at all.

It is the wrong route into an editor. A DAW handed an M4A decodes it on import and the samples are the same ones this conversion produces, but any export back out compounds a compression pass this page skipped. Choosing WAV is choosing where the decode happens, which is the sort of decision that only matters if something else is going to happen to the file.

Uncompressed audio costs a fixed number of bytes per second regardless of what is in it, so a long recording turns into a large file with no variation and no surprises. The M4V’s soundtrack was a small fraction of its size; the WAV is not.

The limit that actually stops people is on the other side. The free tier accepts input files up to 100 MB, and long-form M4V material is routinely a great deal more than that. Trimming the section you need in QuickTime Player first — a keyboard shortcut, no meaningful re-encode — is faster than any route that involves moving gigabytes anywhere, and it is usually what you wanted to edit in the first place.

The common workflow on this pair is a round trip: pull the sound out, level it or clean it in an editor, then lay it back under the video. Nothing here changes the running order or the length of the audio, so the WAV lines up with the M4V it came from at the start.

Check the sync at the end of the file rather than the beginning, because that is where any accumulated drift shows and it is where a mismatched sample rate announces itself unmistakably. If the last minute is out and the first is fine, the rate is the thing to look at, not the edit.

The decode and the write both happen inside the browser tab on your own processor, so nothing carrying the video is transmitted and there is no account. On this pair that is a practical argument as much as a principled one: a WAV of a long recording is large, and uploading a video to receive a larger file back is the slowest possible way to do the job.

It also settles a question this pair raises more often than most. The M4V files that end up in an editor are interviews, depositions, client recordings and unreleased material, and handing those to an unfamiliar converter is the sort of thing that is fine until once it is not.