Google Chrome Moves to a Two-Week Release Cycle With Version 153

The news

Google Chrome has moved to a two-week release cycle. Version 153 is the first major version delivered under the new schedule and is now reaching users through the stable channel.

The sources both place the change into effect on September 8, 2026. The shift follows a preview Google gave earlier in the year and brings Chrome’s cadence in line with the faster pace already used by other browsers.

Context

Until now, Chrome delivered major stable releases on a roughly four-week rhythm. That interval gave teams time to test, stage, and roll out updates inside large organizations. The new schedule halves the gap between visible updates.

Both reports describe the move as Chrome joining an existing industry direction rather than leading it. Users on Windows, macOS, Linux, Android, and iOS who receive automatic updates will see the difference first. Enterprise administrators who maintain internal testing pipelines will also feel the change in their deployment calendars.

The prior four-week cycle had been in place for years. Shortening it means the stable channel now advances twice as often, which alters how quickly new web-platform features and security fixes reach the majority of users.

Details

The 9to5Mac report states that version 153 marks the formal start of the two-week rhythm. Neowin reports the same date and notes that users will encounter major version bumps more frequently from this point forward. Neither source lists new technical changes to the release pipeline itself beyond the altered timing.

Both outlets frame the decision as alignment with a broader trend toward quicker browser updates. No on-the-record quotes appear in the supplied material, and no specific feature set is tied exclusively to version 153. The coverage centers on the schedule change and its immediate effect on release frequency.

The two reports agree on the core facts: the cycle began September 8, 2026, with version 153, and it replaces the previous four-week interval. They differ only in phrasing—one emphasizes the preview that occurred earlier in the year, the other highlights the user-visible impact of more frequent major updates.

Why it matters

A shorter release interval compresses the time between code landing in the repository and reaching hundreds of millions of machines. Security teams gain faster distribution of patches, which narrows the window during which known vulnerabilities remain unaddressed on user devices. Web developers receive new APIs and platform behaviors in smaller, more regular increments instead of larger quarterly bundles.

The cost appears on the operations side. Organizations that built testing and approval processes around a monthly cadence must now adjust those windows or accept that updates will arrive more often. End users will notice version numbers advancing twice as frequently, even if individual updates contain fewer changes.

It remains to be seen whether the tighter schedule improves overall stability or simply multiplies the number of minor regressions that reach the stable channel. The immediate outcome is that Chrome’s release train now runs on the same timetable already used by its quickest competitors. Over the next several months the data will show whether the trade-off favors quicker fixes or creates additional maintenance overhead for the teams that support the browser at scale.

---

Sources:

• 9to5Mac
• Neowin

{
  "word_count": 612,
  "headline": "Google Chrome Moves to a Two-Week Release Cycle With Version 153",
  "sources_used": 2
}