What is a WebM file?

WebM is a container: a wrapper that holds streams encoded by something else. It is used for the web and streaming.

The extension is .webm, and the full name is WebM Video. Both matter less than what the file can hold, which is what the rest of this page is about.

Google published it in 2010.

Age is worth knowing here for one practical reason: the older a format is, the more programs have had time to learn it.

It is published in full, so anyone can implement it from the document rather than by inspection, which is why it turns up in so many programs and why files written twenty years ago still open. A published specification is not the same thing as a royalty-free one: where a format wraps a codec, the patent licensing is a separate question the standard does not settle.

WebM carries an alpha channel, so a logo keeps its soft edges over whatever sits behind it instead of arriving in a white box.

It usually holds VP8, VP9, AV1, Opus and Vorbis. This is the distinction behind most "why will this not play" questions: two files with the same extension can contain entirely different encodings, and a player that refuses one may be perfectly happy with the other.

It also explains why changing container is often fast and lossless while changing codec is neither. Moving the same stream into a different box rewrites the box; re-encoding rewrites the picture.

WebM can hold several audio tracks, subtitle tracks and a layout that lets it start playing before it has finished arriving.

That matters mostly when converting: whatever the target cannot hold is dropped, usually without a warning.

VLC and FFmpeg read it, and so do most programs of the same kind.

If a file will not open, the format is rarely the problem — it is more often that the program predates it. Converting to something older is the reliable way past that, and it is what the rest of this site is for.

Every current browser reads it.

That makes it a safe thing to put on a page or attach to a message without wondering what the other end has installed.

WebM is meant to be handed over rather than worked in. Editing one is possible and rarely pleasant; the sane approach is to change the source and export again.

The recurring complaints: support outside its home ground is uneven.

None of these is a reason to avoid the format. They are the things worth knowing before you are surprised by one, which is a different claim and a more useful one.

Google introduced WebM in 2010 to give the web a video format with no patent licensing attached, at a time when H.264 in MP4 carried royalties that made it awkward for open-source browsers to ship. It is a deliberately narrow container: a small list of permitted codecs, no optional extras, nothing a browser would have to be taught.

That narrowness is why every browser plays it and why so little else does. Televisions, older phones, video editors, messaging apps and most desktop media software were built around MP4 and never added it. A WebM is not a broken file — it is a file that is only fluent in one place.

WebM uses the Matroska container with almost everything switched off. Same underlying design as MKV, same internal organisation, but restricted to VP8 or VP9 for video and Vorbis or Opus for audio, with AV1 added later.

The restriction is the point. A browser implementing WebM needs decoders for a handful of codecs and nothing else, where MKV could contain anything and would demand an open-ended set. That is why WebM shipped in browsers and MKV did not, despite being the same container underneath.

Almost always a browser or something adjacent to one. Video saved or downloaded from a web page. Screen and camera recordings made by browser-based tools — meeting recorders, feedback widgets, coding-interview platforms. Exports from web editors. Files pulled from sites that serve VP9 to save bandwidth.

That origin explains the usual complaint precisely. The recording played back perfectly in the browser that made it, because the browser has the decoders. It arrives at a video editor, a phone gallery or a colleague’s desktop and there is nothing there that speaks VP9.

VP9 delivers roughly the same visible quality as H.264 in noticeably fewer bytes — commonly cited as a saving of a third or more, and AV1 improves on that again. For a service streaming to millions, that is a bandwidth bill rather than a technicality.

The trade is processing. H.264 decodes in dedicated hardware on essentially every device made this century; VP9 support in hardware is far patchier and AV1 patchier still, so playback can fall back to software and cost real battery. Efficient on the wire, expensive on an old laptop.

A large share of WebM files carry video with no audio track, and the file gives no hint. Screen recorders that were never granted microphone permission, animation exports, and short clips converted from GIF all produce silent video routinely.

The reason it surprises people is that they assume the audio was lost in conversion. It usually was not — it was never recorded. Worth checking the original before spending time trying to recover a track that does not exist.

WebM with VP8 or VP9 can carry genuine transparency, and browsers render it — video with see-through regions playing over a page background, used for animated overlays, product cutouts and title sequences.

MP4 has no equivalent in general use. Converting such a file flattens the transparency onto a solid colour, permanently. If a WebM is an overlay rather than a rectangle of footage, converting it destroys the property it exists for, and it should stay WebM until the compositing is done.

Unlike MKV, where the streams inside are often already H.264 and can simply be repackaged, a WebM almost always holds VP8, VP9 or AV1 — none of which MP4 accommodates in practice. The video has to be decoded and encoded again.

So expect it to take real time on a long recording, and expect one generation of quality loss. Choose a generous quality setting to keep that generation invisible; the source has already been compressed once and there is nothing to gain from being frugal with the second pass.

If the destination is a web page, WebM is already the better answer and converting makes the file larger for no benefit. The same holds for anything staying on a computer with a real media player — VLC and MPV handle it without complaint.

Convert when the file is leaving that world: going to a phone gallery, a television, a video editor, a messaging app, or a colleague whose software you do not control. The rule is the same as for every container on this site — the format should match the destination, not the source.

Screen recordings are long and personal in a way that makes upload-based conversion a poor bargain — meeting recordings, interview practice, bug reports showing an application with real data in it. A converter that receives the file receives all of that.

The conversion runs inside the browser tab, so nothing is transmitted and there is no queue or size ceiling beyond your own memory. For an hour-long recording that is the difference between a practical wait and an impossible upload.