Firefox Moves to Two-Week Releases, Testing Its Extension Makers

Mozilla will ship Firefox every two weeks instead of four starting September 1, 2026, when Firefox 155 debuts as the first release under the new cadence. Firefox 154 on August 18 will be the last version on the old schedule. Mozilla Director Sylvestre Ledru confirmed the shift, which lines Firefox up with Google Chrome and Microsoft Edge.

Mozilla calls it a reversible experiment. The heavier adjustment lands on Firefox’s extension developers and its own release engineers, who now face shipping deadlines and API churn twice as often as before. Most everyday users will not notice the switch at all.

Firefox 155 Opens the Two-Week Era on September 1

The mechanics are straightforward. Firefox 154 ships August 18, 2026, closing out the browser’s current monthly-style cadence. Firefox 155 follows on September 1, not the four weeks users have grown used to, and every version after that arrives roughly every two weeks. The community-run release calendar tracking every upcoming Firefox train has already been updated to match.

Mozilla frames the change as an experiment it can reverse if problems appear. Developers are not being asked to work twice as fast, and features that are not ready will still get held back rather than shipped early. What changes is how often a stable build goes out the door, not how quickly any single feature gets built.

Chrome and Edge Already Made the Same Bet

Firefox is the last of the three major desktop browsers to make this move. Google announced Chrome’s own two-week cadence in March 2026. Microsoft followed with Edge, which reaches the same rhythm on August 27 with Edge 152, built on the Chromium codebase Google maintains. Chrome’s shift to shipping a new build every two weeks set the pattern the other two browsers are now following.

Matching that rhythm is simpler for Edge. It already inherits Chromium’s engineering and release infrastructure from Google, so lining up with Chrome is close to a formality. Firefox runs on Gecko, an engine Mozilla builds and tests independently, which is why Ledru is treating the change as a trial rather than settled policy. Web developers who test sites across multiple browsers benefit when release rhythms line up, since a feature landing in Chrome and Firefox around the same time is easier to plan around than one arriving months apart.

Extension Developers Inherit the Real Workload

Ordinary Firefox users are unlikely to notice the switch. Extension developers will notice immediately. A faster release train means more frequent API changes, deprecations, and behavioral updates landing in their add-ons, on half the runway they had before.

That is not a new complaint. Extension makers have struggled for years to keep pace with Firefox’s rolling updates, and compatibility gaps between browser versions and add-ons have repeatedly frustrated users who depend on them. A two-week cycle compresses that adjustment window further. Mozilla’s own advice to developers is practical:

• Monitor Firefox’s release notes closely for API changes that could break an existing extension
• Increase automated testing so compatibility problems surface before a release ships, not after
• Track the Nightly and Beta channels for early warning of behavioral changes still weeks away from stable

None of that removes the workload. It spreads the same scrutiny across a shorter calendar.

Will Your Firefox Experience Change on September 1?

Most Firefox users will not need to do anything differently. Automatic updates keep installing new versions quietly in the background, and the two-week train just means that process now runs twice as often. Anyone who wants manual control can switch Firefox to check for updates without installing them automatically.

Organizations have that second option already built in. Mozilla documents the Extended Support Release channel for enterprise deployments, which keeps its own slower schedule, shipping security and stability fixes without the feature churn of the main release. IT teams that need time to test a build before rolling it out fleet-wide were always going to lean on ESR rather than the two-week channel, and that has not changed. Mozilla’s administrator guide comparing Release, Beta, Nightly, and ESR still treats ESR as the stability-first option for larger deployments.

Firefox Has Sped Up Before

This is not the first time Firefox has compressed its release calendar to keep pace with Chrome. Mozilla moved Firefox to a four-week cycle in 2020, specifically to keep up with Chrome’s support for new web features. That four-week rhythm is the one Firefox is now leaving behind, six years later, for much the same reason.

The pattern shows up on Firefox’s public version-history and support-lifecycle tracker, where each cadence change compresses the gap between one end-of-life version and the next. A two-week train means more version numbers retiring every year, and more builds for administrators and developers to track through their own support windows.

Can Mozilla’s Smaller Team Match Google’s Pace?

Early reaction leans skeptical. Firefox’s release-engineering team is far smaller than the teams Google and Microsoft assign to Chrome and Edge, and doubling the shipping cadence does not automatically double the headcount watching for regressions. Reaction across Reddit and other Firefox forums since the announcement has been mixed rather than uniformly negative, but it is far from a celebration.

Where reactions divide:

• Security-minded users welcome the faster cadence, arguing shorter gaps between releases close vulnerability windows sooner.
• Longtime Firefox users on forums say Mozilla is following Google’s cadence and its WebExtensions add-on model even where the community pushed back before.
• Extension maintainers are less worried about update speed itself than about funding compatibility testing on half the runway.

Mozilla’s counterargument sits in its own documentation. The multi-channel train system running from Nightly through Beta to stable exists precisely to catch problems before they reach a two-week release. Whether that pipeline holds up under double the frequency, without double the staff, is the question critics are asking that Mozilla has not yet answered in public.

Firefox 154 ships first, on August 18, still under the old rules. Two weeks later, on September 1, Firefox 155 starts the clock on the new ones.

Frequently Asked Questions

When Does Firefox’s Two-Week Release Cycle Begin, and Does It Reach Android?

The new cadence begins September 1, 2026, with Firefox 155, and it applies to both desktop and Android builds. Firefox 154 on August 18 is the final release under the old monthly-style schedule before the switch.

How Do I Stop Firefox from Installing Updates Automatically?

Open Firefox, click the menu button, choose Settings, select General, and scroll to the Firefox Updates section. Choosing to check for updates without installing them automatically keeps new builds from landing until you approve them, useful for anyone who wants to skip the twice-a-month pace.

What Is Firefox ESR, and Who Actually Needs It?

Firefox Extended Support Release ships security and stability fixes on a slower schedule and skips the feature churn of the regular channel entirely. Regulated industries and IT departments that need weeks to test a build before deploying it fleet-wide typically standardize on ESR instead of the fast channel.

Why Is Mozilla Speeding Up Firefox’s Release Schedule Now?

Mozilla says shipping more often lets developers deliver updates to users sooner, and Director Sylvestre Ledru has said the change should make the release process more predictable, with fewer hurdles disrupting rollout plans. The timing also follows Chrome and Edge, which moved to the same two-week rhythm earlier in 2026.

Will New Firefox Features Arrive Twice as Fast Under the New Schedule?

No. The two-week cycle changes how often a stable version ships, not how quickly any individual feature gets built. Features that are not ready still wait for a later release instead of going out unfinished.

Is Firefox’s Two-Week Release Cycle Permanent?

Not yet. Mozilla has called this an experiment and says it will judge release quality, developer workload, and user experience before deciding whether the faster pace becomes permanent policy.