Skip to main content
Live Photo Tools

Practical guide

MOV vs MP4: containers, HEVC and H.264 explained

The filename extension tells you the container. It does not tell you which video codec is inside, and that difference decides where your video will actually play.

Updated September 5, 2026 · 7 minute read

Container versus codec

MOV and MP4 are containers: file formats that hold video, audio, timing information, and metadata in one package. HEVC (also called H.265) and H.264 (also called AVC) are codecs: the compression schemes that describe how the video frames themselves are stored.

The two axes are independent. A MOV file can contain H.264 video, and an MP4 file can contain HEVC video. That is why converting between containers does not always fix a compatibility problem: if the codec inside is the unsupported part, changing the wrapper changes little.

Mixing up the two layers is also why common folk remedies fail. Renaming a file from .mov to .mp4 changes the extension and nothing else; the streams inside, and their compatibility, are untouched.

What a widely compatible MP4 contains

When people say a video needs to be a compatible MP4, they usually mean H.264 video with AAC audio inside an MP4 container. MDN's codec support guide calls that combination broadly supported by every major browser, and it is equally at home in editors, messaging apps, smart TVs, and upload forms.

An MP4 that contains HEVC instead is perfectly legal by the format and common in the wild, since modern iPhones shoot HEVC by default. But support for playing it is conditional: it depends on the browser, the operating system, the hardware, and in some cases a separately installed extension.

Remuxing versus transcoding

  • Remuxing copies the existing video and audio streams into a different container without recompressing them. It is fast, loses no quality, and works even when the browser cannot decode the video, but it does not change HEVC into H.264.
  • Transcoding decodes the video and re-encodes it in a new codec. It is slower and technically re-compresses the picture, but it is the only path that turns an HEVC video into a universally playable H.264 one.
  • Choosing wrong is the classic conversion mistake: remuxing to MP4 feels like success, yet the file still fails on devices that lack HEVC support.

HEVC support in browsers today

The support picture, summarized from MDN's compatibility tables, is patchy by design. Safari has supported HEVC on recent macOS versions for years. Chrome's support depends on platform and hardware capability, Edge may require Microsoft's HEVC Video Extensions on Windows, and Firefox has been adding support across recent versions with its own conditions.

Browser builds differ even when the name is familiar, because some builds ship without licensed decoders. This is why assuming rather than checking is risky: two browsers on the same computer can disagree about the same file.

The audio codec counts too

Compatibility problems are not only about video. Our documented tests on a real iPhone Live Photo clip found HEVC video paired with uncompressed PCM audio, an audio format that few web players handle inside an MP4.

So a file can have a perfectly supported video track and still misbehave because of its audio. This is why the widely compatible target is a package deal: H.264 video and AAC audio together, and why the converter reports the audio codec in its result card rather than only the video one.

What the result labels mean

The converter marks every finished download with one of two badges. H.264/AAC Universal MP4 means the file was transcoded into the broadly supported combination and should play essentially anywhere. Source Codec MP4 means the original streams were preserved inside the MP4 container, which keeps quality intact but keeps the original codec requirements too.

Neither label is better in the abstract. The universal badge is what you want for sharing and uploads; the source-codec badge is what you want when maximum quality and Apple or VLC playback are enough.

Why devices shoot HEVC in the first place

HEVC exists because it stores video in less space than H.264 at similar quality, which is why Apple adopted it alongside HEIF images as the High Efficiency capture mode. Apple's support page describes the pair: HEIF for photos and HEVC for video, with older receiving devices automatically getting JPEG and H.264 versions when sharing needs it.

The space saving is real, and it is why camera makers keep choosing newer codecs. The trade-off shows up years later, when those efficient files meet older software that never learned the codec. Conversion is the bridge between the two worlds.

How this converter handles the mess

The converter inspects your file first, then tries the transcode to H.264 with AAC. If your browser cannot decode the source, it remuxes the original stream into an MP4 container and labels the result as a source-codec MP4 with an explanatory note rather than presenting it as universal.

Every output is re-parsed before the download button appears, requiring a real video track (and audio, when you kept it) in the finished file. That guard exists because conversion libraries can report success while silently discarding a track they cannot handle, as our own browser testing found.

If you want the step-by-step version for HEVC files specifically, the HEVC to MP4 guide covers what to expect in different browsers.

Frequently asked questions

Is MOV better than MP4?

Neither is better in general; they are containers. MP4 has broader support outside the Apple ecosystem, which is why converting a MOV to MP4 with H.264 video is the common compatibility fix.

Can an MP4 file contain HEVC video?

Yes. MP4 is a container and HEVC is a codec, so an MP4 can hold HEVC. The file will only play where HEVC decoding is available.

Do I lose quality when converting between MOV and MP4?

Not when the conversion is a remux, which copies the original streams unchanged. Quality only changes when the video is transcoded to a different codec such as H.264.

Why does my converted video still not play everywhere?

The file probably kept its HEVC codec inside the MP4 container. Check the codec label in the result card; for universal playback you need the H.264 version.

Can a MOV file contain HEVC video?

Yes, and it commonly does: iPhones recording in High Efficiency mode save HEVC video in MOV containers. The extension alone does not tell you the codec.

Sources