Opus audio codec logo

As we announced during the beta cycle, Firefox now supports the new Opus audio format. We expect Opus to be published as RFC 6716 any day now, and we’re starting to see Opus support pop up in more and more places. Momentum is really building.

What does this mean for the web?

Keeping the Internet an open platform is part of Mozilla’s mission. When the technology the Web needs doesn’t exist, we will invest the resources to create it, and release it royalty-free, just as we ask of others. Opus is one of these technologies.

Mozilla employs two of the key authors and developers, and has invested significant legal resources into avoiding known patent thickets. It uses processes and methods that have been long known in the field and which are considered patent-free. As a result, Opus is available on a royalty-free basis and can be deployed by anyone, including other open-source projects. Everyone knows this is an incredibly challenging legal environment to operate in, but we think we’ve succeeded.

Why Opus is important?

The Opus support in the <audio> tag we’re shipping today is great. We think it’s as good or better than all the other codecs people use there, particularly in the voice modes, which people have been asking for for a long time. But our goals extend far beyond building a great codec for the <audio> tag.

Mozilla is heavily involved in the new WebRTC standards to bring real-time communication to the Web. This is the real reason we made Opus, and why its low-delay features are so important. At the recent IETF meeting in Vancouver we achieved “strong consensus” to make Opus Mandatory To Implement (MTI) in WebRTC. Interoperability is even more important here than in the <audio> tag. If two browsers ship without any codecs in common, a website still has the option of encoding their content twice to be compatible with both. But that option isn’t available when the browsers are trying to talk to each other directly. So our success here is a big step in bringing interoperable real-time communication to the Web, using native Web technologies, without plug-ins.

Illustration of the quality of different codecs

Opus’s flexibility to scale to both very low bitrates and very high quality, and do all of it with very low delay, were instrumental in achieving this consensus. It would take at least six other codecs to satisfy all the use-cases Opus does. So try out Opus today for your podcasts, music broadcasts, games, and more. But look out for Opus in WebRTC coming soon.


Comments are now closed.

  1. Bernd wrote on August 28th, 2012 at 09:31:

    I hope Microsofts counter proposal doesn’t get in the way..? (They called it something that pronounces like “See You, WebRTC”, right?.. :-/ )

    1. Ralph Giles wrote on August 28th, 2012 at 10:32:

      Microsoft representatives have stated support for Opus in WebRTC. The counter-proposal is about how the javascript api should work.

  2. njn wrote on August 28th, 2012 at 21:31:

    This is awesome.

  3. Fabio wrote on August 31st, 2012 at 23:22:


    it says opus is disabled by default in FF 15. I suppose this is not true since it looks enabled here.

    1. derf wrote on September 3rd, 2012 at 00:46:

      Oops! Thanks, I’ll make sure that gets updated.

  4. pd wrote on September 12th, 2012 at 08:42:

    When you first announced Opus I tried converting some .wavs downloaded from Radiohead. I specified 256 CBR and the files came out smaller than mp3 at lower bitrates. Most importantly, the sound was brilliant.

    Second most importantly, great name! This codec should be the magnum opus of all audio codecs and is! Completely appropriate.

    I just wish the plethora of free media players out there would ramp up support for the codec quick smart.

Comments are closed for this article.