Tor Project blog

A new way to fund internet freedom

2026-05-19T00:00:00Z

A coalition of privacy, internet freedom, cryptocurrency and open-source ecosystems, led by the Tor Project and Funding the Commons, today announced a new participatory funding campaign designed to support critical digital infrastructure at a moment of systemic funding instability.

Launching today at internetfreedom.torproject.org and as an Onion Service, the campaign is the first-ever Web3-native crowdfunding initiative dedicated to the internet freedom ecosystem. The campaign accepts contributions in Bitcoin (BTC), Ethereum (ETH), Zcash (ZEC), Monero (XMR), and Golem (GLM), and benefits 10 nonprofit projects working across privacy, censorship circumvention, secure communications, and public-interest digital infrastructure. An initial $115,000 USD matching pool supported by Cake Wallet, Zcash Community Grants, Logos, and Octant -- with additional ecosystem participation expected throughout the campaign -- will amplify donations made through June 18th, 2026, using a participatory matching model designed to reward broad community participation.

Internet freedom in peril

Internet freedom has declined for 15 consecutive years. As censorship and surveillance become increasingly sophisticated and pervasive, many of the tools people rely on to communicate and organize safely, access information freely, and protect their privacy are facing financial pressure and funding cuts. Some organizations were forced to reduce staffing, scale back technical infrastructure, delay development work, and stop support for the communities that depend on them. This strain threatens the long-term sustainability of critical public-interest infrastructure.

Today, the Tor Project and Funding the Commons, are launching a new experiment: a community-driven crowdfunding campaign exploring how internet freedom services and infrastructure can be funded more sustainably, transparently, and collectively. The campaign benefits organizations and tools supporting secure journalism, private communications, anti-censorship technologies, and privacy-preserving infrastructure used by millions of people worldwide.

SecureDrop: Secure whistleblower submission system used by journalists and newsrooms
OpenArchive: Privacy-first archiving tools for human rights defenders and journalists
OnionShare: Open-source tool for secure, anonymous file sharing and hosting
Ricochet Refresh: Metadata-resistant instant messaging over Tor
Onion Browser: Tor-powered web browser for iOS
Open Observatory of Network Interference (OONI): Global observatory documenting internet censorship and shutdowns
Paskoocheh, by ASL19: Anti-censorship technology and digital security support
Unredacted: Infrastructure supporting censorship circumvention and resilient communications
Digital Security Help Desk, by Miaan Group: Internet freedom technologies supporting users in Iran
Osservatorio Nessuno: Protecting activists, journalists, and civil society organizations with tech support and traceless software

Tor cannot be resilient alone. Its resilience depends on the resilience of the ecosystem around it, especially smaller projects that may not have the same access to institutional funding or donor networks. This campaign is one way to bring more people into the shared responsibility of sustaining public-interest technology.

A participatory funding model

The campaign uses a participatory matching fund model called quadratic funding designed to amplify the impact of many small contributions. Rather than prioritizing only large donations, the model increases support for projects backed by broader community participation, giving more people a meaningful voice in how funds are distributed. In practice, a project supported by many smaller contributors may receive more matching funds than one supported by only a few large donors.

The campaign's matching pool is supported by a coalition of organizations aligned around privacy, open infrastructure, and public goods funding, including: Cake Wallet, Zcash Community Grants, Logos, and Octant. Contributions can be made using ETH, BTC, ZEC, XMR, and GLM.

"Privacy and internet freedom drive everything we build at Cake Wallet. We are proud to support Tor and the broader internet freedom ecosystem through this campaign, helping keep essential privacy tools accessible to everyone. Beyond supporting the mission, we are also users, advocates, and builders who have helped bring Tor's protections to over two million users worldwide." - Vik Sharma, CEO, Cake Wallet

"Tor and Zcash protect complementary layers of privacy: Tor protects network privacy, while Zcash protects financial privacy. By supporting this campaign, Zcash Community Grants (ZCG) is helping sustain critical public-interest infrastructure for people who rely on privacy and internet freedom." - ZCG's members

