Updated November 2026: YouTube’s early-2027 target for AV2 on the web, the close of JVET’s beyond-VVC submissions (October 26, 2026), and who owns video codec patents today.

Why This Matters

If you build, fund, or sell anything that touches video, codec names will show up in your bills, your bug reports and your engineering meetings. "We're moving to AV1." "Our CDN charges more for HEVC." "The Chinese browser doesn't decode VVC." Each of those sentences depends on the history behind the names, and this article covers that history. By the end you'll know which codec generation each name belongs to, why it was invented and who fought over its patents. You'll also be able to read a 2026 codec choice the way an experienced engineer does: as a trade between compression efficiency, hardware availability, licensing risk, and political alignment. That helps when you negotiate with vendors, spec a streaming platform, or read the next codec announcement in your inbox.

You don't need any prior knowledge of compression to read this article. We'll define every term in plain language before using it, and we'll walk the timeline one generation at a time.

The Short Answer: Video Codec History in One Table

The history of video codecs is a forty-year run of standards, from H.120 in 1984 to AV2 in 2026, in which each new generation needs 30 to 50 percent fewer bits than the one before for the same picture. Two standards bodies, the ITU-T Video Coding Experts Group (VCEG) and ISO/IEC MPEG, wrote most of them, usually as joint teams. Since 2015 a third camp, the Alliance for Open Media (AOMedia), has shipped royalty-free rivals. Every codec on the list from H.261 (1988) onward uses the same hybrid block-based design.

Codec Released Written by What it was for
H.1201984CCITT (today ITU-T)First digital video standard, videoconferencing over T1/E1
H.261November 1988ITU-T VCEGISDN videoconferencing; the hybrid blueprint
MPEG-11993ISO/IEC MPEGVideo CD
MPEG-2 / H.2621995Joint VCEG + MPEGDVD and digital TV
H.2631995ITU-T VCEGLow-bitrate calls, Flash video
MPEG-4 Part 21999ISO/IEC MPEGDivX, Xvid, early web video
H.264 / AVCMay 2003Joint Video Team (JVT)Blu-ray, YouTube, every phone; still dominant
VP8May 2010Google (ex-On2)First royalty-free web codec (WebM)
H.265 / HEVC2013 (ITU-T approval April 2013)JCT-VC4K and HDR; Apple devices, TVs
VP9June 2013GoogleYouTube 4K
AV1March 28, 2018AOMediaRoyalty-free web streaming
H.266 / VVCJuly 6, 2020JVETNext-generation broadcast
AV2Specification v1.0.0, May 28, 2026AOMediaSuccessor to AV1, about 30% fewer bits

Three dates people search for most: H.264 was released in May 2003, H.265 (HEVC) came out in 2013 (ITU-T approved it in April 2013), and the AV2 codec specification was finalised on May 28, 2026. The "old video codecs" you still meet in archives (MPEG-1, MPEG-2, H.263, MPEG-4 Part 2/DivX, RealVideo, WMV/VC-1) are covered generation by generation below.

Who is leading standardization for video codecs? In 2026 two groups do. JVET, the joint team of ITU-T VCEG and ISO/IEC MPEG, writes the H.26x line and is now choosing the codec after VVC; AOMedia writes the royalty-free AV1 and AV2. The section on how video codec development works, further down, walks through both processes.

What a Video Codec Actually Is

First, a definition. A codec is two things glued together: an encoder that takes a stream of raw pictures and packs them into a small file, and a decoder that reverses the process to put the pictures back on a screen. The name is a portmanteau of coder + decoder. Hardware codecs run inside chips. Software codecs run as libraries (FFmpeg, libx264, libaom). In this article, "codec" means the encoder and decoder together.

Raw video is enormous. A single second of plain HDTV (1920 × 1080 pixels, 30 frames per second, 24 bits of colour per pixel) takes about 186 megabytes uncompressed. That's roughly 1.5 gigabits per second, more than any home broadband connection can carry or any disc could hold. To make video shippable at all, every stage of the digital era needed a codec that could cut the bit count by a factor of 50 or more with no visible loss of quality. The full bitrate math is laid out in Why we compress video: the math of bitrate. For this article, keep one number in mind: raw HD video is roughly a hundred times too big to send.

Two scientific tricks made everything that followed possible. The first is the discrete cosine transform (DCT), a piece of mathematics published in 1974. It takes an 8 × 8 patch of pixels and re-expresses it as a small list of frequency coefficients, and most of those can be thrown away because the human eye is insensitive to them. The second is motion compensation. Instead of storing each frame from scratch, the encoder describes a new frame as "the previous frame, but shifted slightly to the right here, and copied from over there." Every codec from H.261 onward refines those two ideas. We unpack the mechanics in Hybrid video codec architecture.

That covers the concepts. The rest of the article is the history itself.

