Tor Browser16.0

Tor Browser 16.0 is now available for Desktop and Android. This is our first stable release based on Firefox ESR 153, incorporating a year's worth of changes that have been shipped upstream in Firefox. As part of this process, we've also completed our annual ESR transition audit, where we reviewed and addressed over 270 Bugzilla issues covering changes in Firefox that could negatively affect the privacy and security of Tor Browser users.

What's new for Desktop?

Redesigned Settings Tor Browser connects millions of people to the Tor network (and by extension, the free and open internet) out of the box. However, for those who need to circumvent advanced censorship, boost their security level, or tailor their browsing experience, clear and easy-to-use Settings are essential. To that end, Tor Browser 16.0 introduces a complete redesign of the Settings experience based on a parallel redesign shipped in Firefox in June. Improvements include a cleaner layout, updated navigation, and clearer labels and descriptions aimed at making settings easier to find, understand, and manage. Other noteworthy changes include: - The long-standing "General" page has been retired, with its contents distributed across new pages for Appearance, Downloads, Tabs and browsing, Accessibility and Languages. - Pages and components that are unique to Tor browser like Connection and Security Level have been rebuilt from scratch using Firefox's new components so they look and feel consistent with the rest of Settings. - Some settings that, if enabled, could compromise your privacy or make your browser easier to fingerprint have either been hidden or feature clear warnings. Fear not: your existing preferences will remain saved even if the original setting has moved or changed, and you can use the search bar at the top of Settings to find anything you're struggling to track down.

Generic window titles Another new addition to Settings is the option to use generic window titles, which can be found under Privacy and security → Protections from third‑party applications. Like most browsers, Tor Browser uses the title of the page you're currently viewing for the names of its windows. However, other applications on your computer or your operating system itself can read these titles without special permissions. When enabled, this option simply replaces all window titles with "Tor Browser" — preventing other software from snooping on your browsing history. As always, for more comprehensive protection from third‑party applications on your device, we recommend using Tails. For now, this option is strictly opt‑in, as we did not have sufficient time during this release cycle to properly evaluate potential side‑effects for users. In particular, we worry that enabling this setting may reduce the browser's usability for those who rely on accessibility tools (e.g. screen‑readers) or those with highly customized systems (e.g. less‑popular desktop managers, application switchers, etc). If you are one of these users, we would ask that you try using this setting, and report back any bugs or usability issues you find! 📣 Generic window titles have also been upstreamed to Firefox as part of the Tor Uplift Project. Advanced Firefox users can enable this feature by opening about:config and setting privacy.exposeContentTitleInWindow (for normal windows) and privacy.exposeContentTitleInWindow.pbm (for private browsing windows) to false.

New user manual The Tor Browser manual, which can be found by visiting about:manual or through the application menu (☰) → Help → Tor Browser manual, has also received a complete revamp. Since the release of our new Support portal in 2025, the team has had to maintain two sets of documentation: one for the traditional manual that's available to read in Tor Browser, and another for the new Support site. With this release, we've solved that problem by replacing the older material in the Tor Browser manual with our latest and greatest help content from the new Support site. Like the previous iteration of the manual, the new version is bundled with Tor Browser for Desktop so it can be read offline, which comes in particularly handy when troubleshooting issues that prevent you from connecting to the Tor network.

Linux on ARM Finally, after a year of testing, Tor Browser 16.0 now features native support for Linux computers with 64‑bit ARM (AArch64) processors, such as Raspberry Pis and Apple Silicon Macs running Linux. If you have been relying on Tor Browser Alpha for support for these devices, we recommend switching over to the stable release channel unless you plan to continue testing Alpha releases. Meanwhile, Tor Browser 16.0 follows Firefox in ending support for 32‑bit x86 Linux computers. Fortunately, very few people should be affected, as we currently receive around 200 update checks from this platform a day, down from a peak of around 4,000 in 2019. Most remaining 32‑bit users should be able to switch to the 64‑bit version unless they're running outdated hardware or versions of Linux.