Internet freedom tools are digital public infrastructure, and they face many of the same funding challenges as other public goods: they are widely relied on, difficult to monetize ethically, and often invisible until they are under threat. Funding the Commons has spent years working with builders, funders, researchers, and public institutions to test new ways of sustaining public goods.

Partnering with Funding the Commons gives us a way to bring internet freedom organizations into a broader conversation about how public-interest infrastructure is funded, and to test a model that can be reused, improved, and expanded over time:

"Quadratic funding is one of web3's answers to how critical infrastructure gets funded: Institutional money follows community signals, not the other way around," said David Casey, Director of Funding the Commons. "Any donation moves the match pool, no matter the size, putting weight behind the projects Tor users rely on every day."

The campaign launches today at: internetfreedom.torproject.org and http://swvbwbtmajvfrnz4wztx6ovshilm23ntigi73fz5wczj3aqdquq5icad.onion, and accepts donations through June 18th, 2026.

New Release: Tor Browser 15.0.14

2026-05-19T00:00:00Z

Tor Browser 15.0.14 is now available from the Tor Browser download page and also from our distribution directory.

This version includes important security updates to Firefox.

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 15.0.13 is:

All Platforms
- Bug tor-browser#44958: Backport Security Fixes from Firefox 151
Windows + macOS + Linux
- Updated Firefox to 140.11.0esr
Android
- Updated GeckoView to 140.11.0esr
Build System
- All Platforms
  - Bug tor-browser-build#41781: Fix clean section in rbm.local.conf.example
  - Bug tor-browser-build#41798: Update the URL to versions.ini in relprep.py
- Windows + Linux + Android
  - Updated Go to 1.25.10

Preserving evidence: How OpenArchive fosters accountability and media sovereignty

2026-05-18T00:00:00Z

This post is part of a spotlight series on the organizations defending the free Internet.

A picture may be worth a thousand words, but only if it survives. Behind every image or video is someone making a choice in real time: to document what they are seeing, preserve what others may try to deny, and take on the risks and responsibilities that come with creating archival records.

Now that technology outpaces regulation and social media is the dominant platform for news, communities sharing documentation of world events face exploitation and repression through targeting, surveillance, and media erasure or manipulation. Mobile media can disappear as quickly as it was captured because, for example, a phone gets confiscated, a platform removes it, or a company changes its content moderation policies. This media can become impossible to verify if or when metadata is stripped, potentially leading to unchecked mis- and disinformation due to media manipulation. Additionally, it can become dangerous when the wrong person can see who captured it or where it was stored.

Eyewitnesses and the media they document and preserve, often depicting potential human rights violations, are increasingly at risk of being targets of surveillance, censorship, media manipulation, doxxing, and worse. In response to these growing threats, OpenArchive first created the FLOSS Save app in 2015. Following their mission to offer people access to ethical, secure, decentralized backends, they then created their novel, custom DWeb Storage to further help communities safely preserve their documentation without having to depend on -- at best, unreliable, and, at worst, weaponized -- centralized platforms that can remove, lose, or expose sensitive data at a moment's notice.

Their vision is a future where our histories are easily preserved, securely owned, and freely accessible. OpenArchive builds towards that future through human rights-centered co-research, education/training, and tool development dedicated to the ethical collection and long-term preservation of mobile media. To achieve this, we equally prioritize privacy, usability, archival integrity, and decentralized technology to equip human rights defenders, at-risk communities, journalists, and movements worldwide with tools to preserve, verify, and act on evidence of abuses, challenging extractive technology and amplifying marginalized voices. The premise is straightforward: people should be able to easily preserve their histories safely and on their own terms.

Built for conditions documenters actually face

For over a decade, OpenArchive has maintained Save, their free, open source flagship mobile app that helps people securely archive, verify, and encrypt their mobile media while working under real-world constraints. Co-created with and for its users, it supports authentication via SHA256 hashes and ProofMode, encrypted transit via TLS and Tor, long-term preservation to destinations like the Internet Archive, Nextcloud, their novel DWeb P2P Storage backend (in beta), and redundancy through multi-server backup.

In practice, this work responds to urgent risks. For example, in conditions of conflict, they expedite local deployments of Save and run trainings for local archivist communities. Documenters on the ground had named phone confiscation, arrest, and internet outages as their primary risks, exactly the conditions Save is designed for.

