Beyond the News
Sign in
Web DevelopmentBrowsers & Web Standards Active dossier

Chrome and Firefox are moving major releases to two-week cycles

Chrome and Firefox are both halving their major-release cadence, tightening the window for compatibility testing while keeping important exceptions such as Chrome Extended Stable.

Reviewed and published by Lars Jansen Updated 4 min read
First published

Key details

  1. Chrome's two-week stable cadence begins with Chrome 153, scheduled for September 8, 2026.
  2. Chrome beta and stable will both ship every two weeks.
  3. Chrome Dev and Canary do not change.
  4. Chrome Extended Stable remains on an eight-week cycle.
  5. Firefox Desktop and Android are moving from four-week to two-week releases.
  6. Firefox's transition begins with Firefox 155 Beta; Nightly, Beta and Release periods then become two weeks.

What builders should take away

  1. Add Chrome Beta and Firefox Beta to CI for high-value browser-dependent flows instead of relying only on current stable versions.
  2. Replace support policies tied to long-lived major versions with rolling compatibility windows where possible.
  3. If you serve enterprise customers, distinguish Chrome Stable from Extended Stable in support documentation and incident triage.
  4. Audit browser-extension release processes and web-platform feature flags for assumptions that a major version lasts about a month.

What changed

Google announced that Chrome will move from a four-week to a two-week beta and stable release cycle starting with Chrome 153, whose stable release is scheduled for September 8, 2026. Mozilla is likewise moving Firefox Desktop and Android from four-week to two-week cycles, beginning with Firefox 155 Beta and then making Nightly, Beta and Release periods two weeks each.

Why it matters

Browser-version assumptions age twice as quickly. Web applications, extension developers, QA teams and vendors that certify support by major version will have less calendar time to detect regressions, validate new web-platform behavior and update compatibility documentation.

Chrome changes stable and beta, not every channel

Chrome's new cadence applies across Desktop, Android and iOS for beta and stable releases. Dev and Canary remain unchanged. Google also says Extended Stable will continue on its existing eight-week cycle, preserving a slower enterprise option.

Firefox is changing the full train

Mozilla says Firefox 155 Beta starts the transition, after which Nightly, Beta and Release periods each become two weeks. The localization window also compresses, illustrating that the release-process change affects downstream contributors as well as browser users.

Testing needs to become more continuous

Teams that wait for stable releases to begin compatibility testing will have less time to react before the next major version. Running important suites against beta channels and tracking browser-roadmap changes becomes more valuable, especially for extensions and APIs with version-specific behavior.

Timeline

2026-03-03

Google announces Chrome's two-week cycle

Google set September 2026 as the start of the new cadence.
2026-07-23

Mozilla details Firefox transition

Mozilla described the Firefox 155 Beta transition and two-week release train.
2026-09-08

Chrome 153 stable scheduled

Chrome 153 is scheduled as the first stable release under the new two-week cadence.

What to watch next

  • Whether the faster cadence increases regression frequency or instead reduces per-release change size as vendors expect.
  • How managed-device and enterprise browser policies adapt to the faster standard channel.
  • Whether other Chromium-based browser vendors mirror Chrome's exact schedule.

Still unclear

  • Mozilla has described the move as a transition and operational details may continue to evolve as Firefox 155 moves through channels.
  • Chromium-based browsers other than Chrome may use different release schedules even when they share engine changes.

Sources

Direct reading behind this dossier.

2 sources
Continue reading
Web Development

Chrome 153 changes Email Verification issuance to signed JSON requests

Chrome 153 introduces a breaking provider-integration change in the Email Verification origin trial: issuance requests move to JSON with HTTP Message Signatures. Chrome has also extended the experiment through 156, making the migration more than a one-release test detail while the underlying protocol remains experimental.

Web Development

Next.js will ship a critical security fix on August 26

Next.js is giving builders advance notice of a critical security patch on August 26. The affected weakness is not yet disclosed, so teams on 16.3 or 15.5 should prepare an expedited upgrade and validation path rather than wait for the advisory to land.