What Is H.266 (VVC)? The Versatile Video Coding Codec Explained

By Hieu Dinh

What Is H.266 (VVC)? Versatile Video Coding Explained

Every few years, the video industry produces a new codec that promises to cut file sizes roughly in half while preserving quality. H.266, better known by its formal name Versatile Video Coding (VVC), is the latest entry in that lineage — the direct successor to HEVC (H.265). On paper, it's a remarkable engineering achievement: about 50% better compression than HEVC at the same visual quality. In practice, its path to real-world use has been anything but smooth.

If you've heard the term h266 floating around discussions of 8K streaming, next-generation broadcast, or future-proof archival formats and wondered what it actually means for you, this guide breaks it down. We'll cover what VVC is, who created it, how it improves on HEVC, why licensing keeps holding it back, where hardware and software support stand in 2026, and how it stacks up against the royalty-free AV1 codec.

If you're new to the topic, our primer on what a video codec is explains the fundamentals that make the rest of this article easier to follow.


What Is H.266 / VVC?

H.266, or Versatile Video Coding, is a video compression standard finalized in July 2020 by the Joint Video Experts Team (JVET) — a collaboration between the ITU-T Video Coding Experts Group and the ISO/IEC MPEG group. This is the same joint standardization structure that produced H.264/AVC and H.265/HEVC before it. Much of the core research and development came out of the Fraunhofer Heinrich Hertz Institute (HHI) in Germany, which has long been central to the MPEG codec lineage.

The "versatile" in the name is deliberate. Where earlier codecs were optimized primarily for conventional camera-captured video, VVC was designed from the outset to handle a much wider range of content within a single standard:

  • High resolutions — 4K and 8K video, where the efficiency of older codecs breaks down
  • High Dynamic Range (HDR) and wide color gamut content
  • 360-degree and immersive video for VR and panoramic applications
  • Screen content — text, UI, and computer-generated graphics with sharp edges
  • Adaptive streaming with resolution changes mid-stream

The headline number is the one that matters most: at the same subjective visual quality, VVC produces files roughly 50% smaller than HEVC. That's the same generational leap HEVC delivered over H.264, applied one rung higher up the ladder.


How H.266 Improves on HEVC

The 50% efficiency gain doesn't come from a single trick. VVC is a toolbox of incremental improvements, each squeezing out a bit more compression at the cost of significantly more computational work. Here are the most consequential changes over HEVC.

Larger, More Flexible Block Partitioning

HEVC introduced the Coding Tree Unit (CTU) with variable block sizes up to 64×64 pixels — a major improvement over H.264's fixed 16×16 macroblocks. VVC extends this substantially. It supports CTUs up to 128×128 pixels and, more importantly, introduces a multi-type tree partitioning scheme that can split blocks not just into quarters (quadtree) but also into halves using binary and ternary splits, both horizontally and vertically.

This flexibility lets the encoder match block boundaries to the actual structure of the image far more precisely. Large uniform areas get large blocks; regions with fine detail or diagonal edges get partitions shaped to fit them. For high-resolution 4K and 8K content especially, this partitioning freedom is a major source of VVC's efficiency.

Improved Intra and Inter Prediction

VVC expands the number of intra-prediction directional modes and adds tools like matrix-based intra prediction and cross-component prediction that use already-decoded parts of a frame to predict the rest more accurately. On the inter-prediction side — predicting motion between frames — VVC adds affine motion compensation, which models rotation and zoom rather than just simple translation, plus more sophisticated motion vector coding. Better prediction means smaller residuals to encode, which means smaller files.

Better Handling of 4K, 8K, HDR, and 360 Content

Because VVC was designed with these formats as first-class targets rather than afterthoughts, it includes dedicated tools for them: adaptive loop filtering to reduce artifacts at high resolutions, features tuned for the wide brightness range of HDR, and support for the geometric distortions inherent in 360-degree projections. The result is a codec that scales gracefully into the resolution and format territory where HEVC starts to strain.

The cost of all this is encoding complexity. VVC encoding is dramatically more computationally intensive than HEVC — often an order of magnitude or more — which has direct consequences for how and where it can realistically be deployed.


The Licensing Problem: H.266's Biggest Obstacle

If VVC is so technically strong, why isn't it everywhere? The answer, more than any technical limitation, is licensing.

HEVC's rollout was famously hampered by a fragmented patent landscape. Instead of a single, clear licensor, HEVC royalties were spread across multiple patent pools — MPEG LA, HEVC Advance (now Access Advance), and Velos Media — with inconsistent and sometimes overlapping terms. Some patent holders operated outside any pool entirely. This uncertainty made companies wary of committing, and it's a major reason Google and Mozilla refused to implement HEVC on the web, backing the royalty-free AV1 instead.