Additionally, in one case, human rights defenders facing corporate environmental abuse had a different challenge: none of the documenters they had surveyed were using encrypted tools in their workflows, leaving them vulnerable to tracking and surveillance. In other contexts, human rights defenders also named privacy and inconsistent internet access as major barriers, underscoring how easily documentation can become vulnerable before it ever reaches an archive.

OpenArchive's work grounds those realities. Guided by the human rights-centered design methodology (co-created by OpenArchive's Executive Director, Natalie Cadranel and leading human rights experts), the team works with documenters, archivists, journalists, and advocates to understand their threats, constraints, workflows, and safety needs before designing tools around them.

Most social media platforms are optimized for attention and monetization, not for archival preservation, provenance, or community control. A centralized platform presents a single point of failure, an easy access point for censorship, targeting, link rot, or account / company shutdowns.

From camera roll to decentralized archives

Responding to this specific need, OpenArchive has built a novel p2p DWeb Storage backend for Save, now in beta. In addition to Nextcloud and the Internet Archive, it gives communities an alternative to centralized platforms, one designed around privacy, verifiability, and resilience rather than someone else's business model.

Under the hood, it uses two open source protocols: Veilid for encrypted peer-to-peer networking and anonymous connections, and Iroh for data storage, retrieval, replication, and verification. Save users can create groups, share files into repositories, and replicate media across peers, with encrypted communication and data integrity preserved throughout.

"Decentralized storage" can sound abstract. But it actually means no single company, server, or account holds the records. Copies are distributed. Access is shared among trusted peers. If one node goes down (or gets shut down), the archive survives on the others.

OpenArchive's role in the internet freedom ecosystem is protecting the chain of trust around media: who captured it, how it was handled, whether it remained intact, and whether the people behind it were put at additional risk. That chain is what makes documentation usable for journalism, legal evidence, historical memory, and accountability.

Much of this work is quiet by necessity. The communities most in need of secure archiving are often the least able to publicize their use of it.

By offering diverse and decentralized backends, Save is built for exactly that reality. When the platform shuts down the account, when the server goes offline, or when the border is closed, the record doesn't have to disappear with it.

Keeping the doors open

2026-05-15T00:00:00Z

This guest post is part of a spotlight series on the organizations defending the free internet.

A user in China once said this about our work:

"You have helped many many people to overcome the great firewall. Without your help, I would be in the totally darkness trap and being brain-washed."

We don't hear from the people who use our services very often. Most of them can't or don't feel that they can safely send a message. When one comes through, it's a reminder of what's actually at stake.

We're Unredacted, a US-based 501(c)(3) non-profit. We build and operate Internet infrastructure that helps people reach the open Internet and protect their right to privacy. We do this by operating a network of over 300 servers around the world. We're a way through when the front door is locked, and a place to communicate when the public square isn't safe. Most of the work is invisible: datacenter work, hardware, automation, open source software, bandwidth, abuse queues, monitoring alerts, and the late nights spent keeping all of it online.

What we do falls into three areas. Censorship Evasion is where Unredacted Door lives, our umbrella for the services designed to route around blocking. Secure Infrastructure is where we run things like XMPP.is and our Matrix homeserver, and other free services built with security and privacy in mind. Unredacted Education is the writing and documentation side: guides and explainers for the people who want to understand the work and replicate it. Alongside those, Unredacted Labs is where we experiment with infrastructure ideas that aren't quite production-ready. GreenWare is one of those, our effort to run real network capacity on hardware that doesn't burn a lot of power.

Unredacted Door

The name is literal. When the entrance to the open Internet gets walled off, people need another way in.

Unredacted Door brings together several of our circumvention services: FreeSocks, messaging proxies for Signal and Telegram, Tor bridges, and Snowflake proxies. In a recent 30-day window, these services carried nearly 300 TiB of traffic for tens of thousands of people routing around censorship in their countries. That's roughly the equivalent of bandwidth to stream tens of thousands of hours of 4K video. Demand isn't slowing, and we need to continue building more. Every new filter, every new law, every "for your safety" rollout sends more people looking for a route the censors haven't found yet.

