Video

H.264 vs H.265 vs AV1: Video Codec Showdown

Published Mar 19, 2026 8 min read By ChangeThisFile Team

Quick Answer

H.264 is universally compatible but the least efficient. H.265 compresses 50% better but has a fragmented patent landscape that limits adoption. AV1 compresses 30% better than H.265 and is royalty-free, but encoding is extremely slow. Choose H.264 for compatibility, H.265 for file size on controlled playback, and AV1 for web delivery where you encode once and serve millions of times.

Three codecs dominate video in 2026: H.264 (the universal standard), H.265 (the efficient successor with licensing baggage), and AV1 (the royalty-free future). They each represent a generation of compression technology, and each comes with distinct tradeoffs in quality, speed, compatibility, and cost.

This isn't an abstract comparison. The codec you choose determines whether your video is 500MB or 250MB, whether it plays on a 2015 smartphone or only on a 2022 one, whether encoding takes 2 minutes or 2 hours, and whether you owe patent royalties to anyone.

Here's the technical reality behind each codec, with real numbers and clear recommendations for every use case.

Compression Efficiency: The Numbers

Compression efficiency is measured by how much bitrate each codec needs to achieve the same visual quality. The standard metric is BD-Rate (Bjontegaard Delta Rate): the percentage of bitrate saved at the same quality score (usually SSIM or VMAF).

Codec	BD-Rate vs H.264	1080p Good Quality	4K Good Quality	10-min 1080p File
H.264	Baseline (0%)	5-10 Mbps	35-68 Mbps	~450MB
H.265	-40% to -50%	3-5 Mbps	15-30 Mbps	~250MB
AV1	-55% to -65%	2-4 Mbps	10-20 Mbps	~180MB

These are real-world numbers, not theoretical maximums. Netflix's public AV1 vs H.264 tests showed 50%+ bitrate reduction on their content library. Google's VP9 (similar efficiency to H.265) tests showed 34% savings on YouTube content. Academic comparisons using the JCT-VC test sequences consistently show H.265 at 35-50% savings and AV1 at 50-65% savings versus H.264.

Where the gaps narrow: At very high bitrates (15+ Mbps for 1080p), all three codecs look nearly identical because there's enough data for even the least efficient codec to reproduce the source faithfully. The efficiency differences matter most at medium-to-low bitrates where compression artifacts become visible.

Encoding Speed: The Practical Bottleneck

Better compression requires more computation. Each generation of codec trades encoding speed for file size savings.

Codec	Software Speed (1080p)	Time for 10-min Clip	Hardware Encoder Speed
H.264 (x264)	~60-120 fps	~1-2 min	200-400 fps (NVENC, QSV)
H.265 (x265)	~15-30 fps	~5-10 min	100-200 fps (NVENC, QSV)
AV1 (libaom)	~1-5 fps	~30-150 min	50-120 fps (AV1 HW encoders)
AV1 (SVT-AV1)	~15-40 fps	~4-10 min	N/A (software only)

The libaom vs SVT-AV1 distinction matters. libaom is the reference AV1 encoder — technically best quality but painfully slow (1-5 fps for 1080p). SVT-AV1 (developed by Intel and Netflix) is a practical AV1 encoder that achieves 80-90% of libaom's compression at 5-10x the speed. For real-world use, SVT-AV1 is the right choice.

Hardware encoders (NVIDIA NVENC, Intel Quick Sync, AMD VCE) are dramatically faster but produce files 20-40% larger than software encoders at the same quality. For real-time recording and streaming, hardware encoding is essential. For offline encoding where quality per bit matters, software encoding wins.

Hardware Decode Support

Hardware decode determines which devices can play your video efficiently (without draining battery or overheating). Each codec generation needs newer silicon.

Codec	Mobile	Desktop GPU	Smart TVs
H.264	All smartphones (2008+)	All GPUs (2006+)	All smart TVs
H.265	iPhone 6+ (2014), Android 2015+	NVIDIA Maxwell+ (2014), Intel Skylake+ (2015), AMD Polaris+ (2016)	2016+ smart TVs
AV1	iPhone 15 Pro+ (2023), Pixel 6+ (2021), Snapdragon 888+ (2021)	NVIDIA RTX 30-series+ (2020), Intel 11th-gen+ (2021), AMD RDNA 2+ (2020)	2022+ smart TVs

The practical implication: H.264 plays on everything. H.265 plays on devices from the last ~10 years. AV1 plays on devices from the last ~4 years. If your audience includes older devices (which it probably does), H.264 remains the safe default.

