Chrome 157 is scheduled to reach stable on November 3, 2026, and it will reach Beta on October 14. The headline change for everyday users is a new <install> element that lets websites offer to install themselves as apps.
Here’s the short version before we get into what each change means for you.
- Beta: October 14, 2026
- Stable release: November 3, 2026 (dates can still shift)
- Affects Chrome on desktop and Android, with a few Android-only additions
- Biggest user-facing change: the
<install>element andnavigator.install() - Free update; Chrome installs it automatically
These details come from the Chrome Platform Status release notes, which are still marked as a preview. Treat the dates as planned, not final.
Why the Chrome 157 release date matters now
Google moved Chrome to a two-week release cycle in September, so new versions land fast. If you missed how that works, our guide to Chrome’s two-week release cycle covers it.
Each Beta ships roughly three weeks before its stable release, according to Google’s Chrome two-week release post. That gives you time to test your site, or to spot problems before the update reaches you.
If you read our earlier piece on the Chrome 156 release date and features, think of 157 as the next step in the same fast rhythm.
A new install button for web apps
The most visible addition is the <install> element, paired with a navigator.install() API. Sites can use them to prompt you to install a web app from a manifest URL.
Today, installing a web app often means hunting through Chrome’s menu. A built-in button on the page makes that much easier to find.
Admins can control this through an enterprise policy and Permissions Policy, so companies can still lock it down if they want to.
Faster Back button and tighter security
Pages with active WebSockets can now enter the back/forward cache. The connection is closed when the page goes into the cache, so the page can restore quickly when you press Back.
Admins who prefer the old behavior can use the BackForwardCacheForWebSocketsAllowed policy.
On security, Background Fetch now enforces CORS. That puts it under the same checks as a regular fetch request, which closes a gap developers might otherwise overlook.
What changes for web designers and developers
Chrome 157 also brings several CSS updates. The list below covers the ones most likely to show up in real projects.
- New
cornershorthand properties set bothborder-radiusandcorner-shapeper corner. AccentColorandAccentColorTextnow reflect an element’saccent-colorvalue.text-overflowaccepts a custom string value.object-fitandobject-positionnow apply to SVG documents in<object>and<embed>.
None of these will change how you browse. They give designers more control without extra workarounds.
There’s also an HTML-in-canvas feature, a Sanitizer API option called javascriptURLs, and the Language Detector API arriving on Chrome for Android.
Chrome 157 changes at a glance
| Change | What it does | Who notices it |
|---|---|---|
<install> element |
Lets a site prompt you to install a web app from a manifest URL | Anyone who uses web apps |
corner shorthand |
Sets border-radius and corner-shape per corner in one line | Web designers |
| WebSocket back/forward cache | Pages with active WebSockets can now be cached; the connection closes on entry | Anyone who hits Back a lot |
| Background Fetch CORS | Background Fetch now follows the same CORS checks as regular fetch | Developers, security teams |
If you only care about browsing, the install element and the Back button change are the two to remember. Developers should also read the full release notes before November 3.
How to try Chrome 157 before everyone else
You don’t have to wait for November 3. Once Beta lands on October 14, you can install the Chrome Beta channel next to your normal browser.
It runs separately, so your daily browser stays untouched. Beta builds can be rough, so don’t make it your only browser, and keep an eye on sites that rely on WebSockets or Background Fetch.
Developers can also test the Chrome 157 Dev channel today. Checking your site now is cheaper than debugging a user complaint after stable rolls out.
Frequently Asked Questions
When does Chrome 157 come out?
Chrome Platform Status lists the stable release as November 3, 2026, with Beta on October 14. Those are planned dates and may change.
Do I need to update Chrome manually?
No. Chrome updates itself in the background. You can check by opening Settings, then About Chrome.
Will the install element force apps onto my computer?
No. It only lets a site ask you to install a web app. You still choose whether to accept, and admins can disable it with policy.
Why do Chrome versions arrive so quickly now?
Google switched to a two-week cycle starting in September 2026. Extended Stable stays on an eight-week cycle.
Chrome 157 is a modest release for most people, and that’s fine. The install button is the one feature you may actually use, so watch for it on sites you open daily. If you build websites, try the Beta on October 14 and test your back/forward behavior, especially if your pages use WebSockets.
Leave a Reply