Google Chrome will now ship security updates every two weeks, thanks to AI

Chrome to get two-weekly updates from this month

by · TechRadar

News By Craig Hale Published 9 September 2026

(Image credit: Shutterstock / Ink Drop)

Share this article 0 Join the conversation Follow us Add us as a preferred source on Google Newsletter Subscribe to our newsletter

  • Chrome will get new updates every two weeks to minimize real-world attacks
  • Smaller, incremental changes should also make it easier to track any issues
  • Other major browsers are also shifting to two-weekly release cycles

Google has confirmed that Chrome has officially moved from a four-week Stable release cycle to a two-week one, with effect from September 8 2026 with the launch of Chrome 153.

Besides adding new features, the main objective is for Google to give us performance and security fixes more promptly in an era of increased complexity and heightened vulnerabilities.

And it's exactly those security concerns that pushed Google to want to double Chrome's update frequency in the first lace, with the company now having to deal with a higher volume of patches than ever before.

Latest Videos FromTechRadarWatch full video here:

Chrome will get updates every two weeks

Together with a higher volume of attacks in general, Google has also benefitted from AI-powered vulnerability discovery tools, giving developers more work to do than before. "With automated AI discovery tools and community bug reports generating higher patch volume, shorter release cycles make managing security fixes significantly simpler," the company wrote.

Crucially, the faster cycle reduces the time between a fix landing in Chrome's public codebase and it actually reaching end users, making it less likely for a bug to be exploited in the wild.

Chrome has been adhering to a four-week cycle since 2021, but the world is a very different place in the space of just half a decade.

With the higher pace of releases, Google also anticipates a smaller scope of changes, which could actually be a good thing because it could be easier for developers to identify what went wrong in the event of any issues.

Are you a pro? Subscribe to our newsletter

Sign up to the TechRadar Pro newsletter to get all the top news, opinion, features and guidance your business needs to succeed!

Contact me with news and offers from other Future brandsReceive email from us on behalf of our trusted partners or sponsors