Tor Project blog

New Release: Tails 7.12

2026-09-03T00:00:00Z

Firefox is moving to a 2-week release cadence starting in September, and so Tor Browser and Tails are doing the same. Tails 7.12 is the first release on this new cadence.

Changes and updates

Update Electrum from 4.7.2 to 4.8.1.
Update Tor Browser to 15.0.21.
Update some firmware packages. This improves support for newer hardware, including graphics cards, Wi-Fi, and more.

Get Tails 7.12

To upgrade your Tails USB stick and keep your Persistent Storage

Automatic upgrades are available from Tails 7.0 or later to 7.12.
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.12 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.12 directly:

Support and feedback

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

New Alpha Release: Tor Browser 16.0a11

2026-09-02T00:00:00Z

Tor Browser 16.0a11 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.

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.0a10 is:

All Platforms
- Bug tor-browser#45254: Rebase Tor Browser alpha onto 153.2.0esr
- Bug tor-browser#45259: Backport Security Fixes from Firefox 155
Windows + macOS + Linux
- Updated Firefox to 153.2.0esr
- Bug tor-browser#45264: Use parent process for TorConnect redirections
Android
- Updated GeckoView to 153.2.0esr
- Bug tor-browser#44155: Always enable LNA on Android as a defense-in-depth
Build System
- All Platforms
  - Bug tor-browser-build#41860: Change GCC sources mirror to https://gcc.gnu.org
- Windows + Linux + Android
  - Updated Go to 1.26.8

New Release: Tor Browser 15.0.21

2026-09-01T00:00:00Z

Tor Browser 15.0.21 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.20 is:

All Platforms
- Updated NoScript to 13.6.32.1984
- Updated OpenSSL to 3.5.8
- Bug tor-browser#45223: Backport tor-browser#45220 - about:torconnect doesn't show when launching the browser in non-PBM
- Bug tor-browser#45253: Rebase Tor Browser stable onto 140.15.0esr
- Bug tor-browser#45259: Backport Security Fixes from Firefox 155
Windows + macOS + Linux
- Updated Firefox to 140.15.0esr
- Bug tor-browser#44996: Change the 32-bit linux message to the expired version for the final 15.0 release
- Bug tor-browser#45264: Use parent process for TorConnect redirections
Android
- Updated GeckoView to 140.15.0esr
Build System
- Windows + Linux + Android
  - Updated Go to 1.25.14

Arti 2.6.0 released

2026-09-01T00: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.6.0.

This release continues our ongoing development towards using Arti as a relay and as a directory authority, with much of the work focusing on document parsing, directory mirror support, and DNS stream handling. Additionally, on the RPC front, we are making steady progress towards RPC-based configuration management. Finally, congestion control and Counter Galois Onion cryptography are both now always enabled in arti.

As usual, there also are many under-the-hood improvements to our infrastructure, testing, and documentation, along with multiple bug fixes and internal cleanups.

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, Steven Masnada, iqdecay, pryty26, steven.

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

New Alpha Release: Tor Browser 16.0a10

2026-08-27T00:00:00Z

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

This version includes important security updates to Firefox.

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.

✨ New Features which need attention!

📖 Updated Built-in manual on Desktop Tor Browser

The Tor Project's old support page and content has been updated. Starting with Tor Browser 16.0a10, this updated design and content is now baked into the browser and replaces the legacy manual. You can access the manual directly by navigating to about:manual in the URL bar or by clicking on the various "Learn more" links found in the browser's UI.

⚙️ Settings Redesign now enabled by default

With Tor Browser 16.0a10, we have enabled the new about:preferences designs from Mozilla by default. Our additional settings (connectivity, letterboxing, security level, etc) should now all be migrated over and using the new design language. Please file an issue if you find any regressions!

🪟 Generic Window Titles

On most (all?) desktop operating systems, applications have the ability to programmatically set and update the title of their windows. Normally, this is very useful as it allows the names of your applications to appear in the desktop UI in the title bar or as entries in application switchers (e.g. when you alt-tab between applications).

