Why H.264, HEVC, VP9 and AV1 Decide Whether a Video Plays Directly

What decides whether a video plays directly is the codec the picture is stored with, not the extension in the file name. H.264 is the most widely handled codec today, so almost any device plays it straight away; HEVC (also called H.265) packs more efficiently, but whether it plays directly depends on your device and OS version; VP9 shows up in files that come from online video platforms; AV1 is newer still, and the list of devices that handle it directly keeps growing without being complete.

That is why two files both ending in .mp4 can behave differently: the container only describes the box, while the codec describes how the pictures inside were compressed. If the two layers are still blurry, container versus codec separates them first.

1. What each of the four codecs is for

H.264 has been around longest and is handled almost everywhere. It is not the most efficient of the group, and what it buys in return is that you rarely have to ask whether a device recognises it. Most cameras and the default export settings of most editors still produce it.

HEVC (H.265) aims at the same picture with less data, which is why it is common in high-resolution and 10-bit sources. The saving has a price: decoding takes more from the device, and older hardware may simply not have that support.

VP9 is built around saving bandwidth; the VP9 files you meet locally usually arrived as downloads or reorganised copies of online material.

AV1 is a later generation, more efficient again, and equally dependent on the device and OS handling it directly.

The newer the codec, the smaller the file tends to be — and the less certain it becomes how many devices can read it directly.

2. Why "more efficient" is not "plays everywhere"

To show a picture, a player has to turn compressed data back into frames. If the system already recognises that codec, it just does it; if it does not, a different path is needed, and that path depends on the device, the OS version and the way you are playing the file. So a video that plays on a recent television and fails on a computer from a few years ago is normal — the file is not damaged.

Two things are also unrelated to this: whether a file is an MP4, and whether it is intact. Telling those cases apart is covered in what to check first when a video will not open.

3. Even the same codec name hides further differences

Once the codec matches, other parameters keep influencing the result:

• Bit depth: 8-bit is the common case; 10-bit carries more information and tests device support harder.
• HDR metadata: when the picture has to be compressed again, colour and brightness information may not survive into the finished file.
• Frame rate: more frames per second means proportionally more data to handle, so waiting time grows.

"My device supports HEVC" therefore does not automatically mean "it supports 10-bit, HDR, high-frame-rate HEVC". Parameters are closer to the truth than names.

The codec name is only the first layer. Bit depth, HDR and frame rate decide whether this particular device really copes.

4. How to find out which codec your file uses

Read the file's media information rather than its name. Two lines matter: the video codec and the audio codec. Only with those can you tell whether the problem is the outer container or the content inside it.

The audio line is the one people skip, and it causes failures too: if the picture can be handled directly but the audio cannot, the result may be no playback at all, or picture without sound. Saying "this video is an MP4" contributes none of the information a decision needs.

5. The two ways out

The first is to change the way you play it, leaving the file untouched. The second is to convert it into a common combination — H.264 picture, AAC audio, in an MP4 container. The payoff of the second route is a result that plays almost anywhere; the cost is that the picture is compressed again, which takes longer than only swapping the container.

Which route is worth it depends on the two lines you just read. If the file in question is an MKV refusing to open on a Mac, the trade-offs are ordered in what to do when MKV will not play on Mac.

6. What CineX does with each of these codecs

CineX reads the codecs in the file first, then picks a route. If the picture is already in one of the codecs MP4 commonly carries, it swaps the container and leaves the picture untouched; those jobs finish in seconds. If the picture is outside what can be placed straight into MP4, CineX runs a full conversion and compresses the picture into H.264; those jobs take minutes.

Inputs verified on real devices with actual samples cover the MKV, MP4, AVI, TS, WebM, MOV, M4V, 3GP, M2TS/MTS, VOB, MPG, DV, ASF, WMV and RMVB containers; on the video side H.264 (8-bit), HEVC (8-bit and 10-bit), Hi10P, VP9, AV1, Xvid, MPEG-2/MPEG-1, H.263 and ProRes; on the audio side AAC, AC3, E-AC3, MP3, MP2, Opus, DTS, TrueHD and FLAC; on the subtitle side SRT and ASS, plus Blu-ray PGS image subtitles, which are read back into text and come along as a subtitle track. For codecs without a sample, CineX does not describe support as verified.

• M2TS and MTS — camcorder and Blu-ray recordings — come in with the picture kept as it is, while the audio becomes AAC.
• VOB and MPG from the DVD era and DV from home-video captures go through a full conversion; RMVB has a reading for the rv40 line only, so the rest of RealMedia is not described as tested.
• WMV is tested up to wmv2, and ASF audio comes out as AAC. The 3GP box is tested, but the AMR audio typical of old handsets has no reading, so no claim is made about phone footage as a group.
• M4V usually already plays as it is: files that play directly don't get a second copy made and don't use a conversion.

The speed difference comes from whether the picture has to be compressed again, not from how large the file is.

One case is worth planning around: 120fps Hi10P material — high frame rate plus 10-bit — needs about as long to recompress as the clip itself runs.

7. What this article cannot decide for you

• A matching codec name does not guarantee matching parameters; how far a given device goes is stated by that device.
• Knowing "this is AV1" does not tell you whether the file is intact; those are two different checks.
• Compressing the picture again changes the file, so this article does not describe the result as identical to the original.
• A single problematic file has to be judged on its own video codec, audio codec and integrity; a concept article can only give the order of checks.

Frequently asked questions

Which looks better, H.264 or HEVC?

That comparison has no answer on its own. At the same file size HEVC usually keeps more detail; but when both devices must play the file directly, H.264 behaves more predictably. Quality comes from the codec together with its parameters, not from which one is newer.

Why does my television play AV1 but my computer does not?

Because direct support for a codec is implemented per device and per OS version. A recent television may already handle AV1 while a computer from a few years earlier does not; even on the same computer, another playback route can change the outcome. The file itself did not change.

Will converting AV1 or VP9 to H.264 change the picture?

It compresses the picture again, so the result cannot be described as identical to the source. How visible that is depends on your material and on the screen you watch it on. If it matters, run one unimportant file first and compare before touching the material you care about.

Should I just keep everything in the newest codec?

Newest is the best choice for archiving space and worst for playback reach. Files you actually want to watch on other people's devices, on a TV, or inside a photo library tend to be better off in H.264 — which is exactly the combination CineX outputs.

Axiom One LLC — CineX. Figures current as of 24 September 2026.