HEVC vs H264: 50% Smaller Files, One Real Catch
HEVC vs H.264: 50% Smaller Files, One Real Catch
Use HEVC (H.265) when file size matters and your viewers are on Apple devices, modern Android, or 4K hardware — you'll get ~50% smaller files at identical quality.
Use H.264 (AVC) when you need maximum compatibility — older browsers, web embeds, low-end devices, or legacy editing pipelines.
That's the headline. The rest of this guide walks through why — and the compatibility, encoding-speed, and licensing nuances that decide the call for your specific workflow. If you need a tool-by-tool walkthrough instead, see how to convert HEVC to H.264 — covers Mac, Windows, iPhone, and FFmpeg commands.
Both are video codecs developed by the ITU-T / ISO. H.264 was standardized in 2003 and dominated the next two decades. HEVC arrived in 2013 with a smarter block structure that delivers the same visual quality at roughly half the bitrate. AV1, the open-source challenger, is taking share in 2026 — but for most workflows, HEVC vs H.264 is still the live decision.
This guide covers: how each codec works, head-to-head benchmarks, hardware/software requirements, licensing costs, browser and device support, and a decision matrix at the end. For a deeper look at HEVC alone, see our HEVC codec explained guide. If you're weighing newer codecs, see AV1 vs H.265.
How H.264 Works: The Foundation of Modern Video
H.264 was standardized in 2003 and has been the dominant video codec ever since. It's what YouTube, Netflix (for lower-bandwidth streams), Blu-ray, and virtually every camera manufacturer uses as a baseline.
The core of H.264 is its block-based compression architecture. Video frames are divided into macroblocks — fixed 16×16 pixel blocks — and the codec predicts how each block will change between frames. Instead of storing every pixel in every frame, it stores only the differences (deltas) from the predicted blocks. Intra-frame compression handles spatial redundancy within a single frame; inter-frame compression handles temporal redundancy across frames.
H.264 supports several key profiles:
- Baseline Profile: simple, low-latency, used in video conferencing and mobile streaming
- Main Profile: good balance of compression and compatibility, used in broadcast
- High Profile: maximum compression, used in Blu-ray and high-quality streaming
The result is a codec that works on virtually every device made in the last 15 years — phones, tablets, computers, smart TVs, cameras, streaming boxes. That universal compatibility is H.264's single biggest advantage and why it remains dominant despite being technically outclassed.
Maximum practical resolution: 4K (4096×2160), though 8K is technically possible with High Profile extensions. Real-world 4K H.264 files are large and demanding to encode.
How HEVC (H.265) Works: Smarter, More Efficient
HEVC was standardized in 2013, a decade after H.264, and the architectural improvements are substantial. The most visible change: instead of fixed 16×16 macroblocks, HEVC uses Coding Tree Units (CTUs) that can scale from 8×8 to 64×64 pixels.
This flexibility is a major efficiency win. For complex, detailed areas of a frame — like foliage or textured surfaces — smaller blocks preserve detail. For smooth areas like sky or skin, large blocks eliminate redundancy without wasting bits. The codec dynamically chooses the optimal block size for each region of each frame.
HEVC also significantly expands the motion compensation range (predicting movement across more frames) and adds more sophisticated in-loop filtering to reduce blockiness artifacts. These improvements compound: less blocking means fewer bits needed to correct for it downstream.
The compression result: HEVC achieves the same visual quality as H.264 at roughly half the bitrate — a 40-50% reduction in file size. This is not marketing hype; it's measurable and consistent across content types.
Resolution support: HEVC was designed from the ground up for 8K (8192×4320) video. It's the codec behind 4K UHD Blu-ray and the primary format for 4K/8K broadcast distribution.
File Size Comparison: H.264 vs HEVC in Practice
To make the compression difference concrete, here are real-world benchmarks for a 10-minute 1080p video encoded at comparable visual quality:
| Codec | Bitrate | File Size | Visual Quality |
|---|---|---|---|
| H.264 (High Profile) | 8 Mbps | ~600 MB | Reference |
| HEVC (Main Profile) | 4 Mbps | ~300 MB | Equivalent |
| HEVC (Main10 Profile) | 3.5 Mbps | ~263 MB | Slightly better |
For 4K video, the savings are even more dramatic. A 10-minute 4K clip shot on iPhone that weighs 6 GB in H.264 will compress to roughly 3 GB in HEVC at equivalent quality. Over a library of thousands of videos, this difference becomes terabytes.
This is exactly why Apple's iPhone (since iPhone 7) shoots HEVC by default, and why Compresto uses HEVC encoding on Mac to dramatically reduce video file sizes while preserving quality. See our guide on best video compression methods for more on achieving optimal compression ratios.
Computational Requirements: The Tradeoff
HEVC's efficiency isn't free. The smarter encoding decisions — evaluating multiple CTU sizes, extended motion compensation, sophisticated filtering — require significantly more CPU work.
Encoding comparison:
- H.264: fast to encode, efficient on CPU, well-supported by hardware encoders
- HEVC: 2-5x more CPU-intensive in software encoding; much faster with hardware acceleration
Decoding comparison:
- H.264: hardware-decoded on virtually every device made since 2010
- HEVC: hardware-decoded on devices since ~2015-2017 (varies by manufacturer)
On modern Macs with Apple Silicon (M1 and later), HEVC encoding and decoding are both handled in dedicated media engine hardware. This means HEVC encodes nearly as fast as H.264, with dramatically better output file sizes. For Mac users, this eliminates the encoding speed penalty entirely.
On older hardware or devices without HEVC hardware acceleration, encoding can be slow — a key reason to use a dedicated tool rather than trying to run FFmpeg software encoding on everything.
Encode Cost at a Glance
The real question is not "HEVC or H.264" but "hardware or software encoder". That choice moves encode time far more than the codec does:
| Encoding path | Speed | CPU load | Notes |
|---|---|---|---|
| H.264, hardware (VideoToolbox, NVENC, Quick Sync, AMD VCN) | Faster than real time | Very low | Available on essentially every computer and phone |
| HEVC, hardware (same engines) | Faster than real time, close to H.264 | Very low | Needs an HEVC-capable encoder block (see table below) |
| H.264, software (x264) | Fast | Moderate to high | Best quality per bit among H.264 encoders |
| HEVC, software (x265) | Several times slower than x264 at the same preset | High, uses every core | Best quality per bit, but the slowest path here |
Hardware encoders trade a little efficiency for speed: at the same bitrate, a software x265 encode usually looks slightly better than a hardware HEVC encode. For most people compressing their own videos, hardware HEVC still lands well ahead of hardware H.264 on file size. Our x264 vs x265 breakdown covers the software encoders in detail.
HEVC vs H.264 Hardware Support: Encode vs Decode by Platform
Decode is the part that decides whether a file plays; encode is the part that decides how fast you can make it. H.264 has both everywhere. HEVC has both on most hardware from about 2016 onward:
| Platform | H.264 encode + decode | HEVC encode | HEVC decode |
|---|---|---|---|
| Mac (Apple Silicon) | All M-series | All M-series (M1 through M5) | All M-series |
| iPhone / iPad | Yes | iPhone 7 and later; iPad (6th gen) and later | iOS 11 and later (older models limited by resolution and frame rate) |
| NVIDIA GeForce | Yes (NVENC / NVDEC) | GTX 10-series (Pascal) and later | GTX 10-series and later |
| Intel | Yes (Quick Sync) | 6th-gen Core (Skylake) and later | 6th-gen Core and later; 10-bit from 7th-gen (Kaby Lake) |
| AMD Radeon | Yes (VCN) | VCN cards: RX 5000 series and later (not RX 6400 / 6500 XT) | VCN cards: RX 5000 series and later |
| Android | Yes (decode required, encode recommended) | Depends on the chip; Android does not require an HEVC encoder | Platform decoder since Android 5.0 |
| Browsers | All browsers | — | Safari 13+; Chrome 107+ and Edge 107+ with conditions; Firefox 137+ with hardware support |
The browser row is where HEVC trips people up. Per caniuse, Chrome plays HEVC on macOS Big Sur or later and Android, but on Windows only when the GPU decodes HEVC in hardware. Edge on Windows additionally needs the HEVC Video Extensions. Firefox 137+ relies on hardware support with software fallback only in some cases. H.264 has none of these conditions.
Sources: Apple HEIF/HEVC support, MacBook Pro tech specs, NVIDIA encode/decode support matrix, Intel media-driver codec table, AMD VCN overview, Android supported media formats, caniuse HEVC.
Compatibility: Where Each Codec Works
This is where H.264 still wins clearly, and it matters for distribution:
H.264 compatibility:
- Every web browser (natively, without plugins)
- Every video platform (YouTube, Vimeo, Instagram, TikTok, Twitter)
- Every DVD/Blu-ray player
- Every phone, tablet, and laptop made since ~2010
- All video editing software
HEVC compatibility:
- Safari (full support)
- Chrome, Firefox, Edge (requires hardware support; some systems need codec packs)
- YouTube, Vimeo (transcode on upload, so source format matters less)
- iPhone 7+, most Android phones since ~2017
- Macs with macOS High Sierra or later
- Windows 10+ (requires HEVC Video Extensions from the Microsoft Store)
- PS5, Xbox Series X (not older consoles)
The practical implication: if you're delivering video to a broad audience on the web, encode in H.264. If you're archiving, editing, or sharing with other Apple device users, HEVC is the better choice. Many professional workflows use HEVC for storage and re-encode to H.264 for distribution.
Understanding the difference between lossy and lossless compression also helps clarify why both codecs use lossy encoding — the compression gains require discarding some data.
Licensing: Why HEVC Adoption Was Slowed
One of the messier aspects of the HEVC vs H.264 debate is licensing. H.264 is licensed through MPEG LA with relatively straightforward (if not cheap) terms. HEVC has a fragmented patent pool — multiple separate licensing bodies (MPEG LA, HEVC Advance, Velos Media) all claim royalties, and their fees are substantial.
This fragmentation caused real problems: some browser vendors initially refused to implement HEVC hardware decoding through the web platform because of licensing uncertainty. Google and Mozilla pushed AV1 as an alternative partly to avoid HEVC licensing.
For end users and Mac users using apps like Compresto, this doesn't directly apply — Apple has licensed HEVC patents as part of macOS/iOS. But it explains why HEVC adoption across the web has been slower than its technical superiority would predict.
AV1: The Rising Alternative
No HEVC vs H.264 comparison is complete without mentioning AV1. Developed by the Alliance for Open Media (Google, Apple, Meta, Netflix, and others), AV1 is royalty-free and offers compression efficiency similar to or slightly better than HEVC.
AV1 adoption is accelerating: YouTube uses it, Netflix uses it, and hardware support is appearing in newer chips (Apple M3 and later Macs and A17 Pro and later iPhones include AV1 hardware decode, but no Apple chip encodes AV1 in hardware as of the M5). However, hardware encoding support is still limited, making AV1 encoding slow on most hardware.
For now, the practical choice remains H.264 vs HEVC for most Mac users. AV1 is the future, but HEVC is the present for high-quality compression with broad hardware support.
HEVC or H.264: Which Should You Use?
Match the codec to the job. This is the short answer to HEVC or H.264 for the cases that come up most:
| Use case | Pick | Why |
|---|---|---|
| Sharing with unknown devices (clients, email, web forms, old TVs) | H.264 | Plays everywhere, no codec packs or hardware checks |
| Sending to iPhone, iPad, or Mac users | HEVC | Native playback since iOS 11 / High Sierra, about half the size |
| Archiving your own library | HEVC (10-bit if the source is HDR) | Roughly half the storage; you control future playback |
| Embedding on a website | H.264 baseline | Every browser plays it; HEVC in Chrome depends on the viewer's GPU |
| Uploading to YouTube or Vimeo | Either, at a generous bitrate | The platform re-encodes everything you upload |
| Live streaming | H.264 | Most widely accepted ingest format and cheapest real-time encode |
| Editing | H.264 on older machines; HEVC fine on Apple Silicon | HEVC timelines are heavier to scrub without hardware decode; heavy grading still favors ProRes |
| 4K and HDR | HEVC | Built for 4K/8K and 10-bit; H.264 4K files get very large |
If none of these fit, default to H.264 for anything leaving your hands and HEVC for anything you keep. For the newer codec in the mix, see AV1 vs H.264.
Which Codec Should You Choose?
Choose H.264 when:
- You need maximum compatibility across all devices and browsers
- You're uploading to social media or web platforms
- You're working with older editing software or hardware
- Encoding speed is more important than file size
- You're sharing with people whose device support you can't predict
Choose HEVC (H.265) when:
- You're on a Mac with Apple Silicon (fast hardware encode/decode)
- You're archiving video long-term and storage space matters
- You're working within the Apple ecosystem (iPhone, iPad, Mac, Apple TV)
- You're shooting 4K or 8K content
- You want the smallest possible files without quality loss
For Mac users compressing existing video files, HEVC is almost always the right answer. The file size savings are substantial, Apple Silicon handles encoding quickly, and macOS has full native support.
Using Compresto for HEVC Encoding on Mac
Compresto makes HEVC encoding on Mac as simple as dropping a file. It uses Apple's hardware media engine for fast, efficient H.265 encoding — meaning you get 50% smaller video files without the hours-long encoding sessions you'd expect from software-based tools.
For batch compression of video libraries, Compresto's folder monitoring feature automatically compresses new files as they're added, keeping your video archive lean without manual intervention. If you need to make MP4 files smaller, Compresto handles the codec conversion automatically.
If you're also looking to compress images, PDFs, and other media files alongside video, check our guide on best archive tools for Mac for a complete overview of compression tools for different file types.
Download Compresto for Mac and start cutting your video storage in half.
H.264 vs HEVC, HEVC or H.264 — Same Decision
h264 vs hevc, h.264 vs hevc, and hevc or h264 are this page. H.264 vs HEVC is the same comparison in reverse order. HEVC or H.264 is the same fork: file size versus compatibility. H.264 vs H.265 and H.265 vs AVC are the same two codecs — HEVC is H.265; AVC is H.264.
Pick HEVC for ~50% smaller files on Apple devices, modern Android, and 4K TVs. Pick H.264 when the file has to play in old browsers, web embeds, or unknown devices.
FAQ: HEVC vs H.264
Q: HEVC or H.264 — which should I pick?
Pick HEVC (H.265) when viewers are on Apple devices, modern Android, or 4K TVs and you want ~50% smaller files. Pick H.264 when the file has to play in old browsers, web embeds, or unknown devices. H.264 vs HEVC and H.265 vs AVC are the same two codecs.
Q: Is HEVC always better than H.264?
Technically yes — HEVC offers better compression efficiency and supports higher resolutions. But H.264 is still the right choice when you need maximum device compatibility, especially for web distribution where not all browsers support HEVC hardware decoding.
Q: Can I convert H.264 video to HEVC without losing quality?
Every lossy-to-lossy transcode involves some generation loss. However, if you transcode at a high enough HEVC bitrate (higher than strictly necessary), the generation loss is essentially invisible. Going from H.264 at 8 Mbps to HEVC at 6 Mbps will look identical to most viewers. Going to HEVC at 3 Mbps will look similar but with mild compression in complex scenes.
Q: Does HEVC really save 50% storage space?
Yes, consistently. At equivalent visual quality settings, HEVC files are approximately 40-50% smaller than H.264. The exact savings vary by content type — talking head videos see more savings than fast-action sports footage — but 50% is a reliable estimate for typical content.
Q: Why is HEVC encoding slower than H.264?
Software HEVC encoding is computationally expensive because evaluating variable-size coding tree units and extended motion compensation requires many more calculations than H.264's fixed macroblocks. With hardware encoding (available on Apple Silicon Macs and modern GPUs), this penalty largely disappears — hardware HEVC encoding is nearly as fast as H.264.
Q: Will AV1 replace HEVC?
Eventually, yes — but not yet. AV1 hardware encoding support is still limited to the newest chips, making software AV1 encoding prohibitively slow for most workflows. HEVC remains the practical choice for high-quality compression in 2026.
Q: Does HEVC play in Chrome and on Windows?
Usually, but not everywhere. Chrome 107 and later plays HEVC on macOS Big Sur or newer and on Android, and on Windows only when the GPU has HEVC hardware decode. Edge on Windows also needs the HEVC Video Extensions from the Microsoft Store. Firefox 137+ plays it where hardware support exists. Safari has supported HEVC since macOS High Sierra. H.264 plays in all of them with no conditions.
Q: Does my computer have hardware HEVC encoding?
If it is an Apple Silicon Mac, yes — every M-series chip encodes and decodes HEVC in hardware. On PCs, NVIDIA GeForce GTX 10-series and newer, Intel 6th-gen Core (Skylake) and newer, and most AMD Radeon cards with VCN (RX 5000 series and newer; the entry-level RX 6400 and RX 6500 XT have no encoder) all have HEVC encode. Older or entry-level hardware may only decode HEVC, which makes software encoding slow.