The largest piece of Unredacted Door is FreeSocks: free proxies for people in places where censorship is severe. If you've never run into one, a proxy is a relay point. Your app doesn't talk directly to the blocked service. It talks to a server that carries the connection past whatever filters are sitting between you and the wider Internet. FreeSocks is built to make that relay quietly unremarkable, which is exactly the trait a standard VPN tends to lack. A VPN advertises itself. There's a known endpoint, a known handshake, an obvious shape on the wire. Censors are very good at blocking things they can recognize.

No single tool covers every situation. Tor Browser gives you strong privacy and anonymity for browsing. Snowflake helps people reach Tor when access to the network itself is blocked. FreeSocks proxies push specific traffic through a route that's harder to spot. People living under censorship usually need a few of these on hand, because no single door stays open forever.

That's why we're putting serious work into the next version of FreeSocks (v2). It uses Xray - a powerful and versatile traffic-routing engine, which can make proxy traffic look more like ordinary web traffic bundled with our open source control plane that allows us to rotate endpoints automatically when censors find and block a server. The less a user has to fiddle with their setup while they're already under pressure, the better.

GreenWare: sustainable infrastructure, literally

Tor relays, bridges, proxies, and more. They run on hardware in datacenters, and that hardware has a real footprint: financial, operational, and environmental. If we want privacy infrastructure to last, we have to ask what's actually sustainable to operate.

GreenWare is our attempt to shrink that footprint without shrinking what we can carry on it. The premise is straightforward: most Tor relay traffic doesn't need a server that draws power like a space heater. A relay needs a steady network, predictable CPU, and enough memory to hold its state. That's a workload a single-board computer can handle, if the chassis around it is built to take it seriously.

We started with Raspberry Pi 5 boards powered over PoE, fed entirely through their network cables. The idea worked. A typical server in a datacenter draws as much power as a small space heater. A Pi draws less than a lightbulb. But the first generation had ceilings. Density wasn't where we wanted it, and a few of the supporting components weren't built for the hours we were putting on them.

So we run two deployments in parallel now. The first is a 1U chassis with 20 ComputeBlade modules stacked into it. We deployed all 20 in our datacenter and moved a chunk of our Tor exit relays onto them. That chassis pulls a little over 100W under load, roughly what an old incandescent bulb burns. The second is a custom Raspberry Pi chassis we designed after the ComputeBlade work taught us what we actually wanted in the field. Both are live, and as of writing all 123 of our Tor exit relays run on this combined infrastructure, drawing roughly 400W in total. As time goes on, we'll have more to say about the chassis design and the project as it matures.

The Tor network runs on people and organizations willing to operate infrastructure for it. Exits are the hardest part of that job. They need bandwidth, maintenance, abuse handling, legal nerve, and money. If we can drop the cost and the power required to run real exit capacity, more people can take on a piece of the work and diversify and grow the network.

Our longer-term ambition is to keep pushing on efficient hardware, carbon tracking, and eventually renewable-powered micro points of presence. We'd be more than glad to partner with organizations and companies that want to see this grow.

The open Internet is kept open by many people and organizations investing energy, time, and effort: The researchers measuring censorship, the relay operators providing bandwidth, and the communities that refuse to leave one another behind. At Unredacted, our part is building and maintaining the routes people may need when the obvious ones disappear.

Defending the public's right to know

2026-05-12T00:00:00Z

This post is part of a spotlight series on the organizations defending the free internet.

Internet freedom has declined for 15 consecutive years. Beyond surveillance, the erosion of privacy and anonymity, and information manipulation, governments are targeting specific sites and services, or attacking infrastructure itself, causing shutdowns and deliberate disruptions for internet users. But how do we know when the internet is censored and how?

OONI, the Open Observatory for Network Interference, born out of the Tor Project, exists to answer that question. Through free software tools and open data OONI makes censorship measurable, verifiable, and actionable. This post is about what that looks like in practice.

Protecting the public record

OONI data is the world's largest open dataset on internet censorship: billions of measurements collected across tens of thousands of networks from 245 countries and territories since 2012. OONI's data exists because people around the world run OONI Probe and contribute measurements from the networks that they are connected to. Every new measurement adds to a shared public record.

