When Browsers Meet Video Codecs: A Love Story That Never Happens

If you’ve ever tried to stream video on a flaky airport Wi-Fi connection, you probably don’t think much about video codecs. You just want the movie to play without buffering every six seconds like it’s powered by a hamster on a treadmill. But beneath that smooth playback lies a world of engineering brilliance, legal minefields, corporate tug-of-war, and so many patents that even lawyers sigh deeply when you mention them.

Welcome to the messy intersection of H.264, H.265, H.266 — and the browsers that want absolutely nothing to do with their licensing drama.

Let’s start with H.264, the codec equivalent of that dependable old pickup truck that somehow survived three owners, two road trips, and one questionable camping incident.

H.264 is everywhere: your phone, your smart TV, your browser, your grandma’s baby monitor from 2012. It became the de facto standard for a simple reason: every major platform agreed to tolerate its licensing fees because the market needed a universal codec. Chrome, Firefox, Safari, Edge — they all made peace with it. A bit like how the tech world finally accepted that JavaScript wasn’t going anywhere.

But here’s the twist:

H.264 has always been a licensed technology.

The reason you never noticed? Device makers, chip vendors, OS developers — they handled the bill.

The web got the convenience. The corporations got the invoice. Everyone was relatively happy.

And then H.265 walked into the room like a Silicon Valley startup promising to “revolutionize video efficiency.”

HEVC, also known as H.265, is a technological masterpiece. Marketing pitches proudly claim it delivers the same quality at half the bitrate. Two times the efficiency! Perfect for 4K! Even 8K! HDR! Buzzwords everywhere!

And the numbers check out. Engineers love it. Streaming companies drool over it.

So why didn’t HEVC conquer the web?

Because every time someone tried to deploy it, a patent lawyer materialized like a Pokémon with a cease-and-desist attack.

See, H.264 had one licensing pool. Painful, but manageable.

H.265 has three competing patent pools, each charging different fees. It’s like trying to get onto a highway where every entrance ramp has a different toll booth, and they all insist your car needs a separate subscription.

Browser vendors looked at this licensing Hydra and backed away slowly. Safari added limited support because Apple ships hardware decoders that already carry licenses. Microsoft followed suit. Google and Mozilla? They pretended not to hear the question.

As a result:

And then came H.266, also known as VVC, the codec that makes engineers whisper “wow” under their breath.

This thing is stunning:

If HEVC is a Tesla, then VVC is a Tesla that drives itself and also cooks you dinner.

But with great efficiency comes… another patent pool, naturally. A new one. With new fees. And new obligations. And an even bigger stack of licensing pages you scroll through like a privacy policy you’re definitely not reading.

To browsers, VVC is a perfect codec trapped behind a “Pay to Enter” sign the size of a billboard. So far:

While HEVC and VVC were busy negotiating with their lawyers, a new codec emerged from the shadow realm of Big Tech collaboration: AV1. Supported by Google, Netflix, Amazon, Apple, Microsoft, Mozilla — basically everyone except your toaster.

AV1 made one bold promise:

Suddenly, browsers felt like Neo seeing the Matrix. A codec with great compression and zero licensing traps? Yes, please. Developers were able to sleep again. Executives no longer feared patent bills the size of a small country’s GDP.

So today the browser landscape looks like this:

It turns out the fastest way to win the codec war is not with efficiency — but with fewer lawyers.

In the CCTV and security industry, the story is different. Browsers aren’t the gatekeepers. Cameras and NVRs operate in controlled environments. Vendors license codecs the same way they buy screws: in bulk, with zero drama.

So HEVC absolutely thrives there.

And yet — even in a world that likes HEVC — adoption still takes time.

Manufacturers invested millions into H.264 hardware. Even today, many cheap H.264 one-chip encoders struggle to produce stable 1080p30 streams. Asking them to run HEVC is like asking a flip phone to run Cyberpunk 2077.

Add the cost of new chips, new licenses, new firmware, new VMS support — and suddenly H.264 doesn’t look so outdated after all.

H.266’s situation is even tougher: its computational load is huge, hardware support is rare, and licensing remains an unexplored forest full of legal wolves.

Here’s the honest answer:

But for the open web?

H.264 may be old, but it’s stable.

AV1 may be new, but it’s free.

And free beats brilliant every single time in the browser ecosystem.

Maybe that’s the real moral of the story: