HTML video

History of <video> element

The element started being discussed by the WHATWG in October 2006. The element was proposed by Opera Software in February 2007. Opera also released a preview build that was showcased the same day, and a manifesto that called for video to become a first-class citizen of the web.

<video> element examples

The following HTML code fragment will embed a WebM video into a web page.

<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>

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 elements, as shown below, the browser will choose automatically which file to download. Alternatively, the JavaScript function can be used to achieve the same. The "type" attribute specifies the 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.

<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>

Supported video and audio formats

The HTML 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, replacing the reference to concrete formats:

with a placeholder:

The result was a polarisation of HTML video between industry-standard, ISO-defined but patent-encumbered formats, and open formats. 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

Mozilla and Opera initially supported only the open formats of Theora and WebM. Although Theora is not affected by known non-free patents, Apple expressed concern about unknown patents that might affect it, whose owners might be waiting for a corporation with extensive financial resources to use the format before suing. Formats like 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 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.

Some web developers criticized the removal of the Ogg formats from the specification. A follow-up discussion also occurred on the W3C questions and answers blog.

MPEG-DASH Support via the Media Source Extensions (MSE)

The adaptive bitrate streaming standard MPEG-DASH can be used in Web browsers via the Media Source Extensions (MSE) and JavaScript-based DASH players. Such players are, e.g., the open-source project dash.js of the DASH Industry Forum, but there are also products such as the HTML5 Video Player of Bitmovin (using HTML with JavaScript, but also a Flash-based DASH players for legacy Web browsers not supporting the MSE).

Google's purchase of On2

Google's acquisition of On2 in 2010 resulted in its acquisition of the VP8 video format. Google has provided a royalty-free license to use VP8. 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.

When Google announced in January 2011 that it would end native support of H.264 in Chrome, criticism came from many quarters including Peter Bright of Ars Technica and Microsoft web evangelist Tim Sneath, who compared Google's move to declaring Esperanto the official language of the United States. However, Haavard Moen of Opera Software strongly criticized the Ars Technica article and Google responded to the reaction by clarifying its intent to promote WebM in its products on the basis of openness.

After the launch of WebM, Mozilla and Opera have called for the inclusion of VP8 in HTML.

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.

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.

Non-free formats

H.264/MPEG-4 AVC is widely used, and has good speed, compression, hardware decoders, and video quality, but is patent-encumbered. 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. 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.

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 freely available

Main article: 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.

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. The H.264 module will be available on "all popular or feasibly supportable platforms, which can be loaded into any application".