Both its scale and methodology contribute to OONI's impact. Internet censorship often works by making interference hard to see. It can make a blocked website look broken, a throttled app look unreliable, or a shutdown look like a technical failure. OONI helps expose these tactics through open measurement methodologies, peer review, expert feedback, and comparison against control measurements, so that censorship claims can be tested, challenged, and verified.

To make this dataset user-friendly, OONI launched thematic pages in OONI Explorer focusing on the areas most frequently targeted: social media and messaging apps, news media, and circumvention tools. Each page includes short reports, longer research reports, and charts with the latest OONI data.

In 2025, a dedicated "Blocking of News Media" page helped surface findings that would otherwise require sifting through billions or raw measurements: the blocking of the independent media outlet Zawia3 in Egypt, the blocking of 12 news media websites in Jordan, and the blocking of The Wire in India during the military conflict with Pakistan.

Think about when censorship events tend to happen: elections, protests, armed conflict, national exams, and periods of political unrest. The moment when access to information matters most. OONI gives affected communities a shared factual basis at those moments to make accountability possible.

How journalists and media organizations use OONI

In 2025, Meduza, one of the most prominent Russian media outlets in exile published an article introducing OONI tools and encouraging readers to use them. It's just one example how a newsroom can effectively use censorship measurement not just to report a story, but as an act of public education: helping audiences understand how network interference works, how it can be documented, and how they can contribute to that evidence base themselves.

When a news website is blocked, that's not just a technical event. It's the public losing access to reporting, communities losing access to timely information, and journalists losing access to their audiences. Documentation that can be cited and analyzed is what turns that event into something actionable.

The most concrete example of that chain in action is Kenya. OONI data served as evidence in a public-interest case challenging the unlawful disruption of internet access. The case was filed by a coalition that included BAKE, ICJ Kenya, Paradigm Initiative, the Kenya Union of Journalists, Katiba Institute, the Law Society of Kenya, and CIPESA. To support the petition before the High Court of Kenya, OONI produced a detailed research report, in the form of an expert opinion, documenting the blocking of Telegram during Kenya's 2023 and 2024 KCSE national exams.

This is a case where a journalists' union, digital rights organizations, legal advocates, and technical researchers were able to work from the same datasets to elevate internet disruption to a public-interest issue. And this case also helped set an important regional precedent: lawyers in Tanzania subsequently reached out to OONI for data to support legal efforts challenging the blocking of Twitter/X there, prompting OONI to publish a research report documenting the block.

Collective action for a collective internet

The Kenya-to-Tanzania ripple effect illustrates how internet censorship works across geographies. But also how we can fight it. A block on messaging apps isn't a standalone event. Journalists may lose access to sources. Activists may lose organizing channels. Circumvention tool developers may need to adapt. Researchers may need to verify what happened. Lawyers may need evidence. But everyone needs documentation.

OONI's open data model is built for exactly these moments. Protecting the free internet requires documenting censorship, sharing evidence, and building the collective capacity to respond.

New Release: Tails 7.7.3

2026-05-12T00:00:00Z

This release is an emergency release to fix a critical security vulnerability in the Linux kernel, as well as security vulnerabilities in Tor Browser and in the Tor client.

Changes and updates

Update the Linux kernel to 6.12.86, which fixes Dirty Frag, a vulnerability that could allow an application in Tails to gain administration privileges.

For example, if an attacker was able to exploit other unknown security vulnerabilities in an application included in Tails, they might then use Copy Fail to take full control of your Tails and deanonymize you.

We are not aware of this vulnerability being used in practice until now.
Update Tor Browser to 15.0.12.
Update the Tor client to 0.4.9.8.
Update Thunderbird to 140.10.1.

Fixed problems

For more details, read our changelog.

Get Tails 7.7.3

To upgrade your Tails USB stick and keep your Persistent Storage

Automatic upgrades are available from Tails 7.0 or later to 7.7.3.
If you cannot do an automatic upgrade or if Tails fails to start after an automatic upgrade, please try to do a manual upgrade.

To install Tails 7.7.3 on a new USB stick

Follow our installation instructions.

The Persistent Storage on the USB stick will be lost if you install instead of upgrading.

