H.264 vs HEVC (H.265): Which Video Codec Should You Choose?
tldr:
- “HEVC is 30-50% smaller than H.264 at the same visual quality.”
- “H.264 plays on everything ever made; HEVC fails on some old devices and browsers.”
- “Share with others: H.264. Keep for yourself on modern devices: HEVC.”
- “Kompress falls back to H.264 automatically when a device can’t encode HEVC — no broken files.” faq:
- q: “Is HEVC better than H.264?” a: “Yes for file size: HEVC delivers the same visual quality at 30-50% lower bitrate. But H.264 wins compatibility — it plays on every device, browser, and TV ever made. Choose by who will play the file.”
- q: “Should I shoot in H.264 or HEVC on my phone?” a: “Shoot HEVC if your phone offers it (iPhone default since iOS 11) — same quality, less storage. It only matters for old playback devices. For compressing: HEVC for your own archive, H.264 for sharing.”
- q: “Does HEVC reduce quality compared to H.264?” a: “No — at the same bitrate HEVC looks better, and at lower bitrates it matches H.264. The ‘smaller’ is achieved through smarter encoding, not through discarding more visible detail.”
- q: “Can all phones play HEVC videos?” a: “Most phones from around 2016 onward have hardware HEVC decoding. Old or budget devices, some Windows machines, and Chrome/Firefox on some platforms can’t. When sharing beyond your own devices, H.264 is the safe choice.”
Every compressed video is written in a codec — the grammar that describes how frames are encoded. For the last two decades two codecs have mattered most: H.264 (AVC), the universal default, and HEVC (H.265), its more efficient successor.
Pick the wrong one and you either waste 40% of your possible savings — or produce a file that won’t play on your dad’s laptop. Here’s how to choose.
What a codec actually is
A video codec defines how each frame is compressed: which pixels can be predicted from earlier frames, how motion is estimated, and how much error the decoder tolerates. A better codec achieves the same visual quality with fewer bits — HEVC needs roughly 30–50% less bitrate than H.264 for visually equivalent output.
| H.264 (AVC) | HEVC (H.265) | |
|---|---|---|
| Introduced | 2003 | 2013 |
| Same quality vs H.264 | baseline | ~30–50% smaller |
| Compatibility | Everything, everywhere | Most modern devices |
| Playback on old devices | ✅ | ⚠️ Often no |
| Hardware encode on phones | ✅ | ✅ (most phones since ~2016) |
| Best for | Sharing with anyone | Personal archives, modern devices |
Why HEVC is smaller: the engineering in one minute
Both codecs predict frames from neighboring frames. HEVC does it with finer tools: larger, flexible block sizes (up to 64×64 vs H.264’s 16×16), better motion compensation, and smarter intra-prediction modes. The result is fewer bits spent describing the same scene.
For the mathematically inclined: encoding the same 1080p clip at the same visual quality might cost H.264 10 Mbps and HEVC 6 Mbps — a 40% saving on the entire file, for free.
The compatibility question (the only reason this is a debate)
HEVC patents and licensing kept it out of the web’s core for a decade. The practical fallout:
- Apple devices record HEVC by default since iOS 11 and play it natively — on any reasonably recent iPhone, iPad, or Mac.
- Modern Android phones encode and play HEVC (via hardware) — but old or cheap chipsets may not.
- Windows: plays HEVC only with a paid extension (or via VLC).
- Browsers: Safari handles HEVC; Chrome and Firefox historically don’t (support is emerging on some platforms with hardware).
- Editors and smart TVs: mixed. High-end TVs handle it; some editors still transcode first.
Translation: HEVC files are safe when you control the playback environment — your own devices, your family’s recent iPhones. The moment a file goes to “someone unknown,” H.264 remains the only universally safe choice.
How your phone’s hardware fits in
Your phone has dedicated silicon for encoding video — the same hardware the camera app uses. Both H.264 and HEVC encode through it, which means:
- compression runs fast and cool (software encoding drains battery and takes 10× longer),
- and the encoder quality depends on the vendor, not the app.
This is why Kompress uses the platform’s own encoders (AVFoundation on iOS, MediaCodec on Android) instead of bundling FFmpeg: same hardware path your camera already trusts, in a small app.
The decision, in three cases
1. Compressing videos you’ll share with others → H.264. Guaranteed playback everywhere: every phone, browser, TV, laptop, and messaging app. The slightly larger file is the price of certainty.
2. Compressing videos you’ll keep for yourself → HEVC, if your devices are modern. You’re the playback environment; enjoy the extra 30–40% savings on your archive.
3. Storage emergency, any playback → HEVC where it works, H.264 fallback. In Kompress, Advanced mode exposes the choice; if a device can’t encode HEVC, the app falls back to H.264 automatically and tells you — you never get a file that silently won’t play.
A note on “future-proofing”
H.265’s successor momentum (AV1) is real in streaming, but AV1 encoding on phones is still slow and rare. For files you create yourself on a phone in 2026, H.264 and HEVC remain the practical pair. Don’t over-think codecs you can’t encode with the hardware you own.
Bottom line
- Same visual quality: HEVC is 30–50% smaller than H.264.
- Same playback certainty: H.264 plays literally everywhere.
- The choice is compatibility vs. size — nothing else.
Want to try both? Kompress exposes the codec switch in Advanced mode, compresses on-device, and shows a before/after comparison so you can judge the results yourself. The first run is free on the App Store and Google Play.