A chart titled Forty Years of Video Codecs: H.120 (1984) to AV2 (2026), read left to right and top to bottom, with colour marking the body that wrote each standard. Twelve codec cards are grouped into four eras. 1984 to 1993, proving that digital video compression works: H.120 in 1984 from ITU-T CCITT, the first digital codec and a noble failure; H.261 in 1988 from ITU-T VCEG, the hybrid blueprint, ISDN p times 64 kbps; MPEG-1 in 1993 from ISO/IEC MPEG, Video CD and B-frames, about 1.5 Mbps. 1995 to 2003, discs, digital television, then the open web: MPEG-2 in 1995 from a joint ITU and MPEG team, DVD and digital TV, interlaced support; MPEG-4 Part 2 in 1999 from ISO/IEC MPEG, DivX and Xvid, early web video; H.264 / AVC in 2003 from the JVT joint team, half of MPEG-2's bits, still ruling in 2026. 2010 to 2013, twice the efficiency and the licensing revolt: VP8 in 2010 from Google, formerly On2, the first royalty-free codec, WebM launches; H.265 / HEVC in 2013 from the JCT-VC joint team, half of H.264's bits, three patent pools; VP9 in 2013 from Google, the YouTube 4K codec, royalty-free. 2018 to 2026, the fork into a royalty-free web and licensed broadcast: AV1 in 2018 from AOMedia, 30 percent under HEVC, the 2026 web baseline; H.266 / VVC in 2020 from the JVET joint team, 40 percent under HEVC, broadcast only; AV2 in 2026 from AOMedia, 30 percent under AV1, specification final in May 2026. The legend gives four colours: ITU-T VCEG, ISO/IEC MPEG, joint ITU-T and MPEG, and AOMedia royalty-free Figure 1. The forty-year codec timeline. Each box marks the year a codec specification was published. Colour bands group codecs by governing body: ITU-T (the telecoms standards arm of the United Nations), the ISO/IEC MPEG committee, joint ITU+ISO efforts, and the royalty-free Alliance for Open Media.

Generation Zero — H.120 (1984): the codec nobody used

The timeline starts with a codec that failed commercially and still shaped the industry.

H.120 was the first digital video compression standard ever published. It came out of COST 211, a European research project, and was ratified in 1984 by the CCITT, the predecessor of today's International Telecommunication Union Telecommunication Standardization Sector (ITU-T). 1 It targeted videoconferencing over dedicated digital telephone lines at 1.544 megabits per second (the American "T1" speed) or 2.048 megabits per second (the European "E1" speed). The encoder was a refrigerator-sized box of analog and early digital electronics.

H.120 used three techniques that look primitive today: conditional replenishment (only send a block of pixels if it changed since the last frame), differential pulse-code modulation (send the difference between each pixel and its neighbour rather than the pixel itself), and variable-length coding (use shorter codes for common patterns). A 1988 revision added crude motion compensation, where a moving object in the new frame is described as a copy of the same object from the previous frame, shifted by a few pixels.

The pictures it produced looked, in the polite words of contemporary reports, "not of adequate quality". Almost nobody bought it. The codec disappeared from commercial use within a few years.

H.120 still matters. It proved that digital video compression was technically possible at telecoms data rates, and it exposed every weakness the next generation had to fix. The people who designed it, especially the engineers in the CCITT study group whose video experts later became ITU-T VCEG, went on to design H.261. That second attempt worked.

Generation 1 — H.261 (1988): the architecture that still rules

H.261, ratified by ITU-T in November 1988, is the codec that all subsequent video compression standards descend from. 2 It was the first to combine two techniques into one machine, in the pattern that the industry now calls hybrid block-based coding:

  1. Motion-compensated prediction. Cut every frame into 16 × 16 squares called macroblocks. For each macroblock, search the previous frame for the closest-looking 16 × 16 region. Write down the small displacement (the motion vector) and only the difference between the prediction and the truth. This handles redundancy between frames.
  2. DCT transform of the difference. Apply the discrete cosine transform to that residual difference, then chop the high-frequency coefficients away with a step called quantization. This handles redundancy within the residual.

Both steps were known in the 1970s and early 1980s as separate research topics. H.261 was the first standard that combined them into a single pipeline, ran it at videoconferencing bitrates of p × 64 kilobits per second (where p could be 1 through 30), and shipped it in actual hardware. The 64-kbps multiple was no coincidence: it matched the ISDN telephone-line speed that European telcos were rolling out at the time.

The hybrid block-based architecture invented for H.261 is the one used by every codec we discuss in the rest of this article. Every codec from MPEG-1 in 1993 to AV2 in 2026 is a more powerful version of the same idea: predict, transform, quantize, code. Forty years of gains in compression efficiency came from making each of those four steps smarter, with better predictions, larger and adaptive block sizes, more accurate transforms and smarter quantization. The skeleton has not changed.

H.261 was also the first standard to show that the ITU's Video Coding Experts Group (VCEG) could lead international video standardization. VCEG went on to co-author every "H-dot" codec over the next forty years.

A vertical flow titled The Hybrid Pipeline All Codecs Inherit from H.261, subtitled that every codec from MPEG-1 to AV2 refines these same four stages, in this order. Six boxes connected by downward arrows. Raw frames: uncompressed video, about 186 MB every second at 1080p30, roughly 1.5 Gbps. Step 1, Predict: guess each block from its neighbours, or from an earlier frame; intra and inter prediction. Step 2, Transform: re-express the residual in frequency space so most of the energy lands in a few coefficients; DCT, ADST. Step 3, Quantize, drawn in orange: round the small numbers to zero, the only lossy step, where picture quality is traded for bits. Step 4, Entropy code: pack what is left losslessly, short codes for common values; CABAC, range coder. Bitstream: compressed video, about 1.5 Mbps for AV2 at 1080p, roughly 1,000 times smaller. A panel below says each generation improves the same four stages with bigger adaptive blocks, from 16 by 16 up to 128 by 128, more prediction modes, better transforms and entropy coding, and that the skeleton invented for H.261 in 1988 has not changed Figure 2. The four-stage hybrid pipeline H.261 invented in 1988. Every codec in the rest of this article (MPEG-1, MPEG-2, H.264, HEVC, AV1, VVC, AV2) is a more powerful version of these same four steps, run in the same order.

