Chrome 156 is in beta now and is scheduled to reach the stable channel on October 20, 2026, according to the Chrome Status release notes. Most of what is new sits under the hood, so you probably won’t notice much on day one. Web developers get a longer list of changes to look at.
Here are the quick facts before we get into the details.
- Beta started on September 30, 2026, per the Chrome developer blog.
- Stable release is scheduled for October 20, 2026.
- New IndexedDB data now uses a SQLite backend.
- CSS gets a
random()function and a few new layout tools. - Fenced frames are stubbed out and heading for removal.
That is the whole release in five lines. The rest of this post explains what each item means for you.
When will the Chrome 156 stable release reach you?
The date is October 20, 2026. Chrome now ships a new version roughly every two weeks, which we covered in our guide to the two-week release cycle. Rollouts are staged, so you may see the Chrome update a few days after the official date.
To check early, open the three-dot menu, go to Help, then About Google Chrome. Chrome checks for the update and installs it. A relaunch finishes the job.
If you want a look at what the previous version brought, see our post on Chrome 155 and JPEG XL.
Chrome 156 developer features at a glance
Developers get the biggest share of this Chrome beta. The table below sums up the main additions and what each one does.
| Feature | What it does |
|---|---|
| Module retries | Failed module loads are no longer cached, so calling import() again can succeed after a network drop. |
| WebTransport headers | Lets you send custom HTTP headers during the handshake and read the server’s response headers. |
| WebRTC diagnostic logging | Authorized apps can collect call diagnostics for debugging, and share them with Chrome’s team if the user agrees. |
| WebGPU depth modifiers | frag_depth accepts less or greater, which can enable early-Z optimizations. |
| Compression dictionaries | Link tags now use the correct request settings and respect crossorigin and referrer. |
The module retry fix is the one most people will feel. On a flaky mobile connection, one failed script load used to stick until a full reload.
New CSS tools: random() and scroll control
Chrome 156 adds several CSS features that designers will want to try. The headline one is a random() function that returns a number within a range you set. An optional key controls whether the value is shared across elements and properties.
Next to that, here is what else lands in CSS.
text-decoration-insetmoves underlines and strike-throughs in or out from the text edges.overflow: scroll cliplets one axis scroll while the other clips, soposition: stickyworks per axis.scroll-snap-type: pairsnaps to the same element on both axes.- A new pseudo-class matches the link or button that started a navigation.
@propertydescriptors are now optional.
None of these change how existing sites look. They just give front-end teams cleaner options that used to need JavaScript.
Why IndexedDB moving to SQLite matters
New IndexedDB data stores in Chrome 156 use a SQLite backend instead of LevelDB and flat files. The web API itself stays the same, so sites keep working without changes.
Existing LevelDB data is not migrated yet. That means older stores keep their old format for now, and the full switch will come in a later release.
For you as a user, the likely payoff is steadier performance for web apps that store data offline. Treat that as a hope, not a promise, until real-world testing shows results.
What Chrome 156 removes or retires
Two things are on their way out. Chrome 156 turns the fenced frame element and window.fence into no-ops, and Chrome 157 starts a controlled rollout of removing the element.
IT admins should also note that the LocalNetworkAccessRestrictionsTemporaryOptOut enterprise policy is gone. Earlier releases already split the local network permission into local-network and loopback-network, so check any managed setups that relied on the opt-out.
Frequently Asked Questions
When does Chrome 156 come out?
The stable release is scheduled for October 20, 2026. The beta has been available since September 30.
How do I update to Chrome 156?
Open Chrome’s menu, choose Help, then About Google Chrome. It downloads the update on its own, and you relaunch to finish.
Will Chrome 156 delete my saved site data?
No. Existing LevelDB data is not migrated yet, and only new IndexedDB stores use SQLite.
Is Chrome 156 a big update for regular users?
Not really. Most changes target developers and admins, so the visible difference on your screen will be small.
Our take on this Chrome update
This is a quiet release, and that is fine. Install it when it arrives and move on. If you build websites, though, test the new IndexedDB backend and the module retry behavior early, because those are the changes most likely to touch real projects.
Leave a Reply