Why Did Browsers Hesitate to Support WebM?
When Google introduced the WebM video format in 2010 as a free, open-source alternative for web video, it aimed to revolutionize online streaming. However, the format faced immediate pushback and slow adoption from several major browser manufacturers. This article explores the core reasons behind this initial hesitation, focusing on the fierce battles over patent liabilities, disagreements regarding hardware acceleration, and the competing industry standards that divided the web.
The Patent Indemnity Dilemma
The primary roadblock to WebM’s adoption was the fear of patent infringement lawsuits. While Google released WebM (utilizing the VP8 video codec) under a BSD-style open-source license, competitors—most notably Apple and Microsoft—argued that VP8 likely infringed on existing H.264 patents.
- The MPEG LA Threat: The MPEG LA, a licensing body that manages patent pools for the rival H.264 format, actively sought to establish a patent pool against VP8.
- Lack of Legal Indemnity: Google initially did not offer legal indemnification to companies using WebM. For risk-averse corporations, incorporating a format that could potentially lead to multi-million dollar lawsuits was an unacceptable gamble.
Hardware Acceleration and Efficiency
In the early 2010s, mobile browsing was exploding, making battery life and processing efficiency critical for hardware manufacturers.
- H.264’s Head Start: The competing H.264 codec already enjoyed widespread, dedicated hardware acceleration chips built into almost all mobile processors, laptops, and graphics cards. This allowed devices to decode HD video with minimal battery drain.
- CPU-Heavy Decoding: Because WebM was brand new, chips did not have built-in hardware decoding for it. Browsers attempting to play WebM files had to rely on software decoding, which heavily taxed the device’s CPU, causing laptops to run hot and mobile batteries to drain rapidly. Browser makers like Apple were unwilling to compromise device performance for an unproven format.
Corporate Alliances and Vested Interests
The hesitation was also deeply rooted in the commercial alignments of tech giants who had already invested heavily in the H.264 ecosystem.
- The Apple and Microsoft Stance: Both Apple and Microsoft were part of the MPEG LA consortium and held lucrative patents tied to H.264. Supporting WebM meant backing a rival format created by Google, which would actively devalue their own intellectual property.
- The Mozilla and Opera Contrast: Conversely, open-source advocates like Mozilla (Firefox) and Opera enthusiastically supported WebM from day one. Because they could not afford the hefty licensing fees required to ship H.264 natively in their browsers, they desperately needed a high-quality, royalty-free alternative.
Resolution and Current Status
The deadlock eventually began to break in 2013 when Google reached a settlement with the MPEG LA, securing a license for any patents that VP8 might have infringed upon. Furthermore, as Google iterated on the format with VP9 and eventually joined forces with Apple, Microsoft, and others to create the AV1 codec under the Alliance for Open Media, the industry moved past the early browser wars. Today, WebM is widely supported across all major browsers, but its early history remains a classic case study in how legal and commercial interests can stall open web standards.