Google To Drop H.264 Video Codec Support For Google Chrome

by NowPublic Staff | January 11, 2011 at 01:51 pm
385 views | 1 Recommendation | 2 comments

Changes To HTML 5 (<video>): Google Chrome Dropping Support For H.264 Video Codec | Google Announces Support for VP8 and Theora Only

In a curious move that a lot of developers are unhappy with, Google announced on its Google Chrome blog  Chromium that it will be dropping support for the H.264 video codec.

The changes to Google Chrome's video codec support was announced by Mike Jazayeri, a Product Manager at Google.

...we are changing Chrome’s HTML5 <video> support to make it consistent with the codecs already supported by the open Chromium project. Specifically, we are supporting the WebM (VP8) and Theora video codecs, and will consider adding support for other high-quality open codecs in the future. 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.

These changes will occur in the next couple months but we are announcing them now to give content publishers and developers using HTML <video> an opportunity to make any necessary changes to their sites.


Google's move to drop the H.264 video codec is drawing fire from many people who have left comments on the Chromium Blog.

Jean-Pierre...well, that a violent move : that leave the sites owner with the choice of staying with Flash player + h.264 alone or to double encode their videos : one in WebM for half the browser market, the other in h.264 for the rest of the world ...
I know Youtube is doing it, but for the rest of the world, that's not a cheap enough move

Kevin...Considering that the licensing restrictions surrounding use of H.264 were lifted by their license holder to allow ease of adoption on the web and that H.264 is the most popular Video Codec for HD since it is used on Blue-ray Discs and on all Apple Products, I would think this was a dumb idea. I understand being "open" but people slammed Mozilla for taking this stance with Firefox and it's support of H.264 so this just looks like a lame duck attempt by Google to promote their own Video Codec. Thanks for making the HTML5 Transition even more messy.

I have six devices that can all play digital video: a PS3, an Xbox 360, a laptop, an iMac, a PSP, and an iPhone. Guess what one codec each and every one of those devices is able to play? h264.

Shiodoshi...If I want the widest audience possible to be able to access my content, why in the world would I encode it in either WebM or Theora? I wouldn't.

Advertisement
recommend Sign In or Join to post comments
1
Jordan Yerman

What you're seeing here is Google planting its flag in the still-uncharted HTML5 terrain. Open standards has nothing to do with Google's thinking here.

Google tipped its hand by making noises about supporting open source while still throwing its weight behind the Flash plugin. There's a difference between seeking equality and seeking supremacy.


1
Waleed raza

All this will do is cement Flash as the safest development option for websites for years to come and set back the video option in HTML5, basically Google killed it. What they have done now is toss in a 3rd option to the mix. Firefox and Opera wanted Ogg/Theroa, Microsoft and Apple wanted h.264 and for good reason it has hardware support in all modern video cards, mp3 players, phones and other devices and Google had been on the h.264 camp until now making it look like h.264 would win and the standard was set. Now they put in V8/WebM in addition to h.264 and Ogg/Theroa and what we have is the Blu-Ray vs HDDVD all over again in standard wars. h.264 will win I am sure of that. The default browser on both Mac and Windows will support it. Some one will create a plug-in for h.264 support for firefox and quicktime will support it so all google did is ruin HTML 5 and force the keeping of Flash for a long time. This was probably the goal in the first place to hit Apple.

closeSign in to NowPublic

is reporting from