Chrome 153 for iOS 2026: What the App Store Build Ships
Chrome for iOS stable is 153.0.8010.24. Official one-liner; reviewers saw no new default UI. Beta mentioned keyboard deadlocks and Gemini fullscreen.
On 1 September 2026 the Chrome team posted Chrome Stable for iOS Update on the Chrome Releases blog. Piunikaweb checked the App Store on 2 September and recorded 153.0.8010.24 for iPhone and iPad — a bump from the 152.x line. This is a browser-channel story, not a meeting-product how-to.
The search query is Chrome 153 iOS 2026. Google’s public sentence is the usual stability and performance improvements. The 12 August iOS 152 note (152.0.7977.40) used the same formula. On a two-week train, many iOS stables ship without a UI headline.
What Google wrote vs what reviewers saw
The Chrome Releases title does not print a version. Piunikaweb labeled the store build 153.0.8010.24 and said an install on an iPhone 16 showed “no noteworthy changes.” Beta coverage mentioned occasional keyboard-input deadlocks and fullscreen behavior with the Gemini window. The stable store blurb does not itemize those fixes.
Store build
Piunikaweb: 153.0.8010.24. The previous public iOS stable note was Chrome Stable 152 (152.0.7977.40) on 12 August. Sources: Chrome Releases, Piunikaweb, September 2026.
Official one-liner
Stability and performance. No feature list and no CVE table on that iOS post. Security fixes usually ride the train; check Settings → About Chrome rather than the App Store hero art.
Points raised in beta
Keyboard deadlocks; Gemini floaty vs fullscreen/keyboard. Chromium iOS code also shows Gemini-floaty and keyboard-notification patches. A Canary CL is not the 153.0.8010.24 release note.
Version numbers, flags, two-week trains
Chrome now ships stable about every two weeks. Piunikaweb notes the pace is fast enough that ChromeOS has skipped version numbers to keep up. “Now on 153” mostly means the iOS app joined the desktop/Android train — not a new row of buttons on the iPhone.
| Source | Date | What it said |
|---|---|---|
| Chrome Releases | 2026-09-01 | Chrome Stable for iOS Update (title omits 153) |
| Piunikaweb | 2026-09-02 | 153.0.8010.24; no obvious UI |
| Chrome Releases (prior) | 2026-08-12 | iOS Stable 152.0.7977.40 |
- Should you flip the experimental bottom bar?
- That is an optional flag, not this stable package’s default pitch. Piunikaweb says users split into two camps, which helps explain a slow wide rollout.
- Are automatic updates enough?
- With App Store auto-update on, the build arrives over the next few days. Otherwise refresh the Updates tab. Managed phones may stay pinned by MDM.
What this has to do with a browser room
The Chrome iOS train patches the system browser shell. Short co-creation still means open a browser, share one page, finish the drawing. If you care whether phones join cleanly, read mobile browser notes. For another browser-format story, see JPEG XL in Firefox and Chrome. To open a room now, go to the rtcroom home page.
Still wondering?
Is 153 a new iOS Chrome UI?
The official note does not announce a new default UI. Piunikaweb saw no noteworthy change on an iPhone 16. The bottom-bar redesign is still described as a flag.
Why doesn’t the official blog say 153?
Recent Chrome Stable for iOS Update titles often omit the number; the version sits in the body. The 1 September scrape is mostly the title. Treat App Store / third-party checks as the build id.
Must I update today?
Browser trains usually carry security fixes. Unless a policy pins the version, tracking current stable is the sane default. This is not an rtcroom release.