VVC inherited this problem and, in some respects, amplified it. Multiple licensing administrators have emerged for the VVC patent pool, and clarity around total royalty cost and terms has been slow to materialize. For a device manufacturer or streaming platform deciding whether to invest in VVC, that uncertainty is a serious deterrent. The technical merits are clear; the business risk is not.

This licensing friction is the single biggest reason VVC adoption has lagged despite its performance. It's the same dynamic that shaped the AV1 vs H.265 debate, now playing out one generation later — except the royalty-free alternative (AV1) already exists and already has momentum.


Hardware and Software Support in 2026

For any codec, real-world usefulness depends on whether devices can actually decode it efficiently. This is where VVC's story gets difficult.

Hardware decode support in 2026 is extremely limited. Unlike HEVC, which by now is baked into virtually every phone, GPU, smart TV, and SoC shipped in the last decade, VVC hardware decoders are rare. A handful of newer chipsets and select broadcast equipment support it, but consumer penetration is minimal. Critically, Apple provides no VVC support at all — not in hardware via VideoToolbox, not in software through QuickTime or the system frameworks. iPhones, iPads, and Macs cannot decode H.266 natively.

Without hardware decode, playback falls to software decoders running on the CPU, which is power-hungry and impractical for battery-powered devices or high-resolution content. The two most prominent open-source implementations both come from Fraunhofer:

  • VVenC — an optimized VVC encoder that makes software encoding more feasible than the reference encoder, though still far slower than HEVC
  • VVdeC — a real-time-capable VVC decoder that runs on general-purpose CPUs

These tools make VVC usable for experimentation, research, and specialized workflows, but software-only decoding is not a foundation for mass-market streaming. Until hardware decoders are widespread, VVC playback remains a niche capability.

For context on how mature codec support looks by comparison, our HEVC codec explained guide details just how broadly H.265 is supported — the bar VVC has to clear.


H.266 vs H.265 vs AV1: Full Comparison

Here's how VVC stacks up against the codec it succeeds (HEVC) and its royalty-free rival (AV1).

FeatureH.266 / VVCH.265 / HEVCAV1
Standardized2020 (JVET / MPEG / ITU)2013 (MPEG / ITU)2018 (Alliance for Open Media)
Compression vs HEVC~50% betterBaseline~30–50% better
Encoding complexityVery highModerateHigh
Hardware decode (2026)Very limitedBroad (2015+ devices)Growing (2020+ devices)
Hardware encode (2026)Almost noneBroadLimited (newest chips)
Apple / macOS supportNoneFull (VideoToolbox)Decode only (M1+)
LicensingPaid (fragmented pools)Paid (multiple pools)Royalty-free
Software toolsVVenC / VVdeCMature (x265, hardware)libaom, SVT-AV1, dav1d
Primary use todayBroadcast trials, researchApple ecosystem, captureWeb streaming (YouTube, Netflix)
Max resolution8K+8K8K+
HDR supportYesYesYes

The table tells the strategic story clearly. VVC and AV1 land in roughly the same compression-efficiency neighborhood — both about 50% better than HEVC — but they diverge sharply on licensing and momentum. AV1 is free to implement and already deployed at massive scale by YouTube, Netflix, and other platforms. VVC is technically excellent but commercially encumbered.


How Does H.266 Compare to AV1?

This is the comparison that matters most for VVC's future, so it's worth expanding.

On raw compression, the two are close. Both deliver roughly 50% improvement over HEVC, with results varying by content type and encoder settings. In some tests VVC edges ahead, particularly on high-resolution and screen content where its versatile tooling shines; in others, a well-tuned AV1 encode is competitive or better. Neither has a decisive, across-the-board efficiency advantage.

On licensing, they could not be more different. AV1 was created specifically to be royalty-free — the Alliance for Open Media's member companies (Google, Netflix, Amazon, Microsoft, Apple, Meta, Intel, and more) committed to not charging royalties for AV1 implementations. VVC, by contrast, carries the same paid, fragmented patent-pool model that has dogged the MPEG codec family for years.

For any organization operating at scale, that difference is decisive. When two codecs offer comparable compression and one is free while the other carries uncertain per-device and per-stream royalties, the economics point overwhelmingly toward the free option. This is precisely why the industry's largest video distributors have thrown their weight behind AV1 rather than VVC.

VVC's most plausible foothold is in domains where AV1 has less presence and where licensing can be negotiated as part of larger contracts — broadcast television, professional distribution, and certain 8K applications — rather than in mainstream web streaming, where AV1 has already won the momentum battle.

To understand the codec generations underneath all this, our guides on HEVC vs H.264 and what the AV1 codec is fill in the history.


What This Means for Mac Users: How Compresto Helps

Here's the practical bottom line for anyone working with video on a Mac in 2026: H.266 is not a usable option today.

