Supported media formats

The <audio> and <video> elements provide support for playing audio and video without plug-ins. The format of a media file consists of a container holding one or more streams of data, encoded using a compression format called a codec. A container is identifiable by its file extension. The streams within a container are of multiple types that can include video, audio, data, or captions. A single container (i.e. media file) can hold multiple streams of the same type. Within the audio and video streams are the codecs. A codec, short for "coder-decoder", is an algorithm for compressing data within a file. Each container type has only specific codecs that it supports.

It's important to understand why different media formats are needed for the web. For various reasons mostly outside the scope of this article, different browsers support different media formats. Also, the area of media formats on the Web has greatly suffered from patent law in many countries including the USA and EU countries. (The notes on patents in this article are provided as-is and without any warranty.) This article discusses the formats most relevant to the web, including support in browsers on both mobile and desktop.

Displaying Media

Here's a brief review of how media elements are referenced in HTML. For more details see the articles for each element.

HTML5 supports several media elements. The <video> and <audio> elements may be used singly or combined with the <source> element. A short example illustrates. Although the <video> and <audio> elements both contain src attributes, this sample uses the <source> element to offer video files in multiple formats, allowing each browser to select an element that it supports.

<video controls>
  <source src="somevideo.webm" type="video/webm">
  <source src="somevideo.mp4" type="video/mp4">
  I'm sorry; your browser doesn't support HTML5 video in WebM with VP8/VP9 or MP4 with H.264.
</video>

File Formats

Listed below are a number (though not all) of file formats supported by HTML media elements. To learn which browsers support which formats, see the Browser Compatibility section at the bottom of this page.

WebM

The WebM format is based on a restricted version of the Matroska container format. It always uses the VP8 or VP9 video codec and the Vorbis or Opus audio codec.

The WebM format, specifically the VP8 video codec, had been accused of patent infringment by a group of companies answering a call by the MPEG LA for the formation of a patent pool, but MPEG LA has agreed to license those patents to Google under a "perpetual, transferable, royalty free license". This means, effectively, that all known patents on the WebM format are licensed to everyone for free.

Gecko recognizes the following MIME types as WebM files:

video/webm

A WebM media file containing video (and possibly audio as well).

audio/webm

A WebM media file containing only audio.

Ogg Theora Vorbis

The Ogg container format with the Theora video codec and the Vorbis audio codec is supported in desktop/mobile Gecko (Firefox), Chrome, and Opera, and support for the format can be added to Safari (but not on iOS) by installing an add-on. The format is not supported in Internet Explorer in any way.

