Google Chrome has officially moved from a four-week Stable release cycle to a two-week schedule, starting with Chrome 153 on September 8, 2026. Google says the faster cadence is designed to deliver new features, performance improvements and security fixes to users sooner, while keeping individual releases smaller and easier to manage.
When did Chrome switch to the two-week update cycle?
The change took effect on September 8, 2026, with the rollout of Chrome 153 for desktop, Android and iOS. Chrome 154 is already in Beta and is scheduled to reach the Stable channel on September 22.
Chrome had been using a four-week major release cycle since 2021. Before that, major Chrome releases followed a six-week schedule, making the latest move another significant acceleration in Google's browser release strategy.
Why is Google making Chrome updates more frequent?
Google says the web is changing rapidly and users and developers need faster access to performance improvements, fixes and new capabilities.
Security is another major reason. Google says automated AI-based discovery tools and community reports are generating a higher volume of potential security fixes, making a shorter release cycle useful for reducing the time between a fix becoming available and reaching Chrome users.
This matters because attackers can sometimes exploit vulnerabilities after a fix is publicly available but before users have installed the update. Google refers to this exposure period as the “N-day” patch gap.
What changes for Chrome users?
For everyday users, the biggest difference is simply that major Chrome updates will arrive more frequently.
Instead of waiting roughly a month for a new Stable milestone, users will now see a new milestone every two weeks. Google says these releases will have a smaller scope, which is intended to reduce disruption and make problems easier to isolate after an update.
The faster cycle does not mean users have to manually update Chrome every two weeks. Chrome's normal update process remains in place, with releases rolling out automatically over time.
What does the change mean for security?
The shorter cycle could make it easier for Google to push security improvements to users sooner.
Chrome 153 itself illustrates why browser security remains a major concern. Google's Chrome Releases page says the desktop Stable update included 230 security fixes, with some vulnerability details restricted until a majority of users had received the fix.
The two-week milestone cycle also works alongside Chrome's existing security-update strategy rather than replacing the need for security patches between major releases. Google says security fixes continue on a regular weekly schedule for Extended Stable users, while major feature updates arrive less frequently on that channel.
What does the faster schedule mean for developers?
Developers will have to pay closer attention to Chrome's release calendar because browser changes will reach Stable more often.
Google recommends that developers test websites and applications against Chrome Beta so they can identify compatibility issues before changes reach Stable. Under the new schedule, the smaller scope of individual releases is also intended to make regression testing and troubleshooting easier.
Chrome 153 already includes several changes relevant to web developers, including improvements to CSS scrolling behaviour, new <camera> and <microphone> capability elements, and new JavaScript iterator functionality.
What happens to Chrome's other release channels?
Not every Chrome channel is moving to the two-week schedule.
The Dev and Canary channels remain unchanged. Google's Extended Stable channel for enterprise administrators and Chromium embedders also keeps its eight-week major feature release cycle.
| Chrome channel | Release cadence |
|---|---|
| Stable | Every 2 weeks |
| Beta | Every 2 weeks |
| Extended Stable | Every 8 weeks |
| Dev | No change |
| Canary | No change |
For organisations that cannot accommodate frequent feature changes, Extended Stable provides a longer window between major feature updates while still receiving security fixes. Google says most enterprise users should use the regular two-week Stable option, with Extended Stable available where the longer cycle is necessary.
Will Chrome updates become smaller?
Yes. Google says the faster schedule will be paired with a smaller scope per release.
That approach is important because simply doubling the number of releases without changing their size could create more disruption for users and developers. Smaller milestones should make it easier to identify which change caused a problem and potentially roll out fixes without waiting for a larger release cycle.
What should website owners do now?
Website owners do not need to make major changes solely because Chrome has moved to a two-week schedule. However, developers and businesses that rely on Chrome-specific functionality should tighten their testing and monitoring processes.
A practical approach is:
- Test important websites in Chrome Beta before Stable releases arrive.
- Monitor Chrome release notes for changes that could affect your website.
- Check critical JavaScript and CSS functionality after major Chrome updates.
- Monitor analytics and error reports for unexpected browser-related problems.
- Keep third-party libraries and frameworks updated to reduce compatibility issues.
For teams managing business-critical web applications, the shorter release cycle makes automated browser testing more valuable than relying entirely on manual checks.
Does this mean Chrome will update every two weeks forever?
Google has announced the two-week Stable cycle as its new release model beginning with Chrome 153. There is currently no indication from Google that this is a temporary experiment.
The move also fits a broader trend among browser makers toward faster release cycles as web standards, security threats and browser capabilities evolve more quickly.
Frequently Asked Questions
When did Chrome start its two-week update cycle?
Chrome's new two-week Stable release cycle began on September 8, 2026, with Chrome 153.
How often will Chrome Stable now receive major updates?
A new Chrome Stable milestone will arrive every two weeks instead of every four weeks.
Does Chrome's two-week schedule apply to Android and iPhone?
Yes. Google says the new release cycle applies to Chrome on desktop, Android and iOS.
What is the next Chrome version after 153?
Chrome 154 is scheduled to reach the Stable channel on September 22, 2026.