Generation 2 — MPEG-1 (1993) and MPEG-2/H.262 (1995): video on a disc, then on a satellite

While ITU-T was working on videoconferencing, a parallel committee inside the International Organization for Standardization, the Moving Picture Experts Group (universally called MPEG), was working on a different problem: putting video on consumer media. Tapes were analog, and audio CDs had only just been invented. The MPEG-1 mandate was to fit a usable colour movie onto a CD-ROM.

MPEG-1 was published as ISO/IEC 11172 in 1993. It produced acceptable VHS-quality video at about 1.5 megabits per second on the Video CD format, which became a hit in Asia in the mid-1990s. Architecturally, MPEG-1 refines H.261 and adds one important tool: B-frames (bidirectionally predicted frames), which use both a past and a future frame as references. B-frames save a lot of bits, but the decoder then has to process frames out of order; we explain the mechanics in GOP structure: I, P, B-frames, open vs closed GOP.

The codec that paid for the move to digital television arrived two years later. MPEG-2 Part 2, also published as ITU-T H.262 in 1995, was the first codec produced by a joint VCEG and MPEG team, a pattern later repeated for H.264, H.265 and H.266. 3 MPEG-2 added support for interlaced video, the legacy scan pattern used by every analog television; without it, broadcasters could not have moved their content into digital pipes. The standard powered DVD-Video, digital cable, digital satellite (DirecTV, SkyTV) and the first wave of digital terrestrial broadcasting (ATSC in the US, DVB-T in Europe). Legacy broadcast infrastructure still runs it today, thirty-one years later.

The gains were large. MPEG-2 fit a feature-length movie on a 4.7-GB DVD at 4–8 megabits per second, with picture quality that consumers happily accepted as "near-VHS or better". A satellite transponder that used to carry one analog channel could now carry six to ten compressed digital channels, and that bandwidth multiplier is what made satellite television profitable in the late 1990s.

Generation 3 — H.263 (1995), MPEG-4 Part 2 (1999), and the wild-west era

Two parallel codecs targeted lower-bitrate use cases in the same decade.

H.263, finalised by ITU-T VCEG in 1995, was a low-bitrate refinement of H.261 designed for videoconferencing over plain old analog phone lines (using POTS modems at 28.8 kbit/s and up). It later became the codec inside 3GPP mobile video and inside Flash Video, the format behind the early YouTube. If you watched a video on the internet between 2005 and 2010, you almost certainly watched Adobe Flash video: Sorenson Spark (an H.263 variant) and VP6 at first, then H.264 from 2008.

MPEG-4 Part 2, also called MPEG-4 Visual, was published by ISO in 1999. It was based heavily on H.263 and added more efficient coding tools for medium bitrates. MPEG-4 Part 2 is the codec inside DivX and Xvid. The proprietary DivX and the open-source Xvid carried the era of pirated TV episodes traded over peer-to-peer networks. DivX itself originated when a French hacker reverse-engineered an early Microsoft MPEG-4 codec around 1999, and Xvid forked in 2001 from OpenDivX, a project whose source code had been opened and then closed again. By 2003, "burn DivX to a DVD-R" was how a whole generation of consumers shipped video to friends and family.

In the same period, proprietary codecs from individual companies briefly competed for the streaming market: RealVideo from RealNetworks, Windows Media Video (later standardised as SMPTE VC-1) from Microsoft, Sorenson Spark inside Adobe Flash, and a handful of others. None survived the next generation. They all failed for the same reason: a proprietary codec needs a critical mass of devices to be worth supporting, and no single vendor could reach that scale against a real standard.

Generation 4 — H.264 / AVC (2003): the codec that ate the internet

In December 2001, VCEG and MPEG combined forces into the Joint Video Team (JVT), chaired by Gary Sullivan (Microsoft), Thomas Wiegand (Fraunhofer HHI), and Ajay Luthra (Motorola). 4 Their charter was to build a codec that doubled the compression efficiency of MPEG-2.

They delivered H.264 / Advanced Video Coding (AVC) in May 2003, published jointly as ITU-T H.264 and ISO/IEC 14496-10 (MPEG-4 Part 10). Its headline result is well known in the industry: H.264 halved the bitrate needed for the same visual quality, again. A satellite channel that used 6 Mbps of MPEG-2 could now run at 3 Mbps and look identical, which doubled the number of channels per transponder.

H.264 won at every layer of the internet because it was good enough to ship everywhere. YouTube switched its primary codec to H.264 in 2007, replacing the older Flash/H.263 path. Apple put a hardware H.264 decoder in every iPhone from 2007 onward. Blu-ray Disc adopted H.264 (alongside MPEG-2 and VC-1). Every modern smartphone, browser, smart TV, game console, action camera, dashcam, and surveillance camera shipped between 2008 and 2025 has hardware H.264 support.

More than two decades after its publication, H.264 is still the dominant video codec on the internet in 2026. In Bitmovin’s 8th Video Developer Report (2025), 79 percent of surveyed video developers said they use H.264, against 49 percent for HEVC, the runner-up. 13 Its replacement curve is one of the slowest in software history, mostly because of hardware: the world already has too many installed H.264 decoders to abandon. Every codec since has started out in second place behind it.

