Google Moves Chrome to a Two-Week Development Schedule

Google Moves Chrome to a Two-Week Development Schedule

Starting with Chrome 153 in September 2026, Google will move its web browser to a two-week development schedule.

“The web platform is constantly advancing, and our goal is to ensure developers and users have immediate access to the latest performance improvements, fixes and new capabilities,” Google’s Ben Mason and Deepak Ravichandran explain. “Building on our history of adapting our release process to match the demands of a modern web, Chrome is moving to a two-week release cycle. While releases will be more frequent, their smaller scope minimizes disruption and simplifies post-release debugging. And thanks to recent process enhancements, we are confident this shift will maintain our high standards for stability.”

As you may recall, Google moved Chrome from a six-week to a four week development schedule five years ago, and most other Chromium-based browser makers, including Microsoft with Edge, followed suit. (Mozilla also follows a four-week schedule for Firefox, though Apple ties new Safari releases to new OS releases like it’s still the 1990s.) So I assume we’ll see a similar shift for those companies as well.

With this new schedule, Google will ship new beta and stable versions of Chrome across desktop and mobile every two weeks, starting with Chrome version 153 on September 8. But the Dev and Canary channels will retain their current schedules, as will Chrome Extended Stable, which is aimed at the enterprise and can be used on managed Chromebooks. And Chrome Beta releases will appear three weeks before the corresponding stable release.

Share post

Thurrott