H.264 vs VP9 vs AV1: Video Codec Comparison for Web (2026)

Choosing a video codec for the web comes down to a three-way tradeoff: compatibility, compression, and encoding cost. H.264 works everywhere but produces the largest files. AV1 delivers the best compression, roughly 50% smaller than H.264 at equal quality (Meta Engineering, 2018), but encoding is painfully slow. VP9 sits in the middle, offering 30-40% savings over H.264 with reasonable encode times.

This guide compares all three codecs across the metrics that actually matter: file size, visual quality, encoding speed, hardware support, browser coverage, and licensing. By the end, you'll know which codec fits your project.

Key Takeaways

• AV1 compresses 50% better than H.264 but encodes 10-20x slower
• VP9 offers a practical middle ground with 30-40% savings over H.264
• H.264 has near-universal hardware decode support; AV1 hardware is catching up fast
• Netflix and YouTube both use all three codecs for different device tiers
• AV1 is royalty-free, H.264 requires licensing through MPEG-LA (MPEG LA, 2024)

How Do H.264, VP9, and AV1 Compare Overall?

AV1 leads in compression efficiency, delivering roughly 50% bitrate savings over H.264 and 20-30% over VP9 at matched visual quality (Moscow State University Video Quality Report, 2022). The table below summarizes every key dimension across the three codecs.

[CHART: Bar chart - Average bitrate needed for 1080p at equivalent VMAF 95: H.264 (4.5 Mbps), VP9 (2.9 Mbps), AV1 (2.2 Mbps) - Moscow State University Codec Comparison 2022]

How Fast Is Each Codec at Encoding?

H.264 encodes approximately 10-20x faster than AV1. In practical benchmarks, x264 at its medium preset encodes 1080p content at 200+ fps, while SVT-AV1 at preset 6 manages around 15-25 fps on the same hardware (SVT-AV1 GitHub Benchmarks, 2024). VP9's libvpx encoder falls between the two, typically running 3-5x slower than x264.

These speed differences shape real-world workflows. Live streaming? H.264 is your only practical option, unless you have dedicated hardware encoders. Pre-encoded video for a website? AV1 is worth the wait because you encode once and serve millions of times.

Benchmark: 1080p 60-second Clip on 8-core CPU

SVT-AV1 has improved dramatically since its early releases. Intel's engineering team cut encoding time by over 60% between versions 0.8 and 1.4 while maintaining quality (Intel Open Source Blog, 2023). For most web use cases, SVT-AV1 at preset 6-8 offers the best speed-to-quality tradeoff.

What about GPU encoding? NVIDIA's NVENC added AV1 support in the RTX 40-series, and AMD's VCN 4.0 followed suit. Hardware AV1 encoding is fast but produces larger files than software encoding at matched quality. It's a viable option for real-time streaming, not for archival quality.

[IMAGE: Encoding speed comparison bar chart showing relative encode times for H.264 VP9 and AV1 - search terms: video encoding speed benchmark comparison chart]

Which Browsers and Devices Support Each Codec?

H.264 reaches 98.9% of browsers globally, making it the safest default (Can I Use, May 2026). VP9 covers 96.5% (Can I Use, May 2026), missing mainly older Safari versions. AV1 has climbed to 92.3% support (Can I Use, May 2026), with Safari 17+ closing the last major gap in early 2024.

Hardware decode tells a different story. Every phone, tablet, laptop, and smart TV manufactured in the last decade has H.264 hardware decoding. VP9 hardware decode is standard on Android devices (via Qualcomm, MediaTek) and Intel chips from 2015 onward. AV1 hardware decode requires newer silicon: Apple's M3/A17 Pro chips, Intel 12th-gen+, AMD RDNA 3+, Qualcomm Snapdragon 8 Gen 2+, and Samsung Exynos 2400+.

Why does hardware decode matter? Without it, your users' devices burn through battery and CPU cycles decoding video in software. On mobile, this can cause stuttering, overheating, and poor battery life, especially at 4K.

Hardware Decode Timeline