Software decode is always possible as a fallback, but it uses significantly more CPU/battery. A phone that plays H.264 for 8 hours might last only 4 hours with software AV1 decode.

Patent Licensing: The Hidden Cost

This is where the codec choice gets political.

H.264: Licensed through MPEG LA's AVC patent pool. The licensing terms are well-understood and have been stable since 2004. MPEG LA made H.264 royalty-free for free internet video in 2010 (no per-stream fee for content distributed free of charge). For commercial video services charging subscribers, licensing fees apply but are predictable.

H.265: This is where it gets ugly. Three separate patent pools claim H.265 patents:

MPEG LA — The traditional licensing body
HEVC Advance — A consortium including GE, Dolby, and Philips, demanding higher rates
Velos Media — Another group including Nokia, claiming additional essential patents

The combined licensing cost is unclear and potentially much higher than H.264. This uncertainty is precisely why browser vendors were slow to adopt H.265 — they couldn't predict the licensing exposure. Google funded AV1 specifically to escape this mess.

AV1: Royalty-free, permanently. The Alliance for Open Media (AOM) — whose members include Google, Apple, Amazon, Netflix, Meta, Microsoft, Intel, and NVIDIA — specifically designed AV1 to avoid patent encumbrances. AOM members cross-license their AV1-related patents at no cost. This is the codec's single biggest strategic advantage.

Browser Support Matrix

Browser	H.264	H.265	AV1
Chrome	Yes (always)	Yes (hardware only, 2023+)	Yes (v70+, 2018)
Firefox	Yes (always)	Yes (platform-dependent)	Yes (v67+, 2019)
Safari	Yes (always)	Yes (v11+, 2017)	Yes (v17+, 2023)
Edge	Yes (always)	Yes (hardware only)	Yes (v79+, 2020)

H.264 is universal. Every browser, no exceptions, no hardware requirements.

H.265 is fragmented. Chrome and Firefox only decode H.265 when hardware acceleration is available (no software fallback). Safari supports it fully because every Apple device since 2017 has hardware HEVC decode. Edge follows Chrome's behavior.

AV1 has better browser support than H.265. Chrome, Firefox, and Edge all support software AV1 decode (falling back to CPU when no hardware decoder exists). Safari added AV1 in 2023. For web video, AV1 is actually more reliably supported across browsers than H.265.

Recommendations by Use Case

Use Case	Recommended Codec	Why
Sharing via email/messaging	H.264	Plays on every device, fast to encode
Social media upload	H.264	Platform will re-encode anyway; upload max quality source
Website video embed	AV1 (with H.264 fallback)	Smallest files, royalty-free, good browser support
Streaming service (DASH/HLS)	AV1 primary, H.264 fallback	Bandwidth savings justify encoding cost at scale
Local playback (Plex/Jellyfin)	H.265	Best balance of compression and hardware support for 2020+ clients
4K content	H.265 or AV1	H.264 bitrates for 4K are impractically large (35-68 Mbps)
Security camera recording	H.265	50% storage savings vs H.264, hardware encoders widely available
Screen recording	H.264	Fast encoding, CPU headroom for the recording itself
Archival (encode once, keep forever)	AV1 (SVT-AV1)	Smallest files, royalty-free, future-proof

Converting Between Codecs

Codec conversion always means re-encoding — the video is fully decoded from the source codec and re-encoded with the target codec. This is computationally intensive and introduces a generation of compression.

Quality preservation rule: When re-encoding, use a CRF value that targets slightly higher quality than the source. If the source was H.264 CRF 23, encode the H.265 version at CRF 24-26 (H.265 CRF values produce higher quality at the same number) to get a smaller file at equivalent or slightly better visual quality.

Practical conversions:

MP4 (H.264) to WebM (VP9) — Re-encode for web delivery
MP4 (H.264) to AV1 — Maximum compression, slow encoding
WebM (VP9) to MP4 (H.264) — For compatibility when sharing
MKV (H.265) to MP4 — Often a remux if MP4 is the target container

Never convert lossy-to-lossy unless you need to. Each re-encoding pass degrades quality. If you have the original source (camera file, editing project), always encode directly from source rather than converting between lossy formats.

The codec landscape in 2026 is transitional. H.264 remains the safe default because nothing else matches its universal hardware support. H.265 is the efficient middle ground hamstrung by licensing uncertainty. AV1 is the technical and strategic winner — best compression, royalty-free, good browser support — but slow encoding and limited hardware decode on older devices keep it from being the universal answer yet.

