Convert M4V to MOV

MOV is the QuickTime File Format, published by Apple in 1991 and still the container Final Cut Pro, QuickTime Player and Compressor treat as native. M4V is the extension Apple attached to MPEG-4 video in 2005 for the iTunes Store and the devices around it. The two are not rivals from different camps; they are an ancestor and a descendant of the same design, since ISO based the MPEG-4 file format on QuickTime when it standardised it in 2001.

That is why this pair feels strange, and why the strangeness is worth naming rather than glossing. You are converting Apple video for Apple software, and the reason is almost never that the software cannot decode what is inside. It is that something in the chain reads the last four characters of the file name and stops there.

An application that plays a file and an application that imports one run different checks. QuickTime Player opens what you hand it and decodes what it finds. An import panel filters by extension first, and a file that fails that filter is greyed out before anything inside it is examined — which is how an ordinary H.264 file ends up looking unsupported to software that would have decoded it happily.

The other refusal is real rather than cosmetic, and it is HEVC combined with an older application version. Apple hardware has recorded and exported HEVC by default for years, and plenty of editing and presentation software from before that shift decodes H.264 and nothing newer. Converting fixes that case; renaming does not, and the difference between the two is the first thing worth establishing.

The MOV written here holds H.264 video and AAC audio. So, very often, did the M4V. This is the only pair in the M4V set where the codecs on both sides are the same by default, and the honest description of the operation is that every frame is decoded back to pixels and compressed again in order to change the box around it.

One generation of quality is spent doing that. On a talking-head recording or a screen capture it is not visible; on graded footage or fine text it is the sort of thing you notice on the second conversion rather than the first. Convert from the best copy you have, once, and keep the M4V — if a later timeline wants a different resolution, you want to be starting from the original rather than from this MOV.

In an edit suite "MOV" and "ProRes" are used almost interchangeably, and they are not the same thing. ProRes is Apple’s intermediate codec, licensed and reachable through Apple’s own tools; the encoders a web page can reach are the ones the operating system exposes through WebCodecs, which is H.264 and VP9 for video and nothing else.

The practical consequence sits on the timeline rather than in the player. H.264 describes most frames as changes to other frames, so scrubbing backwards costs the machine work in a way an all-intra codec does not. For a short insert that is irrelevant. For a long cut, treat this conversion as step one and transcode to ProRes inside the editor as step two, where the transcode is a menu item rather than a download.

MOV can carry an alpha channel, which is why animated lower-thirds and logo overlays are handed between editors as MOV files. The registry records that capability against the format, and it is one of the reasons MOV is asked for.

None of it arrives from an M4V. The M4V container was built around H.264 and HEVC, neither of which carries alpha in any form Apple’s delivery pipeline uses, and the H.264 written here has no alpha channel either. If you are converting because a template asks for "a MOV with transparency", this conversion cannot produce one and no setting changes that — the transparency has to come from whatever generated the graphic.

Apple-delivered video is more likely than most to carry chapter marks and an embedded subtitle track, because the Apple TV app and the iTunes-era library displayed both. Neither survives this conversion. What is written is picture and sound.

For a lecture series or a recorded conference that is a real loss and it has a workable answer: export the captions from the tool that produced them and keep them beside the MOV as a sidecar file, which every editor and media player will pick up. Doing that before the M4V is filed away is easier than reconstructing timings from a video afterwards.

M4V files skew long. An iTunes-era film, a recorded three-hour conference, a full course module — these are the files that carry the extension, and they run to gigabytes. The free tier here accepts up to 100 MB, and that limit rules out a large share of what people want to convert on this pair specifically.

It is a limit on the file rather than on the length of the queue, so the practical move is to trim first. Cutting the segment you actually need in QuickTime Player, which does that with a keyboard shortcut and no re-encode worth the name, and converting the segment, gets you a usable MOV in less total time than any route that involves sending four gigabytes anywhere.

The cost is proportional to running time and resolution rather than to the number of bytes, because every frame passes through a decoder and an encoder. A three-minute 1080p export is over quickly. A forty-minute 4K recording is a sustained load on your own machine, and the tab has to stay open while it runs — closing it cancels the work rather than queueing it somewhere.

The H.264 encoder doing that work belongs to the browser and the machine. Chrome, Edge and Safari have one on essentially every current Mac; some Firefox installations do not, and the conversion says so up front instead of failing halfway through. There is no software fallback, because an H.264 encoder compiled to WebAssembly is tens of megabytes and roughly an order of magnitude slower than the hardware one sitting idle beside it.

The decode, the encode and the muxing all happen inside the tab, using the codecs the machine already uses to play the file. Nothing carrying the video is sent anywhere, there is no account and there is no daily count. The network tab confirms it in the time one conversion takes.

On this pair that is a working constraint as often as a principle. The M4V files that reach an editor are client footage, unreleased product recordings, interviews under embargo and material somebody paid for — the category where uploading to a converter nobody has vetted is a contractual problem before it is a privacy one.