We've found that roughly 15-20% of our users' devices still lack AV1 hardware decode. Serving AV1 without a fallback causes visible CPU spikes on older iPads and budget Android phones. Always include an H.264 fallback in your <source> stack.

How Are Netflix and YouTube Using These Codecs?

Netflix reported that AV1 streaming saves 20% bandwidth compared to VP9 across their catalog (Netflix Tech Blog, 2024). YouTube has served VP9 as its default codec since 2015 and began rolling out AV1 for popular videos in 2018. Both platforms use a tiered approach.

YouTube encodes every upload in multiple codecs. New uploads get H.264 immediately for instant availability. Popular videos earn VP9 and eventually AV1 encodes because the encoding cost is justified by millions of views. Google estimated that VP9 alone saves them 30-35% in bandwidth costs compared to H.264 (Google Open Source Blog, 2015).

Netflix takes a similar approach. They serve H.264 to legacy devices, VP9 to most smart TVs, and AV1 to devices with hardware decode support. Their per-title encoding optimization means each show gets individually tuned bitrate ladders.

[CHART: Pie chart - YouTube codec distribution estimate: H.264 (35%), VP9 (50%), AV1 (15%) - based on YouTube Engineering reports 2024]

The Economics of Multi-Codec Encoding

Encoding in three codecs isn't free. But for platforms serving billions of views, the bandwidth savings dwarf the encoding costs. A rough calculation: encoding a 10-minute video in all three codecs costs about $0.15 in cloud compute. Serving that video to 1 million viewers in AV1 instead of H.264 saves approximately 2 TB of bandwidth, worth $50-100 in CDN costs.

For smaller sites, the math changes. If your video gets 1,000 views, multi-codec encoding might not be worth the complexity. But if you're serving the same video to 100,000+ viewers, AV1 pays for itself quickly.

When Should You Use Each Codec?

H.264 remains the right choice for live streaming, video conferencing, and any scenario requiring universal device support with minimal latency. According to Bitmovin's Video Developer Report, 82% of streaming services still use H.264 as their baseline codec (Bitmovin, 2024).

Use H.264 when:

• You need guaranteed playback on every device, including older smart TVs
• Live streaming or real-time video calls demand low-latency encoding
• Email campaigns or platforms that only accept MP4/H.264
• Quick turnaround matters more than file size

Use VP9 when:

• Targeting web audiences primarily on Chrome, Firefox, and Edge
• You want meaningful file size reduction without extreme encoding time
• WebM container with alpha transparency is needed
• YouTube or web video hosting is your distribution channel

Use AV1 when:

• Bandwidth costs are significant and videos receive high view counts
• You can afford longer encoding times (or have access to SVT-AV1)
• Targeting modern devices with hardware AV1 decode
• Royalty-free licensing is a requirement
• HDR content delivery is a priority

How Do You Encode with FFmpeg for Each Codec?

FFmpeg supports all three codecs out of the box. Here are production-ready commands for 1080p web video, tuned for quality-to-size balance. The CRF (Constant Rate Factor) values below produce roughly equivalent visual quality across codecs.

H.264 (x264)

ffmpeg -i input.mp4 -c:v libx264 -crf 23 -preset medium \
  -pix_fmt yuv420p -movflags +faststart output-h264.mp4

CRF 23 is x264's default and produces good quality at reasonable file sizes. Lower values (18-20) for higher quality, higher values (26-28) for smaller files.

VP9 (libvpx-vp9)

ffmpeg -i input.mp4 -c:v libvpx-vp9 -crf 31 -b:v 0 \
  -row-mt 1 -pix_fmt yuv420p output-vp9.webm

The -b:v 0 flag enables pure CRF mode. The -row-mt 1 flag enables row-based multithreading, which dramatically speeds up VP9 encoding. CRF 31 for VP9 roughly matches CRF 23 for H.264 in visual quality.

AV1 (SVT-AV1)

ffmpeg -i input.mp4 -c:v libsvtav1 -crf 30 -preset 6 \
  -pix_fmt yuv420p -movflags +faststart output-av1.mp4

SVT-AV1 preset 6 balances speed and quality for web content. For maximum compression at slower speed, try preset 4. For faster encoding, preset 8-10 still beats VP9 on compression.

