You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 54.163.0.0/16 has been blocked (disabled) by ‪Blablubbs‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider or colocation provider. To prevent abuse, web hosts and colocation providers may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host or colocation provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a colocation provider's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a colocation web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host or colocation provider (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host or colocation provider.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and requests should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 17:28, 10 March 2024.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
Your IP address is in a range that has been blocked on all Wikimedia Foundation wikis. The block was made by ‪Jon Kolbert‬. The reason given is Open proxy/Webhost: See the help page if you are affected .
- Start of block: 18:27, 12 November 2023
- Expiry of block: 18:27, 12 November 2028
Your current IP address is 54.163.179.242. The blocked range is 54.163.0.0/16. Please include all above details in any queries you make. If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

You can view and copy the source of this page:

((Short description|HTML element))
((Use dmy dates|date=December 2019))
<div class="noprint">((HTML))</div>
The [[HTML5]] specification introduced the video element for the purpose of playing videos,<ref name="spec">((cite web| url= http://www.w3.org/TR/html5/video.html#video| title= The video element| work= HTML5: A vocabulary and associated APIs for HTML and XHTML| publisher= [[World Wide Web Consortium]]| date= 24 June 2010| access-date= 27 September 2010| quote= A video element is used for playing videos or movies.| url-status= dead| archive-url= https://web.archive.org/web/20100813023244/http://www.w3.org/TR/html5/video.html#video| archive-date= 13 August 2010))</ref> partially replacing the [[object element]]. '''HTML5 video''' is intended by its creators to become the new standard way to show video on the web, instead of the previous de facto standard of using the proprietary [[Adobe Flash]] plugin, though early adoption was hampered by lack of agreement as to which [[video coding format]]s and [[audio coding format]]s should be supported in web browsers. As of 2020, HTML5 video is the only widely supported video playback technology in modern browsers, with the Flash plugin being phased out.

==History of &lt;video&gt; element==
The &lt;video&gt; element started being discussed by the [[WHATWG]] in October 2006.<ref>((cite web |title=[whatwg] How not to fix HTML from Charles Iliya Krempeaux on 2006-10-30 (whatwg@whatwg.org from October 2006) |url=https://lists.w3.org/Archives/Public/public-whatwg-archive/2006Oct/0189.html |access-date=2022-08-29 |website=lists.w3.org))</ref> The &lt;video&gt; element was proposed by [[Opera Software]] in February 2007.<ref>((cite mailing list |url = http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-February/009702.html |title= [whatwg] &lt;video&gt; element proposal |date=28 February 2007 | access-date=10 April 2010 |mailing-list= What Working Group |last=van Kesteren |first = Anne))</ref> Opera also released a preview build that was showcased the same day,<ref>((cite web | title= Browser War: Episode II – Attack of the DOMs | url= http://browserwarii.eventbrite.com/ | access-date= 10 April 2012 | archive-url= https://web.archive.org/web/20130223083257/http://browserwarii.eventbrite.com/ | archive-date= 23 February 2013 | url-status= dead ))</ref><ref>((cite web |date=March 1, 2007 |title=SV Web Builders Event – World Premier of Opera with builtin video support |url=http://coolastory.blogspot.com/2007/03/sv-web-builders-event-world-premier-of.html |access-date=10 April 2012))</ref> and a manifesto that called for video to become a first-class citizen of the web.<ref>((cite web | title = A Call for Video on the Web | url = http://people.opera.com/howcome/2007/video/ | access-date = 10 April 2012 | archive-url = https://web.archive.org/web/20120426030127/http://people.opera.com/howcome/2007/video/ | archive-date = 26 April 2012 | url-status = dead ))</ref>

==&lt;video&gt; element examples==
The following HTML5 code fragment will embed a [[WebM Project|WebM]] video into a web page.
<syntaxhighlight lang="html">
<video src="movie.webm" poster="movie.jpg" controls>
	This is fallback content to display for user agents that do not support the video tag.
</video>
</syntaxhighlight>
The "controls" attribute enables the browser's own user interface for controlling playback. Alternatively, playback can be controlled with [[JavaScript]], which the web designer can use to create a custom user interface. The optional "poster" attribute specifies an image to show in the video's place before playback is started. Its purpose is to be representative of the video.

===Multiple sources===

Video format support varies among browsers (see below), so a web page can provide video in multiple formats. For other features, [[browser sniffing]] is used sometimes, which may be error-prone: any web developer's knowledge of browsers will inevitably be incomplete or not up-to-date. The browser in question "knows best" what formats it can use. The "video" element supports fallback through specification of multiple sources. Using any number of &lt;source&gt; elements, as shown below, the browser will choose automatically which file to download. Alternatively, the [[JavaScript]] ((mono|canPlayType())) function can be used to achieve the same. The "type" attribute specifies the [[Internet media type|MIME type]] and possibly a list of codecs, which helps the browser to determine whether it can decode the file without beginning to download it. The MIME type denotes the [[container format]] of the file, and the container format defines the interpretation of the codec string.<ref name="moz-codecs">((cite web |title=The "codecs" parameter in common media types |url=https://developer.mozilla.org/en-US/docs/Web/Media/Formats/codecs_parameter |access-date=14 July 2020))</ref>

<syntaxhighlight lang="html">
<video poster="poster.jpg" controls>
	<source src="av1.mp4" type='video/mp4; codecs="av01.0.00M.08, opus"'>
	<source src="avc.mp4" type='video/mp4; codecs="avc1.4D401E, mp4a.40.2"'>
	<source src="vp9.webm" type='video/webm; codecs="vp9.0, opus"'>
	<source src="theora.ogv" type='video/ogg; codecs="theora, vorbis"'>
	<p>This is fallback content to display for user agents that do not support the video tag.</p>
</video>
</syntaxhighlight>

==Supported video and audio formats==
((See also|Use of Ogg formats in HTML5))
The HTML5 specification does not specify which video and audio formats browsers should support. User agents are free to support any video formats they feel are appropriate, but content authors cannot assume that any video will be accessible by all complying user agents, since user agents have no minimal set of video and audio formats to support.

The HTML5 Working Group considered it desirable to specify at least one video format which all user agents (browsers) should support.  The ideal format in this regard would:
*Have good compression, good image quality, and low decode processor use.
*Be royalty-free.
*In addition to software decoders, a hardware [[video decoder]] should exist for the format, as many embedded processors do not have the performance to decode video.

Initially, [[Ogg]] [[Theora]] was the recommended standard video format in HTML5, because it was not affected by any known patents.  But on 10 December 2007, the HTML5 specification was updated,<ref>((cite mailing list |url = http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-December/013135.html |title = Video codec requirements changed |date = 10 December 2007 |access-date = 25 February 2008 |mailing-list = What WG |last = Hickson |first = Ian |url-status = dead |archive-url = https://web.archive.org/web/20120219232940/http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-December/013135.html |archive-date = 19 February 2012 ))</ref> replacing the reference to concrete formats:
((blockquote|User agents should support Theora video and Vorbis audio, as well as the Ogg container format.))

with a placeholder:<ref>((cite web |title=(X)HTML5 Tracking |url=http://html5.org/tools/web-apps-tracker?from=1142&to=1143 |url-status=dead |archive-url=https://web.archive.org/web/20110726160947/http://html5.org/tools/web-apps-tracker?from=1142&to=1143 |archive-date=26 July 2011 |access-date=23 June 2009 |publisher=[[HTML5]]))</ref>
((blockquote |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.<ref>((cite mailing list |url=http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-December/013152.html |title=Removal of Ogg is *preposterous* |first=Manuel |last=Amador |date=11 December 2011 |access-date=25 August 2009 |mailing-list=[[Web Hypertext Application Technology Working Group|WHATWG]] |archive-url=https://web.archive.org/web/20080821163038/http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-December/013152.html |archive-date=21 August 2008 |url-status=dead ))</ref>))

The result was a polarisation of HTML5 video between [[Technical standard|industry-standard]], [[International Organization for Standardization|ISO-defined]] but [[software patent|patent]]-encumbered formats, and [[open format]]s. The new [[AV1]] format by [[Alliance for Open Media]] aims to be both industry standard, royalty-free, and open, and has wide industry support.

===Free formats===
((See also|Theora|WebM))
Although Theora is not affected by known non-free patents, [[Apple Inc.|Apple]]<ref>((cite web |last=Metz |first=Cade |date=April 30, 2010 |title=Steve Jobs: mystery patent pool to attack Ogg Theora |url=https://www.theregister.co.uk/2010/04/30/steve_jobs_claims_ogg_theora_attack/ |access-date=9 July 2011 |publisher=The Register))</ref> has expressed concern about [[patent ambush|unknown patents]] that might affect it, whose owners might be waiting for a corporation with extensive financial resources to use the format before suing.<ref>((cite mailing list |url=http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-December/013154.html |title=Re: Removal of Ogg is *preposterous* |date=11 December 2007 |access-date=25 February 2008 |url-status= dead |mailing-list=[[Web Hypertext Application Technology Working Group|WHATWG]] |last=Hickson |first=Ian |archive-url= https://web.archive.org/web/20080821194930/http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-December/013154.html |archive-date= 21 August 2008))</ref><ref name="apple-ogg" /> Formats like [[Advanced Video Coding|H.264]] might also be subject to unknown patents in principle, but they have been deployed much more widely and so it is presumed that any patent-holders would have already made themselves known. [[Apple Inc.|Apple]] has also opposed requiring Ogg format support in the HTML standard (even as a "should" requirement) on the grounds that some devices might support other formats much more easily, and that HTML has historically not required particular formats for anything.<ref name="apple-ogg">((cite mailing list |url=http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2007-March/010392.html |title=Codecs (was Re: Apple Proposal for Timed Media Elements) |date=21 March 2007 |mailing-list=[[Web Hypertext Application Technology Working Group|WHATWG]] |last=Stachowiak |first=Maciej))</ref>

Some [[web developer]]s criticized the removal of the Ogg formats from the specification.<ref>((cite mailing list |url=http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-December/013152.html |title=[whatwg] Removal of Ogg is *preposterous* |date=11 December 2007 |access-date=25 August 2009 |url-status=dead |mailing-list=[[Web Hypertext Application Technology Working Group|WHATWG]] |archive-url=https://web.archive.org/web/20080821163038/http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-December/013152.html |archive-date=21 August 2008))</ref> A follow-up discussion also occurred on the W3C questions and answers blog.<ref>((cite web |url=http://www.w3.org/QA/2007/12/when_will_html_5_support_soone.html |title=When will HTML 5 support &lt;video&gt;? Sooner if you help |last=Connolly |first=Dan |date=18 December 2007 |publisher=[[W3C]] |access-date=23 June 2009))</ref>

[[Mozilla]] and [[Opera Software|Opera]] support only the open formats of [[Theora]] and [[WebM]]. Google stated its intention to remove support for H.264 in 2011, specifically for the HTML5 video tag.<ref name="chromeonvideo">((cite web |url=https://blog.chromium.org/2011/01/more-about-chrome-html-video-codec.html |title=More about the Chrome HTML Video Codec Change |first=Michael 'Mike' |last=Jazayeri |publisher=[[Chromium (web browser)|Chromium]] blog |date=14 January 2011))</ref> Although it has been removed from [[Chromium (web browser)|Chromium]], ((as of|2021|1|lc=y)) it has yet to be removed from [[Google Chrome]] ten years later.<ref>((cite web |url=http://news.cnet.com/8301-30685_3-57397031-264/mozilla-execs-capitulate-in-h.264-web-video-war/ |title=Mozilla execs capitulate in H.264 Web-video war |first=Stephen |last=Shankland |publisher=CNET |date=14 March 2012))</ref><ref>((cite web |url=http://www.howtogeek.com/227940/why-youtube-in-chrome-and-firefox-is-draining-your-laptop%E2%80%99s-battery-and-how-to-fix-it/ |title=Why YouTube in Chrome (and Firefox) is Draining Your Laptop's Battery and How to Fix It |first=Chris |last=Hoffman |publisher=Howtogeek |date=9 September 2015))</ref>

====MPEG-DASH Support via the HTML5 Media Source Extensions (MSE)====
((see also|Dynamic Adaptive Streaming over HTTP))
The adaptive bitrate streaming standard MPEG-DASH can be used in Web browsers via the [[Media Source Extensions|HTML5 Media Source Extensions (MSE)]]<ref name="mse">((cite web |date=July 26, 2022 |title=Media Source Extensions |url=https://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html))</ref> and JavaScript-based DASH players. Such players are, e.g., the open-source project dash.js<ref name="mse"/> of the DASH Industry Forum, but there are also products such as the HTML5 Video Player of [[Bitmovin]]<ref name="bitmovin player">((cite web |url=https://bitmovin.com/video-player|title=Adaptive Streaming HTML5 Player from Bitmovin|date=20 April 2022 ))</ref> (using HTML5 with JavaScript, but also a Flash-based DASH players for legacy Web browsers not supporting the HTML5 MSE).

====Google's purchase of On2====
[[Google]]'s acquisition of [[On2 Technologies|On2]] in 2010 resulted in its acquisition of the [[VP8]] video format. Google has provided a [[royalty-free]] license to use VP8.<ref>((cite web |author= |title=Additional IP Rights Grant (Patents) |url=http://www.webmproject.org/license/additional/))</ref> Google also started [[WebM]], which combines the standardized open source VP8 video codec with [[Vorbis]] audio in a [[Matroska]] based container. The opening of VP8 was welcomed by the [[Free Software Foundation]].<ref>((cite web |url=http://www.fsf.org/news/free-software-foundation-statement-on-webm-and-vp8 |title=Free Software Foundation statement on WebM and VP8 |first=Matt |last=Lee |publisher=[[Free Software Foundation|FSF]] |date=19 May 2010))</ref>

When Google announced in January 2011 that it would end native support of H.264 in Chrome,<ref>((cite web |last=Jazayeri |first=Michael 'Mike' |date=January 11, 2011 |title=HTML Video Codec Support in Chrome |url=https://blog.chromium.org/2011/01/html-video-codec-support-in-chrome.html |publisher=The Chromium Blog))</ref> criticism came from many quarters including Peter Bright of [[Ars Technica]]<ref>((cite web |url=https://arstechnica.com/web/news/2011/01/googles-dropping-h264-from-chrome-a-step-backward-for-openness.ars/ |title=Google's dropping H.264 from Chrome a step backward for openness |first=Peter |last=Bright |publisher=Ars Technica |date=12 January 2011))</ref> and Microsoft web evangelist Tim Sneath, who compared Google's move to declaring [[Esperanto]] the official language of the United States.<ref>((cite web |url=http://blogs.msdn.com/b/tims/archive/2011/01/11/an-open-letter-from-the-president-of-the-united-states-of-google.aspx |title=An Open Letter from the President of the United States of Google |first=Tim |last=Sneath |publisher=[[Microsoft Developer Network|MSDN]] blogs |date=11 January 2011))</ref> However, Haavard Moen of Opera Software strongly criticized the Ars Technica article<ref>((cite web |url=http://my.opera.com/haavard/blog/2011/01/13/openness |title=Is the removal of H.264 from Chrome a step backward for openness? |first=Haavard K |last=Moen |publisher=[[My Opera]] |date=13 January 2011))</ref> and Google responded to the reaction by clarifying its intent to promote WebM in its products on the basis of openness.<ref name="chromeonvideo"/>

After the launch of WebM, Mozilla and Opera have called for the inclusion of VP8 in HTML.<ref>((cite web |last=Metz |first=Cade |title=Mozilla and Opera call for Google open codec in HTML5 spec |url=https://www.theregister.co.uk/2010/05/28/mozilla_and_opera_want_vp8_in_html5/ |work=The Register |date=28 May 2010))</ref>

On 7 March 2013, Google Inc. and [[MPEG LA]], LLC announced agreements covering techniques that "may be essential" to VP8, with Google receiving a license from MPEG LA and 11 patent holders, and MPEG LA ending its efforts to form a VP8 patent pool.<ref>((cite web |url=http://www.h-online.com/open/news/item/Google-and-MPEG-LA-make-a-deal-over-VP8-codec-Update-1818785.html |title=Google and MPEG LA make a deal over VP8 codec – Update |author=djwm |work=The H Open |publisher=[[Heise Media UK]] |date=7 March 2013 |access-date=3 April 2013))</ref><ref>((cite web |url=http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/88/n-13-03-07.pdf |title=Archived copy |access-date=3 April 2013 |url-status=dead |archive-url=https://web.archive.org/web/20160305123623/http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/88/n-13-03-07.pdf |archive-date=5 March 2016))</ref><ref>((cite web |url=http://blog.webmproject.org/2013/03/vp8-and-mpeg-la.html |title=VP8 and MPEG LA |date=7 March 2013 |access-date=3 April 2013 |work=WebM Project blog))</ref><ref>((cite web |date=March 8, 2013 |title=Patent clouds remain over VP8: Google points to FRAND option, Nokia alleges infringement in court |url=http://www.fosspatents.com/2013/03/patent-clouds-remain-over-vp8-google.html |website=FOSS Patents))</ref>

In 2012, [[VP9]] was released by Google as a successor to VP8, also open and royalty free.

At the end of 2017 the new [[AV1]] format developed by the [[Alliance for Open Media]] (AOMedia) as the evolution of VP9 has reached the feature freeze, and the bitstream freeze is expected for January 2018. Firefox nightly builds already include support for AV1.<ref name="FFnightly"/>

===Non-free formats===
((See also|H.264/MPEG-4 AVC))
[[H.264/MPEG-4 AVC]] is widely used, and has good speed, compression, hardware decoders, and video quality, but is patent-encumbered.<ref>((cite web |url=http://www.mpegla.com/main/programs/avc/Documents/avc-att1.pdf |title=AVC/H.264 Patent List |publisher=MPEG LA |date=1 February 2010 |access-date=13 April 2010 |archive-url=https://web.archive.org/web/20150514191648/http://www.mpegla.com/main/programs/avc/Documents/avc-att1.pdf |archive-date=14 May 2015 |url-status=dead ))</ref> Users of H.264 need licenses either from the individual patent holders, or from the [[MPEG LA]], a group of patent holders including Microsoft and Apple, except for some Internet broadcast video uses.<ref>((citation |url = http://www.mpegla.com/main/programs/AVC/Pages/Licensors.aspx |title = AVC/H.264 Licensors |publisher = [[MPEG LA]] |access-date = 13 April 2010 |archive-url = https://web.archive.org/web/20150530040919/http://www.mpegla.com/main/programs/AVC/Pages/Licensors.aspx |archive-date = 30 May 2015 |url-status = dead ))</ref> H.264 is usually used in the MP4 container format, together with [[Advanced Audio Coding]] (AAC) audio. AAC is also covered by patents in itself, so users of MP4 will have to license both H.264 and AAC.

In June 2009, the WHATWG concluded that no existing format was suitable as a specified requirement.<ref>((cite mailing list |url = http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-June/020620.html |title=Codecs for &lt;audio&gt; and &lt;video&gt; |date= 29 June 2009 |mailing-list=[[Web Hypertext Application Technology Working Group|WHATWG]] |last=Hickson |first=Ian ))</ref>

Apple still only supports H.264, but Microsoft now supports [[VP9]] and WebM, and has pledged support for [[AV1]].

====Cisco makes a licensed H.264 binary module available for free====
((main|OpenH264))
On 30 October 2013, [[Cisco]] announced that it was making a binary H.264 module available for download. Cisco will pay the costs of patent licensing for those binary modules ''when downloaded by the using software while it is being installed'', making H.264 free to use in that specific case.<ref name="openh264-faq">((cite web|url=http://www.openh264.org/faq.html|title=OpenH264))</ref>

In the announcement, Cisco cited its desire of furthering the use of the [[WebRTC]] project as the reason, since WebRTC's video chat feature will benefit from having a video format supported in all browsers.<ref name="cisco-264-release">((cite web|url=http://blogs.cisco.com/collaboration/open-source-h-264-removes-barriers-webrtc|title=Open-Sourced H.264 Removes Barriers to WebRTC|publisher=Cisco|access-date=30 October 2013|date=30 October 2013|archive-url=https://web.archive.org/web/20150706222941/http://blogs.cisco.com/collaboration/open-source-h-264-removes-barriers-webrtc|archive-date=6 July 2015|url-status=dead))</ref> The H.264 module will be available on "all popular or feasibly supportable platforms, which can be loaded into any application".<ref name="h264_mozilla">((cite web|url=https://brendaneich.com/2013/10/ciscos-h-264-good-news/|title=Cisco's H.264 Good News|author=Brendan Eich|date=30 October 2013|publisher=Brendan Eich's blog))<!-- A copy: https://blog.mozilla.org/blog/2013/10/30/video-interoperability-on-the-web-gets-a-boost-from-ciscos-h-264-codec/ --></ref><!-- They also claim to be ready to publish binaries for ports made using the source code. -->

Cisco is also planning to publish source code for those modules under [[BSD licenses|BSD license]], but without paying the royalties,<ref name="openh264-faq"/> so the code will practically be [[free software]] only in countries without H.264 [[software patent]]s, which has already been true about other existing implementations.

Also on 30 October 2013, Mozilla's [[Brendan Eich]] announced that Firefox would automatically download Cisco's H.264 module when needed by default. He also noted that the binary module is not a perfect solution, since users do not have full [[free software]] rights to "modify, recompile, and redistribute without license agreements or fees". Thus Xiph and Mozilla continue the development of [[Daala]].<ref name="h264_mozilla" /><ref name="monty">((cite web|url=http://xiphmont.livejournal.com/61927.html|title=Comments on Cisco, Mozilla, and H.264|publisher=Monty Montgomery blog|author=Monty Montgomery|access-date=30 October 2013|archive-url=https://web.archive.org/web/20150519064602/http://xiphmont.livejournal.com/61927.html|archive-date=19 May 2015|url-status=dead))</ref><!-- comments under Cisco's announcement claim Cisco is also contributing to the development -->

[[OpenH264]] only supports the ''baseline'' profile of H.264, and does not by itself address the need for an AAC decoder. Therefore, it is not considered sufficient for typical MP4 web video, which is typically in the ''high'' profile with AAC audio.<ref>((cite web
|url=https://andreasgal.com/2014/10/14/openh264-now-in-firefox/
|title=OpenH264 now in Firefox
|first=Andreas
|last=Gal
|date=14 October 2014
|access-date=25 February 2015
))</ref><ref>((cite web
|url=https://wiki.mozilla.org/Platform/MediaSourceExtensions
|title=MediaSourceExtensions (mozilla wiki)
|publisher=mozilla
|access-date=25 February 2015
))</ref><ref>((cite web
|url=https://bugzilla.mozilla.org/show_bug.cgi?id=799318#c57
|title=Support H.264/AAC/MP3 video/audio playback on desktop Firefox
|publisher=mozilla
|access-date=25 February 2015
))</ref>
However, for use in WebRTC, the omission of AAC was justified in the release announcement: "the standards bodies have aligned on [[Opus (codec)|Opus]] and [[G.711]] as the common audio codecs for WebRTC".<ref name="cisco-264-release"/> There is doubt as to whether a capped global licensing of AAC, like Cisco's for H.264, is feasible after AAC's licensing bureau removed the price cap shortly after the release of OpenH264.<ref>((cite web |last=xiphmont |title=It's not a strawman after it comes true |url=http://xiphmont.livejournal.com/63152.html |archive-url=https://web.archive.org/web/20170421060115/http://xiphmont.livejournal.com/63152.html |archive-date=April 21, 2017))</ref>

==Browser support==
This table shows which video formats are ''likely'' to be supported by a given [[user agent]]. Most of the browsers listed here use a [[multimedia framework]] for decoding and display of video, instead of incorporating such software components. It is not generally possible to tell the set of formats supported by a multimedia framework without querying it, because that depends on the [[operating system]] and third party codecs.<ref name="phonon-backs">((citation |url= http://doc.qt.nokia.com/latest/phonon-overview.html#backends |contribution= Phonon documentation of backends |access-date= 3 June 2011 |publisher= Nokia |title= Qt |archive-url= https://web.archive.org/web/20160304122148/http://doc.qt.nokia.com/latest/phonon-overview.html#backends |archive-date= 4 March 2016 |url-status= dead ))</ref> In these cases, video format support is an attribute of the framework, not the browser (or its layout engine), assuming the browser properly queries its multimedia framework before rejecting unknown video formats.  In some cases, the support listed here is not a function of either codecs available within the operating system's underlying media framework, or of codec capabilities built into the browser, but rather could be by a browser add-on that might, for example, bypass the browser's normal HTML parsing of the &lt;video&gt; tag to embed a plug-in based video player.

Note that a video file normally contains both video and audio content, each encoded in its own format. The browser has to support both the video and audio formats. See [[HTML5 audio]] for a table of which audio formats are supported by each browser.

The video format can be specified by [[Media type|MIME type]] in HTML (see [[#Multiple sources|example]]). MIME types are used for querying multimedia frameworks for supported formats.<ref name="phonon-query">((citation |url = http://doc.qt.nokia.com/latest/phonon-overview.html#querying-backends-for-support |contribution = Phonon documentation of querying |access-date = 3 June 2011 |publisher = Nokia |title = Qt |archive-url = https://web.archive.org/web/20160304122148/http://doc.qt.nokia.com/latest/phonon-overview.html#querying-backends-for-support |archive-date = 4 March 2016 |url-status = dead ))</ref>

Of these browsers, only Firefox and Opera employ libraries for built-in decoding. In practice, Internet Explorer and Safari can also guarantee certain format support, because their manufacturers also make their multimedia frameworks. At the other end of the scale, Konqueror has identical format support to Internet Explorer when run on Windows, and Safari when run on Mac, but the selected support here for Konqueror is the typical for [[Linux]], where Konqueror has most of its users. In general, the format support of browsers is much dictated by conflicting interests of vendors, specifically that [[Media Foundation]] and [[QuickTime]] support commercial standards, whereas [[GStreamer]] and [[Phonon (software)|Phonon]] cannot legally support other than free formats by default on the free operating systems that they are intended for.<ref name="gpl-license">((Citation |url=https://www.gnu.org/licenses/gpl.html|title=GNU General Public License Version 3|publisher=Free Software Foundation|access-date=27 April 2013|date=29 June 2007))</ref>

{| class="wikitable sortable" style="text-align: center; margin-left:auto; margin-right:auto"
|+ Status of video format support in each web browser
! Browser
! Operating System
! [[Theora]] ([[Ogg]])
! [[H.264/MPEG-4 AVC|H.264]] ([[MP4]])
! [[High Efficiency Video Coding|HEVC]] ([[MP4]])
! [[VP8]] ([[WebM Project|WebM]])
! [[VP9]] ([[WebM Project|WebM]])
! [[AV1]] ([[WebM Project|WebM]])
|-
! [[Android (operating system)|Android]] browser
| Android
| ((yes|Since 2.3))<ref name="androidformats"/>
| ((yes|Since 3.0))<ref name="androidformats"/>
| ((yes|Since 5.0))<ref name="androidformats"/>
| ((yes|Since 2.3))<ref name="androidformats"/>
| ((yes|Since 4.4))<ref name="androidformats">((cite web
|title=Android Core media format and codec support.
|url=http://developer.android.com/guide/appendix/media-formats.html
|access-date=18 December 2015
))</ref>
| ((yes|Since 10))
|-
! [[Chromium (web browser)|Chromium]]
| Unix-like and Windows
| ((yes|Since r18297))<ref>((citation |url=https://code.google.com/p/chromium/issues/detail?id=4363 |title=Issue 4363: [HTML5-Video] Enable HTML5 video/audio elements |access-date=10 September 2010))</ref>
| ((depends|Via [[FFmpeg]]))<ref>((citation |url=https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/44tOScNK9Lc |title=enable proprietary_codecs h.264 |access-date=30 April 2016))</ref><ref>((citation |url=http://blog.ruofeidu.com/chromium-does-not-support-h-264/ |title=Chromium does not support H.264 |date=9 June 2015 |access-date=30 April 2016))</ref>
| ((no))<ref name="chromium-codecs">((citation |url=https://www.chromium.org/audio-video |title=Audio/Video – The Chromium Projects |access-date=21 March 2016))</ref>
| ((yes|Since r47759))<ref>((citation |url=https://codereview.chromium.org/2093007 |title= Code review | contribution= Issue 2093007: Chromium side changes for enabling VP8 and WebM support |access-date=10 September 2010))</ref>
| ((yes|Since r172738))<ref>((cite web|url=https://src.chromium.org/viewvc/chrome?view=rev&revision=172738|title=[chrome] Revision 172738))</ref>
| ((yes))
|-
! [[Google Chrome]]
| Unix-like, Android, macOS, and Windows
| ((yes|Since 3.0))<ref>((citation |url=https://code.google.com/p/chromium/wiki/ChromiumBrowserVsGoogleChrome |title= Code | contribution = Google Chrome support Theora and Vorbis |date= 20 May 2010))</ref><ref name = "chrome-3-video">((cite web |url=http://www.cnetfrance.fr/news/google-chrome-3-39503164.htm |title=Chrome 3.0 supportera la balise vidéo du HTML 5 |website=CNET France |language=fr |trans-title=Google Chrome 3.0 will support &lt;video&gt; tag))</ref>
<!-- Please don't change the value from "yes" to "no" or "manual install" until the H.264 support is actually removed. The table is supposed to reflect the current stage, not some indefinite future. -->
| ((yes|Since 3.0))<ref name="chrome-3-video" />((efn|On 11 January 2011 the removal of support for H.264 was announced on Chromium Blog.<ref>((cite web|last=Mike|first=Jazayeri|title=Chromium Blog: HTML Video Code Support in Chrome|url = https://blog.chromium.org/2011/01/html-video-codec-support-in-chrome.html|work=The Chromium Blog|date=11 January 2011 | access-date =22 April 2012))</ref> ((as of|2016|11|7)) neither actual support was removed, nor the change to this plan was announced.))
| ((Partial|Since 105 (software decoding; needs OS-level codecs) <p> Since 107 (hardware decoding; needs hardware decoder)</p>))<ref name="chrome-supports-hevc-streamingmedia">((cite web|url=https://www.streamingmedia.com/Articles/Editorial/Featured-Articles/Google-Chrome-Plays-HEVC-What-Does-it-Mean-155572.aspx|title=Google Chrome Plays HEVC: What Does it Mean? - Streaming Media))</ref><ref name="chrome-supports-hevc-bitmovin">((cite web|url=https://bitmovin.com/google-adds-hevc-support-chrome/|title=Google Quietly Added HEVC Support in Chrome - Bitmovin))</ref>
| ((yes|Since 6.0))<ref>((cite web |url=https://blog.chromium.org/2010/05/webm-and-vp8-land-in-chromium.html |title=WebM and VP8 land in Chromium |date=19 May 2010 |first=Jim |last=Bankoski |website=Chromium Blog ))</ref><ref>((citation |url = http://googlechromereleases.blogspot.com/2010/06/dev-channel-update.html |title= Chrome Releases | contribution = Dev Channel Update | date = 3 June 2010 |first= Jason |last= Kersey |access-date = 1 July 2010))</ref>
|((yes|Since 29.0))((efn|VP9 support in 25, turned off by default.<ref>((cite web |url=http://webscripts.softpedia.com/blog/Chrome-Adds-Support-for-the-Next-Generation-VP9-Video-Codec-and-Mozilla-s-Opus-Audio-317728.shtml |title=Chrome Adds Support for the Next-Generation VP9 Video Codec and Mozilla's Opus Audio |author=Lucian Parfeni |date=28 December 2012 |website=Softpedia ))</ref> Enabled by default in version 29.<ref>((cite web |url=http://webscripts.softpedia.com/blog/Chrome-Now-Supports-Google-Next-Gen-VP9-Video-Codec-by-Default-361550.shtml | title=Chrome Now Supports Google's Next-Gen VP9 Video Codec by Default |author=Lucian Parfeni |date=17 June 2013 |website=Softpedia ))</ref>))
| ((yes|Since 70))<ref name="AV1 Decode">((cite web |url=https://www.chromestatus.com/feature/5729898442260480 |title=AV1 Decode |website=Chrome Platform Status |access-date=4 September 2018 ))</ref>
|-
! rowspan="3" | [[Internet Explorer]]
| Windows
| ((depends|Via [[OpenCodecs]]))
| ((yes|Since 9.0))<ref>((citation |url=http://technologizer.com/2010/03/16/ie9-platform-preview/ |title=Microsoft Previews the Revamped Internet Explorer 9 Platform |first=Harry |last=McCracken |date=16 March 2010 |publisher= Technologizer))</ref>
|rowspan="3" ((no))<ref name="no_mainstream_hevc">((cite web|url=http://www.streamingmedia.com/Articles/News/Online-Video-News/Apple-Supports-H.265-But-So-Far-Only-in-FaceTime-on-an-iPhone-6-100392.aspx|title=Apple Supports H.265, But So Far Only in FaceTime on an iPhone 6 |author=Jan Ozer |date=5 November 2014))</ref>
| ((depends|Via [[OpenCodecs]]))
|rowspan="3" ((no))
|rowspan="3" ((no))
|-
| Windows Phone
|rowspan="2" ((no))
| ((yes|Since 9.0))<ref name="HTML5 Video Support in IE9 Mobile">((citation |url = http://blogs.windows.com/windows_phone/b/wpdev/archive/2011/10/13/html5-video-support-in-ie9-mobile.aspx |title = HTML5 Video Support in IE9 Mobile |access-date=11 March 2014 |publisher = Microsoft |date=13 October 2011))</ref>
|rowspan="2" ((no))
|-
| Windows RT
| ((yes|Since 10.0))<ref name="HTML5 Video Support in IE9 Mobile"/>
|-
! rowspan="3" |[[Microsoft Edge]]
|Unix-like, macOS and Windows
(Chromium)
|((yes|Since v79))<ref name=":0">((cite web|last=Blog|first=Microsoft Edge|date=2020-01-15|title=Upgrading to the new Microsoft Edge|url=https://blogs.windows.com/msedgedev/2020/01/15/upgrading-new-microsoft-edge-79-chromium/|access-date=2021-03-19|website=Microsoft Edge Blog|language=en-US))</ref><ref>((cite web|title=Can I use... Support tables for HTML5, CSS3, etc|url=https://caniuse.com/ogv|access-date=2021-03-19|website=caniuse.com))</ref>
|((yes|Since v79 (only browser to support DRM PlayReady)))<ref name=":0" /><ref>((cite web|title=Can I use... Support tables for HTML5, CSS3, etc|url=https://caniuse.com/mpeg4|access-date=2021-03-19|website=caniuse.com))</ref>
| ((no))<ref name="no_mainstream_hevc"/>
|((yes|Since v79))<ref name=":0"/><ref name=":1">((cite web|title=Can I use... Support tables for HTML5, CSS3, etc|url=https://caniuse.com/webm|access-date=2021-03-19|website=caniuse.com))</ref>
|((yes|Since v79))<ref name=":0"/><ref name=":1" />
|((yes|Since v79))<ref name=":0"/>
|-
| Windows 10 (Legacy EdgeHTML)
| ((partial|Since 17.0 (with [https://www.microsoft.com/store/productId/9N5TDP8VCMHS Web Media Extensions])))<ref name="Edge-MediaExt">((cite web |url=https://blogs.windows.com/msedgedev/2017/12/05/introducing-web-media-extension-package-ogg-vorbis-theora-support/ |title=Introducing the Web Media Extension Package with OGG Vorbis and Theora support for Microsoft Edge |date=5 December 2017 |website=Microsoft Edge Dev Blog |publisher=[[Microsoft]] ))</ref><ref name="html5test-edge17"/><ref name="edge_better_webm"/>
| ((yes|Since 12.0))<ref>((cite web|url=http://html5test.com/compare/browser/edge-12.html|title=HTML5test – How well does your browser support HTML5?))</ref>
| rowspan=2 ((depends|Needs hardware decoder))((efn|Available if the device has hardware support for HEVC.<ref name="edge_hevc">((cite web|url=https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/10311075-hevc-support|title=HEVC Support))</ref> No software decoding support was included because "HEVC is very computationally complex, this will provide a more consistent experience."<ref>((cite web|url=https://answers.microsoft.com/en-us/insider/forum/insider_apps-insider_wmp/windows-10-hevc-playback-yes-or-no/3c1ab780-a6b2-4b77-ac0f-9faeefd4680d|title=Windows 10 HEVC playback – Yes or No?))</ref>|name=edge_hevc))
| ((Partial|Since 17.0 (supports <video> tag with [https://www.microsoft.com/store/productId/9N5TDP8VCMHS Web Media Extensions] and [https://www.microsoft.com/store/productId/9n4d0msmp0pt VP9 Video Extensions])<ref name="html5test-edge17">((cite web | url=http://html5test.com/compare/browser/edge-17.html |title = HTML5test - How well does your browser support HTML5?))</ref>))
| ((Partial|Only enabled by default if hardware decoder present<ref>((Cite web |url=https://developer.microsoft.com/en-us/microsoft-edge/platform/status/vp9videoplayback/ |title=The status of VP9 Video Playback in Microsoft Edge is Shipped - Microsoft Edge Development |access-date=21 September 2017 |archive-date=7 November 2017 |archive-url=https://web.archive.org/web/20171107125832/https://developer.microsoft.com/en-us/microsoft-edge/platform/status/vp9videoplayback/ |url-status=dead ))</ref> <p> Since 17.0 (supports <video> tag with [https://www.microsoft.com/store/productId/9N5TDP8VCMHS Web Media Extensions] and [https://www.microsoft.com/store/productId/9n4d0msmp0pt VP9 Video Extensions])<ref name="Edge-MediaExt"/><ref name="html5test-edge17"/><ref name="edge_better_webm">((Cite news | url=https://www.petri.com/redstone-4-brings-better-webm-support-in-edge |title = Redstone 4 Brings Better WebM Support in Edge|date = 11 April 2018))</ref></p>))
| ((Partial|Since 18.0 (with [https://www.microsoft.com/store/productId/9mvzqvxjbq9v AV1 Video Extension])))<ref>((cite web |url=https://www.tenforums.com/tutorials/121440-add-av1-codec-support-windows-10-a.html |title=Add AV1 Codec Support to Windows 10 – Tutorials |website=Ten Forums ))</ref>
|-
| Windows 10 Mobile
| ((no))
| ((yes|Since 13.0))<ref>((cite web|url=http://html5test.com/compare/browser/edge.mobile-13.html|title=HTML5test – How well does your browser support HTML5?))</ref>
| ((Partial|Since 15.0 (only via [[Media Source Extensions|MSE]])<ref name="edge_webrtc">((cite web | url=https://blogs.windows.com/msedgedev/2017/01/31/introducing-webrtc-microsoft-edge/ | title=Introducing WebRTC 1.0 and interoperable real-time communications in Microsoft Edge| date=February 2017))</ref>))
| ((Partial|Since 14.0 (only via [[Media Source Extensions|MSE]])<ref name="edge_vp9">((cite web |url=https://blogs.windows.com/msedgedev/2016/04/18/webm-vp9-and-opus-support-in-microsoft-edge |title=WebM, VP9 and Opus Support in Microsoft Edge |work=Microsoft Edge Dev Blog |publisher=[[Microsoft]] |date=18 April 2016))</ref>))
| ((no))
|-
! [[Konqueror]]
| Unix-like and Windows
| colspan="6" ((Depends|Needs OS-level codecs))((efn|Any format supported by Phonon backend. Available Phonon backends include [[DirectShow]], [[QuickTime]], [[GStreamer]] and [[xine]]; backends using [[MPlayer]] and [[VLC media player|VLC]] are in development.|name=konq))
|-
! rowspan="7" | [[Firefox|Mozilla Firefox]]
| Windows 7+
| rowspan="7" ((yes|Since 3.5))<ref>((cite web |url=https://website-archive.mozilla.org/www.mozilla.org/firefox_releasenotes/en-US/firefox/3.5/releasenotes/ |title= Mozilla Firefox 3.5 Release Notes |date=30 June 2009 |publisher=Mozilla ))</ref>
| ((yes|Since 21.0))((efn|As of version 20, prefed off by default.<ref>((citation |url= https://bugzilla.mozilla.org/show_bug.cgi?id=799315 |title= Bug 799315 – Windows Media Foundation backend for media playback |publisher=Mozilla |access-date=21 December 2012))</ref> Enabled by default beginning in version 21.<ref>((citation |url=https://bugzilla.mozilla.org/show_bug.cgi?id=837859|title= Bug 837859 – Enable WMF backend|publisher=Mozilla |access-date=5 April 2013))</ref>))
| rowspan="7" ((no))<ref name="no_mainstream_hevc" />
| rowspan="7" ((yes|Since 4.0))<ref>((cite web |url=https://website-archive.mozilla.org/www.mozilla.org/firefox_releasenotes/en-US/firefox/4.0/releasenotes/ |title= Mozilla Firefox 4.0 Release Notes |date=22 March 2011 |publisher=Mozilla ))</ref>
| rowspan="7" ((yes|Since 28.0))<ref>((citation |url=https://www.phoronix.com/scan.php?page=news_item&px=MTUzODA |title=[Phoronix] Mozilla Firefox Enables VP9 Video Codec By Default |publisher=Phoronix |access-date=8 December 2013))</ref><ref>((cite web|url=https://www.mozilla.org/en-US/firefox/28.0/releasenotes/|title=Firefox – Notes (28.0)))</ref>
| rowspan="3" ((yes|Since 65.0 (64-bit)<ref>((cite web | url = https://www.mozilla.org/en-US/firefox/65.0/releasenotes/ | title = Firefox 65.0, See All New Features, Updates and Fixes | website = mozilla.org | publisher = [[Mozilla Foundation]] | date = 29 January 2019 ))</ref><br>Since 66.0 (32-bit)<ref name="firefox_66_releasenotes">((cite web | url = https://www.mozilla.org/en-US/firefox/66.0/releasenotes/ | title = Firefox 66.0, See All New Features, Updates and Fixes | website = mozilla.org | publisher = [[Mozilla Foundation]] | date = 19 March 2019 ))</ref>))
|-
| Windows Vista
| ((yes|Since 22.0))<ref>((citation |url= https://bugzilla.mozilla.org/show_bug.cgi?id=825153 |title= Bug 825153 – Add support for Windows Vista WMF and prepend the system32 directory path to dll names |publisher=Mozilla |access-date=28 March 2013))</ref>
|-
| Windows XP and N editions
| ((yes|Since 46.0))<ref>((citation |url= https://bugzilla.mozilla.org/show_bug.cgi?id=1250766 |title= Bug 1250766 – Re-enable using Adobe GMP for decoding when system H.264/AAC codecs not available |publisher=Mozilla |access-date=30 April 2016))</ref>
|-
| Linux
| ((depends|26.0 (via [[GStreamer]])))((efn|Disabled by default until version 26.<ref>((citation |url= https://bugzilla.mozilla.org/show_bug.cgi?id=886181 |title= Bug 886181 – Pref on gstreamer backend |publisher=Mozilla |access-date=21 September 2013))</ref> Also, depends on the codec on the system.<ref>((citation |url= https://bugzilla.mozilla.org/show_bug.cgi?id=794282 |title= Bug 794282 – Enable GStreamer in official builds |publisher=Mozilla |access-date=23 June 2013))</ref>))<br />43.0 (via [[FFmpeg]])<ref>((citation |url= https://bugzilla.mozilla.org/show_bug.cgi?id=1207429 |title= Bug 1207429 – Enable FFMpeg by default |publisher=Mozilla |access-date=30 October 2015))</ref>
| ((yes|Since 67.0))((Citation needed|date=April 2023))
|-
| Android
| ((yes|Since 17.0))<ref>((cite news|url=https://arstechnica.com/information-technology/2012/11/mozilla-ships-firefox-with-h-264-support-on-android/|title=Mozilla ships Firefox with H.264 support on Android|newspaper=Ars Technica |date=30 November 2012))</ref>
| ((Partial|in Nightly))((Citation needed|date=April 2023))
|-
| macOS
| ((yes|Since 34.0))<ref>((citation |url= https://bugzilla.mozilla.org/show_bug.cgi?id=1070703 |title= Bug 1070703 – Add mp4 support in 10.6 and 10.7 on Aurora |publisher=Mozilla |access-date=2 October 2014))</ref>
|  ((yes|Since 66.0))<ref name="firefox_66_releasenotes" />
|-
| Firefox OS
| ((yes|Since 1.1))<ref>((cite web|url=https://developer.mozilla.org/en-US/Apps/Build/Audio_and_video_delivery/H.264_support_in_Firefox|title=H.264 support in Firefox))</ref>
|rowspan="1" ((no))
|-
! [[Opera Mobile]]
|Android, iOS, Symbian, and Windows Mobile
| ((yes|Since 13.0))
| ((yes|Since 11.50))
| rowspan="2" ((no))<ref>((cite web|url=http://www.streamingmedia.com/Articles/Editorial/Featured-Articles/The-Case-for-VP9-100833.aspx|title=The Case for VP9 – Streaming Media Magazine|first=Jan|last=Ozer|date=26 November 2014))</ref>
| ((yes|Since 15.0))
| ((yes|Since 16.0))
| ((yes| since 57.0))<ref name="AV1 Decode"/>
|-
! [[Opera (web browser)|Opera]]
| macOS, Windows, Linux
| ((yes|Since 10.50))<ref>((citation |url=http://my.opera.com/core/blog/2009/12/31/re-introducing-video |title=(re-)Introducing &lt;video&gt; | format = official blog | work = Core developers |first=Philip |last=Jägenstedt |publisher=Opera |date=31 December 2009 | access-date =6 February 2010))</ref>
| ((yes|Since 24.0))<ref>((cite web|url=http://blogs.opera.com/desktop/changelog-24/|title=Changelog for 24 – Opera Desktop))</ref>
| ((yes|Since 10.60))<ref>((citation |url=http://labs.opera.com/news/2010/05/19/ |title=Welcome, WebM &lt;video&gt;! |first=Håkon Wium |last=Lie |date=19 May 2010 |publisher=Opera |url-status=dead |archive-url=https://web.archive.org/web/20110321150357/http://labs.opera.com/news/2010/05/19/ |archive-date=21 March 2011 ))</ref><ref>((citation |url= http://dev.opera.com/articles/view/opera-supports-webm-video/ |title=Opera supports the WebM video format |date=19 May 2010 |first=Chris |last=Mills |publisher= Opera))</ref>
| ((yes))
| ((yes| since 57.0))<ref name="AV1 Decode"/>
|-
! rowspan="2" | [[Safari (web browser)|Safari]]
| iOS
| ((no))
| rowspan="2" ((yes|Since 3.1))<ref name="Mozilla Developer Network">((cite web |url=https://developer.mozilla.org/en-US/docs/Web/HTML/Supported_media_formats |title=Media formats supported by the HTML audio and video elements |website=Mozilla Developer Network |publisher=Mozilla ))</ref>
|rowspan="2" ((yes|Since 11))<ref>((cite web|url=https://bitmovin.com/wwdc17-hevc-hls-apple-just-announced-feature-support-box/|title=WWDC17 – HEVC with HLS – Apple just announced a feature that we support out of the box |author=Martin Smole |date=6 June 2017 |website=Bitmovin ))</ref>
| rowspan="2" ((Partial|Since 12.1 (only supports [[WebRTC]])<ref name="safari_12_1">((cite web | url=https://developer.apple.com/documentation/safari_release_notes/safari_12_1_release_notes |title = Safari 12.1 Release Notes ((pipe)) Apple Developer Documentation))</ref>))
| rowspan="2" ((Partial|Since 14 (only supports [[WebRTC]])<ref name="safari_tech_preview_110">((cite web | url=https://webkit.org/blog/10929/release-notes-for-safari-technology-preview-110/" | title=Release Notes for Safari Technology Preview 110 | date=16 July 2020 ))</ref>))
| rowspan="2" ((no))
|-
| macOS
| ((depends|Via [[Xiph QuickTime Components]] ([[OS X El Capitan|macOS 10.11]] and earlier)))
|-
! [[GNOME Web]]
| Linux and BSD
| colspan="6" ((Depends|Needs OS-level codecs))((efn|Any format supported by [[GStreamer]] on Webkit/GTK+.<ref name="epiphany-webkit-announcement">((citation |url=http://mail.gnome.org/archives/epiphany-list/2008-April/msg00000.html |format = announcement | title = The Future of Epiphany |first=Christian |last=Persch |work=epiphany mailing list-list |date=1 April 2008 ))</ref> The support for Ogg Theora, WebM and h.264 formats is included with base, good, and bad plugins respectively.<ref name = "gstreamer-plugins">((citation |url=http://gstreamer.freedesktop.org/documentation/plugins.html |title=Overview of available plug-ins |work=[[GStreamer]] |access-date=4 July 2012 |archive-url=https://web.archive.org/web/20141212183741/http://gstreamer.freedesktop.org/documentation/plugins.html |archive-date=12 December 2014 |url-status=dead ))</ref>|name=epiphany))
|}
((Explanation of the tables2))
;Notes:
((Notelist))

== Transparent video ==
Transparent video, that is video with an [[Alpha Channel|alpha channel]], has multiple design advantages:<ref>((Cite web |title=How to use transparent videos on the web in 2022 - Rotato |url=https://rotato.app/blog/transparent-videos-for-the-web |access-date=2022-10-20 |website=Rotato 3D Mockups |language=en |quote=This blog showcases various use cases of transparent videos in web design, besides advertising their own software product, Rotato.))</ref>

* As it has no burnt-in background color / pattern / motif, you can change the background and/or neighboring objects in a web page any time later without the need to re-generate the video to fit into its surroundings properly, which was the far less flexible technique so far.
* You can very flexibly combine transparent videos with other elements (text, graphics, other videos or dynamically rendered content such as [[Scalable Vector Graphics|SVG]] or [[Canvas element|canvas]]) to achieve very dynamic layering effects.
* It opens a whole lot of possibilities also in terms of [[responsive web design]].

=== Web browser support for videos with alpha channel ===

* [[Google Chrome|Chrome]] supports [[VP8]] and [[VP9]] encoded videos with an alpha channel served in a [[WebM]] container, since version 31 in 2013-07.<ref>((Cite web |date=July 2013 |title=Alpha transparency in Chrome video |url=https://developer.chrome.com/blog/alpha-transparency-in-chrome-video/ |access-date=2022-10-20 |website=Chrome Developers |language=en |quote=Chrome 31 now supports video alpha transparency in WebM. In other words, Chrome takes the alpha channel into account when playing green screen videos encoded to WebM (VP8 and VP9) with an alpha channel. This means you can play videos with transparent backgrounds: over web pages, images or even other videos.))</ref>
* [[Safari (web browser)|Safari]] supports [[High Efficiency Video Coding|HEVC]] encoded videos with an alpha channel served in a [[MP4 file format|MP4]] container,<ref>((Cite web |title=HEVC Video with Alpha - WWDC19 - Videos |url=https://developer.apple.com/videos/play/wwdc2019/506/ |access-date=2022-10-20 |website=Apple Developer |language=en))</ref> since [[iOS 13]] (2019-09) and [[macOS Catalina]] (2019-10).
* There are some other proprietary [[Polyfill (programming)|polyfill]] / [[Legacy system|legacy]] solutions with a [[JavaScript]] based video player playing back a video which upon upload to the [[Software as a service|SaaS]] server got converted into a [[Proprietary file format|proprietary]] video format.

=== Earlier solutions ===

* Before the HTML5 era the only way to play back transparent video was by the help of [[Adobe Flash Player]]<ref>((Cite web |title=Create transparent backgrounds in a SWF file |url=https://helpx.adobe.com/animate/kb/transparent-background-swf-file.html |access-date=2022-10-20 |website=Adobe Technical Documentation |quote=The background color (Stage color) of a SWF file can be set to transparent. The background color or image of the HTML page that contains the SWF file shows through. This technique allows layering of SWF content with DHTML (Dynamic HTML) content. Not every web browser handles transparency in the same way. Be sure to test your SWF file in all browsers that you want to enable your audience to use. Most Linux browsers do not support Animate transparency.))</ref> and using the <code>transparent</code> <ref>((Cite web |title=Apply OBJECT and EMBED tag attributes in Adobe Flash Professional |url=https://helpx.adobe.com/flash/kb/flash-object-embed-tag-attributes.html |access-date=2022-10-20 |website=Adobe Technical Documentation |quote=transparent — The SWF content is layered together with other HTML elements on the page. The SWF file background color (Stage color) is transparent. HTML elements beneath the SWF file are visible through any transparent areas of the SWF, with alpha blending. This option reduces playback performance compared to wmode=window or wmode=direct.))</ref> flag in its embedding code.

==Digital rights management (Encrypted Media Extensions)==
((main|Encrypted Media Extensions))
HTML has support for [[digital rights management]] (DRM, restricting how content can be used) via the HTML5 [[Encrypted Media Extensions]] (EME). The addition of DRM is controversial because it allows restricting users' freedom to use media restricted by DRM, even where fair use gives users the legal right to do so.<ref>((cite web|url=http://www.defectivebydesign.org/sign-on-against-drm-in-html|title=Keep DRM out of Web standards – Reject the Encrypted Media Extensions (EME) proposal – Defective by Design))</ref> A main argument in W3C's approval of EME was that the video content would otherwise be delivered in plugins and apps, and not in the web browser.<ref>((cite web|url=http://www.infoworld.com/article/2612478/html5/berners-lee-and-w3c-approve-html5-video-drm-additions.html?page=2|title=Berners-Lee and W3C approve HTML5 video DRM additions|first=Serdar|last=Yegulalp|date=4 October 2013))</ref>

In 2013 [[Netflix]] added support for HTML5 video using EME, beside their old delivery method using a [[Silverlight]] plugin (also with DRM).<ref>((cite news |last1= |first1= |date=April 15, 2013 |title=HTML5 Video at Netflix |newspaper=Medium |publisher=Netflix Technology Blog |url=https://netflixtechblog.com/html5-video-at-netflix-721d1f143979))</ref>

==Usage==
In 2010, in the wake of Apple [[iPad]] launch and after [[Steve Jobs]] announced that [[Thoughts on Flash|Apple mobile devices would not support Flash]], a number of high-profile sites began to serve H.264 HTML5 video instead of [[Adobe Flash]] for user-agents identifying as iPad.<ref>((cite web |url=https://www.apple.com/ipad/ready-for-ipad/ |title=iPad-ready websites |access-date=5 April 2010 |publisher=Apple |archive-url=https://web.archive.org/web/20110301150334/http://www.apple.com/ipad/ready-for-ipad/ |archive-date=1 March 2011 |url-status=dead ))</ref> HTML5 video was not as widespread as Flash videos, though there were rollouts of experimental HTML5-based video players from [[DailyMotion]] (using Ogg Theora and Vorbis format),<ref>((cite web |title=Watch Video...without Flash | publisher = Dailymotion |date=27 May 2009 |url=https://blog.dailymotion.com/en/watch-videowithout-flash/ | access-date = 11 October 2018))</ref> YouTube (using the H.264 and WebM formats),<ref>((cite web |last1=Carle |first1=Kevin |last2=Zacharias |first2=Chris |date=20 January 2010 |title=Introducing YouTube HTML5 Supported Videos |url=https://blog.youtube/news-and-events/introducing-youtube-html5-supported/ |access-date=7 March 2010 |work=Youtube))</ref> and Vimeo (using the H.264 format).<ref>((cite web |last= Dougherty |first= Brad |title= Try our new HTML5 player! |publisher= Vimeo |date= 21 January 2010 |url= http://vimeo.com/blog:268 |access-date= 7 March 2010 |archive-url= https://web.archive.org/web/20100304180828/http://www.vimeo.com/blog:268 |archive-date= 4 March 2010 |url-status= dead ))</ref>

Support for HTML5 video has been steadily increasing. In June 2013, Netflix added support for HTML5 video.<ref>((cite web |last=Anthony |first=Sebastian |date=28 June 2013 |title=Netflix switches from Silverlight to HTML5 in Windows 8.1, reduces CPU usage dramatically – ExtremeTech |url=http://www.extremetech.com/computing/159960-netflix-switches-from-silverlight-to-html5-in-windows-8-1-reduces-cpu-usage-dramatically))</ref> In January 2015, YouTube switched to using HTML5 video instead of Flash by default.<ref>((cite web|url=https://www.theverge.com/2015/1/27/7926001/youtube-drops-flash-for-html5-video-default|title=YouTube drops Flash for HTML5 video as default|first=Rich|last=McCormick|date=27 January 2015))</ref> In December 2015, Facebook switched from Flash to HTML5 for all video content.<ref>((cite web|url=https://www.theverge.com/2015/12/18/10623738/facebook-now-using-html5-all-videos|title=Facebook's website now uses HTML5 instead of Flash for all videos|first=Chris|last=Welch|date=18 December 2015))</ref>

As of 2016, Flash is still widely installed on desktops, while generally not being supported on mobile devices such as smartphones.<ref name="flashphone">((cite web |last=Paul |first=Ryan |date=16 August 2012 |title=Availability of Adobe's Flash browser plugin discontinued on Android |url=https://arstechnica.com/information-technology/2012/08/availability-of-adobes-flash-browser-plugin-discontinued-on-android/))</ref> The Flash plugin is widely assumed, including by Adobe,<ref name="flashphone" /><ref>((cite web|url=http://www.cio.com/article/2376661/internet/how-adobe-is-moving-on-from-flash-to-embrace-html5.html|title=How Adobe Is Moving on From Flash to Embrace HTML5|first=Chris Minnick and Ed|last=Tittel|date=30 April 2014))</ref> to be destined to be phased out,<ref>((cite news|url=https://thenextweb.com/apps/2015/09/01/adobe-flash-just-took-another-step-towards-death-thanks-to-google/|title=Adobe Flash is finally dead|first=Owen|last=Williams|newspaper=TNW &#124; Apps |date=1 September 2015))</ref><ref>((cite magazine|url=https://www.wired.com/2015/07/adobe-flash-player-die/|title=Flash. Must. Die.|first=Brian|last=Barrett|magazine=Wired|date=15 July 2015))</ref> which will leave HTML5 video as the only widely supported method to play video on the World Wide Web. Chrome,<ref>((cite web |date=May 9, 2016 |title=Intent to implement: HTML5 by Default |url=https://groups.google.com/a/chromium.org/forum/#!searchin/chromium-dev/HTML5$20by$20default/chromium-dev/0wWoRRhTA_E/__E3jf40OAAJ))</ref><ref>((cite web|title=So long, and thanks for all the Flash|url=https://blog.chromium.org/2017/07/so-long-and-thanks-for-all-flash.html|access-date=8 December 2017))</ref> Firefox,<ref>((cite web |last=Smedberg |first=Benjamin |date=July 20, 2016 |title=Reducing Adobe Flash Usage in Firefox |url=https://blog.mozilla.org/futurereleases/2016/07/20/reducing-adobe-flash-usage-in-firefox/))</ref> Safari,<ref>((cite web|last1=Mondello|first1=Ricky|title=Next Steps for Legacy Plug-ins|url=https://webkit.org/blog/6589/next-steps-for-legacy-plug-ins/|website=WEbKit.org|publisher=[[Apple Inc]]|date=14 June 2016))</ref> and Edge,<ref>((cite web|last1=Cowan|first1=Crispin|title=Extending User Control of Flash with Click-to-Run|url=https://blogs.windows.com/msedgedev/2016/12/14/edge-flash-click-run/|website=Microsoft Edge DevBlog|publisher=[[Microsoft]]|date=14 December 2016))</ref> have plans to make almost all flash content click to play in 2017. The only major browser which does not have announced plans to deprecate Flash is Internet Explorer.<ref>((cite web|url=https://technet.microsoft.com/en-us/itpro/microsoft-edge/enterprise-guidance-using-microsoft-edge-and-ie11|title=Microsoft Edge and Internet Explorer 11 (Microsoft Edge for IT Pros)|last=eross-msft))</ref> Adobe announced on 25 July 2017 that they would be permanently ending development of Flash in 2020.<ref>((cite web|title=Flash & The Future of Interactive Content|url=https://blogs.adobe.com/conversations/2017/07/adobe-flash-update.html|access-date=8 December 2017))</ref>

==See also==
* [[HTML5 audio]]
* [[Comparison of HTML5 and Flash]]

==References==
((Reflist|30em|refs =
<ref name="FFnightly">((Cite news|url=https://www.cnet.com/news/firefox-av1-challenges-apple-hevc-for-4k-friendly-video/|title=Firefox now lets you try streaming-video tech that could be better than Apple's|last1=Shankland|first1=Stephen|work=CNET|date=28 November 2017|access-date=25 December 2017|language=en))</ref>
))

==External links==
* ((citation |url= https://html.spec.whatwg.org/multipage/media.html#the-video-element |title= What WG | contribution = HTML Standard – The Video Element | publisher =W3C| access-date = 10 July 2021)).
* ((citation |url=http://www.w3.org/2010/Talks/1014-html5-video-fd/video-html5.pdf | title= Towards Video on the Web with HTML5 | first1=Francois |last1=Daoust |first2=Philipp |last2=Hoschka | first3=Charalampos Z | last3= Patrikakis | year=2010 | publisher = NEM Summit | place = Barcelona )).
* ((citation |url= http://dev.opera.com/articles/view/introduction-html5-video/ |title= Introduction to HTML5 video |first1= Bruce | last1 = Lawson |first2=Patrick H. |last2=Lauke |date=11 February 2010 |publisher=Opera)).
* ((citation |url=http://html5video.org/ |title=HTML5 Video)) video platform software and news.
* ((citation |url=http://my.opera.com/core/blog/2010/03/03/everything-you-need-to-know-about-html5-video-and-audio-2 |title = Everything you need to know about HTML5 video and audio |first=Simon |last=Pieters |date=3 March 2010 |publisher= Opera))
* [http://www.elstel.org/html5video/FlashVersusHtml5Video.html.en HTML5 Video: A Practical Guide: Convert, Embed, Javascript and Flash Fallback for HTML5 Videos]
* [https://developer.mozilla.org/en-US/docs/Web/HTML/Supported_media_formats Mozilla's overview of media formats supported by browsers]

((W3C standards))
((Web interfaces))

[[Category:HTML5]]
[[Category:New media]]
[[Category:Multimedia]]

Pages transcluded onto the current version of this page (help):

HTML5 video (edit)
Template:As of (view source) (template editor protected)
Template:Blockquote (view source) (template editor protected)
Template:Blockquote/styles.css (view source) (template editor protected)
Template:Category handler (view source) (protected)
Template:Citation (view source) (protected)
Template:Citation needed (view source) (protected)
Template:Cite magazine (view source) (protected)
Template:Cite mailing list (view source) (protected)
Template:Cite news (view source) (protected)
Template:Cite web (view source) (protected)
Template:DMCA (view source) (template editor protected)
Template:Dated maintenance category (view source) (template editor protected)
Template:Dated maintenance category (articles) (view source) (template editor protected)
Template:Delink (view source) (protected)
Template:Depends (view source) (semi-protected)
Template:Dropped (view source) (semi-protected)
Template:Efn (view source) (template editor protected)
Template:Explanation of the tables2 (edit)
Template:FULLROOTPAGENAME (view source) (template editor protected)
Template:Fix (view source) (protected)
Template:Fix/category (view source) (protected)
Template:HTML (edit)
Template:Hlist/styles.css (view source) (protected)
Template:Ifsubst (view source) (template editor protected)
Template:Incorrect (edit)
Template:MONTHNAME (view source) (template editor protected)
Template:MONTHNUMBER (view source) (template editor protected)
Template:Main (view source) (template editor protected)
Template:Main other (view source) (protected)
Template:Mono (view source) (template editor protected)
Template:Mono/styles.css (view source) (template editor protected)
Template:Navbox (view source) (template editor protected)
Template:Nightly (edit)
Template:No (view source) (template editor protected)
Template:Notelist (view source) (template editor protected)
Template:Ns has subpages (view source) (protected)
Template:Pagetype (view source) (protected)
Template:Partial (view source) (extended confirmed protected)
Template:Pipe (view source) (template editor protected)
Template:Reflist (view source) (protected)
Template:Reflist/styles.css (view source) (protected)
Template:SDcat (view source) (protected)
Template:See also (view source) (template editor protected)
Template:Short description (view source) (protected)
Template:Short description/lowercasecheck (view source) (protected)
Template:Sidebar (view source) (template editor protected)
Template:Small (view source) (protected)
Template:Smaller (view source) (template editor protected)
Template:Table-experimental (edit)
Template:Use dmy dates (view source) (template editor protected)
Template:W3C standards (edit)
Template:Web interfaces (edit)
Template:Yes (view source) (template editor protected)
Template:Yesno (view source) (protected)
Module:Arguments (view source) (protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:Delink (view source) (protected)
Module:Disambiguation/templates (view source) (protected)
Module:Format link (view source) (template editor protected)
Module:Hatnote (view source) (template editor protected)
Module:Hatnote/styles.css (view source) (template editor protected)
Module:Hatnote list (view source) (template editor protected)
Module:Labelled list hatnote (view source) (template editor protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:Navbar (view source) (protected)
Module:Navbar/configuration (view source) (protected)
Module:Navbar/styles.css (view source) (protected)
Module:Navbox (view source) (template editor protected)
Module:Navbox/configuration (view source) (template editor protected)
Module:Navbox/styles.css (view source) (template editor protected)
Module:Ns has subpages (view source) (protected)
Module:Pagetype (view source) (protected)
Module:Pagetype/config (view source) (protected)
Module:Pagetype/disambiguation (view source) (protected)
Module:Pagetype/setindex (view source) (protected)
Module:Pagetype/softredirect (view source) (protected)
Module:SDcat (view source) (protected)
Module:Sidebar (view source) (template editor protected)
Module:Sidebar/configuration (view source) (template editor protected)
Module:Sidebar/styles.css (view source) (template editor protected)
Module:String (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Wikitext Parsing (view source) (template editor protected)
Module:Yesno (view source) (protected)

Return to HTML5 video.

Retrieved from "https://en.wikipedia.org/wiki/HTML5_video"