Chrome Adopts Two-Week Release Cycle Starting with Version 153

As previously previewed earlier this year, Google Chrome has moved to a two-week release cadence for its Stable channel. This change marks a notable shift in how frequently Google ships milestone updates to the browser and reflects an effort to get improvements, features, and fixes into users’ hands more quickly.

Historically, Chrome’s milestone updates — the releases that increment the major version number, such as from 100 to 101 — arrived every four weeks. Prior to 2021, the cadence was even slower, with a six-week cycle in place. The new two-week schedule effectively doubles the frequency of milestone releases compared with the four-week model, while maintaining the same steady stream of security patches and smaller fixes that Chrome has long provided.

Google says the purpose of releasing larger updates every two weeks is simple: to provide new features, performance gains, and bug fixes faster. With more frequent milestones, each release can have a narrower scope, which helps teams focus on fewer changes at a time. That smaller scope per release also aims to make it easier to identify and isolate regressions when they occur, speeding up resolution and improving overall platform stability.

From a developer perspective, the shorter release window can reduce the time between when new web platform capabilities are announced and when they are broadly available to end users. Google argues that tighter deployment windows will make it easier for developers to ship modern web features with confidence, because interoperability updates and safety improvements can reach all major platforms sooner. For developers who follow Chrome’s release channels closely, the faster cadence means quicker access to enhancements and earlier feedback from real-world usage.

Security is another area Google highlights as benefiting from the accelerated schedule. In an environment where threats evolve rapidly — including those influenced by advances in artificial intelligence — the ability to push security patches and mitigations more frequently helps protect users against emerging risks. Regular, smaller releases make it possible to respond promptly to vulnerabilities without waiting for a larger, less frequent milestone.

Enterprises have different operational needs, so Google continues to offer the Extended Stable channel for organizations that prefer less frequent changes. In that option, milestone updates are grouped into an eight-week cadence, allowing IT departments more time for testing and broader change management. Google recommends that most enterprise users remain on the two-week Stable channel unless their internal policies or compliance requirements call for the extended schedule.

Today’s rollout brings Chrome 153 to desktop, Android, and iOS users, continuing the steady stream of milestone releases under the new cadence. Google also notes that Chrome 154 is slated to arrive on September 22, keeping to the roughly biweekly interval between major releases. For users and administrators, that schedule means a predictable, frequent rhythm of feature updates and fixes, as well as more frequent prompts to review new capabilities and policy impacts.

For everyday users, the switch to two-week milestones should be largely transparent: updates will install in the background as before, and users will experience incremental improvements more often. Power users and developers will likely notice the change first, as APIs, experimental features, and behavior tweaks land more quickly. IT teams and organizations that manage fleets of devices should consider how the accelerated cadence affects testing workflows, compatibility checks, and rollout planning.

Overall, Google positions the move to a two-week milestone cycle as a benefit for the web ecosystem: faster delivery of innovations, quicker security responses, and improved ability to isolate issues when they arise. While it represents a change in rhythm compared with the previous four-week cycle, the goal is to balance speed with stability so users, developers, and enterprises alike can take advantage of a rapidly evolving browser platform.

More on Chrome: