Streaming platforms transmit over 1 billion hours of video daily, and codec efficiency determines the bandwidth cost of every single hour. A platform serving 10,000 concurrent 4K streams consumes approximately 120 Gbps with H.265 (HEVC) compression. Versatile Video Coding (VVC), also known as H.266, cuts that figure to approximately 60–70 Gbps at equivalent visual quality—a 40–50% bitrate reduction that translates directly into lower CDN costs, reduced storage consumption, and higher-quality delivery on bandwidth-constrained networks.
VVC arrived as the official successor to HEVC when the Joint Video Experts Team (JVET) finalized the specification on July 6, 2020. Six years later, VVC adoption follows a split trajectory: broadcast and connected TV ecosystems adopt VVC through hardware decode mandates from the DVB Project and ATSC 3.0, while browser-based streaming remains locked to H.264, H.265, and the royalty-free AV1 codec due to patent licensing barriers. Streaming platform operators face a practical question—where does VVC fit alongside existing codecs, and when does the compression advantage justify integration into their delivery pipeline?
This guide examines VVC’s 6 compression innovations, compares performance against HEVC, AV1, and H.264 with specific bitrate figures, maps hardware and software support as of March 2026, breaks down the patent licensing landscape, identifies the 5 streaming use cases where VVC delivers measurable ROI, and explains how multi-codec delivery architectures—like those built on Ant Media Server—position streaming operators to adopt VVC incrementally as device support expands.
Table of Contents
What is H.266/VVC (Versatile Video Coding)?
What are the 6 Core Technical Innovations in VVC?
How Does VVC Compare to HEVC, AV1, and H.264?
What Hardware and Software Support VVC in 2026?
What are the VVC Patent and Licensing Requirements?
Which 5 Streaming Use Cases Benefit from VVC?
How Does Multi-Codec Delivery Prepare for VVC Adoption?
Frequently Asked Questions
Conclusion
What is H.266/VVC (Versatile Video Coding)?
Versatile Video Coding
H.266, formally designated Versatile Video Coding (VVC), is a video compression standard that achieves approximately 50% bitrate reduction at equivalent perceptual quality compared to HEVC (H.265). The Joint Video Experts Team (JVET)—a collaboration between ITU-T Video Coding Experts Group (VCEG) and ISO/IEC Moving Picture Experts Group (MPEG)—finalized VVC on July 6, 2020, under designations ITU-T H.266 and ISO/IEC 23090-3 (MPEG-I Part 3).
VVC targets the compression demands of 4K, 8K, HDR, 360-degree immersive, and screen content video. The codec supports YCbCr 4:4:4, 4:2:2, and 4:2:0 chroma subsampling at 8–10 bit depth in the Main 10 profile, with 12–16 bit depth added in the 2022 second edition. Frame rate support spans 0 to 120 Hz, BT.2100 wide color gamut, and HDR peak brightness values of 1,000, 4,000, and 10,000 nits. VVC supports resolutions from very low resolution up to 16K as well as 360-degree video formats.
Fraunhofer Heinrich Hertz Institute (HHI) in Germany contributed core encoding tools and announced the standard in July 2020. The development timeline began in October 2015 when MPEG and VCEG formed JVET, issued a formal Call for Proposals in October 2017, produced the first working draft in April 2018, and demonstrated a preliminary implementation at IBC 2018 showing 40% compression gain over HEVC. For streaming platforms already delivering content with H.264 and H.265—the two codecs that Ant Media Server currently supports for WebRTC, HLS, LL-HLS, and DASH/CMAF output—VVC represents the next codec generation entering production pipelines as hardware decode adoption expands.
What are the 6 Core Technical Innovations in VVC?
VVC introduces 6 architectural innovations that collectively produce its 50% compression efficiency gain over HEVC. These innovations span block partitioning, motion prediction, transform coding, and in-loop filtering stages of the encoding pipeline.
What is Multi-Type Tree (MTT) Partitioning?
Multi-Type Tree partitioning replaces HEVC’s fixed quadtree structure with a flexible system supporting binary and ternary splits in horizontal and vertical directions. HEVC limited Coding Tree Units (CTUs) to square blocks between 4×4 and 64×64 pixels using quadtree-only partitioning. VVC extends CTU sizes to 128×128 pixels and permits non-square rectangular blocks through nested quadtree, binary tree, and ternary tree splits. MTT enables precise alignment of block boundaries to object edges, motion boundaries, and texture transitions in source video.
How Does Affine Motion Compensation Improve Prediction?
Affine motion compensation models rotation, zoom, and shear movements that translational motion vectors cannot represent. VVC implements 4-parameter (similarity) and 6-parameter (affine) motion models. According to Fraunhofer HHI research from the Video Communications and Applications department, affine prediction reduces residual energy by 15–20% for sequences containing camera pan or zoom operations compared to translational-only prediction.
What Role Does Adaptive Loop Filtering (ALF) Play?
Adaptive Loop Filtering applies diamond-shaped Wiener filters at the block boundary level to reduce compression artifacts. ALF operates as the final stage in VVC’s three-stage in-loop filtering pipeline, following the deblocking filter and sample adaptive offset (SAO) filter. The filter coefficients adapt per CTU row, preserving texture detail in high-complexity regions while smoothing flat areas.
What are Geometric Partition Modes?
Geometric partition modes divide prediction blocks along diagonal or angular boundaries instead of axis-aligned splits. VVC defines 64 geometric partition angles, each producing two triangular or trapezoidal sub-regions with independent motion vectors. Geometric partitions improve compression for scenes with diagonal edges, oblique object boundaries, and non-rectangular motion patterns that axis-aligned partitions encode inefficiently.
How Does Subpicture Streaming Work?
Subpicture streaming divides a VVC bitstream into independently decodable spatial regions. Each subpicture functions as a self-contained coding unit with its own motion vector constraints and loop filter boundaries. Subpicture support enables viewport-dependent 360-degree video delivery, where a player decodes only the visible viewport subpictures rather than the full spherical frame, reducing decode computational load for 8K 360-degree content by 60–75%.
What is VVC’s Advanced Entropy Coding System?
VVC’s Context-Adaptive Binary Arithmetic Coding (CABAC) engine extends HEVC’s entropy coder with larger context models and a multi-hypothesis probability update mechanism. The expanded context tables for transform coefficient coding contribute 3–5% of VVC’s total bitrate savings, with the largest gains appearing at high bitrates where coefficient distribution modeling dominates compression performance.
How Does VVC Compare to HEVC, AV1, and H.264?
The following 4-codec comparison table presents 7 attributes across H.264 (AVC), H.265 (HEVC), AV1, and H.266 (VVC), covering compression efficiency, licensing, browser support, hardware decode availability, encoding complexity, approximate 4K bitrate, and primary deployment targets in 2026.
Attribute H.264 (AVC) H.265 (HEVC) AV1 H.266 (VVC)
Compression vs H.264 Baseline ~35–40% better ~45–50% better ~50–55% better
Licensing Royalties (MPEG LA) Royalties (3 pools) Royalty-free (AOMedia) Patent pools (Access Advance, Via-LA)
Browser Support Full (all browsers) Limited (Safari, Edge) Strong (Chrome, Firefox, Edge) None (experimental only)
Hardware Decode Universal Universal (4K+ TVs) Growing (Intel, Apple, Qualcomm) Emerging (Intel Lunar Lake, MediaTek Pentonic)
Encoding Complexity 1x baseline ~2–4x AVC ~5–7x AVC ~8–10x AVC
4K Bitrate (approx.) 15–20 Mbps 8–12 Mbps 6–9 Mbps 5–8 Mbps
Primary Use (2026) Universal fallback 4K OTT, Apple ecosystem Web streaming, mobile UHD broadcast, CTV, 8K
VVC achieves the highest compression efficiency of any production codec, delivering 50–55% bitrate reduction over H.264 and approximately 10–15% improvement over AV1 at 4K resolution based on Fraunhofer HHI’s VVenC benchmarks. The VVenC encoder delivered a 39% efficiency gain over x265 (HEVC) in Streaming Media Magazine testing, though the advantage over AV1 narrowed to approximately 11% in those tests. AV1 maintains a deployment advantage in browser-based streaming due to royalty-free licensing and native Chrome, Firefox, and Edge support. VVC dominates in broadcast and connected TV deployments where hardware decode chipsets provide native playback. Ant Media Server currently supports H.264 and H.265 codecs for WebRTC, HLS, LL-HLS, and DASH/CMAF delivery with VP8 available for WebRTC—the multi-protocol architecture that extends to additional codec support as encoder libraries mature.
What Hardware and Software Support VVC in 2026?
Hardware VVC decode reached a milestone in September 2024 when Intel’s Lunar Lake processors (Core Ultra series) shipped with Xe2 graphics featuring native VVC decode up to 8K60. Intel became the first chipmaker to implement VVC hardware decoding, ahead of NVIDIA and AMD. MediaTek’s Pentonic 800 and 700 chipsets, powering 2024–2025 smart TVs from Samsung, LG, and Sony, include VVC hardware decode capability through dedicated decoder silicon. Qualcomm’s Snapdragon 8 Elite mobile SoC added VVC decode for Android flagship devices.
On the software encoding side, Fraunhofer HHI’s open-source VVenC encoder reached version 1.14 in January 2026, delivering speedups between 20x and 2,400x over the VTM reference software depending on the preset selected. VVenC provides 5 encoding presets (faster, fast, medium, slow, slower) and scales to 32 CPU threads with frame-level parallelization. The companion VVdeC decoder is fully compliant with VVC Main 10 profile and scales across 30+ threads. FFmpeg integrates VVC encoding and decoding through experimental patches from Fraunhofer. The uvg266 encoder from the University of Tampere offers an alternative optimized for real-time encoding, and together with uvgRTP and OpenVVC, provides a complete end-to-end pipeline for live 4K30p VVC intra coding and streaming.
Browser support for VVC remains absent across all major browsers as of March 2026. Chrome, Firefox, Edge, and Safari provide no native VVC decode. According to Rethink Research analysis, VVC has seen almost no commercial uptake in web-based streaming—a trajectory the analyst describes as having deviated significantly from historical codec adoption norms, primarily to AV1’s benefit. The DVB Project formally added VVC to its core broadcast specification in February 2022, making it the first standards body to include a next-generation video codec in its media delivery specification. Future DVB-compliant set-top boxes and smart TVs in Europe, Australia, and affiliated regions are required to support VVC hardware decoding. ATSC 3.0 (NextGen TV) in North America also includes VVC as a supported codec.
What are the VVC Patent and Licensing Requirements?
VVC operates under royalty-bearing licensing, unlike royalty-free AV1. Two primary patent pools govern VVC: Access Advance (fees published April 2021) and Via-LA (formerly MPEG LA, fees published January 2022). In December 2025, Access Advance acquired Via-LA’s HEVC and VVC patent pools, consolidating two pools under one administrator—though this acquisition does not resolve the broader licensing fragmentation.
Multiple essential patent holders remain outside both pools as of March 2026: Apple, Broadcom, Canon, Ericsson, Fraunhofer, Google, Huawei, Intel, InterDigital, LG, Microsoft, Nokia, Oppo, Qualcomm, Samsung, Sharp, and Sony. The fragmented patent landscape creates licensing uncertainty for VVC adopters, mirroring the challenges that slowed HEVC adoption after its 2013 finalization. The Media Coding Industry Forum (MC-IF) was founded to reduce licensing risks, but MC-IF has no authority over the standardization process or patent pool terms.
The licensing complexity directly affects VVC’s competitive position against AV1. Alliance for Open Media (AOMedia) members—including Google, Apple, Amazon, Microsoft, Netflix, Intel, Meta, and Samsung—developed AV1 with explicit royalty-free licensing. Browser vendors who are AOMedia members have no commercial incentive to implement VVC decode, repeating the pattern that limited HEVC to approximately 18% browser compatibility according to CanIUse data despite over a decade of availability.
Which 5 Streaming Use Cases Benefit from VVC?
VVC delivers measurable advantages in 5 streaming deployment categories where bandwidth efficiency at high resolution produces direct cost or quality improvements.
4K and 8K broadcast delivery represents VVC’s strongest deployment category. A 4K HEVC stream at 12 Mbps drops to approximately 6–7 Mbps with VVC at equivalent VMAF quality scores. For broadcast operators delivering hundreds of simultaneous 4K channels, VVC reduces satellite transponder and terrestrial multiplex bandwidth requirements by 40–50%. The DVB Project’s specification mandate ensures hardware decode availability in next-generation European broadcast receivers.
Connected TV and set-top box OTT platforms benefit from VVC in controlled device environments where MediaTek Pentonic and Intel-based chipsets guarantee hardware decode. Premium HDR10+ or Dolby Vision content at 4K achieves 35–45% CDN bandwidth savings compared to HEVC delivery, with VVC content delivered via DASH/CMAF to CTV applications.
360-degree and immersive video applications leverage VVC’s subpicture streaming capability. A full 8K equirectangular 360-degree stream at 80–100 Mbps in HEVC reduces to 40–55 Mbps with VVC, and viewport-dependent subpicture delivery further reduces per-viewer bandwidth to 15–25 Mbps by decoding only visible viewport regions.
UHD archival and VOD libraries achieve 45–50% storage reduction when transcoding HEVC masters to VVC. A 100 TB UHD library compressed in HEVC reduces to approximately 50–55 TB in VVC, producing significant long-term storage infrastructure savings for content operators with large back-catalogs.
Low-bandwidth mobile delivery in emerging markets enables HD-quality playback on 2–3 Mbps connections that previously supported only SD resolution with HEVC encoding. VVC’s compression advantage at low bitrates opens HD streaming to viewers on constrained mobile networks where bandwidth costs per GB remain high.
How Does Multi-Codec Delivery Prepare for VVC Adoption?
VVC’s absent browser support and limited hardware decode footprint in 2026 make single-codec VVC delivery impractical for general audiences. The production deployment model is multi-codec adaptive delivery—serving VVC to hardware-capable devices (smart TVs, set-top boxes, Intel Lunar Lake PCs) while maintaining H.265 and H.264 fallback streams for browsers and older devices. This architecture requires a streaming server capable of multi-codec transcoding, multi-protocol packaging, and adaptive bitrate delivery.
Ant Media Server provides this multi-codec infrastructure today. The server accepts ingest via RTMP, SRT, and WebRTC, supports H.264, VP8, and H.265 video codecs with codec selection configurable per application through the web panel or REST API, and delivers output across WebRTC (ultra-low latency), HLS and LL-HLS (low latency), and DASH/CMAF (standard latency). This codec-agnostic, multi-protocol architecture is the same foundation that extends to VVC output as FFmpeg’s VVenC integration moves from experimental to production-ready.
Ant Media Server’s adaptive bitrate streaming feature dynamically adjusts video quality based on each viewer’s network speed and device performance, automatically switching between configured resolution and bitrate renditions. When VVC joins the encoding ladder, the ABR engine serves VVC renditions to capable devices and falls back to H.265 or H.264 for others—without requiring separate delivery infrastructure. The adaptive bitrate streaming documentation at docs.antmedia.io covers configuration of custom resolution/bitrate profiles through both the web panel and broadcast-level API.
Understanding how each codec generation affects bandwidth cost and device compatibility is critical for operators planning multi-codec delivery. The video codecs streaming guide examines H.264, H.265, VP9, and AV1 compression efficiency, encoding speed benchmarks, protocol compatibility, and bitrate requirements across 6 resolutions—the codec selection framework that VVC extends with its 50% compression advantage over HEVC.
VVC’s direct predecessor, HEVC, remains the highest-efficiency codec currently supported in Ant Media Server’s transcoding pipeline. The H.265 HEVC codec guide covers Coding Tree Unit architecture, Main 10 profile HDR support, encoding speed comparisons against H.264, and the three-pool HEVC licensing structure that VVC’s own patent landscape closely mirrors.
H.264 serves as the universal fallback codec in every multi-codec delivery architecture, including VVC-ready pipelines. The H.264 AVC codec guide details profile configurations, protocol-specific encoding requirements across RTMP, HLS, and WebRTC, and the 98.23% browser compatibility that makes H.264 the mandatory baseline rendition in adaptive bitrate ladders.
VVC content delivery relies on DASH/CMAF packaging because HLS does not natively support VVC playback. Ant Media Server’s CMAF streaming support provides LL-DASH output with configurable segment and fragment durations—the same packaging format that carries VVC-encoded segments to smart TVs and set-top boxes with hardware decode capability.
VVC encoding requires 8–10x the computational resources of HEVC at equivalent quality, making GPU acceleration essential for any deployment beyond offline VOD processing. Ant Media’s analysis of GPU vs CPU transcoding performance quantifies the latency, throughput, and cost tradeoffs between CUDA-accelerated and software-only encoding—directly relevant to infrastructure sizing for future VVC transcoding workloads.
Scaling transcoding infrastructure for computationally intensive codecs requires container-orchestrated auto-scaling that allocates GPU-equipped workers dynamically. Ant Media Server’s Kubernetes deployment architecture supports horizontal scaling of origin and edge nodes, with auto-scaling triggers based on CPU load and active stream count—the orchestration model that absorbs VVC’s higher encoding complexity without over-provisioning.
Ultra-low-latency ingest via WebRTC with server-side conversion to HLS and DASH output represents the dominant live streaming architecture. Ant Media Server’s WebRTC to HLS/DASH pipeline handles protocol transcoding from WebRTC ingest to segmented HTTP delivery—the same pipeline that will package VVC-encoded output as DASH/CMAF segments for hardware-capable playback endpoints.
Content protection for premium VVC streams applies at the DASH/CMAF packaging stage, where Widevine and PlayReady encryption work identically regardless of the underlying video codec. Ant Media Server’s DRM support for secure streaming covers the encryption workflow for DASH-delivered content—infrastructure that extends to VVC-encoded streams without protocol-level changes.
Cloud deployment with automated cluster provisioning enables cost-efficient scaling for multi-codec transcoding workloads. The AWS CloudFormation scaling guide provides templates for auto-scaling origin-edge clusters on AWS, supporting concurrent H.264 and H.265 transcoding with load-balanced stream distribution across availability zones.
Monitoring transcoding pipeline health becomes critical when operating multi-codec encoding ladders. Ant Media Server’s Grafana monitoring integration provides real-time dashboards tracking per-stream encoding performance, system CPU load, JVM heap memory, and active stream counts—the observability layer that identifies transcoding bottlenecks before they impact viewer experience.
Operators building multi-codec delivery infrastructure need to validate that adaptive bitrate transcoding, DASH/CMAF packaging, WebRTC ingest, and HLS output function correctly before adding codec complexity. Ant Media Server’s self-hosted evaluation provides 14 days of Enterprise Edition access to test H.264, H.265, and VP8 transcoding pipelines, Kubernetes auto-scaling, and multi-protocol output in a production-representative environment—establishing the infrastructure foundation that extends to VVC as encoder support reaches production readiness.
Frequently Asked Questions
What is the H.266 VVC Codec?
H.266 VVC (Versatile Video Coding) is a video compression standard finalized in July 2020 by JVET. VVC achieves 50% bitrate reduction over HEVC at equivalent visual quality through multi-type tree partitioning, affine motion compensation, and adaptive loop filtering. VVC carries the formal designations ITU-T H.266 and ISO/IEC 23090-3.
How Much Bandwidth Does VVC Save Over HEVC?
VVC reduces bitrate by 40–50% compared to HEVC at equivalent perceptual quality. A 4K stream at 12 Mbps in HEVC drops to 6–7 Mbps with VVC. Fraunhofer HHI’s VVenC encoder demonstrated a 39% efficiency gain over x265 in Streaming Media Magazine benchmarks.
Is VVC Royalty-Free Like AV1?
VVC requires royalty payments through Access Advance and Via-LA patent pools, with 17+ essential patent holders remaining outside both pools as of March 2026. AV1 operates royalty-free through the Alliance for Open Media—a distinction that directly determines browser support and web deployment viability.
Which Browsers Support H.266 VVC?
No major browser supports native VVC playback as of March 2026. Chrome, Firefox, Edge, and Safari lack VVC decode. AOMedia member companies that develop these browsers have no commercial incentive to add VVC support, mirroring the limited browser adoption of HEVC.
Does Ant Media Server Support VVC?
Ant Media Server currently supports H.264, VP8, and H.265 (HEVC) codecs for WebRTC, HLS, LL-HLS, and DASH/CMAF delivery. VVC is not yet a supported codec. Ant Media Server’s multi-codec transcoding architecture and DASH/CMAF packaging engine provide the infrastructure foundation that extends to VVC output as FFmpeg’s VVenC integration matures.
When Will VVC Replace HEVC?
VVC coexists with HEVC, AV1, and H.264 rather than replacing any single codec. Broadcast and CTV adopt VVC first through hardware decode mandates. Web streaming continues using H.264 and H.265 for compatibility. Multi-codec adaptive delivery—serving each viewer the best codec their device supports—defines the 2026–2028 deployment model.
Conclusion
H.266 VVC delivers 50% bitrate reduction over HEVC through 6 architectural innovations including MTT partitioning, affine motion compensation, and subpicture streaming. Intel Lunar Lake, MediaTek Pentonic, and DVB-mandated devices establish VVC’s initial deployment in broadcast and connected TV. Patent pool fragmentation with 17+ unlicensed essential patent holders and zero browser support constrain VVC adoption in web-based streaming, where H.265 and H.264 remain the production codecs.
Ant Media Server’s multi-codec architecture—supporting H.264, VP8, and H.265 with adaptive bitrate transcoding across WebRTC, HLS, LL-HLS, and DASH/CMAF—provides the infrastructure foundation for incremental VVC adoption. The same DASH/CMAF packaging pipeline, Kubernetes auto-scaling, and DRM integration that serve H.265 content today extend to VVC streams as encoder libraries and hardware decode support reach production maturity through 2026–2028.
Streaming teams preparing their infrastructure for next-generation codec support can start a 14-day Enterprise Edition trial to validate adaptive bitrate transcoding, multi-protocol delivery, cluster auto-scaling, and DASH/CMAF output in a self-hosted environment—building the production-ready foundation that accommodates VVC the moment encoder integration reaches general availability.
Visit: antmedia.io
Top comments (0)