Latest Chrome Update Starts Google’s New Two-Week Release Cycle

Google Chrome has officially moved to a two-week release cycle, allowing Google to deliver major browser updates, security improvements, and new features faster.

The change begins with Chrome 153, which is rolling out now and marks the first major release under Google’s new schedule.

Chrome 153 starts Google’s new two-week release schedule

Google’s move to faster Chrome releases has been expected for some time, with the company previously confirming that Chrome would switch to a two-week update cycle.

Chrome 153 is rolling out today, officially starting the new cadence.

Instead of waiting four weeks between major releases, Chrome users will now receive a new major version every two weeks.

Chrome 153 also introduces several developer and web usability improvements as Google continues updating the browser alongside the faster release schedule.

Chrome should download the update automatically once Google makes it available for your device. Users can also check manually by opening the three-dot menu and going to Help > About Google Chrome.

Google wants to deliver Chrome security improvements faster

Security is one of the main reasons Google has shortened Chrome’s major release cycle.

The company says the two-week schedule will help it deliver security improvements and other browser enhancements sooner. The change also comes as AI-powered cybersecurity threats continue to evolve.

Shorter development cycles also mean Google can include fewer changes in each individual major release, rather than grouping a larger number of updates into a four-week window.

Chrome will still receive minor security updates whenever necessary, so important fixes will not have to wait for the next major version.

Chrome Extended Stable stays on an eight-week cycle

Enterprise customers using Chrome’s Extended Stable Channel will not have to adopt the faster two-week schedule.

Google will continue releasing major Extended Stable versions every eight weeks.

The longer cycle gives organizations more time to test browser updates before deploying them across managed environments. It can also reduce the disruption caused by frequent feature and behavior changes.

Chrome Dev and Canary schedules aren’t changing

Google isn’t changing the release schedules for Chrome Dev or Canary.

Those channels will continue operating under their existing update schedules, while Stable moves to the new two-week major release cadence.

Security updates can also continue arriving independently of major Chrome releases across the available channels.

Other browsers are moving toward two-week updates

Google isn’t the only company shortening its browser-related release schedule.

Microsoft has confirmed that WebView2 is switching to a two-week release cycle, starting with version 152.

Mozilla has also been considering moving Firefox to the same two-week update schedule.

The shift suggests that faster browser release cycles could become increasingly common as vendors try to deliver security fixes, web platform changes, and other improvements more quickly.

Via Neowin