Firefox is speeding up its release schedule
Mozilla is shortening the gap between Firefox releases from roughly four weeks to two weeks. Firefox 154, due August 18, 2026, will be the last version shipped on the old cadence. Firefox 155 starts the new pace on September 1, 2026, after its target date was moved up from an originally planned September 15.
From Firefox 155 onward, a new version is expected to land roughly every two weeks, covering both Firefox for desktop and Firefox for Android.
Why Mozilla is making the change
The move was announced on July 10, 2026 by Sylvestre Ledru, Mozilla's director of engineering, in a post to the dev-platform mailing list. Ledru called it an experiment and said it does not mean all work needs to ship twice as fast just because releases arrive twice as often; work that is not ready still waits for a later release rather than being rushed out.
Mozilla's stated goal is to get bug fixes, updates and features in front of users sooner after they are finished, and to make the release process itself more predictable, with fewer scheduling conflicts for teams planning rollouts. Mozilla has also said it can reverse the change if the faster pace ends up hurting release quality, straining developer workload, or degrading the experience for users.
Catching up with Chrome and Edge
The switch lines Firefox up with its two biggest rivals. Google Chrome adopted a two-week release cadence in March 2026, and Microsoft Edge is set to begin its own two-week schedule on August 27, 2026. Firefox had been running on a roughly four-week cycle since 2019, when Mozilla last slowed its release train down from an even faster schedule it used earlier in the 2010s.
What stays the same: Extended Support Release
The Extended Support Release (ESR) channel, aimed mainly at enterprises and organizations that prioritize stability over new features, is not part of this change. ESR keeps its existing annual schedule, with point releases in between that mostly carry security fixes rather than user-facing changes. Firefox 153 is set to become the next ESR baseline, and Mozilla plans to support it with security updates for at least 15 months, into late 2027.
The knock-on effect for localization
Mozilla's localization team has already flagged how the tighter schedule changes its own workflow. Translation deadlines in Mozilla's Pontoon platform shrink from roughly three weeks to two, a change that started affecting cycles from around August 12, 2026. As an example of the new rhythm, Firefox 157 has its code merge day set for September 10, 2026 and its release candidate build due September 24, 2026.
Because each cycle is shorter, Mozilla expects less new text to translate per release. To soften the transition, the team plans to show translated strings when they already exist rather than falling back to English mid-cycle, push some translation updates through point releases, and rely more on an optional pretranslation feature to fill gaps faster.
What this means in practice for web developers
The faster cadence does not change what Firefox can render, but it does change how often the ground shifts under a project, so a few habits are worth adjusting.
- Compatibility testing should shift to a lighter, more frequent rhythm rather than one deep pass a month. A given version now sits in front of users for about two weeks instead of four, so regressions need to surface and get fixed faster.
- Version-detection or feature-detection code that assumes a certain gap between Firefox releases should be reviewed. Two features that used to land a month apart may now ship only one release apart, or spread across two shorter releases instead of one.
- Quality assurance cycles tied to Firefox's release train need recalibrating. Teams that ran a Firefox-specific check once a month should either double that cadence or start testing against Beta and Nightly builds earlier, since there is less lead time between a bug appearing and it reaching general release.
- Feature-flag rollouts and staged deployments that assumed a four-week buffer before a Firefox update reached most users should plan for roughly half that buffer going forward.
- Sites and extensions that specifically support Firefox Extended Support Release are unaffected by this change and can keep testing against it on its usual annual schedule.
- Since Mozilla has framed this as a reversible experiment, it is worth treating it as a scheduling adjustment rather than a reason to overhaul release processes; if it does not work out, Mozilla could slow back down.
Overall, the change brings Firefox's release rhythm closer to Chrome and Edge, which may simplify cross-browser testing calendars for teams already tracking all three. The scope of what ships is not changing, only how often it arrives.
