Google feels the need for security speed, so will ship Chrome updates every two weeks

Steven

Google feels the need for security speed, so will ship Chrome updates every two weeks

Summary

Google will shorten the general release cadence for Chrome to every two weeks across desktop, Android and iOS, starting 8 September with Chrome 153. The company says smaller, more frequent releases reduce disruption, simplify post-release debugging and give users and developers faster access to performance improvements, fixes and new capabilities.

Enterprises and embedded Chromium users keep the eight-week Extended Stable channel. Google also plans fortnightly beta releases so organisations can spot potential issues earlier. The move follows earlier cadence increases (notably 2021’s shift from six to four weeks) and is framed as a security-driven change to deliver fixes faster.

Key Points

  • Chrome will adopt a two-week release cadence for mainstream channels across desktop, Android and iOS from 8 September (Chrome 153).
  • Extended Stable releases remain on an eight-week schedule for enterprise and embedded Chromium consumers.
  • Google argues smaller, more frequent updates reduce disruption and make post-release debugging simpler.
  • Fortnightly releases are recommended as the most secure option; Google advises enterprises to choose them if security outweighs maintenance costs.
  • Beta channel will also move to two-week updates, giving admins earlier visibility of changes that might affect SaaS or web apps.
  • This continues a trend: Google tightened cadence in 2021 (six to four weeks) for similar reasons — faster security fixes and feature delivery.

Why should I read this?

Short version: if you run browsers, manage web apps, or look after corporate endpoints, this affects your patching and testing rhythm. Expect more frequent updates and more chances to catch — or be surprised by — changes. We read the detail so you don’t have to; plan your testing windows and update policies now.

Context and relevance

This is a significant operational change for IT teams, security ops and SaaS providers. Faster releases mean quicker fixes for in-the-wild vulnerabilities but increase the cadence of compatibility testing and deployment work. The retention of an eight-week Extended Stable channel gives enterprises a slower, predictable option, while the fortnightly beta channel offers earlier warnings about potentially disruptive features.

Organisations should review update policies, automation for patch rollout and QA procedures. The move reflects wider industry trends toward quicker security response and smaller, incremental releases across major platforms.

Source

Source: https://www.theregister.com/2026/03/04/google_speeds_chrome_release_cadence/