H.264 vs H.265 (HEVC): what matters

If you’ve ever seen a video refuse to play, or watched a file take up half the space you expected, you’ve bumped into the difference between these two codecs. H.264 and H.265 are the two names that dominate video, and the practical gap between them comes down to a single trade: efficiency against compatibility. Here’s what each one is and how to decide which you want.

H.264, the universal veteran

H.264, also called AVC (Advanced Video Coding), is the codec that runs the world. It’s been around since the mid-2000s, and by now it plays on essentially everything: every phone, every browser, every editor, every smart TV, every old laptop in a drawer. When you want a video to just work, no questions asked, H.264 is the safe bet. Its only real weakness is age. It compresses well, but not as tightly as what came after, so the files are bigger than they strictly need to be.

That ubiquity isn’t an accident. Years of hardware, from phone chips to graphics cards to TV boxes, shipped with H.264 decoding built in, so playing it costs almost nothing in power or heat even on weak devices. Software followed the same path. The practical upshot is that you can hand an H.264 MP4 to almost anyone and be confident it opens, which is a kind of value that pure efficiency doesn’t capture.

H.265, the efficient successor

H.265, better known as HEVC, is the follow-up designed to fix exactly that. Its headline feature is compression: HEVC achieves roughly the same visual quality as H.264 at about half the bitrate. In plain terms, that means a video that looks the same but takes up around half the space, or a video the same size that looks noticeably better. That efficiency is why 4K and HDR video lean on it so heavily, since those formats would be punishingly large in older codecs.

What is HEVC, and why your iPhone uses it

HEVC and H.265 are two names for the same thing, so if a program mentions one and your camera mentions the other, they’re talking about the same codec. The reason the name shows up in everyday life is that modern iPhones, and a lot of recent cameras, record in HEVC by default to keep video file sizes down. On a phone where storage is precious, halving the size of every clip you shoot is a real win. So you may be producing HEVC video constantly without ever having picked it, which is also why the “why won’t this play” problem tends to surprise people.

The trade-off that decides everything

Here’s the whole tension in one sentence: HEVC gives you smaller files, and H.264 gives you files that play anywhere.

HEVC support has become common on modern hardware, recent phones, current computers, newer TVs, but it’s patchy on older devices and inconsistent across software. Part of that is licensing: HEVC’s patent situation made some companies slow to support it, so you’ll find programs and browsers that handle H.264 without a thought but stumble on H.265. On Windows especially, playing HEVC often requires installing a specific extension first, which is a common reason a file that plays fine on someone’s iPhone shows a black screen on their PC. H.264, by contrast, has no such gaps. It plays on literally everything.

So the guidance is less about which codec is “best” and more about matching the codec to the situation.

Keep HEVC when storage matters and your devices are modern. If you’re archiving a lot of 4K footage, or you shoot on a recent iPhone and watch on recent Apple gear, HEVC’s smaller files are a genuine benefit and everything in your chain can read them. There’s no reason to bloat your library by converting.

Convert to H.264 when compatibility matters more than size. If you’re sending a clip to someone on an older phone, uploading to a site or program that rejects HEVC, or editing in software that stutters on H.265 (some editors handle it far worse than H.264), then a plain H.264 MP4 is the version that just works. Maximum reach beats maximum efficiency the moment a file won’t open.

Container versus codec: the confusion behind renaming

A lot of “my video won’t play” trouble comes from mixing up two separate things: the codec and the container.

The codec is how the video is compressed, H.264 or H.265. The container is the file wrapper that holds it, like .mp4 or .mov, along with the audio and other tracks. The important part is that a single .mp4 file can hold either codec inside it. So a file ending in .mp4 tells you nothing about whether the video within is H.264 or H.265. And renaming a file, changing .mov to .mp4 by editing the name, changes nothing at all: it just relabels the wrapper while the actual video data stays exactly as it was. If a player couldn’t decode the codec before, renaming won’t help.

What can help, when the container is the only issue, is repackaging: moving the same video stream into a different wrapper without touching the compression. That’s a fast, lossless operation because no video is re-encoded. For the case where you have HEVC in an awkward wrapper and want it in a clean MP4, the free HEVC to MP4 converter handles the repackage, and for the very common iPhone situation of a .mov file you need as an MP4, MOV to MP4 does the same. Both run in your browser, on your device, with nothing uploaded.

When repackaging isn’t enough, because the target genuinely can’t read H.265 at all, then you need a true re-encode into H.264, which changes the video data and does cost a little quality, unlike the repackage.

A note on downloading

One more practical point. If you’re saving video from the web with Vidferry, it writes a standard MP4 using the most compatible streams the source offers, which for most videos means H.264, the play-everywhere choice. So downloaded video rarely raises any of this. The codec question mostly comes up for footage you shoot yourself, which is where HEVC tends to show up uninvited.