SYSTEM Cited by 1 source

libwebrtc¶

What it is¶

libwebrtc is the open-source real-time communication library originally released by Google and now maintained as part of the Chromium project. It provides the standard-compliant implementation of WebRTC (peer-to-peer audio, video, and data channels) used in Chrome, Edge, Firefox (partially), and most of the industry's native RTC clients.

Why it matters¶

libwebrtc is the de facto industry substrate for RTC in native applications. Implementing WebRTC from scratch is economically untenable for any individual company. But libwebrtc is large, fast-moving (shipped on Chromium's ~6-week release cadence), and deeply opinionated in places internal consumers often want to override (codec selection, bandwidth estimation, jitter buffer, network transport). This produces the recurring pressure toward internal forking — see concepts/internal-fork-divergence — and the corresponding engineering problem of staying current once you've forked.

Release anchoring¶

libwebrtc ships with Chromium. Each Chromium milestone (M143, M145, ...) has an associated libwebrtc Git tag (M143 = tag 7499, M145 ≈ 7559). Branch-tracking schemes for internal patches typically anchor to these tags — see patterns/external-feature-branch-repo-for-monorepo-patches.

Upstream tooling¶

The upstream libwebrtc project uses Chromium's build and contribution toolchain: gn (build configuration), gclient (multi-repo dependency management), git cl (code-review CLI). Anyone basing an internal patch system on the libwebrtc Git repo inherits this toolchain — one of Meta's stated reasons for choosing Solution 2 (feature branches in an external Git repo based on libwebrtc) was being able to reuse these tools directly.

Seen in¶

sources/2026-04-09-meta-escaping-the-fork-webrtc-modernization — Meta describes retiring its years-divergent libwebrtc fork, migrating 50+ use cases to upstream via the dual-stack shim. Launched webrtc/latest at M120, now at M145 ("living at head"). Concrete wins from the upstream version: up to 10% CPU drop, up to 3% crash-rate improvement, 100–200 KB compressed binary size reduction, deprecated insecure libraries (e.g. usrsctp) retired with the legacy stack.

systems/chromium-git — the upstream Git hosting + tooling context libwebrtc lives in.
systems/meta-webrtc-shim — Meta's proxy layer over dual-linked libwebrtc copies.
concepts/internal-fork-divergence — the failure mode Meta's retirement story is the escape hatch from.