What's new for Android? Tor Browser for Android has also benefited from Mozilla's ongoing work to modernize Firefox, as seen in the Settings redesign on desktop. Over the past year, Firefox has been gradually transitioning to Jetpack Compose — Google's newest framework for building native Android interfaces. In this release, we've made significant progress applying the same changes to Tor Browser. As a result, large swaths of Tor Browser's user interface has been updated to Material Design 3 — the latest iteration of Google's design language for Android — with more yet to come in future releases. Google Play limits the size of apps distributed as APKs to 100 MB. Since Firefox for Android continues to grow with each release, keeping Tor Browser within this limit has been an ongoing challenge — for example, this issue has prevented us from bundling Tor Browser's manual on Android so that it can be accessed offline. Nevertheless, we've found various ways to reduce the size of our Android package over the years and stay within the limit. Most recently, this involved carefully and creatively compressing some of the built‑in resources Firefox uses to display its interface.

What's in the works? Tor Browser users can expect additional improvements over the next few months as we continue to refine the new Settings experience for desktop and Material Design 3 for Android. If you find a bug or have a suggestion for how we could improve this release, we'd love to hear your feedback. The team is also working hard on a new and improved circuit display, coming soon to Tor Browser Alpha, which integrates site information directly into the circuit panel and can visualize more complex multi‑path circuits. Multi‑path circuits use additional relays to split your traffic into two paths that converge on a single exit, improving both connection speed and reliability. These circuits already exist for regular websites (but not onion sites) and are randomly assigned based on network availability. Although Tor Browser's traditional circuit display can only show a single path at a time, you have likely benefited from a multi‑path circuit without even knowing it. What's more, this exciting update will mark the debut of the circuit display on Tor Browser for Android, which has been exclusive to desktop until now.

Contributions <3 - NoisyCoil - Soni

Full changelog

All Platforms - Updated NoScript to 13.6.37.1984 - Updated tor to 0.4.9.15 - Bug tor-browser#43857: Review in-source TODOs - Bug tor-browser#43858: Clean out deprecated or unused methods in TorConnect - Bug tor-browser#44118: Decide how to deal with upstream feature gates in a RR world - Bug tor-browser#44251: Drop pt_config.json meek-azure migration logic - Bug tor-browser#44257: Disable locale-based font rules as a defense-in-depth - Bug tor-browser#44280: Test stream isolation - Bug tor-browser#44420: Drop "rights" from components.conf - Bug tor-browser#44492: Fix python linting warnings in our test files - Bug tor-browser#44562: Set the new online Suggest prefs to false - Bug tor-browser#44571: Disable restrict_to_adults for potential fingerprintability - Bug tor-browser#44580: Registers NoScript to check for updates on first run - Bug tor-browser#44619: Add custom logs to Tor logs - Bug tor-browser#44621: Move about:torconnect back to browser - Bug tor-browser#44647: Clean up patch for SearchEngineSelector.sys.mjs. - Bug tor-browser#44663: NoScript behavior on “Safer” security level prevents integrity checks for dynamically loaded javascript - Bug tor-browser#44687: Expect javascript.options.asmjs to be false for all security levels - Bug tor-browser#44701: Unexpected change to netwerk/url-classifier/components.conf - Bug tor-browser#44720: Migrate New Identity commit to Tor Browser - Bug tor-browser#44753: Drop TorProvider.isBootstrapDone - Bug tor-browser#44755: Trusted Types (Firefox 148 and above) + Web Workers broken on Safer Level - Bug tor-browser#44763: Disable WebGPU until audited - Bug tor-browser#44764: Hide some AI settings using browser.ai.control.default - Bug tor-browser#44767: Safer Level's worker patching throws on new about:blank frames with Trusted Types - Bug tor-browser#44778: Safer Level: xray causes patched TrustedTypePolicy instances to be unusable by content. - Bug tor-browser#44795: Revert BB 27604 patch as not needed anymore - Bug tor-browser#44796: Adjust TorProviderBuilder to report the provider state to consumers - Bug tor-browser#44801: Redact onion origins from Location.ancestorOrigins. - Bug tor-browser#44811: Remove the lock on pdfjs.disable. - Bug tor-browser#44814: Disable trustpanel until our new designs are ready - Bug tor-browser#44815: Disable harmful addon URL blocking - Bug tor-browser#44828: Remove browser module references from toolkit/modules/ActorManagerParent.sys.mjs