Home / Blog / Chrome 158 Ships the Web Install API
Browsers
Chrome 158 Ships the Web Install API, No More Guessing at beforeinstallprompt
Stable on November 17, 2026, Chrome 158 turns app installation into a standards-track primitive: a one-line navigator.install() call or a declarative <install> element, both able to install a different site's app from your own page.
Chrome 158 reaches stable on November 17, 2026, carrying the Web Install API out of origin trial and onto every desktop and Android install. For as long as PWAs have existed, getting a user to actually install one meant intercepting the browser's own beforeinstallprompt event, stashing it, and hoping your custom "Add to Home Screen" button fired at the right moment, a pattern every web developer has implemented and every web developer has quietly hated. Chrome 158 replaces that dance with a direct call: navigator.install(), or, if you'd rather skip JavaScript entirely, a new declarative <install> element that renders its own trusted install button.
The timing lines up with how teams actually ship software: a startup validating a product doesn't want app-store review cycles standing between a working build and real users. Standards-track installability is exactly the kind of platform shift worth factoring into scope before you pick a tech stack, and it's the sort of decision an experienced MVP development engagement is built to weigh against native-app alternatives early, rather than after a review-queue delay has already cost momentum.
What actually ships in Chrome 158
Two install paths land together, both gated behind a valid web app manifest:
navigator.install(): a promise-based JavaScript call that requests installation of a web app. It accepts an optional manifest URL and manifestId, which means a site can prompt installation of an app that lives on a different origin, something beforeinstallprompt never allowed.
The <install> element: a declarative, browser-rendered button that needs no script at all. Drop it in markup with a manifest attribute and Chrome handles the trust UI itself.
Both run through the same permission surface: the browser always shows its own confirmation UI before anything installs. "The site can only ask," as Chrome's own release notes put it: users still decide. Enterprises get explicit knobs too, through the WebAppInstallByUserEnabled policy and a web-app-installation permissions policy that can scope which origins are allowed to trigger cross-origin installs at all.
What this means for developers
If you've shipped a custom "Install app" button before, the migration is mostly subtraction:
drop the beforeinstallprompt listener and the event-stashing state machine, then feature-detect navigator.install instead and call it directly on a user gesture;
decide whether you even need JavaScript for this control; the <install> element covers the common case of "install this app" with zero script and better default accessibility semantics;
if you run a directory, marketplace, or companion site, the cross-origin install capability is new ground, so test the manifest-URL and manifestId parameters against the actual target app's manifest before relying on them in production, since a mismatched ID will silently fail to resolve to an existing install;
re-test your install funnel on Android specifically; that's where most users will encounter the new browser-rendered button first.
None of this requires a rewrite. It's a smaller, more honest API surface for a thing every installable web app already needed to do, which is also why it's worth revisiting the install flow as part of any new build rather than bolting it on after launch.
When does this ship / timeline
Chrome 158 is scheduled for stable release on November 17, 2026, per Chrome's own Platform Status release notes; the beta channel carrying the same build reached desktop and Android on November 12, 2026. Both the Web Install API and the <install> element launch together in this release, having moved through origin trial earlier in the year — Chrome is the only browser shipping either today, so cross-browser availability (Firefox, Safari) is not yet confirmed and is worth checking before depending on the feature for a non-Chromium audience.