The trend is clear: AV1 adoption is accelerating as hardware encoders and decoders proliferate. Within a few years, AV1 will have the hardware coverage that H.265 has today. When that happens, H.264's thirty-year reign as the universal codec will finally end — not because it stops working, but because AV1 does everything better without the patent baggage.

Key Takeaways

H.265 saves ~50% bitrate vs H.264; AV1 saves ~30% more vs H.265 (or ~65% vs H.264)
H.264 encoding is 5-8x faster than H.265 and 10-50x faster than AV1 (software encoding)
H.264 hardware decode is universal; H.265 needs 2014+ devices; AV1 needs 2020+ devices
H.265's fragmented patent licensing (3 separate pools) is why AV1 was created
AV1 has better browser support than H.265 because browsers implement software AV1 decode
Use H.264 for compatibility, H.265 for local media, AV1 for web delivery at scale
SVT-AV1 is 5-10x faster than libaom at 80-90% of the compression efficiency

Frequently Asked Questions

Is H.265 twice as good as H.264?

H.265 achieves roughly the same visual quality at 40-50% lower bitrate. So a 10Mbps H.264 file looks about the same as a 5-6Mbps H.265 file. It's not 'twice as good' in quality — it's roughly half the file size at the same quality. The visual ceiling is determined by the source material, not the codec. Both can produce visually lossless output; H.265 just needs fewer bits to get there.

Should I re-encode my H.264 library to H.265?

Only if storage savings justify the time investment. Re-encoding a lossy H.264 source to H.265 will save 30-40% file size (less than the theoretical 50% because you're compressing already-compressed data). For a 10TB library, that's 3-4TB saved — potentially worth it. But re-encoding will take days to weeks of CPU time and introduces a generation of quality loss. If the files play fine and storage isn't tight, leave them.

Can I use AV1 for live streaming?

Hardware AV1 encoders (NVIDIA RTX 40-series, Intel Arc) make real-time AV1 encoding possible at 1080p 30fps. OBS supports hardware AV1 encoding, and YouTube accepts AV1 live streams. However, hardware AV1 encoding produces larger files than software encoding (by 20-40%), partially negating the compression advantage. For live streaming to broad audiences, H.264 remains more practical because viewers need compatible decoders.

Why does YouTube use VP9 instead of H.265?

Licensing. YouTube serves billions of hours of video. H.265's fragmented patent pools would create enormous and unpredictable licensing costs. VP9 (and now AV1) are royalty-free — Google pays nothing per stream. VP9 achieves compression comparable to H.265, so there's no quality sacrifice. This same logic drives Netflix, Amazon, and other large platforms toward AV1.

What's the best CRF value for each codec?

CRF scales differently per codec. For visually transparent quality: H.264 CRF 18, H.265 CRF 22, AV1 CRF 24-26. For good quality with smaller files: H.264 CRF 23, H.265 CRF 28, AV1 CRF 30-32. For acceptable quality at minimum size: H.264 CRF 28, H.265 CRF 32, AV1 CRF 36-38. Always test with your content — animation, film grain, and fast motion all affect optimal CRF.

Does transcoding between codecs always lose quality?

Yes. Transcoding (re-encoding from one lossy codec to another) always introduces additional compression artifacts. The degradation may be visually imperceptible at high quality settings (low CRF), but it's technically present. The rule: never transcode between lossy formats unless you need to. If you have the original source, encode directly from source to the target codec.

Will AV1 replace H.264?

Eventually, yes — but not for several more years. AV1's compression advantage and royalty-free status make it the inevitable successor. The blockers are encoding speed (improving rapidly with SVT-AV1 and hardware encoders) and hardware decode coverage (expanding with each chip generation). By 2028-2030, most active devices will have AV1 hardware decode, and the transition will accelerate sharply.

Which codec is best for 4K video?

H.265 or AV1. H.264 at 4K requires 35-68 Mbps for good quality, producing impractically large files (25-50GB per hour). H.265 cuts that to 15-30 Mbps (10-22GB per hour). AV1 cuts further to 10-20 Mbps (7-15GB per hour). For 4K content, the compression efficiency of newer codecs isn't just nice-to-have — it's a practical necessity for reasonable file sizes and streaming bandwidth.

Ready to convert your files?

Use ChangeThisFile to convert between 600+ formats — free, fast, and private.

Start Converting