Chrome’s Shift From a Four-Week Release Schedule to Bi-Weekly Releases

Google is moving Chrome to a new release every two weeks starting in September. Until now, Chrome has been on a four-week release schedule for new major versions for five years.

This cadence change isn’t framed as “more change, faster.” It’s positioned as “smaller batches, shipped more often.” In practice, that means Chrome users and teams maintaining Chrome-dependent environments should expect major-version releases to arrive twice as frequently as they do today—just with fewer individual changes bundled into each drop.

Why Google Is Moving to a Two-Week Chrome Release Cycle

Google’s stated rationale for the faster two-week cycle is straightforward: it enables faster delivery of:

  • Performance improvements
  • Bug fixes
  • Security updates
  • New features

And that matters because Chrome is used by both everyday users and developers who build, test, and ship experiences that run inside it. A shorter cycle is essentially an attempt to reduce the “waiting period” between a fix being ready and that fix landing in the stable channel.

What “More Frequent Updates” Really Means: Fewer Changes Per Release

Google’s argument is that while updates will be more frequent, each individual update will contain fewer changes. That smaller scope per release is meant to do two things:

Reduce the risk of problems per launch

Fewer changes in a given release should, in theory, lower the odds that any single update introduces a broad, hard-to-trace issue.

Make troubleshooting easier when something breaks

When a release contains fewer changes, narrowing down the source of a problem becomes less messy. Instead of searching across a large bundle of modifications, teams can isolate the likely cause more quickly after launch.

For organizations that treat Chrome updates as operational events—testing internal apps, validating extension behavior, monitoring user impact—this “smaller batch” logic is the real backbone of the change.

When the Bi-Weekly Chrome Update Cadence Starts (Chrome 153)

The new cadence model begins with Chrome 153, with the stable version scheduled for release on Sept. 8, 2026.

That’s the practical starting line: from that release forward, the expectation becomes a two-week rhythm rather than a monthly one.

Which Platforms Are Included: Desktop, Android, and iOS

This isn’t a desktop-only adjustment. The change applies to Chrome versions for:

  • Desktop
  • Android
  • iOS

So if you manage Chrome across multiple device types—company laptops plus mobile fleets, for example—this cadence shift will show up across the board rather than in just one corner of your environment.

What Users and Developers Should Expect From the New Chrome Cadence Model

The big tradeoff is pretty clear:

  • Pros: faster delivery of improvements, fixes, and security updates
  • Operational reality: more frequent releases to absorb

Even with smaller changes per release, the browser will now introduce new stable versions twice as often. That inherently increases the number of moments where teams might need to validate behavior, confirm compatibility, or respond to edge-case issues.

At the same time, Google’s emphasis on reduced risk and easier troubleshooting suggests the company is trying to make these release events less dramatic—more routine, less “everything changed at once.”