To download only

If you don't need installation or upgrade instructions, you can download Tails 7.7.3 directly:

Support and feedback

For support and feedback, visit the Support section on the Tails website.

New Release: Tor Browser 15.0.13

2026-05-08T00:00:00Z

Tor Browser 15.0.13 is now available from the Tor Browser download page and also from our distribution directory.

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 15.0.12 is:

All Platforms
- Updated tor to 0.4.9.8
- Updated NoScript to 13.6.19.1984

New Alpha Release: Tor Browser 16.0a6

2026-05-07T00:00:00Z

Tor Browser 16.0a6 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.0a5 is:

All Platforms
- Updated tor to 0.4.9.7
- Updated NoScript to 13.6.18.90101984
- Updated OpenSSL to 3.5.6
- Bug tor-browser#43857: Review in-source TODOs
- Bug tor-browser#44402: Re-enable ESLint rule mozilla/no-browser-refs-in-toolkit as an error
- Bug tor-browser#44749: Check search engines parameter replacements
- Bug tor-browser#44792: Rebase alpha onto 150.0a1
- Bug tor-browser#44796: Adjust TorProviderBuilder to report the provider state to consumers
- Bug tor-browser#44828: Remove browser module references from toolkit/modules/ActorManagerParent.sys.mjs
- Bug tor-browser#44841: TorDomainIsolator proxy filter returns null on exception instead of preserving SOCKS proxy
- Bug tor-browser#44865: Block chrome:///locale/ to content
- Bug tor-browser#44868: Backport 138c33ea964b2e0a4875aadc39d8a948e0c2aace to 150 to fix Windows builds
- Bug tor-browser#44870: Remove legacy branch from gitlab templates
- Bug tor-browser#44895: Undo the patch for #44772
- Bug tor-browser-build#41775: Update list of Snowflake STUN servers in default bridge line, 2026 edition
- Bug tor-browser-build#41778: Remove base-browser from protected-branches.py
- Bug tor-browser-build#41780: Create sha256sums-unsigned-build.txt in artifacts/$platform directories
Windows + macOS + Linux
- Updated Firefox to 150.0a1
- Bug tor-browser#43824: Switch resource:// modules to use moz-src:
- Bug tor-browser#44288: New identity fails to block loading a custom home page
- Bug tor-browser#44458: Fix the "Connect" and ".onion available" button height
- Bug tor-browser#44560: Customize the flags for alternate 'Application Data' directories
- Bug tor-browser#44630: Use settings config to hide settings, rather than data-hidden-from-search or commenting out
- Bug tor-browser#44648: Unexpected changes to SearchService.sys.mjs
- Bug tor-browser#44685: Use border radius for letterboxing
- Bug tor-browser#44798: Don't load about:torconnect into iframes
- Bug tor-browser#44829: Hide the settings privacy card
- Bug tor-browser#44832: Hide the Firefox mascot in about:neterror
- Bug tor-browser#44846: about:torconnect redirect doesn't work with the new neterror page
- Bug tor-browser#44847: Drop letterboxing sidebar rounded corner logic
- Bug tor-browser#44902: Error in privacy preference initialisation due to missing dataCollectionViewProfilesMultiProfileBackupWarning
- Bug tor-browser-build#31860: Start using LTO for firefox project
Windows
- Bug tor-browser#44862: Fontvis is missing Segoe MDL2 Assets
- Bug tor-browser#44868: Backport 138c33ea964b2e0a4875aadc39d8a948e0c2aace to 150 to fix Windows builds
macOS
- Bug tor-browser#44850: Wrong path for bootstrapped tor daemon on macOS
- Bug tor-browser-build#41476: Since 13.5-legacy is not longer supported, remove tools/signing/wrappers/sign-rcodesign
Linux
- Bug tor-browser#44361: Notify Linux i686 users that they won't receive updates anymore
- Bug tor-browser#44521: Disable widget.wayland.fractional-scale.enabled
Android
- Updated GeckoView to 150.0a1
- Bug tor-browser#44615: Remove ability to "Rate/Review in Google Play" in app
- Bug tor-browser#44827: Always enable noscript for android
- Bug tor-browser#44842: Replace instances of SwitchPreference with SwitchPreferenceCompat
- Bug tor-browser#44848: Do not overwrite Android toolchains on default mozconfigs
- Bug tor-browser#44880: Fix edgeToEdge display issue presented in 150 android rebase
- Bug tor-browser#44925: Fix bootstrap screen color styling for light mode presented in one of the rebases between 140 and 150
- Bug tor-browser#44935: Remove incorrectly shown "open in app" notification dot on settings button
Build System
- All Platforms
  - Bug tor-browser-build#41591: Remove support for old mar filenames when 13.5 legacy branch is EOL
  - Bug tor-browser-build#41764: Update toolchains for Firefox 150
  - Bug tor-browser-build#41767: Add jwilde to allowed signer for browser projects
  - Bug tor-browser-build#41778: Remove base-browser from protected-branches.py
  - Bug tor-browser-build#41780: Create sha256sums-unsigned-build.txt in artifacts/$platform directories
  - Bug tor-browser-build#41786: Add comment to rbm.local.conf.example warning about potential recursive loops in tmp_dir definition
  - Bug rbm#40106: Improve error message in case of recursive definition
