Now I will be honest, I wasn’t expecting this.
Google have today decided that they will remove support for the video codec H.264 from their Chrome browser in the next couple of months. H.264 is the codec that’s used currently in Flash, PS3, Xbox and even my trusty little flip cam.
More importantly for HTML5 it’s also the codec that’s used by Safari, that means iPads and iPhones.
Going forward Chrome will only support WebM(V8) and Theora.
IE9 Beta currently supports V8 and H.264 but not Theora .
Safari currently only supports H.264
There are currently 3 main codecs used with HTML 5 video:
- H.264 – is patent-encumbered meaning that people that build encoders or decoders need to pay a licence fee to MPEG LA.
- VP8 – is open source and was released by Google although the licence situation is a little murky
- Theora – is distributed without licensing fees freely available, but is seen by many as having inferior playback quality.
The current state of browser support looks something like this:
| H.264 | VP8 | Theora | |
| IE9 Beta | Yes | Yes (if codec installed) | No |
| Chrome | No | Yes | Yes |
| Safari | Yes | No | No |
| FireFox | No | Yes | Yes |
| Opera | Depends on OS | Yes | Yes |
How can you tell if a browser supports a particular codec?
This position switch by Google is a great example of why feature detection is so important when coding HTML5. You can’t rely on browser sniffing as browser vendors can change the HTML5 features they implement at any time.
Modernizer is a great JavaScript library which will tell you if a visitors browser supports a particular codec. I talked about it earlier in the month here.
How do you encode VP8?

I had a quick look on my machine and the net to find software to encode WebM and didn’t find much, after asking Robert Reinhard for a good tool (In regard to video encoding: if he doesn’t know about it, it’s not worth knowing) he recommended his video encoding service videoRx.com (of course he would) so If you need to encode alot of video to support Chrome, it might be worth paying him a visit.
This seems a stupid step to take – I can understand Google’s open-source stance, but do wonder whether they risk market share by removing H.264 support. It was the only browser to support H.264, WebM and Theora.
Pingback:Tweets that mention Underbelly » Google Drops H.264 codec support -- Topsy.com
I’m not quite sure what they get out of it. I guess they have a plan. I kind of just assumed that there was going to be a convergence around H.264 at some stage. I suppose I was wrong.
I bet it has something to do with royalties: http://www.streaminglearningcenter.com/articles/h264-royalties-what-you-need-to-know.html
I’m certainly happy to see standards converge on something legitimately free. The world doesn’t need another MP3…
Pingback:Underbelly » Idealism or Pragmatism
That’s not so good news for the downloaders out there, anyways I will go with google’s decision because what ever do becomes a rage afterwards!!..
Pingback:HTML5 Video and Sky News - Ubelly