Tor Browser 16.0a8 is now available from the Tor Browser download page and also from our distribution directory.
This version includes important security updates to Firefox.
⚠️ Reminder: The Tor Browser Alpha release-channel is for testing only. As such, Tor Browser Alpha is not intended for general use because it is more likely to include bugs affecting usability, security, and privacy.
Moreover, Tor Browser Alphas are now based on Firefox's betas. Please read more about this important change in the Future of Tor Browser Alpha blog post.
If you are an at-risk user, require strong anonymity, or just want a reliably-working browser, please stick with the stable release channel.
Send us your feedback
If you find a bug or have a suggestion for how we could improve this release, please let us know.
Full changelog
The full changelog since Tor Browser 16.0a7 is:
- All Platforms
- Updated NoScript to 13.6.25.90301984
- Updated Tor to 0.4.9.11
- Updated OpenSSL to 3.5.7
- Bug tor-browser#44857: Drop
browser.display.use_system_colors
from our preference list - Bug tor-browser#44896: Review Mozilla 2030929: Remove unused pref privacy.partition.network_state
- Bug tor-browser#45018: resistfingerprinting not available in appearance.mjs in 152
- Bug tor-browser#45019: ReportBrokenSite startup error in 152
- Bug tor-browser#45047: Cross-site oracle via worklet rejection error in Safer Mode
- Bug tor-browser#45072: Disable XSLT already for 16.0
- Windows + macOS + Linux
- Updated Firefox to 152.0a1
- Bug tor-browser#44528: Make sure desktop IP Protection is disabled on desktop
- Bug tor-browser#44795: Revert BB 27604 patch as not needed anymore
- Bug tor-browser#44844: Use new urlbar CSS variables
- Bug tor-browser#44888: Use
--button-opacity-disabled
for disabled styling. - Bug tor-browser#44955: Use
context-fill
forabout-wordmark.svg
- Bug tor-browser#44956: Switch colours in letterboxing setting icons to match the tab-alignment icons
- Bug tor-browser#45016: Several errors about EngineProcess.sys.mjs in 152
- Bug tor-browser#45017: Wrong letterboxing background in 152
- Bug tor-browser#45037: Potential runtime errors in the search service when changing JS status
- Bug tor-browser#45043: Re-add missing changes to settings after 151/152 rebase
- Bug tor-browser#45083: Error in about:preferences due to ipprotection missing
- macOS
- Bug tor-browser#44728: Bundled fonts are broken on macOS when the GPU process is enabled
- Linux
- Bug @ libfontconfig.so.1#45048: Backport Bugzilla 2041887: Crash in after users upgraded to fontconfig 2.18.0 [tor-browser]
- Android
- Updated GeckoView to 152.0a1
- Bug tor-browser#43856: Fix onBackPressed() deprecation
- Bug tor-browser#44091: Add frequent regions to tor connection assist for android
- Bug tor-browser#44175: Remove all default browser functionality (Android)
- Bug tor-browser#44769: TBA crash screen has firefox asset as well as a "Send crash report" button
- Bug tor-browser#45052: Initialise Tor modules on android in the same order as desktop
- Build System
- All Platforms
- Bug tor-browser-build#41802: Remove the tor daemon requirement for signing
- Bug tor-browser-build#41809: Update toolchains for Firefox 152
- Bug tor-browser-build#41813: Disable build artifacts in
make generate_gradle_dependencies_list-geckoview
- Bug tor-browser-build#41821: Update gpg subkeys for boklm
- Bug tor-browser-build#41823: Add versions information to the toolchain list update
- Bug tor-browser-build#41827: Update morgan's keychain with renewed key
- Windows + Linux + Android
- Updated Go to 1.26.4
- Windows
- Bug tor-browser-build#41810: Define GetAddrInfoExCancel on mingw
- Android
- Bug tor-browser#45086: Compress omni.ja with xz on Android
- Bug tor-browser-build#41830: Update the browser project to change omni.ja.xz
- All Platforms
Comments
We encourage respectful, on-topic comments. Comments that violate our Code of Conduct will be deleted. Off-topic comments may be deleted at the discretion of the moderators. Please do not comment as a way to receive support or to report bugs on a post unrelated to a release. If you are looking for support, please see our FAQ, user support forum or ways to get in touch with us.