- Windows + macOS + Linux
  - Bug tor-browser-build#41759: Remove references to legacy release in tor-browser-build
- Windows + Linux + Android
  - Bug tor-browser-build#41770: Update Go to 1.26.x
  - Updated Go to 1.26.2
- Windows
  - Bug tor-browser#44853: Update target in mozconfig-windows-x86_64 and mozconfig-windows-i686
- macOS
  - Bug tor-browser-build#41773: Change the position of -mindepth when creating the dmg
- Linux
  - Bug tor-browser#44555: Remove mozconfig-linux-i686
- Android
  - Bug tor-browser#44848: Do not overwrite Android toolchains on default mozconfigs

Arti 2.3.0 released: Logging, Relay, Directory authority, and RPC development.

2026-05-07T00:00:00Z

Arti is our ongoing project to create a next-generation Tor implementation in Rust. We're happy to announce the latest release, Arti 2.3.0.

This release bumps the minimum MacOS version supported by Arti to 10.14, up from 10.12. Despite being supported on a technical level, we do not recommend the use of MacOS versions that old, as they are no longer receiving updates from Apple and may have unpatched security issues.

This release continues our ongoing development towards using Arti as a relay and as a directory authority. It also continues development on RPC, including adding a new RPC API for inspecting tunnel paths.

Additionally, there are a couple new logging related features. Arti now supports logging to syslog when the syslog feature is enabled and the logging.syslog config option is enabled. We've also added a new logging.protocol_warnings option to log protocol violations as warnings.

Developers who use the arti-client crate should note that in the release after this one, we plan to change TorClient to be wrapped in an Arc explicitly, rather than implicitly having Arc-like semantics. Be prepared for this breaking change, and if you have any thoughts about it, please speak up in #2469.

As usual, there is also a signigicant amount of cleanup, improvements to testing, infrastructure, and documentation, and many small bugfixes.

For full details on what we've done, including API changes, and for information about many more minor and less-visible changes, please see the CHANGELOG.

For more information on using Arti, see our top-level README, and the documentation for the arti binary.

Thanks to everybody who's contributed to this release, including Andrew Kloet, hjrgrn, and moumenalaoui.

Also, our deep thanks to our sponsors for funding the development of Arti!

New Release: Tor Browser 15.0.12

2026-05-07T00:00:00Z

Tor Browser 15.0.12 is now available from the Tor Browser download page and also from our distribution directory.

This version includes important security updates to Firefox.

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 15.0.11 is:

All Platforms
- Updated tor to 0.4.9.7
- Bug tor-browser#44940: Rebase Tor Browser stable onto 140.10.2esr
Windows + macOS + Linux
- Updated Firefox to 140.10.2esr
- Bug tor-browser#44746: Funding the Commons Implementation (Desktop)
Android
- Updated GeckoView to 140.10.2esr
- Bug tor-browser#44747: Funding the Commons Implementation (Android)
Build System
- All Platforms
  - Bug tor-browser-build#41781: Fix clean section in rbm.local.conf.example