The Tor Project is fundamentally changing its release schedule for the Alpha channel, switching it from the Firefox Extended Support Release base to the much faster Rapid Release cadence. This will come with real consequences for both testers and stable users.
Historically, both the Tor Browser Stable and Alpha releases were based on Firefox ESR. ESR is Mozilla’s long-term support version, which typically receives major feature bumps only once a year, focusing mostly on security patches in between. The new approach, starting with Tor Browser 16.0a1, will base the Alpha channel on Firefox Rapid Release.
Rapid Release receives big new features every four weeks. Tor Browser Stable, beginning with version 15.0, will stick to the latest Firefox ESR channel, which is exactly what you want if you prioritize stability and security above all else.
This means fewer features per alpha update, but this helps relieve a massive, high-stress window developers had to work within every year. The team would spend several months working on new features, followed by a frantic four to five-month period dedicated almost entirely to the ESR transition.
Mozilla only offers about 16 weeks of overlap where both the old and new ESR versions receive security updates. If the Tor team didn’t finish the audit and patch rebase within that window, the stable version of Tor Browser could become vulnerable. This fixed deadline often led to cascading delays for feature development, and it was a major contributor to developer burnout.
The new model aims to spread that transition work out over the entire year. Instead of one massive rebase after 52 weeks of changes, the team will be performing smaller, incremental rebases every four weeks as part of the Firefox Rapid Release updates. This is easier to perform, much simpler to code review, and it lets the developers catch integration bugs individually rather than having to untangle them all at once.
This change should increase the number of major features shipped annually and significantly boost confidence in the transition process itself. If you’re running the Alpha channel, you need to understand that this change comes with a hefty warning label.
While you will get access to new upstream features developed by Mozilla much faster, you’re also going to get upstream bugs much quicker, too. These bugs could easily introduce security or privacy implications. This means if you are an at-risk user, concerned about your privacy, or just need a reliably working web browser, you absolutely should not use Tor Browser Alpha. Stick with Stable, please.
There are other consequences for Alpha users. You can expect a less predictable release cadence because integrating Tor’s privacy patches with Firefox’s rapidly changing codebase is tough. If a difficult problem takes longer than the scheduled four weeks to solve, the Alpha release will be delayed, meaning it won’t receive security updates as promptly as it used to.
The Alpha channel will also drop support for legacy platforms sooner, mirroring Firefox Rapid Release. This means Tor Browser 16.0a1 will no longer support 32-bit x86 processors on Linux and Android, and you’ll need at least Android 8.0 to run it.
For Stable users, the impact is less dramatic but still noticeable. The team expects to ship only one major feature release per year now. This replaces the two we’re used to, the one in Q2 and one in Q3/Q4. So, with Tor Browser 15.0 just released, you won’t see version 15.5. Instead, you can expect Tor Browser Stable 16.0 to land around the middle of 2026.
This is a big change, but keeping the team out of crunch mode is a great thing.
Source: Tor Blog
