WebM Video MIME Type

What does video/webm mean?

The video/webm media type identifies a WebM file containing video, usually with the .webm extension. WebM is a multimedia container rather than a codec. It packages timed video, audio, and optional WebVTT text tracks while the codecs determine how those tracks are compressed.¹²

WebM is based on Matroska, but it defines a narrower profile for predictable web playback. The WebM Project specifies VP8 or VP9 video and Vorbis or Opus audio. Modern tools also commonly use AV1 video in WebM.¹³

The WebM Project documents .webm and video/webm as the format's conventional identifiers. The current IANA media-type registry does not list video/webm, so it is best described as a well-established industry media type rather than an IANA registration.²⁴

How WebM differs from a codec

A WebM filename does not mean “VP9 video.” Container and codec answer different questions:

This distinction matters when a file opens but one track does not play. A browser may understand the WebM container yet lack support for a particular codec, profile, bit depth, or hardware path.

For HTML, include a codecs parameter when you know the track formats:

<source src="movie.webm" type='video/webm; codecs="vp9, opus"'>

The browser can use that declaration to choose among sources before downloading the whole video. The actual file still needs to match the label.²

History of WebM

The WebM Project introduced WebM in 2010 as an open media format designed for the web. The project is open source and sponsored by Google. Its container structure uses a constrained subset of Matroska, paired initially with VP8 video and Vorbis audio. VP9, Opus, WebVTT tracks, and AV1-based workflows followed as the open-media ecosystem developed.¹³

That deliberately narrow design gives .webm a clearer compatibility promise than a general .mkv file. Matroska can carry a much broader range of codecs and features, while WebM focuses on combinations intended for web delivery.³

How to identify and open a WebM file

WebM uses EBML, the same binary framework as Matroska. Both can begin with the EBML header bytes 1A 45 DF A3, so those bytes alone are not a unique WebM magic number. A reliable inspector parses the EBML header and checks that its document type is webm before examining the tracks and codecs.²⁵

Current Chrome, Edge, Firefox, Opera, and Safari releases can play common WebM combinations. Codec support remains the deciding factor, especially on older devices or with unusual profiles. MDN recommends WebM as an open web-video container and suggests an MP4 fallback when broad compatibility matters.⁶

For local playback and inspection:

• VLC supports WebM and its common codecs.⁷
• FFmpeg can inspect, remux, and encode WebM files.⁸
• A current browser is often enough for a delivery-ready file.

WebM support in Poly

Poly turns supported .webm videos into media you can browse, search, and discuss:

• Browse with a representative thumbnail and timeline previews.
• Play the video in Poly and jump to relevant moments.
• Find available details such as duration, dimensions, frame rate, codecs, color information, and audio tracks.
• Search by filename, spoken transcript, and visual content.
• Ask the Poly agent about supported visual content, speech, and metadata.

Transcript search requires a usable audio track with audible speech. Silent video can still benefit from visual search. Playback and content-aware features depend on the media carried inside the container.

See Supported File Types for the compact video feature comparison.

WebM compared with MP4 and Matroska

These containers overlap, but they serve different priorities:

WebM's narrower profile can make web delivery simpler. MP4 often provides the widest compatibility, particularly with H.264 video and AAC audio. Matroska is a better fit when retaining many tracks, attachments, or less common codecs matters more than native browser playback.³⁶

Changing .mkv or .mp4 to .webm does not convert the file. The container must be written correctly, and every retained track must be suitable for the destination.

Converting WebM without unnecessary quality loss

Inspect the source tracks before choosing a conversion method:

FFmpeg supports WebM demuxing and muxing. Stream copying avoids another lossy generation when the existing tracks already suit the destination; otherwise transcoding is required.⁸ After conversion, check duration, synchronization, captions, color, transparency, and every required audio track before removing the source.

Security and privacy considerations

Treat WebM files from unknown sources as untrusted media. The container and its codecs are complex inputs, so use maintained browsers and players. Matroska's security guidance also warns readers not to execute attachments and to validate data before using it outside the container.⁵

WebM can carry titles, language labels, timestamps, captions, and multiple tracks. Review those details before publishing sensitive footage. Removing the visible video alone may not remove private speech, captions, or descriptive metadata.