Use of Ogg formats in HTML5

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages) This article needs to be updated. Please help update this article to reflect recent events or newly available information. (January 2019) This article may be unbalanced toward certain viewpoints. Please improve the article by adding information on neglected viewpoints, or discuss the issue on the talk page. (January 2018) (Learn how and when to remove this message)

The HTML5 draft specification adds video and audio elements for embedding video and audio in HTML documents. The specification had formerly recommended support for playback of Theora video and Vorbis audio encapsulated in Ogg containers to provide for easier distribution of audio and video over the internet by using open standards, but the recommendation was soon after dropped.

This section possibly contains original research. Please improve it by verifying the claims made and adding inline citations. Statements consisting only of original research should be removed. (January 2012) (Learn how and when to remove this message)

Because some visitors and publishers choose not to take part in the use of proprietary software, web content has been made available through open standards in order to reach these users. As multimedia is already mainstream on the web through proprietary data formats (such as Windows Media Video and MP4) and browser plugins (such as Adobe Flash Player), developers^[who?] had hoped Theora and Vorbis would become part of the HTML5 specification.^[1]

Users affiliated with the free software movement claimed the following advantages:

• The potential for universal adoption of Theora and Vorbis, no matter the computer or the user, would ease "codec hell" by eliminating an unnecessary amount of codecs required to view and publish videos to a select few.^{[citation needed]}
• Browser plugins needed to accommodate the many different codecs would then become a thing of the past:
  • Browsers could handle the playback of Theora and Vorbis and allow the user to customize the manner in which that was done.
  • Bugs and exploits in obsolete versions of those plugins would affect the user less, as they are phased out; the loss of multiple attack vectors would happen once browser plugins were ultimately removed.^{[citation needed]}
  • The HTML5-conformant player, not having to be coded for compatibility with different browsers, could make bugs and exploits easier to find during browser development, and any exploits found would only be able to target that one browser.^{[clarification needed]}
• Free software encoders would compete with rival proprietary encoders, increasing encoder quality through competition.^{[citation needed]}
• Embedding of multimedia by the use of clear and straightforward video and audio elements would require less effort than mastering the object element or learning ActionScript as required by Adobe Flash.^{[citation needed]}

CTO at Opera Software, Håkon Wium Lie explained in a Google tech talk entitled "The <video> element" the proposal of Theora as the video format for HTML5:^[2]

I believe very strongly, that we need to agree on some kind of baseline video format if [the video element] is going to succeed. [...] We want a freely implementable open standard to hold the content we put out. That's why we developed the PNG image format. [...] PNG [...] came late to the party. Therefore I think it's important that from the beginning we think about this.

After the presentation, Lie was asked whether Opera will support other formats than Ogg:

My opinion is that browsers shouldn't support other codecs, at least not in the beginning, until we have established a baseline format. [...] We don't want to contaminate <video> with other formats.

Opera Software and Mozilla have been advocates for including the Ogg formats into the HTML standard.^[3] Support has been available in experimental builds of Opera 9.5 since 2007,^[4] and Ogg Theora is fully supported since Opera 10.50.^[5] Gecko 1.9.1 (browsers based on this engine include Mozilla Firefox 3.5 and SeaMonkey 2.0^[6]), released on June 30, 2009, was the first non-experimental layout engine to support Ogg formats. Google Chrome included support in their 3.0 release (September 2009),^[7] along with support for H.264. However, they did not support MPEG-1 (the parts patents on which are thought to have expired), citing concerns over performance.^[8]

Microsoft began work in October 2017 on implementing support for Ogg, Vorbis, and Theora in Windows 10 and Microsoft Edge.^[9]

In October 2023, Google announced their plans to deprecate and remove support for the Theora video codec starting with experiments reducing Theora support in Chrome 120 and a full removal in Chrome 123, Google states that the reason for the removal is due to low use and security risks associated with the codec.^[10][11]

On October 17, 2007, the World Wide Web Consortium encouraged interested people to take part in a "Video on the Web Workshop", held on December 12, 2007, for two days.^[12] A number of global companies were involved, submitting position papers.^[13] Among them, Nokia's paper^[14] states that "a W3C-led standardization of a 'free' codec, or the active endorsement of proprietary technology such as Ogg [...] by W3C, is, in our opinion, not helpful". Xiph.org's codecs, while licensed under a BSD-style permissive free software license, implement a standard controlled by Xiph.org themselves, rather than a multi-vendor community such as MPEG. Apple Inc., a member of the MPEG LA, has also opposed the inclusion of Ogg formats in the HTML standard on the grounds that H.264 performs better and is already more widely supported, citing patents on their codec's efficiency and the lack of precedents of "Placing requirements on format support", even at the "SHOULD" level, in HTML specifications.^[15]

On December 10, 2007, the HTML 5 specification was updated,^[16] replacing the reference to Theora and Vorbis with a placeholder:^[17]

It would be helpful for interoperability if all browsers could support the same codecs. However, there are no known codecs that satisfy all the current players: we need a codec that is known to not require per-unit or per-distributor licensing, that is compatible with the open source development model, that is of sufficient quality as to be usable, and that is not an additional submarine patent risk for large companies. This is an ongoing issue and this section will be updated once more information is available.^[18]

The removal of the Ogg formats from the specification made it completely file format neutral, like previous versions of HTML. The decision was criticized by a number of Web developers. A follow-up discussion also occurred on the W3C questions and answers blog.^[19]

In response to criticism, the WHATWG has cited concerns over the Ogg formats still being within patent lifetime and thus vulnerable to unknown patents.^[20] Such submarine patents may also exist for formats like MP3. Also, the AVC patent licensing policy is subject to change in a not-yet-clear manner.^[21]

This section needs to be updated. Please help update this article to reflect recent events or newly available information. (October 2021)

As of December 31, 2020, Adobe Flash Player has stopped receiving support from Adobe,^[22] with HTML video being one of the main technologies replacing it.^[23]

"WebRTC Audio Codec and Processing Requirements" Internet standard drafts, published in 2011–2013, require free formats, including Opus, which was developed, among others, by programmers associated with Xiph.Org Foundation (the maintainer of Ogg).^[24][25]

• HTML video