H.264 also set the licensing template the industry still struggles with. The standard is covered by patents from dozens of companies; those companies pooled their patents into MPEG LA, a single licensing administrator that offered a published, capped, predictable royalty schedule. Device and software makers pay a capped per-unit royalty, and internet video that is free to end users was made royalty-free, so the model works for everyone involved. By industry consensus, the MPEG LA H.264 pool was the best-designed video-codec patent pool ever assembled; MPEG LA merged with Via Licensing in 2023 to form Via LA, which still administers it. Licensing for its successors went much worse.

Generation 5 — H.265 / HEVC (2013): twice the efficiency, three patent pools

The next codec generation began work in 2010 inside the Joint Collaborative Team on Video Coding (JCT-VC), a successor to JVT co-chaired by Gary Sullivan and Jens-Rainer Ohm. The goal was another halving of bitrate against H.264, this time to make 4K streaming viable.

H.265 / High Efficiency Video Coding (HEVC) was first consented by ITU-T in January 2013, received final approval on April 13, 2013, and was published in June 2013. 5 The headline number held up: at matched perceptual quality, HEVC needs roughly 50 percent fewer bits than H.264. A 4K stream that takes 25–35 Mbps of H.264 drops to 12–16 Mbps of HEVC. A 1080p stream drops from 4.5–6 Mbps to 2.25–3 Mbps.

Architecturally, HEVC replaced the fixed 16 × 16 macroblock of H.264 with Coding Tree Units of up to 64 × 64 pixels, recursively subdivided into smaller blocks as needed. It added more accurate intra-frame prediction, more reference frames for motion compensation, and a new Sample-Adaptive Offset in-loop filter that compensated for ringing artefacts on the decoded image. We unpack each of those tools in H.265 / HEVC: +50% over H.264 and the patent nightmare.

Then licensing broke down. Instead of one MPEG LA pool with a published rate card, three separate pools emerged: MPEG LA, HEVC Advance (now Access Advance), and Velos Media. 6 The pools differed in members, rates and terms. Some major patent owners, including Nokia, Microsoft and Texas Instruments, joined no pool at all. Velos never published its rates. Streaming services trying to ship HEVC at scale had to work out which pools each relevant patent fell into and negotiate separate licences with each, while still carrying the risk that an unaffiliated patent holder might appear with an infringement claim.

The damage was predictable. Browser vendors refused to add HEVC playback for years; Chrome only turned on hardware HEVC decoding in 2022, and Mozilla Firefox stayed out until version 134 in January 2025, which added hardware HEVC decoding on Windows. 14 Streaming services who could technically deliver HEVC chose not to, because the cost and risk had no upper limit. By 2026, HEVC is dominant on Apple devices (where Apple paid licences upfront on behalf of the platform), strong on smart TVs and set-top boxes, and quietly avoided on the open web. Technically the codec is excellent, but its licensing nearly killed it. Consolidation came late: in December 2025 Access Advance announced it would acquire Via LA’s HEVC and VVC licensing program, pitching the deal as a one-stop shop for both codecs. 15 By January 2026 the acquired administrator had been renamed VCL Advance, and Access Advance reported more than 120 licensees in its HEVC Advance pool. 22

Who owns video codec patents? No single company owns a video codec. Each standard is covered by patents from dozens of firms, mostly the electronics makers, telecoms operators and research labs whose engineers sat in the standards meetings. Patent pools license them as one bundle: Via LA for H.264, Access Advance for HEVC and VVC, and Sisvel for VP9 and AV1, with an AV2 pool announced. 6 AOMedia members do the opposite and license their own AV1 and AV2 patents to everyone royalty-free.

Generation 5b — The royalty-free counter-revolt: VP8, VP9, and the founding of AOMedia

The royalty-free counter-movement started before HEVC was even finished, and the HEVC licensing mess gave it real momentum. Google had bought On2 Technologies in February 2010 for about $124.6 million, acquiring the VPx family of proprietary codecs. 7 In May 2010 Google released the latest of them, VP8, as an open, royalty-free format, together with an irrevocable patent promise covering Google's own implementing patents.

On its own, VP8 changed little: its compression efficiency roughly matched H.264, but its ecosystem was much narrower. Its successor, VP9, mattered far more. Released by Google in June 2013, VP9 targeted HEVC-class efficiency. Google needed it for one specific job: YouTube was about to roll out 4K streaming, and using HEVC at YouTube's scale would have cost a fortune in licences. Chrome enabled VP9 decoding in August 2013, Firefox followed in March 2014, and by 2015 the first generation of 4K-capable smart TVs (Samsung, Sony, LG, Sharp, Philips) shipped with VP9 hardware decoders so they could play YouTube 4K. 8 Apple held out until 2020, when iOS 14 and tvOS 14 finally added VP9.

VP9 mattered mostly as strategy. It showed that one large enough player could move a major proprietary codec ecosystem to royalty-free, and that precedent set up the next step.

In September 2015, seven companies (Amazon, Cisco, Google, Intel, Microsoft, Mozilla, and Netflix) founded the Alliance for Open Media (AOMedia), an industry consortium set up to design and ship a next-generation royalty-free codec without the licensing problems that had crippled HEVC. Apple joined in 2018. The result was AV1.

Generation 6 — AV1 (2018) and H.266 / VVC (2020): the great split

Two parallel codec efforts produced two products at the end of the 2010s.

AV1 was finalised by AOMedia on March 28, 2018. 9 It met its targets: roughly 30 percent better compression than HEVC at matched perceptual quality, fully royalty-free, with the patents of every founding member contractually pooled into AOMedia's royalty-free patent policy. Architecturally, AV1 combined techniques from Google's experimental VP10, Cisco's Thor, and Mozilla's Daala, and added new tools such as a 128 × 128 superblock size, more intra-prediction modes, advanced motion-vector reference handling, and a new Constrained Directional Enhancement Filter.