Historically, web browsers have dynamically updated their application's window title to the contents of the current web page's <title> element. For example, the window name for the browser window you are currently using is very likely some variant of New Alpha Release: Tor Browser 16.0a10 | The Tor Project — Tor Browser. If you were to navigate away from this page (please don't), the title would be updated to some variant of that page's <title> element contents.

While this process provides convenient usability to end-users, these title changes are generally detectable and readable by 3rd party applications or the operating system itself. This is typically not a privileged action, meaning software does not typically require special permissions to do this. These same APIs which allow programs to enumerate open windows also allow them to record browsing history using window title changes as a side-channel.

To counteract this, we've developed (and upstreamed) an opt-in feature disabling these window title changes and instead replacing them with just the the name of the browser. You can try this feature out by going to about:preferences, clicking on Privacy and security in the navigation panel, clicking on Advanced settings within the Connection and software security group, and checking Use generic window titles in the Protections from third-party applications group. With this setting enabled, all Tor Browser window titles should now simply read Tor Browser Alpha.

For any vanilla Firefox users out there, you can enable this feature by going to about:config and setting the privacy.exposeContentTitleInWindow (for normal-browsing windows) and privacy.exposeContentTitleInWindow.pbm (for private-browsing windows) boolean options to false.

We had hoped to enable this feature by default in the 16.0 series, but it is a bit late in the release cycle to push out such a feature with potentially unseen side-effects (e.g. causing breakage with a11y software, specific desktop environments, or other custom configurations) without user testing. Please give this feature a go (especially if your desktop environment is non-standard) and report back any issues or incompatibilities you find.

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.0a9 is:

All Platforms
- Updated NoScript to 13.6.31.90301984
- Updated OpenSSL to 3.5.8
- Bug tor-browser#44257: Disable locale-based font rules as a defense-in-depth
- Bug tor-browser#45161: Drop TorProviderBuilder.firstWindowLoaded
- Bug tor-browser#45205: Rebase Tor Browser onto 153.1.0esr
- Bug tor-browser#45219: Backport Security Fixes from Firefox 154
Windows + macOS + Linux
- Updated Firefox to 153.1.0esr
- Bug tor-browser#43570: Report errors in about:torconnect when tor daemon crashes (Desktop)
- Bug tor-browser#43640: Poor screen reader experience when opening preferences and scrolling to element
- Bug tor-browser#43939: Update Bridge settings when connection failed
- Bug tor-browser#44247: Adapt Tor Browser manual to use the new support pages
- Bug tor-browser#44511: Make sure new search suggest features are disabled for 16.0
- Bug tor-browser#44629: Add a search suggestion warning in the settings
- Bug tor-browser#44699: Amend commit message for "BB 43322: Customize the font visibility lists"
- Bug tor-browser#44802: Hide the "safe browsing" settings
- Bug tor-browser#44830: Migrate our home page adjustments to the settings config
- Bug tor-browser#44831: Misleading banner in "Search engine suggestions" settings
- Bug tor-browser#44855: Use ariaNotify for bridge updates
- Bug tor-browser#44959: Integrate the new Tor Browser manual into Tor Browser
- Bug tor-browser#44998: Remove Firefox branding from about:preferences
- Bug tor-browser#45039: Make it easier to test ProfileDataUpgrader customization
- Bug tor-browser#45051: Show a separate Tor error prompt for users who do not see about:torconnect (desktop)
- Bug tor-browser#45058: Convert bridge settings to new design and config approach
- Bug tor-browser#45059: Convert advanced connection settings to new design and config approach
- Bug tor-browser#45079: Move letterboxing to the appearance setting pane
- Bug tor-browser#45123: Disable profile backup for 16.0
- Bug tor-browser#45125: Tidy up bridge emoji widget
- Bug tor-browser#45143: Modify moz-fieldset to allow focusing the heading
- Bug tor-browser#45156: Remove "Firefox Home" from the appearance settings
- Bug tor-browser#45157: Grant "access local files" permission to NoScript (Firefox 153 and above)
- Bug tor-browser#45168: Hide the history search option, again
- Bug tor-browser#45169: Cannot open history sidebar in private browsing window
- Bug tor-browser#45171: Disable split view for 16.0
- Bug tor-browser#45176: Add "Request English" to the website language config
- Bug tor-browser#45178: Change support URLs in new settings
- Bug tor-browser#45179: Update the feedback URL to point to the new support page.
- Bug tor-browser#45180: Also show download warning in download settings
- Bug tor-browser#45185: Disable network also in the Rust implementation of the remote settings client
- Bug tor-browser#45186: Remove duplicate alert roles in moz-message-bar
- Bug tor-browser#45187: Disable private browsing "delete downloaded files" feature
- Bug tor-browser#45190: New circuit urlbar icon button is squished
- Bug tor-browser#45192: Some URLs trigger The proxy server is refusing connections rather than about:torconnect prior to bootstrap
- Bug tor-browser#45194: "Your bridges" background color
- Bug tor-browser#45195: Modify our calls to openPreferences to work with the new settings
- Bug tor-browser#45196: Replace old connection settings with setting-group widgets
- Bug tor-browser#45197: Hide password settings by default
- Bug tor-browser#45200: Include onion authentication in the new password settings
- Bug tor-browser#45201: Convert security level settings to the new config
- Bug tor-browser#45208: Switch on the setting redesign
- Bug tor-browser#45209: Remove mention of "sync" from new settings
- Bug tor-browser#45211: Add settings for protections from third party applications
- Bug tor-browser#45214: Keep megalist (contextual password manager) disabled for 16.0
- Bug tor-browser#45220: about:torconnect doesn't show when launching the browser in non-PBM
- Bug tor-browser#45226: Stylelint issues on browser/components/torpreferences/content/torPreferences.css
- Bug tor-browser#45228: Drop browser.urlbar.update2.engineAliasRefresh
- Bug tor-browser#45232: Spoof picture-in-picture sizes under RFP
- Bug tor-browser#45236: Resolve miscellaneus accessibility issues in about:torconnect
- Bug tor-browser#45245: Fix a ML file inclusion that creates an error
Windows + Android
- Bug tor-browser#44513: Backport Bugzilla 2059471: Do not spoof screen orientation when it is locked
Windows
- Bug tor-browser#45144: Do not offer to make the browser a PDF viewer when in portable mode
- Bug tor-browser#45243: Disable taskbar tabs
macOS
- Bug tor-browser#45163: Consistently do not disable app group container support
Android
- Updated GeckoView to 153.1.0esr
- Bug tor-browser#41758: Don't allow PDFs to be opened by 3rd party apps
- Bug tor-browser#43571: Implement improved error handling and tor restart flow (Android)
- Bug Download v2#44054: Review Mozilla 1970806: Implement new UI for External Download Manager dialog [tor-browser]
- Bug tor-browser#44210: Consider dropping shouldDisableNormalMode setting
- Bug 44448: Trivialise assets rather than delete them in "[android] Delete unused media" [tor-browser]
- Bug tor-browser#44758: Disable email mask feature
- Bug tor-browser#44881: Remove link sharing setting on android
- Bug tor-browser#44921: Disable Google Lens feature
- Bug tor-browser#45049: Opening a pdf from outside TBA crashes TBA after bootstrapping it not already bootstrapped
- Bug tor-browser#45085: Disable GooglePlay Integrity
- Bug tor-browser#45098: Share link button shows in landscape mode on android despite being removed elsewhere
- Bug tor-browser#45115: Padlock always shows insecure even for HTTPS and Onion sites
- Bug tor-browser#45159: Fix Android Padlock security pane colors
- Bug tor-browser#45170: Tab Switcher shows Firefox's private browsing mask badge on tab switcher icon
- Bug tor-browser#45173: Disable Search Optimizations for android
- Bug android#45203: Rebase error with: TB 40041: Implement Tor Network Settings [tor-browser]
- Bug tor-browser#45221: Remove "Manage downloads with another app" setting from TBA download settings
- Bug tor-browser#45227: Remove "Default search engine for Standard Mode"
- Bug tor-browser#45234: Do not spoof secondary screen orientations if they were requested by a lock
Build System
- All Platforms
  - Bug tor-browser#45224: Enable Rust linter in CI
  - Bug tor-browser#45231: Backport Bugzilla 2053518: Rust target detection fails to translate the host triple with rustc nightly >= 2026-07-02 (new -oe-linux- targets)
  - Bug tor-browser-build#41844: Add scripts to backup/deploy signing keys on signing machines
  - Bug tor-browser-build#41850: Update keyring/torbrowser.gpg for new subkey and updated expiration date of the main key
- Windows + macOS + Linux
  - Bug tor-browser-build#41711: Update our manual machinery for its new home
- Windows + Linux + Android
  - Updated Go to 1.26.7
- Android
  - Bug tor-browser-build#41843: Remove unused universal apk from geckoview

New Release: Tails 7.11

2026-08-19T00:00:00Z

Changes and updates

Update Tor Browser to 15.0.20.

Fixed problems

Fix activation of Persistent Storage on some computers. (#19913)

For more details, read our changelog.

Get Tails 7.11

To upgrade your Tails USB stick and keep your Persistent Storage

Automatic upgrades are available from Tails 7.0 or later to 7.11.
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.11 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.11 directly:

Support and feedback

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

New Release: Tor Browser 15.0.20

2026-08-18T00:00:00Z

Tor Browser 15.0.20 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.19 is:

All Platforms
- Bug tor-browser#45204: Rebase Tor Browser stable onto 140.14.0esr
- Bug tor-browser#45219: Backport Security Fixes from Firefox 154
Windows + macOS + Linux
- Updated Firefox to 140.14.0esr
Android
- Updated GeckoView to 140.14.0esr
Build System
- All Platforms
  - Bug tor-browser-build#41839: Backport tor-browser-build-browser#41831: Update libevent to 2.1.13
  - Bug tor-browser-build#41850: Update keyring/torbrowser.gpg for new subkey and updated expiration date of the main key
- Windows + Linux + Android
  - Updated Go to 1.25.13

Funding internet freedom together: results from our first participatory funding round

2026-08-17T00:00:00Z

What if funding internet freedom wasn't driven by a few large donors, but by how many people showed up? What if $1 dollar could go as far as $100? Earlier this year, we set out to answer these questions by launching a participatory funding campaign. The goal was to test new funding mechanisms to support critical digital infrastructure at a moment of systemic funding instability.

The round officially closed on June 19th, and the results give us reason to be encouraged. Today, we can share that the community showed up: more than $200,000 USD has been raised in total, with $174,536 being distributed to participating grantee projects.

More than the total, what matters is how we got there: 580 unique donors made 662 contributions, with an average donation size of $41. The direct donation total was modest compared to a traditional Tor fundraising campaign, but that was baked into the design. Participation helped shape how matching funds were allocated (by using the quadratic funding algorithm), turning community support into financial impact for participating projects.

Why did we run this experiment?

There is an entire ecosystem of internet freedom tools that help people communicate safely, access information, document censorship, share files securely, and protect their privacy. These tools are often used as emergency infrastructure, but funded like optional projects.

Many depend on small teams doing difficult, long-term work that is invisible until urgently needed. When funding sources shift suddenly or disappear, the effects are immediate: teams reduce staffing, delay development, scale back infrastructure, and narrow support for the communities that depend on them.

That fragility became impossible to ignore after a major policy shift in 2025 disrupted long-standing funding for parts of the internet freedom community. Some projects had grants rescinded in the middle of active contracts. Others were suddenly forced to rethink whether they could continue operating at the same scale, or at all.

That highlighted a deeper problem with centralized funding. When public-interest infrastructure depends too heavily on one funder, a single decision can put essential work at risk---whether that funder is a government, foundation, company, or individual patron. For tools that people rely on in moments of crisis, that is not a sustainable model.

What the community made possible

We saw an opportunity to test new ways of sustaining public goods funding. Rather than replace traditional nonprofit funding, the campaign aimed at testing the impact of collective investment and shared responsibility in response to the challenges of funding for public-interest technology.

The campaign brought together privacy, internet freedom, cryptocurrency, and open-source communities to support 10 participating projects working across censorship circumvention, secure communications, secure journalism, and critical digital infrastructure.

Final project allocations are:

Project	Direct donations	Donor units	QF share	Match	Total to project
Onion Browser	$11,854	190	63.3%	$99,266	$111,119
Unredacted	$5,262	129	22.6%	$35,467	$40,729
Osservatorio Nessuno	$2,894	84	7.5%	$11,740	$14,633
Paskoocheh (ASL19)	$390	32	0.6%	$4,611	$5,000
OpenArchive	$462	23	0.4%	$4,538	$5,000
SecureDrop	$475	19	0.3%	$4,525	$5,000
Ricochet Refresh	$930	34	1.0%	$4,070	$5,000
OONI	$986	24	0.8%	$4,014	$5,000
OnionShare	$1,066	53	2.4%	$3,934	$5,000
Miaan Group	$2,628	23	1.2%	$2,372	$5,000
Total	$26,945		100%	$174,536	$201,481

15% of funds raised were used to cover the staff and infrastructure to build and run the campaign. We kept it as low as possible while still running a secure, privacy-preserving campaign.

Visibility

One of the clearest outcomes from this round was the strength of community support for Onion Browser, which received the largest allocation. That result reflects both the project's role in facilitating Tor access on iOS and the way a participation-based model can amplify projects with strong name recognition and an existing audience. This also showed us where future rounds can improve.

However, some smaller or less widely known projects benefited from this campaign in important non-monetary ways by gaining visibility, followers, and direct outreach from people discovering their work for the first time.

Unredacted shared that many people appeared to discover the project for the first time, and that having the fundraiser visible in Tor Browser was especially valuable for visibility.

Osservatorio Nessuno said the campaign amplified its audience and led to new people getting in touch after discovering its work.

OONI confirmed that broader visibility may have helped increase its social media following, which in turn may have contributed to more OONI Probe installations and increased measurement coverage.

When more people understand what these projects do, why they matter, and how they fit into the larger ecosystem, the whole movement becomes stronger. For future rounds, we want to help discovery happen earlier and more evenly. In this round, we addressed part of that imbalance by raising the minimum distribution threshold to $5,000, ensuring that every participating project received support in recognition of the work required to take part in the campaign.

Participation

Quadratic funding is designed to reward broad participation, not only the size of individual donations. In practice, this means that a project backed by many contributors can receive more matching support than one supported by only a few larger gifts.

For this round, direct community donations totaled $26,945.29. Those donations helped unlock a larger matching pool, supported by our matchfunders, and influenced how matching funds were allocated across the participating projects.

Community donations came in through BTC, ETH, ZEC, XMR, and GLM: By value, the direct donations split about 52% Bitcoin, 27% Monero, 13% Ethereum, and 8% Zcash. Monero was invisible to the public tracker, yet made up more than a quarter of the total. The site's public total showed transparent chains only with about $19,620 raised. The roughly $7,300 that came in Monero then brings direct donations to about $27,000.

source:

Thank you to our matchfunders

This campaign brought together communities that understand privacy, open infrastructure, and public goods as shared responsibilities. It showed what becomes possible when funders, users, and public-interest technology projects move together.

We are grateful to Cake Wallet, Ethereum Foundation, Logos, Octant, Xeovo and Zcash Community Grants for stepping forward and helping turn individual contributions into ecosystem-wide support. Their participation made it possible for small donations to carry more weight and for community support to influence how funds were distributed.

We also want to shout out Web3Privacy Now who acted as our media partner for this campaign. The non-profit amplified the campaign's reach with the production of four campaign videos and multiple testimonial videos featuring Naomi Brockwell, Eva Galperin, and Kurt Opsahl among others.

A few lessons stand out.

First, participation can meaningfully shape funding outcomes. The campaign showed that hundreds of individual donors can influence how support moves through an ecosystem, even when direct donation totals are relatively modest.
Second, discoverability needs to be designed more intentionally in future rounds: Tor-owned channels, including prominently featuring the campaign in Tor Browser, helped participating projects reach people who may not have encountered their work otherwise. That visibility created value beyond the dollars raised. But better-known projects entered this campaign with an advantage and benefited disproportionately from their visibility and existing community reach.
Third, this model is promising, but operationally complex. Multi-currency donations, privacy-preserving contributions, conversions, matching calculations, campaign infrastructure, and project-level reconciliation all take time and care. We waited to share final results because we wanted to provide accurate numbers.

These are exactly the kinds of lessons we hoped this experiment would surface. If internet freedom infrastructure needs more resilient funding models, we need to be honest about what works, what is hard, and what we can improve next time. For additional insights into the campaign,

This round has ended, but the work continues

You can still support the participating projects directly and help sustain the tools people rely on to communicate safely, access information, and resist censorship.

We are exploring what future rounds could look like. If your organization is interested in supporting internet freedom infrastructure through a future matching pool, we'd like to hear from you.

We are also interested in hearing from the broader ecosystem. If there are internet freedom projects, tools, or communities you believe should be part of a future round, let us know.

Thank you to everyone who showed up.

New Release: Tails 7.10.1

2026-08-05T00:00:00Z

This release is an emergency release to fix critical security vulnerabilities in the Linux kernel and the expat XML library.

Changes and updates

Update the Linux kernel to 6.12.100, which fixes CVE-2026-64560, a vulnerability that could allow Tor Browser in Tails to gain administrator privileges.

For example, if a malicious website that you visit is able to exploit CVE-2026-64560, they might take full control of your Tails and deanonymize you.

This attack is very unlikely but could be performed by a strong attacker, such as a government or a hacking firm. We are not aware of this attack being used in practice until now.

Update the expat XML library to 2.8.2, which fixes DSA-6404-1, a set of vulnerabilities that could allow different applications in Tails to gain administrator privileges.

For example, if an attacker tricks you into opening a malicious file in an application that uses expat , such as LibreOffice , Audacity , or Git , they might then use one of these vulnerabilities to take full control of your Tails and deanonymize you.

This attack is very unlikely but could be performed by a strong attacker, such as a government or a hacking firm. We are not aware of this attack being used in practice until now.

Compress automatic upgrades with zstd for a faster startup, as we already did for the USB image in Tails 7.0.
Make USB images and automatic upgrades 70 MB smaller by removing unused firmware.

For more details, read our changelog.

Get Tails 7.10.1

To upgrade your Tails USB stick and keep your Persistent Storage

Automatic upgrades are available from Tails 7.0 or later to 7.10.1.
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.10.1 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.10.1 directly:

Support and feedback

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

Arti 2.5.1 released

2026-08-04T00: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.5.1.

This release consists mostly of internal improvements and bug fixes, as well as our ongoing development towards using Arti as a relay and as a directory authority. For onion service hosts, onion services can now be configured to connect to unix socket addresses. Arti also now has experimental support for congestion control and Counter Galois Onion cryptography on onion service circuits, which we hope to make stable soon.

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, Jérôme Charaoui, hjrgrn, pryty26, ramdoys, and syphyr.

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