Updated November 2026: YouTube's plan to stream AV2 on the web from early 2027, Netflix's AV1 share above a third of VOD, Intel's SVT-AV2 encoder, new AV2 vs HEVC and H.264 answers, and VVC Advance pool growth.
Video Codec Comparison: The Short Answer
Every codec generation cuts the bitrate needed for the same picture by roughly 30–50%. H.264 (2003) is the universal default, H.265 / HEVC (2013) needs about half the bits of H.264 but comes with multi-pool patent licensing, VP9 (2013) reaches a similar saving royalty-free, AV1 (2018) needs about 30% fewer bits than HEVC and VP9 and is royalty-free, and H.266 / VVC (2020) halves HEVC again but plays in no web browser. AV2, whose final 1.0.0 specification AOMedia dated 28 May 2026, is reported at about 30% fewer bits than AV1 in tests from its development group, with no consumer devices decoding it yet as of November 2026; YouTube plans to serve AV2 on the web from early 2027.181928
For a product shipping in 2026, the practical answer is a ladder with no single winner: H.264 for reach, HEVC or AV1 on the top rungs, VP9 as the open-web fallback. VVC belongs in broadcast and closed device fleets. AV2 stays on the roadmap until hardware decoders reach phones and TVs.
Why this matters
If you are picking a codec for a streaming platform, a videoconferencing product, an OTT app, or a surveillance system, this single decision will shape your bandwidth bill, your device coverage, your legal exposure, and the picture quality your customers see for the next five to ten years. Every other choice follows from the codec, from your bitrate ladder and CDN to your DRM and encoder farm. Marketing pages and vendor blogs make every codec sound like the best one, and a clean comparison table cuts through that. This article assumes no prior knowledge: we define every term in plain language before we use it, then walk you through the trade-offs the way an experienced video engineer would.
How to read this article
The comparison table sits at the top of the article so you can grab it and go. Underneath, every column gets its own short section that explains what the column measures and why a number in that column is good or bad. Near the end there is a VVC vs AV1 vs AV2 comparison, a VP9 section, a decision guide, three common mistakes we see Fora Soft clients make, an FAQ, a downloadable one-page version of the table, and a short list of related Learn articles for the columns you want to read more about.
You do not need any prior knowledge of codecs to read this article. If you have time for only one section, read the table and the "Bitrate savings" column underneath it. That column matters most.
Figure 1. The half of the comparison that describes the codecs themselves: when each one arrived, how much bitrate it claims over its predecessor, and the ceilings written into the spec. Read the savings column first, because it is the one that moves your CDN bill.
Figure 2. The half that decides what you can actually ship: who you pay, what plays in the browser, what decodes on silicon, and who is using it in production. A codec that wins Figure 1 and loses this one is not a shipping option yet.
The Six Codecs at a Glance
The main video codecs in use in 2026, oldest first, are MPEG-2 (H.262), H.264 / AVC, H.265 / HEVC, VP9, AV1 and H.266 / VVC. AV2 joins the list as the newest finished specification (May 2026), and VP8 is still common in WebRTC calls.
The codecs in this comparison ship under two parallel naming conventions because they were standardised by two different bodies. The ITU-T (the telecoms standards arm of the United Nations) and the ISO/IEC MPEG committee publish a joint standard under two names: the H-dot number comes from ITU-T and the MPEG name comes from ISO. H.264, H.265, and H.266 are the ones that have both names. The Alliance for Open Media (AOMedia) is a separate industry consortium founded in 2015 by Google, Netflix, Amazon, Cisco, Intel, Microsoft, Mozilla, and later Apple. AOMedia publishes the AV1 specification (and AV2, finalised in May 2026) under a single name and a royalty-free patent policy. Google's VPx family, VP8 and VP9, sits in a third bucket: standardised by Google alone, royalty-free, never blessed by ITU or MPEG. We tell the full story of how these camps formed in A short history of video codecs: from H.120 to AV2.
| Criterion | MPEG-2 (H.262) | H.264 / AVC | H.265 / HEVC | VP9 | AV1 | H.266 / VVC |
|---|---|---|---|---|---|---|
| Year published | 1995 1 | 2003 2 | 2013 3 | 2013 4 | 2018 5 | 2020 6 |
| Governing body | ITU-T + ISO/IEC (joint) | ITU-T + ISO/IEC (joint, JVT) | ITU-T + ISO/IEC (joint, JCT-VC) | Google (open source) | AOMedia | ITU-T + ISO/IEC (joint, JVET) |
| Reference encoders | MainConcept, FFmpeg mpeg2video |
x264, OpenH264, NVENC | x265, HM, NVENC | libvpx-vp9 | libaom, SVT-AV1, rav1e | VVenC, VTM, MainConcept |
| Bitrate savings vs predecessor | baseline | ≈ 50% vs MPEG-2 2 | ≈ 50% vs H.264 3 | ≈ 50% vs H.264 7 | ≈ 30% vs HEVC and VP9 8 | ≈ 50% vs HEVC 9 |
| Max coding block | 16×16 macroblock | 16×16 macroblock (down to 4×4) | 64×64 CTU (down to 4×4) | 64×64 superblock (down to 4×4) | 128×128 superblock (down to 4×4) | 128×128 CTU + multi-type tree |
| Max reference frames | 1–2 | up to 16 | up to 16 (8 active) | 3 active of 8 | 7 named refs | up to 15 |
| Bit depth | 8-bit | up to 14-bit (High 4:4:4) | up to 16-bit | 8 / 10 / 12-bit | 8 / 10 / 12-bit | 8 / 10 / 12-bit (Main 10, Main 12) |
| Chroma | 4:2:0 | 4:2:0 to 4:4:4 | 4:0:0 to 4:4:4 | 4:2:0 to 4:4:4 | 4:0:0 to 4:4:4 | 4:2:0 to 4:4:4 |
| Max resolution | 1920×1152 (High profile) | 4096×2304 (Level 5.2) | 8192×4320 | 8192×4320 | 7680×4320 (Level 6.3) | 16384×8704 |
| Patent model | one pool (MPEG LA / Via LA) | one pool (MPEG LA / Via LA) | three pools, partly consolidated 2025 10 11 | royalty-free | royalty-free (AOMedia) | two pools (Access Advance + Via LA, consolidated 2025) 11 |
| Browser support (2026) | none (legacy only) | universal | Safari + Edge; Chrome via OS hardware decode; Firefox 134+ on Windows via OS hardware decode | Chrome, Firefox, Edge; Safari since 14 | Chrome 70+, Firefox 67+, Edge 121+, Safari 17+ on HW | none native; experimental via WASM |
| HW decode coverage | TV set-top boxes | universal since 2008 | nearly universal since 2018 | Android dominant; Apple from iOS 14 / tvOS 14 | iPhone 15 Pro+, M3 Mac+, Snapdragon 8 Gen 2+, most 2022+ TVs | Brazilian DTV+ receivers; first phones on MediaTek Dimensity 9600 Pro (Sept 2026) 21 |
| Encode complexity (relative) | 1× | 1× | 5–10× | 3–5× | 5–30× (SVT-AV1) to 1,000×+ (libaom) | 7–20× HEVC (VVenC) |
| Use cases dominant in 2026 | digital TV broadcast, DVD legacy | the universal fallback; most internet video | 4K Blu-ray, Apple, premium 4K OTT, Twitch 2K (1440p) | YouTube 4K, Android, fallback for AV1 | Netflix premium, YouTube high-res, Meta short video | Brazil DTV+ broadcast (on air since June 2026); almost no streaming |
| 2026 production deployment | broadcast-only | ≈ 80% of video providers use it 13 14 | ≈ 65% in production, +20% planned 13 | YouTube + Android first-party | ≈ 17% in production, +40% planning 2026 13 | < 1% streaming; growing in broadcast |
Table 1. Side-by-side comparison of MPEG-2, H.264, H.265, VP9, AV1, and H.266. AV2 is compared separately in Table 2 below, because no shipping product decodes it yet. Sources are footnoted in the References section.
The rest of this article goes through each row of the table in plain language and explains what the numbers mean.
Year Published — Why the Birth Year Matters
The year a codec was published is also, roughly, the year the world started shipping hardware decoders for it. Decoder chips are easier and cheaper to build than encoders, so silicon vendors usually add a decoder to their flagship phone or TV chip within 18 to 36 months of a codec being ratified. Once a hardware decoder ships, the codec lives in the wild for at least a decade. Phones from 2014 still play H.264 because their decoder is still inside them.
This is why old codecs do not die. MPEG-2 was ratified in 1995 and is still inside every digital-TV set-top box in the world thirty-one years later. H.264 was ratified in 2003 and remains the most-used video codec on the internet in 2026, twenty-three years after publication. Each new codec gets added on top of the old ones, and the old codec stays as the universal fallback. The Bitmovin annual Video Developer Report shows the same picture year after year: H.264 at the top, HEVC and VP9 in the middle, AV1 climbing fast, and VVC barely visible. 14
In practice, if your audience includes phones, TVs, or browsers older than five years, plan to deliver H.264 as a fallback whichever codec you pick as your primary.
Governing Body — Why the Patent Math Is Set Here
The body that governs a codec decides who pays whom from then on. Three bodies matter.
The ITU-T's Video Coding Experts Group (VCEG) and ISO/IEC's Moving Picture Experts Group (MPEG) are the two formal standards bodies. They produce most of the H-dot codecs jointly: MPEG-2 / H.262, H.264, H.265, and H.266 are all joint products. Their standards are governed by patents owned by member companies. Those companies license their patents through patent pools, administrative bodies that collect royalties and divide them among patent holders. The pool is the legal mechanism that lets you ship a codec without negotiating with each patent holder individually.
The Alliance for Open Media (AOMedia) was founded in 2015 to break out of this loop. Every AOMedia member commits to a royalty-free licence on all essential patents under the AOMedia Patent License 1.0. The result is AV1 and AV2, whose 1.0.0 specification is dated 28 May 2026. You can ship both codecs without paying anyone. The commitment is a real legal one: AOMedia maintains an explicit patent policy and tracks contributor declarations.
Google, separately, released VP8 in 2010 and VP9 in 2013 under a similar royalty-free model. VP8 and VP9 predate AOMedia but seeded the same idea; we cover how VP8 and VP9 work in a separate article. VP9 in particular runs inside YouTube as the default 4K codec for non-AV1-capable devices.
This matters in 2026 because large distributors with deep pockets (Apple, Netflix, Disney+) can absorb patent royalties and ship HEVC, while smaller distributors avoid the pools and ship AV1 instead. The 2025 consolidation in which Access Advance acquired Via LA's HEVC and VVC pool administration shrank three HEVC pools down to two, but did not eliminate the legal uncertainty. Many essential patent holders (Apple, Google, Samsung, Microsoft) remain outside every pool. 11 For VVC the same uncertainty has frozen adoption: in 2026 no streaming service ships VVC at meaningful scale, even though the codec is six years old. In January 2026 Access Advance confirmed that the former Via LA HEVC/VVC pool now runs under its roof as VCL Advance, next to HEVC Advance and VVC Advance.25 By October 2026 Samsung and Sharp had joined VVC Advance as licensors, the pool counted more than 6,000 patents, and its licensees included phone makers holding about 62% of the global smartphone market.30
Bitrate Savings — The Headline Number
This is the most important column in the table. Bitrate savings measures how many fewer bits a new codec needs to deliver the same picture quality. The conventional unit is "percent fewer bits at equivalent perceptual quality", and the conventional measurement method is a Bjøntegaard delta-rate (BD-rate) test, which compares two codecs at matched values of objective quality metrics like Peak Signal-to-Noise Ratio (PSNR) and Structural Similarity Index Measure (SSIM). We cover the metrics themselves in Objective quality metrics: PSNR, SSIM, MS-SSIM, VMAF.
Treat these headline numbers with care. They come from controlled lab tests with reference encoders at their slowest, highest-quality settings, which nobody runs at production scale because they are too slow. Real-world bitrate savings are typically two-thirds to three-quarters of the headline.
Here is the maths, so you can see what a savings number does for you in practice. Suppose you stream a 1080p movie that uses 4.5 Mbps of H.264. HEVC's headline 50% savings means the same quality fits in:
4.5 Mbps × (1 − 0.50) = 2.25 Mbps of HEVC
In real-world production, HEVC delivers more like 30–40% savings on this kind of content, so a realistic target is:
4.5 Mbps × (1 − 0.35) ≈ 2.9 Mbps of HEVC
AV1's headline number is "30% savings vs HEVC and VP9", measured by AOMedia and confirmed by Meta's 2018 production benchmark on a 400-clip Facebook test set, where libaom-AV1 beat libvpx-VP9 by 34% and x264 High by 46.2% on BD-rate against the Visual Multimethod Assessment Fusion (VMAF) quality metric. 8 At Netflix scale, AV1 sessions in 2025 used roughly a third less bandwidth than AVC and HEVC for matched quality. 12
VVC's design target is another 50% reduction relative to HEVC. Independent confirmations from Fraunhofer HHI and the JVET test set agree. 9 That is the largest codec generation step in two decades. With near-zero deployment in 2026, though, you cannot actually use those savings yet.
At scale, a 30% bandwidth saving is a real number. For a streaming service doing 1 petabyte of egress per month, moving from HEVC to AV1 saves roughly 300 terabytes. At typical CDN prices of $0.005 to $0.02 per gigabyte, that comes to $1,500 to $6,000 per month in bandwidth alone, before any quality improvement.
Max Coding Block — Why Bigger Blocks Save Bits
When an encoder compresses a frame, it does not work on the whole frame at once. It cuts the frame into squares and encodes each square separately. The maximum coding block is how big each of those squares is allowed to be.
A bigger maximum block size helps compression for one reason. Large flat regions of the image, such as a blue sky, a wall or the carpet on the floor, can be coded as a single block with one motion vector and one set of transform coefficients. With a small block size, the encoder has to repeat that information for every small square inside the flat region. The metadata an encoder spends on block headers, motion vectors and prediction modes goes down quadratically as block size goes up.
Across the six codecs, block sizes keep growing. MPEG-2 and H.264 both use a macroblock, a 16×16 grid of luma samples plus the corresponding chroma. H.264 lets the macroblock subdivide down to 4×4 for the parts of the frame that need fine detail. HEVC replaced the macroblock with a Coding Tree Unit (CTU) of up to 64×64, four times the maximum size of an H.264 macroblock. The CTU is split recursively with a quadtree down to 8×8, with predictions down to 4×4. VP9 uses a superblock of the same size, 64×64. AV1 doubled it again with a 128×128 superblock, sixteen times the area of a macroblock. VVC reached the same 128×128 ceiling but added a multi-type tree that allows binary and ternary splits on top of the quadtree, so the encoder gets much finer control over block shape.
We unpack how each codec partitions its blocks in Block-based prediction: MBs, CTUs, SBs and superblocks. For this comparison, remember one thing: every doubling of maximum block size has been worth roughly 10–15% of the headline bitrate savings each new codec delivers.
Bit Depth and Chroma — Where HDR Lives
Bit depth is the number of bits an encoder uses to store the value of one pixel sample. 8 bits gives 256 distinct levels of brightness per channel, 10 bits gives 1024, and 12 bits gives 4096. Chroma subsampling sets how many colour samples are stored per brightness sample. 4:4:4 stores full colour. 4:2:2 halves the colour horizontally. 4:2:0 halves it both horizontally and vertically, and most consumer video uses it because the human eye can't see the difference.
High Dynamic Range (HDR) needs 10-bit. So does any production workflow that grades colour and wants to avoid visible banding, the stripes you see across a smooth gradient when there aren't enough quantization levels. We cover banding in detail in Bit depth: 8, 10, 12 bits and the banding problem.
Here is how the codecs compare. MPEG-2 is 8-bit only, which is why nobody uses it for HDR. H.264 supports up to 14-bit in its High 4:4:4 Predictive profile, but the profile that actually ships everywhere is the mass-market High at 8-bit. HEVC, VP9, AV1, and VVC all support 10-bit and 12-bit natively in their mainstream profiles (HEVC Main 10, VP9 Profile 2/3, AV1 High/Professional, VVC Main 10/Main 12). If you ship HDR in 2026, you are picking between HEVC, AV1, VP9 Profile 2 (web and YouTube HDR), and possibly VVC. If you ship anything 8-bit, all six codecs are on the table.
Max Resolution — A Spec Number That Rarely Matters
Every codec lists a maximum resolution it supports: 4096×2304 for H.264 Level 5.2, 8192×4320 for HEVC and VP9, 7680×4320 for AV1 Level 6.3, 16384×8704 for VVC. The numbers are correct and almost never bind in practice. Long before you hit the codec ceiling, you hit decoder level support, meaning how many macroblocks per second your specific chip can decode. A phone chip that says it does HEVC may only do HEVC up to 4K at 60 fps. The codec spec allows 8K. The chip doesn't.
For everyday product decisions, ignore this column unless you're shipping 8K. If you are shipping 8K, your decoder list is short: AV1 on very recent Apple Silicon, HEVC on recent Apple TV and high-end TVs, VVC almost nowhere.
Patent Model — The Column That Decides Your Lawyer's Mood
A codec is a stack of mathematical algorithms, and many of them are covered by patents. To ship a codec product, you must licence the essential patents. How you do that depends on the codec's governing body.
MPEG-2 and H.264 sit under a single, public, capped patent pool administered by MPEG LA (rebranded Via LA in 2023). MPEG LA negotiated a published rate card and a cap. For H.264, internet streaming of free-to-end-user content was zero, and unit royalties on devices were capped at a few cents. The math worked well enough for the codec to dominate.
HEVC went off the rails because three pools formed instead of one: MPEG LA, HEVC Advance (run by Access Advance), and Velos Media, each with its own members, rates and terms. Some major patent holders never joined any pool, which left distributors exposed to surprise infringement claims. Browser vendors stayed out for years; Firefox only added hardware-accelerated HEVC playback on Windows in version 134 (January 2025).24 In the 2025 consolidation, Access Advance acquired Via LA's HEVC and VVC pool administration and brought two of the three pools together. Unpooled patents from Apple, Google, Samsung, Microsoft, and others remain. 11
VVC inherited the same problem in a smaller form. Two pools exist (Access Advance and the former Via LA, now consolidated), some essential holders are outside both, and large streamers have refused to ship the codec at scale. As a result, VVC leads technically and has almost zero deployment.
VP9 and AV1 are royalty-free. AOMedia members commit to royalty-free licensing on essential patents through the AOMedia Patent License 1.0. The legal commitment is real, but a separate patent holder (Sisvel) has set up a private licensing programme over AV1. Large distributors with deep legal teams have so far ignored it, and AOMedia continues to assert that AV1 is royalty-free under its founding terms. The largest streamers (Netflix, YouTube, Meta) ship AV1 in production with no apparent legal slowdown. Smaller distributors should consult counsel.
A simple way to decide: if your business model can absorb a few cents per device, HEVC is fine. If it can't, ship AV1. If you want to avoid legal correspondence entirely, ship VP9 (royalty-free, well-established, no third-party pool).
Figure 3. Three patent regimes. Single-pool codecs are simple to licence; multi-pool codecs are not; royalty-free codecs require an internal patent-policy review but no royalty payments to a pool.
Browser Support — Where Most Internet Video Is Actually Watched
This column tells you whether a codec plays in the browser without a plug-in, on the device you care about, in 2026.
H.264 plays in every browser, on every desktop, on every mobile OS released since 2010. There is no asterisk. Hardware decoders are universal.
HEVC plays in Safari natively (Apple paid the licences for its platform), in Microsoft Edge through Windows OS extensions, and on Chrome only via OS-provided hardware decoders. Chrome itself does not include a software HEVC decoder for licensing reasons. Firefox plays HEVC through the operating system's hardware decoder, on Windows since Firefox 134 (January 2025)24, so support still depends on the GPU and OS. In practice, HEVC is reliable on Apple devices and unreliable on the open web.
VP9 plays in Chrome since version 29 (August 2013), Firefox since March 2014, Edge, and Safari since version 14 (September 2020). It is the closest thing to a universally supported open-web codec besides H.264.
AV1 plays in Chrome since version 70 (October 2018), Firefox since version 67 (May 2019), Edge since version 121 (January 2024), and Safari since version 17 (September 2023) but only on hardware that has an AV1 decoder. Today that means iPhone 15 Pro and newer, M3 Macs and newer, M4 iPad Pro and newer. Older Apple devices on Safari 17 cannot play AV1, because the system has no software fallback. Every product team shipping AV1 has to account for this quirk.
VVC has no native browser support in 2026. Experimental WASM decoders exist but are not production-ready for serious workloads.
For product teams this means: if you are building an in-browser player without flash, your codec choice is H.264 (everywhere), VP9 (most browsers), or AV1 (modern Chrome / Firefox / Edge, plus Apple Silicon Safari 17+). HEVC and VVC are not realistic open-web options.
Hardware Decoder Coverage — The Real Bottleneck on AV1
Software decoders run on the device CPU and burn battery. Hardware decoders run on a dedicated piece of silicon and use a fraction of the power. For mobile and connected-TV video, hardware decode is a requirement. Without it, instead of watchable battery life you get a phone that gets warm in twenty minutes.
The rollout follows the age of each codec. H.264 hardware decoders are universal since roughly 2008. HEVC hardware decoders are universal in the smartphone, set-top, and TV markets since roughly 2018. VP9 hardware decoders ship on most Android devices since 2016 and on Apple platforms since iOS 14 / tvOS 14 / macOS Big Sur in 2020.
AV1 hardware decode is the column where careful product planning still pays off. Apple shipped its first AV1 hardware decoder in the A17 Pro chip (iPhone 15 Pro, September 2023), followed by the M3 family for Macs (October 2023) and the M4 iPad Pro (May 2024). Apple ships no system-wide software fallback, so older Apple devices simply cannot decode AV1. On Android, Qualcomm added AV1 decode (up to 8K60) in the Snapdragon 8 Gen 2 (late 2022)27, and broad flagship coverage arrived with the 8 Gen 3 generation, Google Tensor and recent Samsung Exynos chips. Mid- and low-tier Android SoCs largely lack it. On smart TVs, AV1 hardware decoders are nearly universal on 2022-and-newer Samsung and LG OLED models, and Netflix's certification submissions show 88% of large-screen devices submitted from 2021 to 2025 had AV1, with nearly 100% from 2023 onward. 12
VVC hardware decoders are still rare in consumer SoCs in 2026. Brazil's DTV+ receivers decode it, and MediaTek's Dimensity 9600 Pro (September 2026) is the first phone chip with 8K60 10-bit VVC decode21, but most phones, tablets and TVs still skip the codec. On the software side, Android 17 added VVC to the platform's codec profile list in its first beta (February 2026).31
The practical rule: if you are planning AV1 delivery in 2026, segment your audience by device generation. Modern flagship phones and 2022+ TVs decode AV1 in hardware. Everything else needs an H.264 or HEVC fallback.
Figure 4. Hardware decoder coverage for AV1 across consumer device categories in 2026. The grey part of each bar is the older devices that still need an H.264 or HEVC fallback path.
Encode Complexity — Why Your Encoder Bill Goes Up
Decoding is cheap. Encoding is the hard work. The encoder has to choose, for every block in every frame, the best prediction mode, the best motion vector, the best transform, and the best quantization step from an exponentially large space of possibilities. A more powerful codec has more options to evaluate, so each frame takes more compute.
The numbers in the table are rough, because they depend heavily on which encoder you use and which speed preset. Industry consensus in 2026: x265 (HEVC reference encoder) is roughly 5–10× slower than x264 (H.264) at quality-equivalent presets. libaom-AV1 at its slow presets is famously slow: one measurement put it at 2,500–3,000× slower than x265 on the same hardware for the same clip. SVT-AV1, the Intel-and-Netflix-developed encoder that now dominates production AV1, runs at presets 4–6 at roughly 30–50× faster than libaom while keeping most of the compression gain, bringing AV1 encoding closer to x265 speeds. 15 SVT-AV1 4.0, released in early 2026, extended the CRF range and added finer quarter-step rate control.26 VVenC (the open-source VVC encoder) runs roughly 7–20× slower than x265 depending on preset.
Now the encoding bill. For a VOD service producing thousands of hours of content per month, the encoder cost difference between H.264 and AV1 with SVT-AV1 is real but manageable: a 5–30× cost increase depending on preset, often offset by bandwidth savings. For a live streaming service, the math is different: AV1 live encoding still requires either purpose-built hardware (NETINT ASIC-based encoders, NVIDIA RTX 40-series), an aggressive speed preset (which gives up most of the compression gain), or a CPU farm an order of magnitude larger than the H.264 equivalent. We cover the production trade-offs in Hardware acceleration: GPU, VPU, ASIC.
Use Cases Dominant in 2026 — Who Actually Uses What
Reading the use-cases row of the table answers the practical "what should I pick?" question for the most common workloads.
Digital TV broadcast still uses MPEG-2 on legacy infrastructure and H.264 or HEVC on newer DVB / ATSC pipes. ATSC 3.0, the modern North-American broadcast standard, uses HEVC. Brazil's DTV+ is the only national broadcast standard built around VVC; Globo began commercial DTV+ broadcasts in São Paulo, Rio de Janeiro and Brasília for the 2026 FIFA World Cup, with VVC carrying 1080p and VVC plus MPEG-5 LCEVC carrying 2160p (June 2026). 1720
Premium 4K OTT (Netflix, Disney+, Amazon Prime Video 4K, Apple TV+) ships HEVC for the bulk of 4K content, with AV1 layered on top for AV1-capable devices. Netflix announced in December 2025 that AV1 powers about 30% of all its streaming and is on track to become its number-one codec. 12 By September 2026 Netflix put AV1 at more than a third of its global VOD streaming and named AV2 as its next-generation streaming codec; Prime Video says it will help deploy AV2.29
Mass-market OTT, AVOD, SVOD ships H.264 as the base ladder rung, HEVC on top for premium tiers and Apple devices, and AV1 for modern devices when the platform has rolled it out. NETINT's 2026 State of Video Encoding survey puts AV1 in production at about 17% of video providers, with another 40% planning it during 2026.13
YouTube ships AV1 for popular and high-resolution content on AV1-capable devices (8K is AV1-only), VP9 for most 4K and desktop delivery, and H.264 universally as the compatibility fallback. Every YouTube upload gets transcoded to all three. As of 19 March 2026 more than 90% of YouTube's catalogue, weighted by watch time, was available in AV1, and YouTube engineering director Des Keane said AV2 streams will reach the web as soon as early 2027.28
Twitch keeps H.264 for 1080p and below. On 17 June 2026 it began rolling out 2K (1440p) streams for Partners and Affiliates, and those use HEVC at up to 9 Mbps through Enhanced Broadcasting; AV1 is still not part of the public rollout.23 16
Surveillance and conferencing ship H.264 first and HEVC second; AV1 is rare in real-time use because the encoder math is hard. WebRTC stacks are starting to ship AV1, but H.264 and VP8 are still the universal default.
H.266 (VVC) vs AV1 vs AV2: The Next-Generation Codecs Compared
Short answer: on compression, VVC and AV2 are in the same class and both sit about one generation ahead of AV1. On deployment, AV1 wins in 2026: it plays in browsers and on most recent flagship phones and TVs, VVC is on air in Brazilian broadcast and in the first phone chip but in no browser, and AV2 is a finished specification with no consumer devices yet.
The arithmetic from Table 1: VVC needs about 50% fewer bits than HEVC and AV1 about 30% fewer, so VVC needs roughly 0.50 / 0.70 ≈ 0.71 of AV1's bitrate, about 29% less. AV2 is reported at about 30% below AV1 in tests from its own development group; independent results are still pending.19
| Criterion | AV1 | H.266 / VVC | AV2 |
|---|---|---|---|
| Final specification | March 2018 | July 2020 | 28 May 2026 (v1.0.0) |
| Governing body | AOMedia | ITU-T + ISO/IEC (JVET) | AOMedia |
| Bitrate vs AV1 at equal quality | baseline | ≈ 29% less (from headline figures) | ≈ 30% less (development-group tests, 2026) |
| Patent model | royalty-free; Sisvel runs a separate pool | Access Advance pools (VVC Advance, VCL Advance) plus holders outside any pool | royalty-free |
| Browser playback (Nov 2026) | Chrome, Firefox, Edge; Safari on AV1 hardware | none | none shipped; Google demonstrated AV2 playback in Chrome (Oct 2026) |
| Hardware decode (Nov 2026) | most 2022+ TVs, iPhone 15 Pro and later, M3+ Macs, Snapdragon 8 Gen 2+ | Brazilian DTV+ receivers, MediaTek Dimensity 9600 Pro | decoder IP cores announced (Allegro DVT, Chips&Media, VeriSilicon); no consumer devices |
| Main software | SVT-AV1 4.0, libaom, rav1e | VVenC, VTM | AVM reference (libavm), dav2d decoder in progress, SVT-AV2 encoder in development (Intel) |
| Production use | about 30% of Netflix streaming (Dec 2025), YouTube, Meta | Brazil DTV+ broadcast since June 2026 | none yet |
| Pick it for | internet streaming today | broadcast, 8K, closed device fleets | roadmap: test now, ship when devices decode it |
Table 2. AV1, H.266 / VVC and AV2 as of November 2026. Sources: AOMedia AV2 release, Netflix TechBlog, Access Advance, V-Nova and the footnotes in the References section.
Both camps already have a next step. AOMedia finished AV2 in May 2026, and ITU-T and ISO/IEC issued a joint call for proposals for a codec beyond VVC in July 2026, with responses evaluated in January 2027 and a new standard targeted by 2029.22 For the full picture of each codec, read H.266 / VVC explained and what to expect from AV2 through 2031.
AV2 vs HEVC, AV2 vs H.264 and AV1 vs AV2
Short answer: on headline figures AV2 needs about 30% fewer bits than AV1, roughly half the bits of H.265 / HEVC and about a quarter of the bits of H.264 for the same picture. In November 2026 that saving is still on paper for viewers: no consumer device decodes AV2, while HEVC and H.264 play almost everywhere.
We chain the headline numbers from Table 1 and Table 2. AV1 needs about 0.70 of HEVC's bitrate and AV2 about 0.70 of AV1's, so AV2 needs 0.70 × 0.70 ≈ 0.49 of HEVC, about 51% less. HEVC needs about 0.50 of H.264, so AV2 needs 0.49 × 0.50 ≈ 0.25 of H.264, about 75% less. Every link in that chain is a lab result with slow reference encoders, so production savings will be smaller, and so far AV2 has only been measured by its own development group.19
| Pair | AV2 bitrate at equal quality (headline) | What decides it in 2026 |
|---|---|---|
| AV2 vs AV1 | ≈ 30% less | AV1 plays in browsers and on recent hardware; AV2 has no consumer decoders yet |
| AV2 vs H.265 / HEVC | ≈ 51% less | HEVC is the 4K and Apple workhorse but carries pool licensing; AV2 is royalty-free |
| AV2 vs H.264 / AVC | ≈ 75% less | H.264 is the universal fallback and stays in every ladder |
Table 3. AV2 against the codecs it is most often compared with, from chained headline figures. Real-world savings on production presets are typically two-thirds to three-quarters of these.
In practice, AV2 does not replace HEVC or H.264 in a ladder. Once devices decode it, it will sit on the top rung above AV1. YouTube is the first service with a date (AV2 on the web from early 2027), and AV1 and AV2 are expected to run side by side for years.28
VP9 vs H.264 and VP9 vs H.265
Short answer: VP9 needs about half the bitrate of H.264 for the same quality and lands in the same compression class as H.265 / HEVC, while staying royalty-free.7 Pick VP9 over H.264 for 1080p and 4K delivered to browsers and Android; pick HEVC over VP9 when Apple devices, smart TVs or broadcast are your main screens.
VP9 vs H.264. H.264 still wins on reach: every browser, every device since about 2010 and cheap real-time encoding. So VP9 is a top-rung addition to an H.264 ladder, not a replacement. VP9 vs H.265. Compression is close. What differs is where each one plays. VP9 runs natively in Chrome, Firefox, Edge and Safari 14+, while HEVC is reliable on Apple platforms and elsewhere depends on OS hardware decoders. For new builds in 2026, AV1 has taken over VP9's role as the royalty-free top rung, and VP9 stays as the fallback for devices without AV1 decode.
A Decision Guide in Six Questions
You should be able to read the table in one pass. For a faster route to a decision, work through these six questions in order.
- Are you shipping into a TV broadcast pipe? If yes and the pipe is in Brazil, pick VVC. If yes anywhere else, pick HEVC for new builds and MPEG-2 only for legacy compatibility.
- Do you have to support phones older than 2018? If yes, your base codec is H.264. Everything else layers on top.
- Do you need HDR or 10-bit content? If yes, your codec list is HEVC, AV1, VP9 Profile 2 for web HDR, or (in narrow contexts) VVC.
- Are you a small-team distributor who cannot absorb HEVC licence risk? If yes, ship AV1 and VP9 instead. Use H.264 as the fallback. For the rest of the stack around that choice (protocols, CDN, player), see our video streaming technology stack guide.
- Are you running live streaming? If yes, your real-time encoder choice is H.264 or HEVC. AV1 live is possible on dedicated hardware but expensive. VVC live is not realistic in 2026.
- Are you targeting 8K? If yes, your only practical options are AV1 (on Apple Silicon and recent flagships) or HEVC (where the device chain supports it). VVC's 16K theoretical ceiling does not translate into ship-able product yet.
Three Common Mistakes Product Teams Make
Mistake 1: Picking a single codec. None of the production platforms we've shipped uses a single codec. The right answer is a ladder of codecs, H.264 plus one or two newer ones, and the player picks among them at request time based on device capability and network conditions. That is what Adaptive Bitrate streaming (ABR) is for. We unpack the mechanics in Adaptive bitrate streaming: how it really works.
Mistake 2: Reading the headline savings number as a guarantee. When AOMedia or Fraunhofer publishes a "50% savings" number, it comes from a reference encoder on its slowest preset, in curated lab conditions. Real-world production with fast presets delivers two-thirds to three-quarters of the headline. Budget your bandwidth on the realistic number rather than the marketing one.
Mistake 3: Picking VVC for "future-proofing". Several Fora Soft clients in 2024–2025 asked whether they should pick VVC as a forward-looking choice. In 2026 our answer is still no. VVC has almost no hardware decoder coverage in consumer devices and no native browser support, and on headline figures it compresses only about 29% better than AV1 while its deployment is much weaker. The forward-looking pick in 2026 is AV1 today and AV2 once decoders ship in devices. Its specification was finalised in May 2026, but as of November 2026 only decoder IP cores have been announced, and the first large rollout on the calendar is YouTube on the web in early 2027.18
Frequently Asked Questions
H.264 vs H.265 vs H.266: which is better?
In lab tests H.265 needs about 50% fewer bits than H.264, and H.266 about 50% fewer than H.265, at the same quality. In 2026 H.264 is still the safest for reach, H.265 is the choice for 4K and Apple devices, and H.266 fits only broadcast and closed fleets because no browser plays it.
How does H.264, HEVC and VVC licensing compare?
H.264 is licensed through one Via LA pool with published caps and no royalty on free-to-viewer internet streaming. HEVC and VVC are split across several pools, now mostly under Access Advance (HEVC Advance, VVC Advance and the former Via LA pool, renamed VCL Advance), and some major patent holders license outside any pool. For how the licensing math changes the codec set an OTT service ships, see our codec strategy for OTT.
Is H.266 (VVC) better than AV1?
VVC compresses roughly 29% better than AV1 on headline figures, but AV1 is royalty-free and plays in Chrome, Firefox, Edge and Safari on AV1 hardware, while VVC plays in no browser. For internet streaming AV1 is the better choice in 2026; VVC wins in broadcast, 8K and closed device fleets. The full H.266 vs AV1 breakdown sits in our VVC article.
VVC vs AV2: which should I plan for?
Both sit about a generation ahead of AV1: AV2 is reported at about 30% below AV1, and VVC at about 29% below on headline figures. VVC is the option for broadcast today; AV2 is royalty-free and the likelier successor to AV1 for web streaming, but no consumer device decodes it as of November 2026.
Is there an SVT-AV2 encoder?
It is in development: Intel is building SVT-AV2 as an open-source AV2 encoder and demonstrated it at IBC 2026 (September), but as of November 2026 there is no production release. The public AV2 software today is the AVM reference codebase (libavm) and the dav2d decoder project.29
How much better is AV2 than HEVC and H.264?
On headline figures AV2 needs roughly half the bitrate of H.265 / HEVC and about a quarter of the bitrate of H.264 for the same quality. Those numbers come from chaining lab results (about 30% below AV1, AV1 about 30% below HEVC, HEVC about 50% below H.264), so expect less on production presets, and no consumer device decodes AV2 yet.
Is VP9 better than H.264?
On compression, yes: VP9 needs about half the bitrate of H.264 for the same quality and is royalty-free. On reach, no: H.264 plays on every device and encodes far faster, so production ladders keep H.264 and add VP9 or AV1 on top.
What is the best video codec in 2026?
There is no single best codec; ship a ladder. Use H.264 for universal reach, AV1 for royalty-free efficiency on modern devices, HEVC for Apple and 4K TV, and VP9 as the open-web fallback.
Free download: Codec Comparison Cheat SheetThe whole comparison on one A4 page: MPEG-2, H.264, H.265, VP9, AV1 and H.266 with bitrate savings, patent model, browser and hardware support, and where each one ships in 2026.Where Fora Soft Fits In
We've shipped video products for two decades, and codec choice is one of the first decisions we make on every new project. For an OTT platform launching in 2026 we typically ship a three-codec ladder: H.264 as the universal fallback, HEVC for premium 4K on Apple devices, and AV1 for modern Chrome / Firefox / Edge and recent Apple Silicon Safari, with device-side capability detection deciding which manifest the player asks for. For a WebRTC conferencing product we still default to H.264 and VP8 and enable AV1 selectively on the devices that can encode it efficiently. For a video surveillance platform we usually pick H.264 plus HEVC, because the recorder hardware in this market still standardises on those two. We've delivered video streaming, OTT/Internet TV, WebRTC conferencing, telemedicine, e-learning, and AR/VR projects across all of these stacks, and we read codec choices the same way this article does: as engineering trade-offs rather than vendor pitches. For streaming products, our OTT and Internet TV developers build the multi-codec ladder end to end; for camera fleets, our video surveillance software team matches codecs to the recorders and storage budget you already have. When the work is the encoding pipeline itself (ladder design, SVT-AV1 or hardware encoders, quality measurement on your own content), our video encoding and processing engineers build and benchmark it.
The book
Video Encoding: A Complete Guide to Video Compression
Every column of the table above gets a chapter here: what a coding block is and why a 128×128 superblock saves bits, where bit depth and chroma subsampling change the picture you actually see, and how a bitrate-savings number is measured — which is why the 50 per cent headline shrinks when you switch to a production preset. The codec chapters take MPEG-2, H.264, HEVC, VP9, AV1 and VVC one at a time, and the rate-control and quality-metric chapters give you the arithmetic to run this comparison on your own content instead of trusting anyone else's table. It is volume 1 of the seven-volume Fora Soft Video Engineering Handbook, which walks the whole video stack from the pixel to production. 1,522 pages, written by Nikolay Sapunov, CEO at Fora Soft.
Which codecs should your 2026 ladder actually carry?
Send us your device and player analytics, your current bitrate ladder and your CDN bill, and we will come back with three numbers on your own traffic: the share of your audience that decodes AV1 on silicon today, what HEVC or AV1 on the top rungs is worth against your actual egress, and what the extra encode time costs on your transcode farm. If you are shipping live rather than VOD, we run the same arithmetic against real-time encoder budgets instead, because that is where AV1 stops being free. 250+ video products shipped since 2005.
See our case studies
Case study
Speed.Space
Live 1080p at 8 Mb/s for production clients including Netflix, EA and HBO. This is mistake 1 from the section above answered in production: the ladder carries H.264 for reach and a newer codec on the top rungs, and the player picks per device.
Case study
Worldcast Live
Concert streaming at 1.5 Gb/s with 0.4–0.5 s latency to 10,000 simultaneous viewers. Live is where the encode-complexity column bites: at that latency budget the codec choice is made by what a real-time encoder can finish, not by what compresses best.
Case study
Mindbox
RTSP cameras through FFmpeg to HLS, 50+ deployments. The hardware-decode column decides this one before anyone opens a spec: the cameras emit H.264, so H.264 is the codec, whatever the comparison table says about the newer three.
What to read next
Codecs
AV1: The New Internet Standard And Where It Stands In 2026
The row with the most movement in it: how far AV1 hardware decode has really spread, and what the encode still costs you.
Codecs
H.265 / HEVC: +50% Over H.264 And The Patent Nightmare
The long version of the patent column: how three pools formed, what consolidation changed in 2025, and when HEVC is still the right pick.
Tooling
Hardware Acceleration: GPU, VPU, ASIC
What NVENC, QuickSync, VideoToolbox and NETINT ASICs change about the encode-cost arithmetic behind the comparison.
Quality
Objective Quality Metrics: PSNR, SSIM, MS-SSIM, VMAF
How a bitrate-savings number is measured, so you can run the comparison on your own content instead of trusting a table.
-
ITU-T H.262 / ISO/IEC 13818-2, Generic coding of moving pictures and associated audio information: Video (MPEG-2 Part 2). First edition published 1995. Wikipedia summary. Accessed 2026-05-16. ↩
-
ITU-T H.264 / ISO/IEC 14496-10, Advanced Video Coding. First edition approved March 2003, published May 30, 2003. Wikipedia: Advanced Video Coding. Accessed 2026-05-16. ↩↩
-
ITU-T H.265 / ISO/IEC 23008-2, High Efficiency Video Coding. Ratified January 2013, published June 2013. Wikipedia: High Efficiency Video Coding. Accessed 2026-05-16. ↩↩
-
VP9 bitstream specification (Google, 2016). VP9 Bitstream Specification. Released June 2013; Chrome 29 (August 2013), Firefox (March 2014), Safari 14 (September 2020). Accessed 2026-05-16. ↩
-
Alliance for Open Media, "AV1 Roadmap". AV1 bitstream specification 1.0 frozen 28 March 2018. AV1 Roadmap (AOMedia). Accessed 2026-05-16. ↩
-
ITU-T H.266 / ISO/IEC 23090-3, Versatile Video Coding. Finalised 6 July 2020 by JVET; version 3 published September 2023. Wikipedia: Versatile Video Coding. Accessed 2026-05-16. ↩
-
Mukherjee et al., "A Technical Overview of VP9" (Google, 2015) — VP9 design targets and ≈ 50% reduction vs H.264 in BD-rate tests. Accessed 2026-05-16. ↩↩
-
David Ronca, "AV1 beats x264 and libvpx-VP9 in practical use case", Meta / Facebook Engineering, 2018. AV1 beat libvpx-vp9 by 34% and x264 High by 46.2% on BD-rate against VMAF on a 400-clip Facebook test set. Meta Engineering blog. Accessed 2026-05-16. ↩↩
-
Fraunhofer HHI, "H.266 / VVC". Design target: ≈ 50% bitrate reduction vs HEVC at equal subjective quality. Fraunhofer HHI VVC page. Accessed 2026-05-16. ↩↩
-
"Video Coding and Related Patent Licensing Pools — Beginner's Guide", Sagacious IP, 2024. Sagacious IP overview. Accessed 2026-05-16. ↩
-
"Access Advance Acquires Via Licensing Alliance's HEVC/VVC Patent Pools" (December 2025) — consolidation of two of the three HEVC pools and both VVC pools. IP Fray report. Accessed 2026-05-16. ↩↩↩↩
-
Netflix Technology Blog, "AV1 — Now Powering 30% of Netflix Streaming" (December 2025). Streaming Media Blog summary of the Netflix post. Accessed 2026-05-16. ↩↩↩
-
NETINT, "2026 State of Video Encoding" survey (286 respondents). H.264 ≈ 80% production deployment; HEVC ≈ 65% production + 20% planned; AV1 17% production + 40% planning. NETINT 2026 State of Video Encoding. Accessed 2026-05-16. ↩↩↩↩
-
Bitmovin, 8th Annual Video Developer Report 2024/2025 (167 respondents, 34 countries). H.264 ≈ 79% use; HEVC ≈ 49%; AV1 stagnant in deployment but #1 in planned adoption. Streaming Learning Center summary of the Bitmovin report. Accessed 2026-05-16. ↩↩
-
Streaming Learning Center, "SVT-AV1 vs libaom". SVT-AV1 at presets 4–6 runs ~30–50× faster than libaom while keeping most of the compression gain. SVT-AV1 vs libaom. Accessed 2026-05-16. ↩
-
NVIDIA, "Twitch Multi-Encode AV1 Live Streaming". Twitch Enhanced Broadcasting beta supports HEVC and AV1 on RTX 40-series; mainstream AV1 rollout pending broader device decode penetration. NVIDIA blog. Accessed 2026-05-16. ↩
-
ATSC, "Brazil Officially Adopts ATSC 3.0 Technologies For Its Next-Generation Television System" (27 August 2025). TV 3.0 / DTV+ adopts VVC as primary codec with LCEVC enhancement; commercial launch timed to the 2026 FIFA World Cup. ATSC announcement. Accessed 2026-05-16. ↩
-
Alliance for Open Media, "Alliance for Open Media Releases AV2 Codec" (June 2026). AV2 Bitstream & Decoding Process Specification v1.0.0 dated 28 May 2026; reference software libavm, dav2d decoder in progress. AOMedia press release. Accessed 2026-10-14. ↩↩
-
heise online, "AV2 saves 30 percent bitrate compared to AV1" (2026). About 30% lower bitrate than AV1 at comparable quality, from evaluations within the AV2 development group; independent comparisons pending. heise report. Accessed 2026-10-14. ↩↩↩
-
V-Nova, "DTV+ goes live in Brazil with MPEG-5 LCEVC" (11 June 2026); SET, "Copa do Mundo 2026 marca início da operação comercial da DTV+" (August 2026) — Globo in São Paulo, Rio de Janeiro and Brasília. V-Nova announcement. Accessed 2026-10-14. ↩
-
FoneArena, "MediaTek Dimensity 9600 Pro specifications" (September 2026): 8K60 10-bit VVC decode. FoneArena. Accessed 2026-10-14. ↩↩
-
ITU, "Beyond VVC: Call for proposals on future video coding" (28 July 2026). Registration August 2026, evaluation at the January 2027 JVET meeting, standard targeted by 2029. ITU Hub. Accessed 2026-10-14. ↩
-
Twitch Blog, "Introducing Dual Format and 2K Streaming on Twitch" (17 June 2026). 1440p uses HEVC at up to 9 Mbps; 1080p and below use AVC. Twitch Blog. Accessed 2026-10-14. ↩
-
Mozilla, Firefox 134.0 release notes (7 January 2025): hardware-accelerated HEVC playback on Windows. Firefox release notes. Accessed 2026-10-14. ↩↩
-
Access Advance, "Access Advance Closes 2025 with Record Quarter" (22 January 2026): former Via LA HEVC/VVC pool renamed VCL Advance; HEVC Advance 120+ licensees. Access Advance press release. Accessed 2026-10-14. ↩
-
Alliance for Open Media, "SVT-AV1 4.0 Boasts Major API Updates" (March 2026). AOMedia blog. Accessed 2026-10-14. ↩
-
DisplayDaily, "Qualcomm Snapdragon 8 Gen 2 Supports 8K60p AV1 Decoding" (November 2022). DisplayDaily. Accessed 2026-10-14. ↩
-
Alliance for Open Media, "Alliance for Open Media Sees Rapid AV2 Adoption Across the Video Ecosystem Just Four Months After Release" (22 October 2026): YouTube engineering director Des Keane (AV2 on the web as soon as early 2027; over 90% of YouTube's catalogue by watch time in AV1 as of 19 March 2026), Google Chrome AV2 playback demo, Intel SVT-AV2. AOMedia press release; coverage: TV Tech, 27 October 2026. Accessed 2026-11-15. ↩↩↩
-
Alliance for Open Media, "Alliance for Open Media Members Showcase AV2 Ecosystem Developments at IBC 2026" (9 September 2026): Netflix (AV1 above a third of global VOD streaming; AV2 as its next-generation streaming codec), Prime Video, Intel SVT-AV2 open-source encoder demo. AOMedia press release. Accessed 2026-11-15. ↩↩
-
SVG, "VVC adoption advances as mobile hardware support expands" (9 October 2026): Samsung and Sharp join VVC Advance as licensors; 6,000+ patents; licensees with about 62% of the smartphone market. Sports Video Group. Accessed 2026-11-15. ↩
-
ip fray, "Breakthrough for VVC as Google implements video standard in Android 17" (17 February 2026), citing the Android 17 beta 1 release (13 February 2026) and VVC entries in MediaCodecInfo.CodecProfileLevel. ip fray. Accessed 2026-11-15. ↩