Multi-Codec HTML Fallback

<video autoplay muted loop playsinline>
  <source src="video.av1.mp4" type='video/mp4; codecs="av01.0.05M.08"'>
  <source src="video.vp9.webm" type="video/webm">
  <source src="video.h264.mp4" type="video/mp4">
</video>

Browsers pick the first source they support. This stack serves AV1 to modern browsers, VP9 as a fallback, and H.264 as the universal safety net.

[IMAGE: Terminal window showing FFmpeg encoding output with progress bars for each codec - search terms: ffmpeg terminal encoding video command line]

What's the Future of Video Codecs?

AV1 adoption is accelerating, but it won't be the end of the road. The Alliance for Open Media is already developing AV2, targeting another 30-40% compression improvement over AV1. Meanwhile, the ITU's VVC (H.266) standard promises similar gains but carries the same royalty concerns that plagued H.265/HEVC.

The HEVC licensing debacle, where multiple patent pools demanded separate fees, effectively killed H.265 adoption on the open web. Firefox and Chrome never added H.265 support for web content. VVC risks repeating this pattern. The industry's clear preference for royalty-free codecs suggests AV2 will dominate the next generation, just as AV1 is winning the current one.

Hardware support is the final piece. By 2027, most new devices will include AV1 hardware decode. Apple's inclusion of AV1 decode in M3 and A17 Pro chips was the tipping point (Apple Developer Documentation, 2023). Once AV1 hardware is ubiquitous, there's little reason to encode in H.264 for new content.

But "ubiquitous" takes time. We've found that device replacement cycles mean H.264 will remain necessary as a fallback for at least 3-5 more years. Don't drop it from your encoding pipeline yet.

Frequently Asked Questions

Is AV1 better than H.264 for web video?

AV1 produces files roughly 50% smaller than H.264 at equivalent visual quality (Moscow State University, 2022). The tradeoff is encoding speed, which runs 10-20x slower, and hardware decode support on older devices. For pre-encoded web content with a fallback, AV1 is the better choice.

Why doesn't everyone use AV1 already?

Three reasons: slow encoding, limited hardware decode on older devices, and ecosystem inertia. Encoding a 10-minute 1080p video in AV1 can take 10-30 minutes versus 30 seconds for H.264. Devices manufactured before 2021 generally lack AV1 hardware decode, forcing power-hungry software decoding.

Is VP9 still worth using in 2026?

VP9 remains a strong middle-ground codec. It offers 30-40% compression improvement over H.264 with encoding speeds 3-5x slower rather than 10-20x. YouTube still serves roughly half its traffic in VP9 (YouTube Engineering, 2024). It's especially useful when you need alpha transparency in WebM containers.

Does H.264 require licensing fees?

Yes. H.264 is covered by patents administered through MPEG-LA. Free internet video that's distributed without charge is exempt, but commercial encoders, decoders, and paid streaming services owe royalties (MPEG LA, 2024). AV1 and VP9 are both royalty-free alternatives.

Can I use all three codecs with a fallback?

Absolutely. The HTML <video> element supports multiple <source> tags. List AV1 first, VP9 second, and H.264 last. The browser picks the first codec it supports. This approach delivers the smallest files to modern browsers while maintaining universal compatibility.

Conclusion

The codec landscape in 2026 is straightforward. AV1 delivers the best compression and is royalty-free, making it the top choice for pre-encoded web video. VP9 offers a practical middle ground with good compression and faster encoding. H.264 remains essential as a universal fallback.

For most web projects, the winning strategy is encoding in all three and letting browsers choose. Start with SVT-AV1 at preset 6 for your primary encode, add VP9 and H.264 fallbacks, and use the multi-source HTML pattern. You'll serve the smallest possible files to 92%+ of your audience while maintaining 100% compatibility.

The future belongs to royalty-free codecs. AV2 will eventually succeed AV1, and VVC will likely struggle with the same licensing barriers that sidelined H.265. Invest in AV1 tooling now and you'll be well-positioned for whatever comes next.