WebM

Google introduced WebM in 2010, after acquiring On2 Technologies, as an open, royalty-free video container and codec pairing (VP8, later VP9 and AV1, with Vorbis or Opus audio) built specifically for the web. The goal was to give HTML5 video a viable alternative to H.264/MP4, whose patent pool required licensing fees, so browser vendors and publishers weren't locked into royalty-bearing codecs for web playback.

WebM pairs open video codecs (VP8, VP9, AV1) with Vorbis or Opus audio, and is technically a constrained profile of the Matroska container, restricted to a defined set of open codecs so browsers know exactly what to decode.

No — WebM is a strong choice for the web-delivery proxy tier because of its royalty-free licensing and strong compression efficiency, but it's a lossy delivery codec optimized for streaming bandwidth, not post-production fidelity, so it shouldn't replace a higher-fidelity archival master.

WebM typically compresses more efficiently than H.264 at a given visual quality and carries no per-unit royalty exposure, while MP4 offers the broadest compatibility — generating both from the same archival master covers compression efficiency and universal playback at once.

Mostly, but not universally. Chrome, Firefox, and Edge have supported WebM natively for years, and desktop Safari added support starting with Safari 16. Safari on iOS/iPadOS only gained native WebM playback in version 17.4 — far later than its MP4/H.264 support, which has existed since the first iPhone. So unlike MP4, which plays almost everywhere, WebM support depends on browser and OS version.

A DAM should pin the exact encoder — libvpx for VP8/VP9 or SVT-AV1 for AV1 — plus its version number and encoding preset (CRF/bitrate, speed setting, two-pass flags) inside the transcode profile's metadata, not just "WebM" as a format label. Encoder defaults shift between releases, so recording the precise version and settings used for each proxy ensures regenerating it years later reproduces the same bitrate and visual result instead of drifting silently.

Android has supported WebM natively since early versions and treats it like any other HTML5 video format. iOS is the outlier: Safari on iPhone and iPad only gained native WebM playback in iOS/iPadOS 17.4 (2024), and no native app decoder supports it outside Safari — third-party apps need their own decoder or a conversion step. That's a sharp contrast with MP4/H.264, which iOS has supported natively since its first release, so mobile delivery pipelines often still default to MP4 for iOS-heavy audiences.

Google announced WebM in May 2010 after acquiring On2 Technologies and its VP8 codec, releasing it under a royalty-free patent license and open-sourcing the libvpx encoder/decoder — giving DAM teams licensing certainty when choosing it for delivery proxies.