Chrome 155 is rolling out now, and the biggest changes are under the hood: it can open JPEG XL images, supports post-quantum encryption tools for web developers, and lets sites put digital IDs into your phone wallet. You don’t need to change any settings. Chrome updates itself, and you can check your version at chrome://settings/help.
Here’s the short version of what you need to know.
- Early stable build started reaching some Windows and Mac users on September 30, 2026.
- Desktop broad availability was expected on October 6, with Android following in the coming days.
- Mobile versions need Android 10 or iOS 18 and newer.
- Headline additions: JPEG XL decoding, post-quantum WebCrypto algorithms, and digital credential issuance.
Most of this is plumbing. You’ll notice it slowly, as websites start using it.
JPEG XL is back in Chrome, and it’s built to be safer
JPEG XL is a modern image format that can look as good as a JPEG at smaller file sizes. It also handles HDR, wide color, high bit depth, and animation. According to DigitBin, Chrome 155 decodes it with a memory-safe Rust decoder.
That last detail matters. Image decoders are a classic place for security bugs, and Rust makes a whole family of memory errors much harder to write.
It also supports progressive loading, so a photo appears blurry and sharpens as the rest arrives. On a slow connection, that feels faster than waiting for a blank box.
The catch: nothing changes until publishers actually convert their images to JPEG XL. Expect it to show up first on photo-heavy sites and in developer demos. Older browsers will still need fallback formats, so publishers can’t drop JPEG overnight.
Post-quantum tools arrive in WebCrypto
Chrome 155 adds new algorithms to the WebCrypto API, including ML-KEM and ML-DSA, plus ChaCha20-Poly1305 and X-Wing. The Chrome beta notes list them under web API changes.
In plain terms, these are encryption methods designed to hold up against future quantum computers. Developers can now use them directly in the browser.
Your own browsing won’t suddenly get safer. The benefit arrives site by site, as developers adopt the tools. If you want the bigger picture on why this matters, our explainer on Windows 11 post-quantum encryption covers what these algorithms actually protect against.
Digital IDs can now be issued straight to your wallet
The Digital Credentials API gained issuance support. Before this, it was mostly about showing a credential you already had. Now a university, bank, or agency can hand one to your phone wallet.
On Android, this works through Credential Manager. On desktop, Chrome uses the CTAP protocol so you can approve the transfer from your phone.
Picture getting your diploma as a wallet credential, straight from the school’s website. That’s the kind of use case Google is pointing at. It also means fewer paper forms and fewer scans of documents sitting in your email.
Smaller Chrome 155 changes worth knowing
Not everything is a headline. This table covers the other changes from the beta notes, and who is most likely to care.
| Change | What it does | Who notices |
|---|---|---|
| Module retry | Failed JavaScript module loads can be retried instead of cached as failures | Developers, and anyone on flaky Wi-Fi |
| Hidden iframe media | A new permission policy pauses audio and video in invisible iframes | Anyone annoyed by mystery sound from a tab |
| Window controls | Sites can maximize, minimize, and restore windows with extra permission | Web app users |
| CSS corner shorthand | Set radius and corner shape together for each corner | Web designers |
| Text modules | Import text files as strings with a simple import statement | Developers |
The hidden iframe change is the one regular users might feel. Media that plays from a frame you can’t even see is a common source of surprise noise.
Should you update Chrome 155 right now?
Yes, though you probably don’t have to do anything. Chrome checks for updates on its own, and a restart finishes the job. Browser releases also carry security fixes, so staying current is the safest habit.
Google shortened its stable release cycle from four weeks to two as of September 2026, according to Born City. That means smaller, more frequent updates. If you missed the last one, our look at the Chrome 154 HTTP warning shows how fast the browser is changing.
To update by hand, open the three-dot menu, go to Help, then About Google Chrome. It will download the latest version and ask you to relaunch.
Frequently Asked Questions
How do I get Chrome 155?
Open chrome://settings/help and let Chrome check for updates. Rollouts are staged, so it may take a few days to appear on your computer.
Does Chrome 155 support JPEG XL?
Yes. It can decode JPEG XL images, including HDR and animated ones. You’ll only see them on sites that actually publish that format.
Will post-quantum encryption protect my browsing automatically?
Not by itself. The new algorithms are tools for web developers, so protection depends on sites choosing to use them.
Which phones can run Chrome 155?
Android 10 or newer, and iOS 18 or newer. The iOS version was already in the App Store, with Android rolling out through Google Play.
The takeaway on Chrome 155
This is a quiet release with a long tail. Nothing here will change your day today, but JPEG XL and post-quantum support set up the next few years of the web. Update when Chrome asks, and if you build websites, JPEG XL is worth testing this month.
Leave a Reply