Chrome 158 is already reaching some people. Google pushed early stable builds to Windows on November 4, and the full stable release is listed for November 17, according to Chrome Platform Status.
Here’s what you need to know before the update lands on your own machine.
- Early stable: version 158.0.8127.18/.19 on Windows since November 4, with Mac “coming shortly.”
- Full stable date: November 17, 2026.
- Biggest user-facing change: a new Web Install API for web apps.
- Cost: free, and it installs itself through the normal Chrome update.
The early release goes to only a small share of users first. If you don’t see it yet, that’s normal.
Chrome 158 release date: early stable now, everyone else on November 17
Google’s Chrome Releases blog confirmed the early stable update on November 4. Windows got it first, and Mac builds were listed as coming shortly.
The wider Chrome stable release follows on November 17. Most people never need to do anything, because Chrome updates itself in the background and asks you to relaunch.
If you read our rundown of the Chrome 157 update and its security fixes, this is the next step in the same four-week cycle.
The Web Install API could change how sites ask you to install apps
The headline addition is the HTML <install> element and the navigator.install() call. Together they make up the Web Install API, which lets a site prompt you to install a web app, including one hosted on a different origin.
For you, that should mean a clearer install button inside the page rather than hunting through Chrome’s menu. For site owners, it’s a cleaner way to turn a website into an app on your desktop.
Admins get control too. The WebAppInstallByUserEnabled policy and a web-app-installation permissions policy decide whether installs are allowed. If you manage work laptops, check those settings before the rollout reaches everyone.
It’s worth watching how sites use it. Any prompt that can appear on a page deserves a little suspicion until you know the site.
Smaller Chrome 158 changes that matter to developers
Most of the rest of this release is aimed at people who build for the web. This table shows the changes listed in the Chrome 158 release notes and who they affect.
| Change | What it does | Who notices |
|---|---|---|
| Web Install API | Lets a site prompt installs of web apps, including cross-origin ones | Everyday users, IT admins |
:playing, :paused, :muted and more |
New CSS pseudo-classes that style audio and video by playback state | Front-end developers |
::highlight(*) |
One selector that styles every custom text highlight | Front-end developers |
| WebHID on Android 17 | Lets web apps talk to HID devices on Android 17 and later | Developers building device tools |
| WebTransport additions | New draining promise and reliability hints for connections |
Networking developers |
None of these will change how a normal page looks on day one. They give developers cleaner tools, which tends to show up as smoother sites over the following months.
WebHID support on Android 17 is the one to note if you build hardware-related web tools. WebView isn’t supported, so apps embedding a web view won’t get it.
How to get the Chrome 158 update today
You can check for it manually instead of waiting for the staged rollout. Open the three-dot menu, go to Help, then About Google Chrome. Chrome checks for the Chrome update and downloads it if your device is in the first group.
If it says you’re up to date but you’re still on 157, the release probably hasn’t reached you yet. Check again after November 17. Relaunch the browser once the download finishes, or the new version won’t load.
Edge users on Windows get their own speed changes on a different schedule. We covered those in our guide to Edge’s faster app launch on Windows 11.
Frequently Asked Questions
When is the Chrome 158 stable release?
Chrome Platform Status lists November 17, 2026 for the full stable release. An early stable build reached some Windows users on November 4.
Why don’t I see Chrome 158 yet?
Early stable goes to a small percentage of users first. Google rolls the update out in stages, so your turn may simply not have come.
Is Chrome 158 safe to install?
Yes, it’s the normal stable channel, and Chrome updates are how Google ships its fixes. Install it when Chrome offers it rather than using a download from a third-party site.
What is the Web Install API?
It’s a new way for a website to prompt you to install a web app using the <install> element or navigator.install(). Admins can control it with a Chrome policy.
Does Chrome 158 work on Mac and Android?
Mac builds were listed as coming shortly after Windows. The WebHID change specifically applies to Android 17 and later.
Our take: let it update on its own
Chrome 158 isn’t a release that needs you to act. Let the browser update itself, relaunch when it asks, and keep an eye out for the new install prompts. If you run work devices, the one thing worth doing now is reviewing your web app install policy before November 17.
Leave a Reply