instantpwa
Help centre

Answer

What are the requirements for the Chrome install prompt?

Short answer

Chrome fires beforeinstallprompt when the site is served over HTTPS, links a valid manifest with name, start_url and 192px + 512px icons, registers a service worker with a fetch handler, and passes a user-engagement heuristic (typically one interaction and ~30 seconds of use). Any failing criterion silently blocks the prompt.

By InstantPWA engineering·Reviewed July 7, 2026

The technical checklist

HTTPS. Manifest with name (or short_name), start_url, display "standalone" or "fullscreen", icons at 192px and 512px, background_color and theme_color. A registered service worker whose fetch handler responds to at least the start_url.

The engagement heuristic

Chrome requires a click or tap on the page and, historically, ~30 seconds of active use. This is why beforeinstallprompt often fires late — not on page load.

The suppression rules

If the user dismisses twice, Chrome backs off for 90 days. Testing tip: use a fresh incognito window per attempt.

Sources

Related
Why is my PWA install prompt not showing?
Chrome shows the install prompt only when the site passes strict installability criteria: HTTPS, a valid manifest with name, icons and start_url, a registered service worker with a fetch handler, and the user has not previously dismissed the prompt. Any one of these missing is enough to block the prompt entirely.
What is a PWA?
A PWA (Progressive Web App) is a regular website that meets three technical criteria — HTTPS, a Web App Manifest and a service worker — so browsers let visitors install it on their home screen. Once installed, it launches like a native app, works offline and can send push notifications.
Can PWAs accept payments?
Yes. A PWA can accept payments through any standard web checkout — Stripe, PayPal, Adyen — and can also use the native Payment Request API to surface Apple Pay on iOS 16.4+ and Google Pay on Android. There is no App Store 30% cut because payments run through the web, not through a native store SDK.
Do PWAs support background sync?
Partially. Chromium browsers (Chrome, Edge, Android WebView, Samsung Internet) support the Background Sync API for retrying failed requests, and Periodic Background Sync for scheduled updates. iOS Safari and Firefox do not support either. Fall back to Push notifications for cross-platform re-engagement.
PWA vs hybrid app — what is the difference?
A PWA is a website users install from the browser — no store, no shell, no native code. A hybrid app (Ionic + Capacitor, Cordova, older React Native WebView apps) wraps the same web code in a native binary submitted to the App Store and Play Store. PWAs are cheaper and faster to ship. Hybrid apps unlock store distribution and deeper hardware APIs.