For its first three years AV1 was very slow to encode and had limited hardware decoder coverage. By 2022 AV1 hardware decoders were shipping in mainstream silicon, including Intel 11th-gen and 12th-gen CPUs, AMD Ryzen 6000, NVIDIA RTX 30/40 series, flagship Android SoCs from MediaTek Dimensity 1000 onward and Qualcomm Snapdragon 8 Gen 2 (late 2022). Apple followed with the A17 Pro and M3 in 2023. Netflix reported in December 2025 that AV1 powered 30 percent of its streaming, 11 and in September 2026 AOMedia said AV1 now powers more than a third of Netflix’s global VOD streaming. 16 Chrome, Edge, Firefox, and Safari all decode AV1 natively (Safari where the device has a hardware decoder).

The competing track produced H.266 / Versatile Video Coding (VVC), finalised by the Joint Video Experts Team (JVET) on July 6, 2020. 10 On paper, VVC cut bitrate by another 40–50 percent against HEVC, a strong engineering result. It added flexible block partitioning down to wedges and triangles, affine motion compensation that can model rotation and zoom, and explicit support for 360-degree video, screen content, and HDR up to 16 stops of dynamic range.

In 2026, VVC adoption depends almost entirely on licensing. Its patent situation looks more like HEVC's than H.264's, with multiple patent pools, complex terms, and unaffiliated patent owners. As of November 2026 there is still no browser support: Chrome, Firefox, Edge, and Safari do not decode VVC natively. VVC has gained ground in broadcast instead. DVB has added VVC to its broadcast specifications, Brazil’s next-generation TV 3.0 system chose VVC as its main video codec, 17 and Intel Lunar Lake plus MediaTek Pentonic chipsets ship with VVC decoders for connected-TV use cases. We unpack the trade-off in H.266 / VVC: technically excellent, market-weak.

The 2020 split is the biggest divergence in codec history. VP9 versus HEVC had previewed it in 2013, and in 2020 it became structural. The next-generation codec for the open web (AV1) and the next-generation codec for traditional broadcast (VVC) were different codecs, each shipping in its own ecosystem with little cross-pollination.

Generation 7 — AV2 (2026): the next leap, royalty-free

AV2 is AOMedia’s successor to AV1: a royalty-free codec whose version 1.0.0 specification was finalised on May 28, 2026 and publicly released in June 2026. 19 On AOMedia’s tenth anniversary in September 2025 the alliance had promised a year-end release; 12 the schedule slipped by about five months, which is normal for a codec this size. The release ships with the libavm reference software. VideoLAN’s dav2d project is building a fast production decoder, and Allegro DVT and HDR Nova already sell conformance streams. 18

AV2 is, in compression terms, what AV1 was for HEVC. AOMedia puts its gain at about 30 percent better compression than AV1 on objective quality metrics (September 2026), 16 and positions it as competitive with VVC. The format adds scalable bitstreams and multi-stream and multi-view coding (stereoscopic video, several camera angles or a composite layout inside one bitstream), along with extended recursive block partitioning, new inter-prediction modes and improved film-grain synthesis. A 12-bit profile for cinema and HDR workflows is already in the works. 18

The strategic position matches AV1’s: royalty-free under AOMedia’s patent policy, with open governance and an open reference implementation. An AOMedia member survey in 2025 found 53 percent planned to deploy AV2 within 12 months of release and 88 percent within two years. The first concrete signals arrived in 2026: Netflix said it plans to adopt AV2 as its next-generation streaming codec, Intel showed an open-source SVT-AV2 encoder at IBC in September, 16 and Allegro DVT, Chips&Media and VeriSilicon announced 8K AV2 hardware decoder IP. 19 Google had already played YouTube AV2 content in a custom Chrome build with the libavm reference decoder at CES 2026. 23 In October 2026 YouTube said its first AV2 streams could reach the web as soon as early 2027, decoded in software because AV2 hardware decoders are not yet in consumer devices in volume, and Meta said it plans to adopt AV2 as well. 24 One caveat repeats AV1’s history: Sisvel has announced plans for an AV2 patent pool, so "royalty-free" is AOMedia’s position and does not guarantee that nobody will ask for royalties. Phones and TVs with AV2 decoders realistically arrive in 2027–2028, and premium DRM-protected services will follow once Widevine, FairPlay, and PlayReady support lands.

For a closer look at the tools inside AV2, see AV2: what to expect in the next 5–10 years.

Who Killed Whom: A Compact Score-Card

Here is the codec ecosystem as of 2026, framed by which codec beat which.

Codec (Year) Beat Lost to Status in 2026
H.120 (1984) nothing H.261 Historical only
H.261 (1988) analog MPEG-1/-2 Replaced
MPEG-1 (1993) nothing MPEG-2 Replaced
MPEG-2 / H.262 (1995) analog TV H.264 Legacy broadcast only
H.263 (1995) analog conf. H.264 Replaced
MPEG-4 Part 2 / DivX (1999) MPEG-2 for web H.264 Replaced
VC-1 / WMV (2006) nothing structurally H.264 Niche / archival
H.264 / AVC (2003) MPEG-2 being displaced Dominant baseline
H.265 / HEVC (2013) H.264 licensing Apple + broadcast
VP8 (2010) H.264 (failed) VP9 Replaced
VP9 (2013) nothing structurally AV1 Legacy on YouTube
AV1 (2018) HEVC, VP9 (being extended by AV2) Modern royalty-free baseline
H.266 / VVC (2020) HEVC technically Web rejection Broadcast (DVB, Brazil TV 3.0)
AV2 (2026) AV1 (n/a) Spec final May 2026; YouTube web rollout targeted early 2027

