MP4 vs MOV: What Actually Changes When You Convert

By Andrew Butson · July 2, 2026 · 6 min read

MP4 and MOV get compared constantly because they are, in a real sense, the same family: the MP4 standard was built directly on Apple's original QuickTime container design, and both commonly wrap identical video. The difference that matters is less about the box and more about who wrote the box, who expects it by name, and what happens when a file shot on one platform lands somewhere else.

This page covers what the containers actually hold, why an iPhone or Mac defaults to MOV in the first place, why a MOV sometimes refuses to play on Windows or Android, and what a MOV-to-MP4 conversion changes and does not change.

Same family, different name on the box

A container's job is just to hold and label tracks (video, audio, subtitles, metadata) so a player knows where each one starts; the codec inside does the actual compression. MP4 and MOV share almost the same design because MP4's ISO base media format was derived from Apple's QuickTime container, so at the structural level they are close cousins rather than rivals. That is why a video app can often read either format with the same code path, and why renaming a .mov to .mp4 sometimes appears to work: the wrapper is similar enough that some lenient players do not look closely at the extension at all.

What genuinely determines whether a file plays is the codec inside, not which of these two boxes it is sitting in. A MOV carrying ordinary H.264 video and AAC audio is, for playback purposes, nearly indistinguishable from an MP4 carrying the same streams. The meaningful differences between MP4 and MOV are less about capability and more about reputation: which one a given device, app or upload form was built to expect by name.

Why your iPhone shoots MOV, not MP4

MOV is the format an iPhone camera and a Mac's screen recorder write by default because it is Apple's own container, tuned to Apple's own pipeline. Recording straight to a flexible container built in-house lets Apple bundle in extras a general-purpose MP4 workflow rarely bothers with — accurate timecode tracks, particular metadata fields, and compatibility with editing tools like Final Cut Pro that expect QuickTime's structure. None of that is exotic: the video itself is very often plain H.264, and on recent iPhones increasingly HEVC, the same codecs a freshly created MP4 would use.

That is also why a MOV recorded on an iPhone frequently just plays when you air-drop it to a Mac, open it in Photos, or drop it into iMovie: the whole chain, from capture to playback, was designed around this one container. The friction only shows up once the file leaves that chain.

Why a MOV sometimes won't play on Windows or Android

Two different problems get lumped together under "MOV doesn't work," and they have different fixes. The first is a container problem: some upload widgets and older software look at the .mov extension and refuse it outright, even though the H.264 video sitting inside would play perfectly well if it were simply relabelled MP4. The second, more genuine problem is a codec problem — recent iPhones often record in HEVC (H.265) for its better compression, and plenty of Windows PCs, Android phones and browsers still lack a working HEVC decoder, especially without extra codec packs installed. Repackaging that file as an MP4 does not fix a missing HEVC decoder; it fixes the first problem but not the second.

In short: an H.264 source needs little more than a container change; an HEVC source that a device cannot decode needs the video itself re-encoded into H.264, which is unavoidably slower.

What converting MOV to MP4 actually does

Because Morphr runs entirely in your browser rather than on a server, it treats every MOV the same way for safety: it decodes the video and re-encodes it fresh as H.264 in an MP4 wrapper, using a sensible, fixed quality setting (libx264 at CRF 23), rather than gambling on whether the source codec can simply be re-labelled. That is a genuine transcode, not a quick remux — it is unavoidably slower on a long or high-resolution clip, since the whole file has to be decoded and re-encoded rather than just relabelled, but it also means the result is guaranteed to be an ordinary H.264 MP4 that plays almost anywhere, HEVC source or not.

The honest trade-off is that a real re-encode is a fresh generation of lossy compression on top of whatever the source already had, and it takes real time on a large file rather than finishing instantly. For everyday clips the quality loss at CRF 23 is not something you would notice; for footage you intend to edit further, it is worth keeping the original MOV as your master rather than repeatedly round-tripping it through conversions.

Frequently asked questions

Is MOV basically the same as MP4?

Structurally, very nearly — MP4's container format was derived from Apple's QuickTime, and both frequently carry identical H.264 or HEVC video with AAC audio. The practical difference is less about capability and more about which devices and services expect which name.

Why won't my iPhone video play on my Windows PC?

Usually because the video is encoded in HEVC (H.265) rather than H.264, and the PC lacks a working HEVC decoder. Converting to MP4 with H.264 video, which is what a genuine transcode does, resolves it — simply renaming the file to .mp4 will not, if the codec inside is the actual problem.

Does converting MOV to MP4 lose quality?

A little, yes, because a proper conversion decodes the video and re-encodes it fresh — a real generation of lossy compression, not a free repackage. Morphr uses a sensible default quality setting that keeps everyday footage looking clean; for editing masters, keep the original MOV.

Can I convert MP4 back to MOV?

Morphr currently converts MOV to MP4 rather than the reverse, since that is by far the more common need — getting an iPhone or Mac recording ready to play anywhere. There is rarely a reason to convert the other way, since an ordinary MP4 already opens fine on Apple devices.