Chrome has started its two-week stable-release cadence with version 153. Google announced the schedule change in March, and September 8 is the first stable release under it. The change applies to desktop, Android, and iOS, so Android is not a separate or delayed track.
That does not mean every Android phone receives a visible new feature every other Tuesday. A Chrome milestone can contain fixes, platform work, security changes, and web capabilities that are more noticeable to sites and developers than to a person opening tabs on a phone. The useful change is simpler: the stable channel now has a shorter path for shipping completed work.
What changes in practice on Android
Before this switch, Chrome shipped a new stable milestone every four weeks. Google says stable and beta releases now arrive every two weeks, while Dev and Canary keep their existing cadence. The company also says the smaller scope of each release is intended to make post-release debugging less disruptive.
For Android users, faster milestones are not a reason to chase every version number. Chrome has had weekly security updates since 2023, according to Google’s release note. The two-week change is about the feature and stability train, not a promise that urgent security fixes only arrive twice a month.
The practical consequence is that a bug fix or finished browser feature may reach stable Chrome in a smaller release window. Availability can still vary: Play Store delivery, device compatibility, enterprise policies, and server-side rollouts can all mean that two phones show different behavior on the same day.
How to check your Chrome version safely
- Open Chrome on your Android phone.
- Tap the three-dot menu, then open Settings.
- Scroll to About Chrome to view the installed version.
- Open the official Chrome page on Google Play and use Update if it is offered.
- If an announced feature is absent after updating, wait for the rollout rather than installing an APK from an unofficial mirror. A newer version is not proof that every server-controlled feature is enabled.
Why the schedule matters
Two-week milestones reduce the time between stable releases, but they also make version numbers less useful as a shortcut for support advice. When troubleshooting Chrome, record the full version, the device model, Android version, and whether the issue reproduces in Incognito. That is more actionable than saying only that Chrome is “up to date.”
The change matters most for people who follow web features, browser bugs, and Android app compatibility. It is less dramatic for ordinary browsing: automatic updates remain the sensible default, and a stable channel should still be treated as stable rather than as a public test build.
For a separate Android-side check on Gemini features that can use page context in Chrome, see our Gemini in Chrome privacy checklist. The same rule applies here: a browser update can deliver the code, while a feature rollout determines when the interface actually appears.
In brief
- Chrome 153 begins a two-week stable and beta release schedule on Android, desktop, and iOS.
- Weekly security updates remain a separate part of Chrome’s release process.
- Check Chrome through Settings and Google Play, but do not use unofficial APK mirrors to force a rollout.
Sources
- Chrome for Developers: Get features faster with Chrome’s two-week release cycle, published March 3, 2026 and checked September 8, 2026.
- 9to5Google: Google Chrome starts two-week release cycle with version 153, published September 8, 2026.
- Android Authority: Google puts Chrome updates on the fast track with its newest release, published September 8, 2026.