PWAStore.io
Experimental

The Web Install API

Two Chromium experiments are exploring a simpler way to install the current PWA—or another PWA—without sending users through a hidden browser menu.

Status last verified 29 July 2026

Do not treat either API as stable

The published navigator.install() origin trial covers Chrome and Edge 143–150 and exposes an earlier API shape. The newer <install> trial covers Chrome and Edge 148–153. Trials are time-limited, so always keep a normal installation or navigation fallback.

Two approaches

navigator.install()
An imperative JavaScript API for fully custom install experiences.
It returns a promise and must be called from a user action. The evolving proposal accepts a manifest URL and, when needed, a manifest ID.
<install>
A declarative element whose visible install control is rendered by the browser.
It needs very little JavaScript, supports fallback content, and offers a higher-trust browser-controlled interaction.

Trial shape versus evolving proposal

This distinction matters. The origin trial for navigator.install() exposes the earlier URL-based signature:

navigator.install(installUrl, manifestId);

The active explainer is replacing that design with a manifest-first dictionary:

const installApp = async () => {
  if (!("install" in navigator)) return;

  await navigator.install({
    manifest: "https://app.example/manifest.webmanifest",
    manifestId: "https://app.example/"
  });
};

The no-argument form targets the current page's linked manifest. For another app, the proposed dictionary points directly to its manifest. Do not ship one signature without checking the browser implementation you are targeting.

The HTML install element

Use installurl to target another app. When the browser does not support the element, its child content remains available as the fallback.

<install installurl="https://app.example/">
  <a href="https://app.example/">Open app</a>
</install>
Detect enhanced support with "HTMLInstallElement" in window. For local testing in Chrome or Edge 148+, enable about://flags/#web-app-install-element. The browser must be restarted after changing the flag.

What an integration must handle

Manifest identity

Use a stable manifest id. Cross-origin targets must provide enough information for the browser to identify the intended app.

Real user intent

Installation requires a user action and browser-controlled confirmation. Silent installation is not a goal.

Cross-origin permission

Installing a different origin is permission-gated. The installed app does not inherit permissions from the catalog.

Progressive fallback

Unsupported browsers still need a working route to the app and ordinary Add to Home Screen or Install App guidance.

Support at a glance

CapabilityPublished test windowFallback
navigator.install()Chrome and Edge 143–150 origin trialLink to the app or show device install steps
<install>Chrome and Edge 148–153 origin trialChild HTML inside the element
Safari and FirefoxNo support for these experimental entry pointsNormal browser installation or navigation
How PWAStore approaches it
PWAStore keeps a familiar install action and uses capability detection before attempting an experimental API.
Unsupported or failed attempts fall back to device-specific instructions. This guide documents the evolving platform; it does not silently change the runtime installation flow.

Primary sources

Looking for installation help?

Follow the simple guide for iPhone, Android, and desktop.

View install guide