Every five to ten years a new generation arrives that halves the bitrate of the previous one. The codec that a mass-market device platform picks up survives, and the others fade.

The Geopolitics of Standards

The forty-year history splits into three governing camps.

ITU-T VCEG is part of the UN's telecommunications body. It produced H.120, H.261, H.262 (jointly), H.263, H.264 (jointly), H.265 (jointly), and H.266 (jointly). VCEG is funded mostly by telecoms and broadcast companies and tends to value standards stability and inter-operator agreements.

ISO/IEC MPEG is part of the international standards body. It produced MPEG-1, MPEG-2 / H.262 (jointly), MPEG-4 Visual, MPEG-4 Part 10 / H.264 (jointly), and shares H.265 and H.266 through joint teams. MPEG is funded by consumer-electronics and software companies and tends to value licensing pragmatism and richness of features.

Where the two bodies cooperate (H.262, H.264, H.265, H.266), the result is a single global standard with broad industry support. Joint standards can still fragment on licensing, as both HEVC and VVC did, and that fragmentation is what motivated the third camp.

The Alliance for Open Media is an industry consortium founded in 2015. It belongs neither to the UN nor to ISO. It exists specifically because the licensing apparatus around HEVC made the codec commercially unusable on the open web. AOMedia has released two codecs, AV1 (2018) and AV2 (2026). Both explicitly compete with the H-dot codec on technology, and as a matter of principle both reject the H-dot codec's licensing model.

Today the market has forked. The web runs AV1 today and AV2 tomorrow, while broadcast and connected TV will keep deploying HEVC and VVC. The hard question left for every streaming service is how many codec ladders to maintain in parallel. Each codec generation you ship at scale costs you encoding cycles, storage, and CDN egress, and each generation you skip costs you delivery efficiency to the devices that do support the newer codec. We cover that decision-tree in detail in How to choose a codec for your service in 2026.

A chart titled Who Writes the Standards: Three Camps, noting that every codec in commercial use came from one of these bodies or from a joint team. Three columns. ITU-T VCEG, the UN telecoms body: H.120, 1984, the first digital codec; H.261, 1988, the blueprint; H.263, 1995, phone lines and Flash. ISO/IEC MPEG, the ISO standards body: MPEG-1, 1993, Video CD; MPEG-4 Part 2, 1999, DivX and Xvid. AOMedia, an industry consortium: VP8, 2010, royalty-free; VP9, 2013, YouTube 4K; AV1, 2018, the web default; AV2, 2026, specification final. Below the first two columns a group headed Written jointly by ITU-T VCEG and ISO/IEC MPEG holds four codecs: H.262 / MPEG-2, 1995, DVD and DVB; H.264 / AVC, 2003, still rules; H.265 / HEVC, 2013, patent pools; H.266 / VVC, 2020, broadcast. A note under the AOMedia column says AOMedia is the Alliance for Open Media, founded in 2015 because HEVC licensing blocked the codec on the open web Figure 3. The three governing camps. ITU-T (telecoms-driven) on the left, ISO/IEC MPEG (electronics-driven) in the centre, and the Alliance for Open Media (web-driven) on the right. Codecs that span columns are joint efforts.

How Video Codec Development Works, and What Comes After VVC and AV2

Video codec development is a multi-year competition run by a standards body: it calls for proposals, tests them against each other under fixed conditions, merges the winning tools into a shared test model, and freezes a specification once the gain holds up. Two groups lead it in 2026. JVET, the Joint Video Experts Team of ITU-T and ISO/IEC MPEG, writes the H.26x line. AOMedia writes AV1 and AV2. The IETF has its own guidelines for codec work (RFC 6569, written for the Opus audio codec), 21 but no IETF video codec is in wide use today.

The JVET route has four stages. First a call for evidence asks whether a big enough gain exists. Then a call for proposals invites complete codecs, which are scored in formal subjective tests. The best tools are merged into a test model and refined over two to three years of core experiments. Finally the text is frozen and approved. VVC took that route from its 2017 call for evidence to approval in July 2020. AOMedia works code-first: members land tools in an open-source repository (AVM for AV2), measure them on shared test sets, and write the specification once the software settles.

The next round has already started. On July 17, 2026 JVET issued a joint call for proposals for video compression with capability beyond VVC. Registration closed on September 1, 2026, and the coded submissions were due on October 26, 2026. The proposals are evaluated at the January 2027 meeting in Brisbane, and the first version of the new standard is tentatively targeted for October 2029. 20 The groundwork is JVET’s Enhanced Compression Model. ECM 20.0, its last feature release (June 2026), cuts luma bitrate by about 28 percent against the VVC reference encoder for natural content and by about 43 percent for screen content. Neural-network coding tools (the NNVC software) are tested in parallel. Expect the AV2-versus-"H.267" split of the 2030s to replay the AV1-versus-VVC split of the 2020s.

A second branch of codec development is aimed at machines rather than people. At its October 2026 meeting in Hangzhou, MPEG moved Video Coding for Machines (VCM, ISO/IEC 23888-2), a format tuned for video that a neural network analyses instead of a human watching it, to Final Draft International Standard. 25 For surveillance and robotics pipelines it is the first standard codec built around what the detector needs to see.

