An unofficial blog that watches Google's attempts to move your operating system online since 2005. Not affiliated with Google.

Send your tips to

February 13, 2013

WebM and Broken Promises

Two years ago, a surprising post from Chromium's blog announced that Google Chrome will drop support for H.264 HTML5 videos. "Though H.264 plays an important role in video, as our goal is to enable open innovation, support for the codec will be removed and our resources directed towards completely open codec technologies."

Nothing happened since then, so I assume that Google changed its mind. Mostly likely, Google hoped that this announcement will increase WebM's adoption, but that was wrong. Other than YouTube, few other sites converted their videos to WebM. Why spend time and money to convert videos when they could simply use a Flash player?

After all, Adobe Flash doesn't support WebM and that's the second broken promise: "As Kevin Lynch mentioned today at Google I/O, we are excited to include the VP8 video codec in Flash Player in an upcoming release, which will help provide users with seamless access to high quality video content on all of their Internet-connected devices," announced a blog post from 2010.

Adobe didn't support the VP8 codec, so Flash is still mostly H.264-only. And so are Internet Explorer, Safari, iOS, Windows Phone. WebM is mostly non-existent in the mobile space and that's where the future lies. Even if Android 2.3+ supports WebM, there aren't many devices with hardware acceleration for WebM.

Now Firefox's Windows nightly builds allow you to play H.264 HTML5 videos using the Windows Media Foundation backend. "That means if you're using a Windows computer that already has a licensed H.264 decoder installed, you'll be able to enjoy HTML5 video that's been encoded using MPEG LA's codec."

That means in the near future the most important browsers will support H.264 videos natively and WebM will matter even less. There's a VP8 successor that's more efficient, there's WebP for images and there's the WebRTC API for native video chat apps, but H.264 will continue to dominate web video. Those broken promises just made it more obvious.


  1. Perhaps G is waiting until Chrome gets to >50% market share. Then they will drop the H.264 bomb! :)

  2. My guess is that H.265 will take over.

  3. My guest is that Google decided to wait until the next generation of codecs to arrive to fight this battle.

  4. considering Google bought Motorola Mobility (a company with h.264 patents in the patent pool) it would appear that this makes sense :)

  5. I think that Google is one to blame, at least for some part too.
    In example, they never made HTML5 player switch VERY noticable. You still need to go and try "experimental" feature to torn on WebM.
    They still force you to go to Flash when they want to show ads and they want to do it OFTEN.
    They didnt followed they words and not dropped H264 at all. They didnt upgraded WebM to VP9 (it seems). How can they now blame Firefox?
    Personally, i very unhappy with all this. I very like idea to get rid of Flash in vide watching process and i dont see much difference with H264 and WebM, its only youtube after all, not fresh anime BD-rip.
    If they really wanted to make WebM to be domanant they shoul put more soul in.