How Web Browsers License MPEG-4 Playback

This article explores how major web browsers navigate the complex legal and financial landscape of MPEG-4 licensing. While the MPEG-4 format—specifically the H.264 video and AAC audio codecs—is universally used across the web, it is patent-encumbered, requiring royalty payments to the Via Licensing Alliance (formerly MPEG LA). Web browsers must resolve these licensing requirements to provide native media playback without passing direct costs or legal liabilities onto their users.

The MPEG-4 Licensing Challenge

The MPEG-4 standard, particularly its AVC (H.264) video component, is protected by thousands of patents. Anyone distributing software capable of decoding H.264 video must pay royalty fees once certain distribution thresholds are met. Because web browsers are distributed to hundreds of millions of users for free, managing these licensing costs is a massive financial and legal hurdle.

Mainstream web browsers use three primary strategies to handle these commercial licensing requirements.

1. Direct Licensing (Google Chrome and Microsoft Edge)

Commercial tech giants like Google and Microsoft handle MPEG-4 licensing through direct payment.

• Google Chrome: Google pays the necessary royalty fees to the licensing consortium for every installation of Chrome. Because Chrome is a proprietary browser built on top of the open-source Chromium project, Google can legally bundle the licensed, closed-source H.264 decoders directly into the Chrome binary.
• Microsoft Edge: Similarly, Microsoft covers the licensing fees for Edge. Because Edge is tightly integrated with the Windows operating system, it can also leverage Windows’ native, system-wide media pipeline, which Microsoft has already licensed.

Note: The open-source Chromium browser does not include these licensed codecs by default because open-source distributors cannot pay royalties on behalf of anonymous downstream users.

2. Operating System Integration (Apple Safari)

Apple handles MPEG-4 licensing by shifting the decoding responsibility from the browser to the hardware and operating system.

• Safari: Apple is a founding member of the MPEG LA consortium and holds many of the patents. Safari does not decode MPEG-4 content independently; instead, it delegates decoding to the underlying macOS or iOS operating system.
• Because the licensing fees for MPEG-4 are already baked into the purchase price of Apple hardware (iPads, iPhones, and Macs), Safari can play MPEG-4 content natively without requiring separate browser-specific licenses.

3. Third-Party and OS Delegation (Mozilla Firefox)

As a non-profit organization dedicated to open-source software, Mozilla cannot afford the multi-million dollar annual licensing fees required to bundle H.264 decoders directly inside Firefox. To provide native MPEG-4 playback, Firefox uses two alternative methods:

System-Level Decoders (Platform Decoding)

Firefox bypasses licensing fees by refusing to ship the decoder code within its browser. Instead, when Firefox encounters an MPEG-4 video, it utilizes the host operating system’s built-in, pre-licensed decoders: * On Windows, Firefox calls the Windows Media Foundation APIs. * On macOS, it calls Apple’s native AVFoundation APIs. * On Android, it utilizes the mobile operating system’s media framework.

The Cisco OpenH264 Partnership

For platforms like Linux, which often do not come with pre-licensed commercial codecs, Mozilla partners with Cisco.

Cisco created an open-source H.264 codec project called OpenH264 and agreed to pay the MPEG LA patent licensing fees for any software that downloads their pre-compiled binary module. When a user installs Firefox, the browser automatically downloads a compiled OpenH264 binary module directly from Cisco’s servers. Because the binary comes from Cisco, Cisco covers the royalty fees, allowing Firefox users to play H.264 legally and for free.

Summary of Browser Approaches