A Worked Example: Bitrate Across Generations for the Same 1080p Clip

To make the half-the-bits-every-generation pattern concrete, here is what it costs to encode the same one-hour 1080p movie at visually comparable quality on each codec. The numbers below are typical streaming ladder midpoints, and exact mileage varies with content type.

Codec Bitrate (Mbps) File size for one hour (GB) Bitrate vs predecessor
MPEG-2 (1995) 12 5.4 baseline
H.264 / AVC (2003) 6 2.7 −50%
H.265 / HEVC (2013) 3 1.4 −50%
AV1 (2018) 2.1 0.95 −30%
H.266 / VVC (2020) 1.8 0.8 −40% (vs HEVC)
AV2 (2026) 1.5 0.7 −30% (vs AV1)

A horizontal bar chart titled Bitrate at Matched Quality: One Hour of 1080p, subtitled that each generation roughly halves the bits needed for the same picture. Three columns: codec, bitrate for the same picture, and one hour of video. Six bars, each labelled with its value at the end. MPEG-2, 1995, baseline: 12 Mbps, 5.4 GB. H.264 / AVC, 2003, 50 percent under MPEG-2: 6 Mbps, 2.7 GB. H.265 / HEVC, 2013, 50 percent under H.264: 3 Mbps, 1.4 GB. AV1, 2018, 30 percent under HEVC: 2.1 Mbps, 0.95 GB. H.266 / VVC, 2020, 40 percent under HEVC: 1.8 Mbps, 0.8 GB. AV2, 2026, 30 percent under AV1: 1.5 Mbps, 0.7 GB. The axis below runs from 0 to 12 Mbps. Bar colour marks the family: dark blue for the licensed MPEG-2 and H.264, light blue for the licensed HEVC and VVC, green for the royalty-free AV1 and AV2. A note says the figures are typical streaming-ladder midpoints at matched perceptual quality and that exact mileage varies with content type and encoder tuning Figure 4. The same table as a picture: what one hour of 1080p costs on each generation at matched quality, and what that is in gigabytes on disk.

A back-of-envelope arithmetic example: a Netflix-sized service streaming one billion hours per month at 6 Mbps of H.264 sends about 2.7 exabytes (21.6 exabits) of CDN egress per month. Move the same content to AV1 at 2.1 Mbps and the egress drops to about 0.95 exabytes, a 65 percent reduction. At an illustrative CDN price of $0.005 per gigabyte, the 1.75 exabytes saved is roughly $8.8 million a month, before any storage win. That arithmetic explains why Netflix, YouTube, and Meta pushed AV1 hard, and why Netflix has already said AV2 is next.

A Common Pitfall: "We'll Switch to AV1 Next Quarter"

The single most common mistake we see in product roadmaps is treating a codec migration as a software task that engineering can finish in a sprint. In practice a codec migration is about device coverage first and software second.

The decision tree we ask product teams to run is:

  1. What fraction of your viewers' devices have hardware AV1 decode? Pull the answer from your own player analytics, not from an industry average, because device mix varies wildly by market and audience. With hardware decode there is no significant battery hit, and the CPU does not spike or stutter on the decode side. Software AV1 decode is fine on a modern laptop but punishes a 2019 Android phone.
  2. Do you keep encoding H.264 in parallel for the long tail of devices? Yes, basically forever. In practice you are adding AV1 on top of H.264 rather than migrating away from it.
  3. How do you trigger which codec a viewer gets? Your player and your manifest need to negotiate codec support per session. Most streaming stacks already support this (HLS and DASH both have codec-tag fields). Your encoder needs to produce both ladders. Every title encoded in both carries a second full ladder in storage.

Anyone proposing to "switch to AV1" without that triangulation is proposing a partial outage for the slowest 20 percent of your viewers, and we would push back on that plan.

↓ Free download: Codec History Cheat SheetOne-page A4 timeline of every major video codec from H.120 (1984) to AV2, with governing body, headline bitrate saving, and 2026 status.

Where Fora Soft Fits In

We've been building video products since 2005, across video and audio streaming software development, OTT and Internet TV platforms, video conferencing, video surveillance software, e-learning, telemedicine, and AR/VR. That spans every codec generation in this article. In our shipped projects we still encode H.264 by default on every product, layer HEVC where Apple devices dominate the viewer mix, and add AV1 wherever the encoding cost can be amortised over millions of views. We've delivered live WebRTC pipelines, multi-codec adaptive bitrate ladders for OTT platforms, and surveillance backends that retain footage for years; codec choice in each of those jobs is a different decision shaped by different constraints. When a client asks "what codec should we use", our first three questions are about their viewer device mix, their content shelf life, and the legal jurisdictions they ship into. The codec itself is almost never where the answer starts.

Video Encoding: A Complete Guide to Video Compression - book cover

The book

Video Encoding: A Complete Guide to Video Compression

This article walks the timeline; the book works through what each generation on it actually changed. The codec chapters take H.264, HEVC, VP9, AV1, VVC and AV2 one at a time — which coding tools each added, where its headline bitrate saving was measured, and what its licensing costs in practice — while the earlier chapters build the hybrid pipeline this whole history is a story about, from pixels and colour through prediction, transform, quantization and entropy coding. By the end you can read a codec announcement the way the engineers who wrote it do. Written by Nikolay Sapunov, CEO at Fora Soft.

Read it on Amazon →Kindle & paperback · Fora Soft Video Engineering Handbook

Which codec generations should your service actually ship in 2026?

