Why the Tor Browser Uses Firefox Extended Support Release

The Tor Browser relies on Mozilla's Firefox Extended Support Release (ESR) as its foundational code to maximize user security, privacy, and development stability. By choosing Firefox ESR over standard browser releases or competing engines like Chromium, the Tor Project benefits from a predictable update cycle, an open-source architecture free from corporate surveillance, and a collaborative relationship with Mozilla. This strategic choice allows Tor developers to focus their limited resources on maintaining vital anonymity features rather than constantly fixing broken code caused by rapid browser updates.

Stability Through a Predictable Update Cycle

Standard web browsers, including the regular version of Firefox, release major updates every few weeks. These updates constantly introduce new features, redesigns, and underlying code changes. For the Tor Project, which applies hundreds of custom privacy and security patches to the browser, a four-week update cycle is unsustainable. Every new feature introduced by a standard browser update must be audited by Tor developers to ensure it does not accidentally leak user data or break existing anonymity protections.

Firefox ESR solves this problem. Designed primarily for universities, businesses, and government organizations, the ESR version freezes feature updates for roughly a year. During this period, Mozilla only pushes critical high-level security patches to the ESR branch. This stability allows the Tor Project to maintain its custom patches without them breaking every month, giving developers the time they need to thoroughly vet major code changes once a year.

Focus on Security Over New Features

New browser features often introduce new security vulnerabilities and tracking vectors. Because the Tor Browser is used by journalists, activists, and whistleblowers who require the highest level of operational security, newly introduced bugs can have severe real-world consequences.

By using Firefox ESR, the Tor Browser avoids the risks associated with bleeding-edge browser features. The codebase remains static, and the only updates applied are those that fix known security flaws. When the time comes to transition to the next major ESR version, those "new" features have already been tested by millions of standard Firefox users for nearly a year, ensuring most bugs have already been discovered and resolved.

Mission Alignment and the "Uplift" Project

The Tor Project requires an open-source browser to ensure the code can be audited for backdoors and data leaks. While Google’s Chromium is also open-source, Google's primary business model relies on data collection and targeted advertising—the exact opposite of Tor's mission. Stripping Google's tracking mechanisms out of Chromium is a massive, ongoing challenge for other privacy browsers.

Mozilla, a non-profit-backed organization, aligns much more closely with the Tor Project's goals. In fact, Mozilla and Tor actively collaborate. Through an initiative known as the "Tor Uplift" project, Mozilla has taken many of the custom anti-fingerprinting and privacy patches created by the Tor Project and built them directly into the core code of Firefox. This reduces the number of custom patches the Tor Project has to maintain on its own.

Advanced Proxy and Network Control

From a technical standpoint, Firefox has historically offered much better support for complex proxy configurations than its competitors. The Tor Browser must route all of its traffic through the encrypted Tor network without leaking any data, such as DNS requests, to the user's local internet service provider. Firefox's architecture makes it significantly easier to isolate network connections, disable risky web APIs, and enforce strict proxy rules compared to the Blink/Chromium engine, which is more tightly integrated with the host operating system's network stack.