Chrome Moves to Biweekly Updates as AI Reshapes Browser Security
Google has doubled the pace of Chrome releases: since Chrome 153 in September 2026, a new major version ships every two weeks instead of every four. We explain what actually changed, why Google says AI-assisted bug hunting forced the move, what stays the same, and what users and IT teams should do.
⚡ Quick facts
- What changed: Chrome's major release cycle went from four weeks to two
- Started: with Chrome 153 Stable on September 8, 2026; Chrome 154 followed two weeks later
- Platforms: desktop, Android and iOS; ChromeOS keeps a four-week rhythm
- Enterprises: Extended Stable stays on an eight-week cycle with weekly security fixes
- Why: more fixes arriving, partly from AI bug-finding tools, and a smaller gap before patches reach users
What actually changed
Chrome now ships a new major version, or milestone, every two weeks instead of every four. Google announced the plan in March 2026 (9to5Google covered it at the time) and the first release on the new schedule was Chrome 153, which reached the Stable channel on September 8, 2026, according to Google's Chrome for Developers blog. Chrome 154 followed on September 22. The change covers Chrome on desktop, Android and iOS. It is the second speed-up in five years: Chrome moved from six weeks to four in 2021.
This is not the same as security fixes arriving only every two weeks. Chrome already shipped security updates between milestones, and still does; what has doubled is how often a full new version lands.
Why Google says it needed to move faster
Google gives three reasons in its original announcement:
- Faster features and fixes: smaller, more frequent releases get changes to users sooner.
- More fixes to ship: AI-assisted bug-finding tools and outside researchers are reporting more flaws. It was reported that Google received more external bug reports in March 2026 than in all of 2025.
- A smaller “N-day” window: Chrome is built on open-source Chromium, so a fix becomes public in the code before it reaches users. Attackers can study that fix and target people still on the old version. Shorter cycles shrink that gap.
It was also reported that 1,072 fixes landed across two milestones, more than the previous 23 releases combined. Treat that figure as reported rather than independently checked.
What stays the same
- Extended Stable: businesses that need fewer changes can stay on an eight-week cycle (for example Chrome 156, then 160) and still get weekly security backports. Google says the two-week Stable channel is still the most secure choice for most enterprise users.
- ChromeOS: HotHardware reports that ChromeOS skips odd-numbered milestones, so it keeps a four-week rhythm.
- Automatic updates: Chrome still downloads updates in the background, but each one only takes effect after a restart.
Our take: a checklist for users and IT teams
- Restart Chrome regularly. Open the menu, go to Help, then About Google Chrome. If a relaunch is waiting, do it; a browser left open for weeks gains nothing from faster releases.
- Do not turn off auto-update. With a new version every two weeks, a machine that skips updates falls behind quickly.
- Review extensions. Faster patches fix Chrome itself, not a risky extension you installed. Remove the ones you no longer use.
- IT teams: pick a channel on purpose. If you test every release, budget for twice as many; if you cannot, Extended Stable is the supported way to slow down, not delaying Stable updates.
- Watch web apps you depend on. Changes land in smaller steps, so internal tools are less likely to break all at once, but test against Beta if they are critical.
Sources
- Chrome for Developers: Chrome's two-week release cycle starts
- Chrome for Developers: Moving Chrome to a two-week release cycle
- 9to5Google: Chrome is moving to two-week updates (March 3, 2026)
- HotHardware: Google doubles Chrome update velocity with a two-week schedule
- TechRadar: Google Chrome will now ship updates every two weeks
Frequently asked questions
How often does Chrome update now?
Chrome ships a new major version every two weeks, down from four. Security fixes can still arrive between those releases.
When did the two-week cycle start?
With Chrome 153, which reached the Stable channel on September 8, 2026. Chrome 154 followed on September 22.
Why did Google speed up Chrome releases?
To ship features and fixes faster, to keep up with more bug reports, including from AI-assisted tools, and to shrink the window between a fix appearing in open-source Chromium and reaching users.
Does the change apply to ChromeOS?
ChromeOS is reported to skip odd-numbered milestones, so it keeps a four-week rhythm. Chrome on desktop, Android and iOS moves to two weeks.
What should businesses do?
Either test and roll out every two weeks, or use the Extended Stable channel, which stays on an eight-week cycle with weekly security backports.
Do I need to do anything?
Leave automatic updates on and restart Chrome when it asks, or check Help, then About Google Chrome, so new versions actually take effect.