Tell us what your viewers watch on and what your CDN invoice looks like, and we will work out which ladders are worth encoding in parallel: what AV1 buys you against the hardware-decode coverage you really have, how long H.264 has to stay underneath it, and what HEVC or VVC adds in licensing on top. You get the arithmetic on your own numbers instead of on a test set. 250+ video products shipped since 2005.

Book a 30-min call →WhatsApp →Email us →

See our case studies


  1. ITU-T H.120, "Codecs for videoconferencing using primary digital group transmission", March 1993 (final revision). Wikipedia summary: H.120. Accessed 2026-05-15. ↩

  2. ITU-T H.261, "Video codec for audiovisual services at p × 64 kbit/s", November 1988. Wikipedia: H.261. Accessed 2026-05-15. ↩

  3. ITU-T H.262 / ISO/IEC 13818-2, "Information technology — Generic coding of moving pictures and associated audio information: Video", July 1995. ITU page: H.262 recommendation. Accessed 2026-05-15. ↩

  4. ITU-T H.264 / ISO/IEC 14496-10, "Advanced Video Coding", first edition May 2003. Wikipedia: Advanced Video Coding. Accessed 2026-05-15. ↩

  5. 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-15. ↩

  6. "Video Coding and Related Patent Licensing Pools", Sagacious IP, 2024. Sagacious IP article. Accessed 2026-05-15. ↩

  7. "VP8", Wikipedia. Google acquired On2 Technologies in February 2010 for approximately $124.6 million; VP8 released as royalty-free in May 2010. VP8 on Wikipedia. Accessed 2026-05-15. ↩

  8. "VP9", Wikipedia. Chrome enabled VP9 decoding in version 29 (August 2013); Firefox in March 2014. VP9 on Wikipedia. Accessed 2026-05-15. ↩

  9. AOMedia, "AV1 Roadmap" and the AV1 specification, finalised March 28, 2018. AV1 Roadmap (AOMedia). Accessed 2026-05-15. ↩

  10. ITU-T H.266 / ISO/IEC 23090-3, "Versatile Video Coding", finalised July 6, 2020. Wikipedia: Versatile Video Coding. Accessed 2026-05-15. ↩

  11. Netflix Technology Blog, "AV1 — Now Powering 30% of Netflix Streaming", December 2025. Coverage of the post: GIGAZINE, December 5, 2025 (the original on netflixtechblog.com blocks automated link checks). Accessed 2026-10-10. ↩

  12. AOMedia, "AOMedia Announces Year-End Launch of Next Generation Video Codec AV2 on 10th Anniversary", September 2025. AOMedia AV2 announcement. Accessed 2026-05-15. ↩

  13. Bitmovin, "8th Annual Video Developer Report" (2025): H.264 79%, HEVC 49% of respondents. summary of the report: Streaming Learning Center. Accessed 2026-10-10. ↩

  14. Mozilla, "Firefox 134.0 release notes", January 7, 2025: "Hardware-accelerated playback of HEVC video content is now supported on Windows." Firefox 134 release notes. Accessed 2026-10-10. ↩

  15. Access Advance, "Access Advance and Via Licensing Alliance announce HEVC/VVC program acquisition", December 15, 2025. Access Advance. Accessed 2026-10-10. ↩

  16. AOMedia, "Alliance for Open Media Members Showcase AV2 Ecosystem Developments at IBC 2026", September 2026. AOMedia. Accessed 2026-10-10. ↩

  17. Ultra HD Forum, "Brazil adopts TV 3.0 with many component technologies described in the Ultra HD Forum’s Guidelines" (VVC as main video codec). Ultra HD Forum. Accessed 2026-10-10. ↩

  18. AOMedia, "Alliance for Open Media Releases AV2 Codec", June 2026. AOMedia. Accessed 2026-10-10. ↩

  19. "AV2", Wikipedia: AV2 Bitstream & Decoding Process Specification v1.0.0 dated May 28, 2026; decoder IP announcements; Sisvel pool plans. AV2 on Wikipedia. Accessed 2026-10-10. ↩

  20. ITU-T, "Joint Video Experts Team (JVET)" page, and Ofinno, "JVET issues the joint call for proposals for video coding beyond VVC", July 2026 (timeline, ECM 20.0 results). ITU-T JVET; Ofinno readout. Accessed 2026-10-10. ↩

  21. IETF RFC 6569, "Guidelines for Development of an Audio Codec within the IETF", March 2012. RFC 6569. Accessed 2026-10-10. ↩

  22. Access Advance, "Access Advance closes 2025 with record quarter, eight major licensees, 100% renewal rate, litigations resolved", January 22, 2026 (VCL Advance, 120+ HEVC Advance licensees). Access Advance. Accessed 2026-11-17. ↩

  23. AOMedia, "Demonstrating Real Time AV2 Decoding on Consumer Laptops", March 16, 2026 (Chrome with libavm, YouTube content at 1080p24; VLC 4). AOMedia blog. Accessed 2026-11-17. ↩

  24. PBX Science, "AV2 Video Codec Moves Toward Streaming Deployment, With YouTube Targeting Early 2027 on the Web", October 23, 2026, on AOMedia’s October 22, 2026 announcement (YouTube timing, software decoding, Meta plans). PBX Science. Accessed 2026-11-17. ↩

  25. "MPEG Column: 156th MPEG Meeting", ACM SIGMM Records, November 9, 2026 (VCM, ISO/IEC 23888-2, to FDIS). SIGMM Records. Accessed 2026-11-17. ↩