WebM is generally preferred over Ogg Theora Vorbis when available, because it provides a better compression to quality ratio and is supported in more browsers. The Ogg format can however be used to support older browser versions (for example Firefox 3.5/3.6 don't support WebM, but do support Ogg.)

The patent situation of Theora is similar to that of WebM.

You can learn more about creating Ogg media by reading the Theora Cookbook.

Gecko recognizes the following MIME types as Ogg files:

audio/ogg

An Ogg file containing only audio.

video/ogg

An ogg file containing video (and possibly also audio).

application/ogg

An Ogg file with unspecified content. Using one of the other two MIME types is preferred, but you can use this if you don't know what the contents of the file are.

Ogg Opus

The Ogg container can also contain audio encoded using the Opus codec. Support for this is available in Gecko 15.0 (Firefox 15.0 / Thunderbird 15.0 / SeaMonkey 2.12) and later, on desktop and mobile browsers.

Firefox recognizes the following MIME type:

audio/ogg; codecs=opus

See RFC 7845 section 9.

Ogg FLAC

The Ogg container can also contain audio encoded using the FLAC codec. Support for this is available in Gecko 51.0 (Firefox 51.0 / Thunderbird 51.0 / SeaMonkey 2.48) and later on desktop and on mobile in Gecko 58.0 (Firefox 58.0 / Thunderbird 58.0 / SeaMonkey 2.55).

MP4 H.264 (AAC or MP3)

The MP4 container format with the H.264 video codec and the AAC audio codec is natively supported by desktop/mobile Internet Explorer, Safari and Chrome, but Chromium and Opera do not support the format. IE and Chrome also support the MP3 audio codec in the MP4 container, but Safari does not. Firefox/Firefox for Android/Firefox OS supports the format in some cases, but only when a third-party decoder is available, and the device hardware can handle the profile used to encode the MP4.

The MPEG media formats are covered by patents, which are not freely licensed. Some of the necessary licenses can be bought from MPEG LA. Since H.264 is currently not a royalty free format, it is unfit for the open web platform, according to Mozilla [1, 2], Google [1, 2] and Opera. However, since royalty free formats are not supported by Internet Explorer and Safari, Mozilla has decided to support the format anyway, and Google never fulfilled their promise to remove support for it in Chrome.

MP4 FLAC

Starting in Firefox 51, you can play MP4 files using the FLAC codec, both with and without MediaSource Extensions and DRM support.

MP3

The MP3 audio format (.mp3, audio/mpeg; distinct from the above MP3 audio in an MP4 container case) is supported in <audio> by Firefox/Firefox for Android/Firefox OS when the operating system provides an MP3 decoder, and by Internet Explorer, Chrome and Safari.

WAVE PCM

The WAVE container format, with the PCM audio codec (WAVE codec "1") is supported by desktop/mobile Gecko (Firefox) and Safari. Files in the WAVE container format typically end with the ".wav" extension.

Gecko recognizes the following MIME types as WAVE audio files:

• audio/wave (preferred; does not work in Chrome)
• audio/wav
• audio/x-wav
• audio/x-pn-wav

FLAC

The FLAC container format, with the FLAC audio codec (FLAC codec) is supported by desktop Gecko Firefox 51.0 (Firefox 51.0 / Thunderbird 51.0 / SeaMonkey 2.48) and by mobile Gecko 58.0 (Firefox 58.0 / Thunderbird 58.0 / SeaMonkey 2.55). Files in the FLAC container format typically end with the ".flac" extension.

Gecko recognizes the following MIME types as FLAC audio files:

• audio/flac (preferred)
• audio/x-flac

Browser compatibility

[1] Must be installed separately.

[2] In Nightly/Dev Edition only.

[3] Only on platforms that support H.264.

[4] AAC is only supported in the MP4 container. Not in Chromium.

[5] To avoid patent issues, support for MP3 is not built directly into Firefox. Instead it relies on support from the OS. Firefox supports this format on the following platforms: Windows Vista+ since Firefox 22.0, Android since Firefox 20.0, Firefox OS since Firefox 15.0, Linux since Firefox 26.0 (relies on GStreamer codecs) and OS X 10.7 since Firefox 35.0.

[6] Main only. Not in Chromium. AAC is only supported in the MP4 container.

[7] AAC is only supported in the MP4 container. To avoid patent issues, support for MPEG 4 and AAC is not built directly into Firefox. Instead it relies on support from the OS or hardware (the hardware also needs to be able to support the profile used to encode the video, in the case of MP4). Firefox supports these formats on the following platforms: Windows Vista+ since Firefox 22.0, Android since Firefox 20.0, Firefox OS since Firefox 15.0, Linux since Firefox 26.0 (relies on GStreamer codecs) and OS X 10.7 since Firefox 35.0.

[8] must be installed separately, e.g. WebM MF.

[9] Must be installed separately, e.g. Perian.

[10] To avoid patent issues, support for MPEG 4, H.264 and MP3 is not built directly into Firefox. Instead it relies on support from the OS or hardware (the hardware also needs to be able to support the profile used to encode the video, in the case of MP4). Firefox supports these formats on the following platforms: Windows Vista+ since Firefox 22.0, Android since Firefox 20.0, Firefox OS since Firefox 15.0, Linux since Firefox 26.0 (relies on GStreamer codecs) and OS X 10.7 since Firefox 35.0.

[11] AAC is only supported in the MP4 container. To avoid patent issues, support for MPEG 4, H.264 and AAC is not built directly into Firefox. Instead it relies on support from the OS or hardware (the hardware also needs to be able to support the profile used to encode the video, in the case of MP4). Firefox supports these formats on the following platforms: Windows Vista+ since Firefox 22.0, Android since Firefox 20.0, Firefox OS since Firefox 15.0, Linux since Firefox 26.0 (relies on GStreamer codecs) and OS X 10.7 since Firefox 35.0.

[12] Plays all formats available via QuickTime.

[13] Opera Mini itself doesn't support any video or audio, but any video or audio is passed to the device to play if it has support for that format. Opera Mobile also does this with unsupported formats.

[14] Opera Mini itself doesn't support any video or audio, but any video or audio is passed to the device to play if it has support for that format. Opera Mobile also does this with unsupported formats.

[15] Opera Mini itself doesn't support any video or audio, but any video or audio is passed to the device to play if it has support for that format. Opera Mobile also does this with unsupported formats.

[16] Opera Mini itself doesn't support any video or audio, but any video or audio is passed to the device to play if it has support for that format. Opera Mobile also does this with unsupported formats.

[17] To avoid patent issues, support for MP3 is not built directly into Firefox Mobile (Android). Instead it relies on support from the OS or hardware.

[18] To avoid patent issues, support for MP3 is not built directly into Firefox OS. Instead it relies on support from the OS or hardware.

[19] Opera Mini itself doesn't support any video or audio, but any video or audio is passed to the device to play if it has support for that format. Opera Mobile also does this with unsupported formats.

[20] AAC is only supported in the MP4 container. To avoid patent issues, support for MPEG 4 and AAC is not built directly into Firefox Mobile (Android). Instead it relies on support from the OS or hardware (the hardware also needs to be able to support the profile used to encode the video, in the case of MP4).

[21] AAC is only supported in the MP4 container. To avoid patent issues, support for MPEG 4 and AAC is not built directly into Firefox OS. Instead it relies on support from the OS or hardware (the hardware also needs to be able to support the profile used to encode the video, in the case of MP4).

[22] Opera Mini itself doesn't support any video or audio, but any video or audio is passed to the device to play if it has support for that format. Opera Mobile also does this with unsupported formats. AAC is only supported in the MP4 container.

[23] Opera Mini itself doesn't support any video or audio, but any video or audio is passed to the device to play if it has support for that format. Opera Mobile also does this with unsupported formats.

[24] Opera Mini itself doesn't support any video or audio, but any video or audio is passed to the device to play if it has support for that format. Opera Mobile also does this with unsupported formats.

[25] Opera Mini itself doesn't support any video or audio, but any video or audio is passed to the device to play if it has support for that format. Opera Mobile also does this with unsupported formats.

[26] To get the default Android browser to play H.264 video, you need to jump through some hoops, as explained by Peter Gasston.

[27] In Firefox OS 1.0.1, when detecting <video> support for different formats, HTMLMediaElement.prototype.canPlayType incorrectly reports true for h.264 video whereas in actual fact h.264 is not supported. In Firefox OS 1.1 this problem has been fixed.
To avoid patent issues, support for MPEG 4, H.264 and MP3 is not built directly into Firefox Mobile (Android) and Firefox OS. Instead it relies on support from the OS or hardware (the hardware also needs to be able to support the profile used to encode the video, in the case of MP4).

[28] Partial since 11.0. AAC is only supported in the MP4 container.

[29] Opera Mini itself doesn't support any video or audio, but any video or audio is passed to the device to play if it has support for that format. Opera Mobile also does this with unsupported formats.

[30] AAC is only supported in the MP4 container. To get the default Android browser to play H.264 video, you need to jump through some hoops, as explained by Peter Gasston.

[31] In Firefox OS 1.0.1, when detecting <video> support for different formats, HTMLMediaElement.prototype.canPlayType incorrectly reports true for h.264 video whereas in actual fact h.264 is not supported. In Firefox OS 1.1 this problem has been fixed. AAC is only supported in the MP4 container.
To avoid patent issues, support for MPEG 4, H.264 and ACC is not built directly into Firefox OS. Instead it relies on support from the OS or hardware (the hardware also needs to be able to support the profile used to encode the video, in the case of MP4).

[32] Opera Mini itself doesn't support any video or audio, but any video or audio is passed to the device to play if it has support for that format. Opera Mobile also does this with unsupported formats. AAC is only supported in the MP4 container.

[33] To avoid patent issues, support for MPEG 4, H.264 and MP3 is not built directly into Firefox Mobile (Android). Instead it relies on support from the OS or hardware (the hardware also needs to be able to support the profile used to encode the video, in the case of MP4).

[34] To avoid patent issues, support for MPEG 4, H.264 and ACC is not built directly into Firefox Mobile (Android). Instead it relies on support from the OS or hardware (the hardware also needs to be able to support the profile used to encode the video, in the case of MP4).

[35] VP8/VP9 video codecs are only available in MSE when H.264 hardware decoders are not available. Checking for availability via MediaSource.isTypeSupported() is recommended.

[36] Starting in Firefox 46, when attempting to initiate a WebRTC call using RTCPeerConnection.createOffer() uses VP9 by default; in the past, VP8 was the default video format.

See also

• Media Source Extensions API
• Using audio and video in Firefox
• HTML media support in Firefox
• Media elements (HTML 5 specification)
• <video>
• <audio>
• Video codecs in Opera
• Video codecs in Internet Explorer
• Audio codecs in Internet Explorer
• Audio & Video codecs in Chrome