Apple provides no H.266 support anywhere in macOS — no hardware decode, no software decode through the system frameworks, no encode path in VideoToolbox. You cannot play a VVC file in QuickTime, and you cannot export one through any Apple-native pipeline. Any VVC work on a Mac requires third-party software tools like VVdeC running entirely on the CPU, which is slow, power-hungry, and impractical for everyday compression.

That leaves HEVC (H.265) as the practical choice for Mac video compression — and it's a genuinely good one. HEVC is hardware-accelerated on every Apple Silicon Mac through the dedicated media engine in VideoToolbox. It plays natively across every Apple device, delivers roughly 50% smaller files than H.264, and encodes at near-real-time speeds.

Compresto is built around exactly this reality. It uses Apple's VideoToolbox framework for hardware-accelerated HEVC encoding, so a 10-minute 4K video compresses in a few minutes on an M-series Mac, producing a file dramatically smaller than the original with no perceptible quality loss. Rather than chasing codecs your devices can't play, Compresto gives you fast, hardware-accelerated results in a format that works everywhere in the Apple ecosystem today.

If your workflow involves professional formats, our guide on what ProRes is explains where high-bitrate editing codecs fit alongside delivery codecs like HEVC. And Compresto handles batch video compression too, processing entire folders of footage automatically.

As hardware VVC decoders eventually appear and Apple's support materializes — if it does — the calculus may shift. But for the foreseeable future, HEVC remains the right tool for the job on Mac.


Realistic Outlook for H.266

Where does VVC go from here? A few things seem likely.

Broadcast and professional adoption first. VVC's clearest opportunity is in broadcast television and professional distribution, where 8K and advanced HDR delivery genuinely benefit from its efficiency and where licensing can be folded into existing commercial arrangements. Several broadcasters and standards bodies have already run VVC trials for next-generation terrestrial and satellite services.

Slow consumer penetration. Without widespread hardware decoders — and with Apple absent entirely — consumer VVC will remain marginal. Codecs live or die on device support, and VVC has a long climb ahead compared to the near-universal HEVC footprint.

Continued AV1 dominance on the web. For internet streaming, the battle is effectively settled: AV1's royalty-free model and existing deployment give it a lead that VVC's licensing model makes very hard to overcome. Meanwhile the Alliance for Open Media is already developing AV2, which threatens to widen the gap further.

The likely equilibrium through the late 2020s: AV1 rules web streaming, HEVC remains the workhorse for device capture and Apple workflows, and VVC finds a professional and broadcast niche rather than mainstream ubiquity. It's a technically superb codec that arrived into a market where the economics favored a free competitor — a reminder that the best technology doesn't always win.


FAQ: H.266 (VVC)

Q: What is H.266 and how is it different from H.265?

H.266, officially Versatile Video Coding (VVC), is the successor to H.265 (HEVC), standardized in 2020. It delivers roughly 50% better compression at the same visual quality, achieved through larger and more flexible block partitioning, improved intra and inter prediction, and dedicated tools for 4K, 8K, HDR, and 360-degree content. The tradeoff is much higher encoding complexity and, in 2026, almost no hardware support.

Q: Is H.266 better than AV1?

In compression efficiency they're roughly comparable — both about 50% better than HEVC, with the winner varying by content and encoder. The decisive difference is licensing: AV1 is royalty-free, while H.266 requires payments to fragmented patent pools. That economic gap is why large streaming platforms favor AV1 despite VVC's strong technical performance.

Q: Can I play H.266 video on a Mac?

Not natively. As of 2026, Apple offers no hardware or software H.266 support in macOS, QuickTime, or VideoToolbox. Playing VVC requires third-party CPU-based software decoders like VVdeC, which are slow and power-hungry. For Mac video work, HEVC via VideoToolbox remains the practical choice.

Q: Why is H.266 adoption so slow?

Licensing and hardware. VVC inherited HEVC's fragmented patent-pool problem — multiple licensors with unclear, overlapping terms — which makes companies hesitant to commit. On top of that, almost no consumer devices ship with hardware VVC decoders, so efficient playback isn't possible at scale. Both problems reinforce each other.

Q: What does VVC stand for?

VVC stands for Versatile Video Coding, the official name of the H.266 standard. It was developed by the Joint Video Experts Team (ITU-T and ISO/IEC MPEG) with major contributions from Germany's Fraunhofer HHI. "Versatile" reflects its design goal of handling conventional video, 8K, HDR, 360-degree, and screen content within a single codec.


New to codecs? Start with our HEVC codec explained guide, then compare the current contenders in AV1 vs H.265.

Download Compresto for Mac and compress your video library with hardware-accelerated HEVC encoding — fast encodes, dramatically smaller files, and playback that works across every Apple device today.

Ready to compress your files? Join thousands of creators using Compresto ⚡