Convert MP4 to MOV

MP4 was standardised in 2001 directly from Apple’s QuickTime file format, and the two share most of their structure. Final Cut Pro, iMovie, QuickTime Player, Photos and Motion all read MP4 without complaint, and have for years.

So the first useful thing this page can do is ask what actually went wrong. If an application refused the file, the problem is frequently the codec rather than the container — HEVC in an older application, or an unusual audio format — and changing the wrapper will not fix it. If a workflow document specifies MOV because it was written in 2011, it is worth asking whether anyone has tested MP4 since.

Older applications and plug-ins that predate broad MP4 support and check the extension rather than the contents. Workflows built around ProRes, where every asset in a project is expected to be a MOV. Anything needing an alpha channel, which MOV carries and MP4 in practice does not. And multi-camera work using timecode tracks, which live in MOV.

Those are real, and they are a smaller set than the volume of people converting suggests. If none applies, the MP4 will work and this conversion is a step nobody needs — which matters here more than usual, for the reason in the next section.

The two containers are close enough that a tool could in principle lift the streams out of one and drop them into the other untouched. That is not what happens here: the video is decoded and encoded again, which means some detail is given up even at the highest quality setting.

It is stated plainly rather than buried because it changes the advice. A conversion that costs nothing can be done casually; one that costs a generation of quality should be done when it is needed. Convert once, from the best copy you have, and keep the original — not from a file that has already been through a conversion or two.

Since the video is being encoded anyway, the settings are worth using rather than accepting. The balanced setting is right for footage that will be watched; the highest is worth the size for anything going into an edit, where the file will be cut, graded and encoded again afterwards.

Resolution is the other control, and it only ever goes down. Keeping the original size is the default and the right choice for editing. Reducing it is useful when the destination is smaller than the source — a 4K recording bound for a 1080p timeline — because doing it once here is better than asking the editor to scale every frame.

This is the misunderstanding worth heading off. ProRes is an editing codec — very large, very fast to scrub, designed to be decoded a frame at a time — and it is what people usually mean when they say a project needs MOV files.

Changing the container does not change the codec, and encoding a compressed source into ProRes gains nothing: the file becomes many times larger while containing exactly the detail the MP4 already had. If a project genuinely needs ProRes, it needs it from the camera or the master, not from a delivery file.

Subtitle tracks and chapter markers are not carried over, and neither are most container-level extras — tags, and anything an application wrote into the file for its own purposes.

The video, the audio and the timing all do. For footage going into an edit that is everything that matters, but it is worth checking a file that came from a distributor or a delivery platform rather than a camera, since those are where embedded subtitles and chapters tend to live.

Most traffic between these two formats runs the other way: an iPhone records MOV, and people convert it to MP4 so the rest of the world will accept it. Converting *to* MOV usually means feeding a Mac editing workflow rather than solving a compatibility problem.

Worth knowing in that direction too: recent iPhones record HEVC by default, and HEVC in a MOV is refused by more software than H.264 in one. Setting the camera to "Most Compatible" records H.264 instead, which removes a class of problem at the source rather than after the fact.

The conversion runs inside the browser tab on your own processor. A five-gigabyte file is read from disk rather than sent anywhere, so there is no upload to sit through before the work begins and no download afterwards.

On any hosted converter the transfer is the slow part — usually far slower than the conversion itself — which makes doing this in the browser a bigger practical difference for video than for images. There is also no queue, no account and no daily allowance.