Definition
PWA install criteria
Chromium's PWA install criteria require: the site served over HTTPS; a linked Web App Manifest with at least a name (or short_name), a 192x192 and 512x512 icon, a start_url, and a display value of standalone, fullscreen, minimal-ui or a display_override entry; and a registered service worker with a fetch event handler, even a minimal pass-through one.
A missing fetch handler used to be strictly required historically as evidence of offline capability; Chromium has since relaxed some specifics over browser versions, so the current authoritative checklist is always the one in the Chrome for Developers installability documentation rather than any fixed historical list: https://developer.chrome.com/docs/lighthouse/pwa/installable-manifest/.
Meeting the criteria makes a site eligible for beforeinstallprompt and the address-bar install icon, but does not itself install anything — the user (or your own prompt() call in response to a gesture) still has to complete the install action.
Sites that meet only some criteria may still be "addable to home screen" as a plain bookmark shortcut without full PWA behaviour (no standalone window, no WebAPK on Android), which is a common source of "why doesn't my install look right" confusion.
Lighthouse's PWA audit category checks most of these criteria automatically and lists exactly which one is failing, making it the fastest way to debug an install prompt that never appears.