Cisco is also planning to publish source code for those modules under BSD license, but without paying the royalties, so the code will practically be free software only in countries without H.264 software patents, 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.

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.{{cite web |access-date=25 February 2015 |access-date=25 February 2015 |access-date=25 February 2015 However, for use in WebRTC, the omission of AAC was justified in the release announcement: "the standards bodies have aligned on Opus and G.711 as the common audio codecs for WebRTC". 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.

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. 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 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 HTML audio for a table of which audio formats are supported by each browser.

The video format can be specified by MIME type in HTML (see example). MIME types are used for querying multimedia frameworks for supported formats.

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 cannot legally support other than free formats by default on the free operating systems that they are intended for.

;Notes:

Transparent video

Transparent video, that is video with an alpha channel, has multiple design advantages:

• 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 SVG or 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

• Chrome supports VP8 and VP9 encoded videos with an alpha channel served in a WebM container, since version 31 in 2013-07.
• Safari supports HEVC encoded videos with an alpha channel served in a MP4 container, since iOS 13 (2019-09) and macOS Catalina (2019-10).
• There are some other proprietary polyfill / legacy solutions with a JavaScript based video player playing back a video which upon upload to the SaaS server got converted into a 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 and using the transparent flag in its embedding code.

Digital rights management (Encrypted Media Extensions)

Main article: Encrypted Media Extensions

HTML has support for digital rights management (DRM, restricting how content can be used) via the 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. 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.

In 2013 Netflix added support for HTML video using EME, beside their old delivery method using a Silverlight plugin (also with DRM).

Usage

In 2010, in the wake of Apple iPad launch and after Steve Jobs announced that Apple mobile devices would not support Flash, a number of high-profile sites began to serve H.264 HTML video instead of Adobe Flash for user-agents identifying as iPad. HTML video was not as widespread as Flash videos, though there were rollouts of experimental HTML-based video players from DailyMotion (using Ogg Theora and Vorbis format), YouTube (using the H.264 and WebM formats), and Vimeo (using the H.264 format).

Support for HTML video has been steadily increasing. In June 2013, Netflix added support for HTML video. In January 2015, YouTube switched to using HTML video instead of Flash by default. In December 2015, Facebook switched from Flash to HTML video for all video content.

As of 2016, Flash is still widely installed on desktops, while generally not being supported on mobile devices such as smartphones. The Flash plugin is widely assumed, including by Adobe, to be destined to be phased out, which will leave HTML video as the only widely supported method to play video on the World Wide Web. Chrome, Firefox, Safari, and Edge, 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. Adobe announced on 25 July 2017 that they would be permanently ending development of Flash in 2020.

References

References

1. (24 June 2010). "The video element". [[World Wide Web Consortium]].
2. "[whatwg] How not to fix HTML from Charles Iliya Krempeaux on 2006-10-30 (whatwg@whatwg.org from October 2006)".
3. van Kesteren, Anne. (28 February 2007). "[whatwg] <video> element proposal".
4. "Browser War: Episode II – Attack of the DOMs".
5. (March 1, 2007). "SV Web Builders Event – World Premier of Opera with builtin video support".
6. "A Call for Video on the Web".
7. "The "codecs" parameter in common media types".
8. Hickson, Ian. (10 December 2007). "Video codec requirements changed".
9. "(X)HTML5 Tracking". [[HTML5]].
10. Amador, Manuel. (11 December 2011). "Removal of Ogg is preposterous".
11. Metz, Cade. (April 30, 2010). "Steve Jobs: mystery patent pool to attack Ogg Theora". The Register.
12. Hickson, Ian. (11 December 2007). "Re: Removal of Ogg is preposterous".
13. Stachowiak, Maciej. (21 March 2007). "Codecs (was Re: Apple Proposal for Timed Media Elements)".
14. (11 December 2007). "[whatwg] Removal of Ogg is preposterous".
15. Connolly, Dan. (18 December 2007). "When will HTML 5 support <video>? Sooner if you help". [[W3C]].
16. (July 26, 2022). "Media Source Extensions".
17. (20 April 2022). "Adaptive Streaming HTML5 Player from Bitmovin".
18. "Additional IP Rights Grant (Patents)".
19. Lee, Matt. (19 May 2010). "Free Software Foundation statement on WebM and VP8". [[Free Software Foundation.
20. Jazayeri, Michael 'Mike'. (January 11, 2011). "HTML Video Codec Support in Chrome". The Chromium Blog.
21. Bright, Peter. (12 January 2011). "Google's dropping H.264 from Chrome a step backward for openness". Ars Technica.
22. Sneath, Tim. (11 January 2011). "An Open Letter from the President of the United States of Google". [[Microsoft Developer Network.
23. Moen, Haavard K. (13 January 2011). "Is the removal of H.264 from Chrome a step backward for openness?". [[My Opera]].
24. Jazayeri, Michael 'Mike'. (14 January 2011). "More about the Chrome HTML Video Codec Change". [[Chromium (web browser).
25. Metz, Cade. (28 May 2010). "Mozilla and Opera call for Google open codec in HTML5 spec". The Register.
26. djwm. (7 March 2013). "Google and MPEG LA make a deal over VP8 codec – Update". [[Heise Media UK]].
27. "Archived copy".
28. (7 March 2013). "VP8 and MPEG LA". WebM Project blog.
29. (March 8, 2013). "Patent clouds remain over VP8: Google points to FRAND option, Nokia alleges infringement in court".
30. (1 February 2010). "AVC/H.264 Patent List". MPEG LA.
31. "AVC/H.264 Licensors". [[MPEG LA]].
32. Hickson, Ian. (29 June 2009). "Codecs for <audio> and <video>".
33. "OpenH264".
34. (30 October 2013). "Open-Sourced H.264 Removes Barriers to WebRTC". Cisco.
35. Brendan Eich. (30 October 2013). "Cisco's H.264 Good News". Brendan Eich's blog.
36. Monty Montgomery. "Comments on Cisco, Mozilla, and H.264". Monty Montgomery blog.
37. xiphmont. "It's not a strawman after it comes true".
38. "Qt". Nokia.
39. "Codec Support Table".
40. "Qt". Nokia.
41. (29 June 2007). "GNU General Public License Version 3". Free Software Foundation.
42. "Issue 4363: [HTML5-Video] Enable HTML5 video/audio elements".
43. "enable proprietary_codecs h.264".
44. (9 June 2015). "Chromium does not support H.264".
45. "Audio/Video – The Chromium Projects".
46. "Code review".
47. "[chrome] Revision 172738".
48. (20 May 2010). "Code".
49. "Chrome 3.0 supportera la balise vidéo du HTML 5".
50. Mike, Jazayeri. (11 January 2011). "Chromium Blog: HTML Video Code Support in Chrome". The Chromium Blog.
51. "Google Chrome Plays HEVC: What Does it Mean? - Streaming Media".
52. "Google Quietly Added HEVC Support in Chrome - Bitmovin".
53. Bankoski, Jim. (19 May 2010). "WebM and VP8 land in Chromium".
54. Kersey, Jason. (3 June 2010). "Chrome Releases".
55. Lucian Parfeni. (28 December 2012). "Chrome Adds Support for the Next-Generation VP9 Video Codec and Mozilla's Opus Audio".
56. Lucian Parfeni. (17 June 2013). "Chrome Now Supports Google's Next-Gen VP9 Video Codec by Default".
57. "AV1 Decode".
58. McCracken, Harry. (16 March 2010). "Microsoft Previews the Revamped Internet Explorer 9 Platform". Technologizer.
59. Jan Ozer. (5 November 2014). "Apple Supports H.265, But So Far Only in FaceTime on an iPhone 6".
60. (13 October 2011). "HTML5 Video Support in IE9 Mobile". Microsoft.
61. Blog, Microsoft Edge. (2020-01-15). "Upgrading to the new Microsoft Edge".
62. "Can I use... Support tables for HTML5, CSS3, etc".
63. "Can I use... Support tables for HTML5, CSS3, etc".
64. "Can I use... Support tables for HTML5, CSS3, etc".
65. (5 December 2017). "Introducing the Web Media Extension Package with OGG Vorbis and Theora support for Microsoft Edge". [[Microsoft]].
66. "HTML5test – How well does your browser support HTML5?".
67. "HEVC Support".
68. "Windows 10 HEVC playback – Yes or No?".
69. "HTML5test - How well does your browser support HTML5?".
70. "The status of VP9 Video Playback in Microsoft Edge is Shipped - Microsoft Edge Development".
71. (11 April 2018). "Redstone 4 Brings Better WebM Support in Edge".
72. "Add AV1 Codec Support to Windows 10 – Tutorials".
73. "HTML5test – How well does your browser support HTML5?".
74. (February 2017). "Introducing WebRTC 1.0 and interoperable real-time communications in Microsoft Edge".
75. (18 April 2016). "WebM, VP9 and Opus Support in Microsoft Edge". [[Microsoft]].
76. (30 June 2009). "Mozilla Firefox 3.5 Release Notes". Mozilla.
77. "Bug 799315 – Windows Media Foundation backend for media playback". Mozilla.
78. "Bug 837859 – Enable WMF backend". Mozilla.
79. (2025-03-04). "Web video codec guide - Media technologies on the web {{!}} MDN".
80. (22 March 2011). "Mozilla Firefox 4.0 Release Notes". Mozilla.
81. "[Phoronix] Mozilla Firefox Enables VP9 Video Codec By Default". Phoronix.
82. "Firefox – Notes (28.0)".
83. (29 January 2019). "Firefox 65.0, See All New Features, Updates and Fixes". [[Mozilla Foundation]].
84. (19 March 2019). "Firefox 66.0, See All New Features, Updates and Fixes". [[Mozilla Foundation]].
85. "Bug 886181 – Pref on gstreamer backend". Mozilla.
86. "Bug 794282 – Enable GStreamer in official builds". Mozilla.
87. "Bug 1207429 – Enable FFMpeg by default". Mozilla.
88. (30 November 2012). "Mozilla ships Firefox with H.264 support on Android". Ars Technica.
89. "Bug 1070703 – Add mp4 support in 10.6 and 10.7 on Aurora". Mozilla.
90. Ozer, Jan. (26 November 2014). "The Case for VP9 – Streaming Media Magazine".
91. Jägenstedt, Philip. (31 December 2009). "(re-)Introducing <video>". Opera.
92. "Changelog for 24 – Opera Desktop".
93. Lie, Håkon Wium. (19 May 2010). "Welcome, WebM <video>!". Opera.
94. Mills, Chris. (19 May 2010). "Opera supports the WebM video format". Opera.
95. [https://forums.opera.com/topic/30578/ffmpeg-installation-instructions/3 FFMPEG installation instructions] on orums.opera.com
96. "Media formats supported by the HTML audio and video elements". Mozilla.
97. Martin Smole. (6 June 2017). "WWDC17 – HEVC with HLS – Apple just announced a feature that we support out of the box".
98. (5 March 2024). "WebKit Features in Safari 17.4 {{pipe}} WebKit".
99. "Safari 12.1 Release Notes {{pipe".
100. (16 July 2020). "Release Notes for Safari Technology Preview 110".
101. (18 September 2023). "WebKit Features in Safari 17.0".
102. (29 April 2021). "Safari New WebKit Features in Safari 14.1".
103. Persch, Christian. (1 April 2008). "The Future of Epiphany". epiphany mailing list-list.
104. "Overview of available plug-ins". [[GStreamer]].
105. "How to use transparent videos on the web in 2022 - Rotato".
106. (July 2013). "Alpha transparency in Chrome video".
107. "HEVC Video with Alpha - WWDC19 - Videos".
108. "Create transparent backgrounds in a SWF file".
109. "Apply OBJECT and EMBED tag attributes in Adobe Flash Professional".
110. "Keep DRM out of Web standards – Reject the Encrypted Media Extensions (EME) proposal – Defective by Design".
111. Yegulalp, Serdar. (4 October 2013). "Berners-Lee and W3C approve HTML5 video DRM additions".
112. (April 15, 2013). "HTML5 Video at Netflix". Netflix Technology Blog.
113. "iPad-ready websites". Apple.
114. (27 May 2009). "Watch Video...without Flash". Dailymotion.
115. (20 January 2010). "Introducing YouTube HTML5 Supported Videos". Youtube.
116. Dougherty, Brad. (21 January 2010). "Try our new HTML5 player!". Vimeo.
117. Anthony, Sebastian. (28 June 2013). "Netflix switches from Silverlight to HTML5 in Windows 8.1, reduces CPU usage dramatically – ExtremeTech".
118. McCormick, Rich. (27 January 2015). "YouTube drops Flash for HTML5 video as default".
119. Welch, Chris. (18 December 2015). "Facebook's website now uses HTML5 instead of Flash for all videos".
120. Paul, Ryan. (16 August 2012). "Availability of Adobe's Flash browser plugin discontinued on Android".
121. Tittel, Chris Minnick and Ed. (30 April 2014). "How Adobe Is Moving on From Flash to Embrace HTML5".
122. Williams, Owen. (1 September 2015). "Adobe Flash is finally dead". TNW | Apps.
123. Barrett, Brian. (15 July 2015). "Flash. Must. Die.".
124. (May 9, 2016). "Intent to implement: HTML5 by Default".
125. "So long, and thanks for all the Flash".
126. Smedberg, Benjamin. (July 20, 2016). "Reducing Adobe Flash Usage in Firefox".
127. (14 June 2016). "Next Steps for Legacy Plug-ins". [[Apple Inc]].
128. (14 December 2016). "Extending User Control of Flash with Click-to-Run". [[Microsoft]].
129. eross-msft. "Microsoft Edge and Internet Explorer 11 (Microsoft Edge for IT Pros)".
130. "Flash & The Future of Interactive Content".
131. (28 November 2017). "Firefox now lets you try streaming-video tech that could be better than Apple's". CNET.