PWA Not Installing? Fix a Missing Install Prompt

Description

Troubleshooting PWA not installing? Why 'Add to Home Screen' is missing

On iPhone and iPad there is no install prompt at all: the user adds the app from the Share menu. In Chrome and Edge, installation is offered only when the page is on HTTPS and links a manifest with a name, 192 and 512 pixel icons, a start URL and an app display mode. Chrome DevTools lists what is failing under Application, then Manifest.

Get a technical assessment Last updated 2 October 2026

Read the browser's own report first

Open the site in Chrome on a computer, open DevTools, and go to Application , then Manifest . Chrome's documentation describes what this pane shows: the manifest's identity and presentation fields, every icon it declares, and, when DevTools meets an error such as an icon that cannot be loaded, an Installability section that describes the fault. Edge has the same panel, and Firefox DevTools has an Application panel that displays the manifest.

That report settles most cases. The causes below are in order of likelihood, which is a judgement about how often each turns up and not a measured ranking. Each check comes from the browser maker's documentation, read on 2 October 2026.

Cause

Affects

Quick check

You are waiting for a prompt on iPhone or iPad

iOS, iPadOS

Share menu, then Add to Home Screen

The manifest is not linked or does not load

All

Application, then Manifest, is empty

A required manifest member is missing or wrong

Chrome, Edge, Samsung Internet

Compare the pane with the list below

An icon is missing, the wrong size or fails to load

Chrome, Edge

Installability section; open each icon URL

The page is not on HTTPS

Address bar

The browser, or an in-app browser, does not install

Firefox desktop, in-app browsers

Open the URL in Chrome or Safari

Already installed, or not enough engagement yet

Chrome

chrome://apps ; use the page for 30 seconds

Your own install button depends on an event that never fires

Safari, Firefox

Test the button in Chrome

1. iPhone and iPad have no install prompt

web.dev states it plainly: a browser prompt to install a PWA does not exist on iOS and iPadOS. MDN adds that the beforeinstallprompt technique is not supported on iOS.

Check. In Safari, follow Apple's own steps: tap Share, scroll to Add to Home Screen , turn on Open as Web App , tap Add. If Add to Home Screen is not in the list, Apple's guide says to scroll to the bottom, tap Edit Actions and add it. From iOS 16.4 the Share menu in Chrome, Edge and Firefox offers the same option; before 16.4 only Safari could install.

Fix. Nothing is broken. WebKit says that from iOS 26 there are no installability requirements in Safari: any site added to the Home Screen opens as a web app by default. Put a short instruction on the page for iOS visitors. More on iPhone behaviour is in what works in a PWA on iOS .

2. The manifest is not linked or does not load

Check. If the Manifest pane is empty, the page has no working <link rel="manifest"> in its <head> , or the file returns an error. Open the manifest URL directly; it should return JSON.

Fix. Link the manifest on every page, including the start URL. MDN notes one trap for staging sites and logged-in areas: if fetching the manifest needs credentials, the link must carry crossorigin="use-credentials" , even on the same origin.

3. A required manifest member is missing or wrong

Chrome's criteria, which MDN says Chromium-based browsers including Edge and Samsung Internet share, need:

name or short_name

icons with a 192 pixel and a 512 pixel icon

start_url

display set to fullscreen , standalone , minimal-ui or window-controls-overlay

prefer_related_applications absent or false

Check. Read each field in the Manifest pane. Two mistakes are easy to miss. Leaving out display gives the default, browser , which is not an installable mode in Chrome. Setting prefer_related_applications to true sends Android users to the Play Store listing instead.

Fix. A manifest that meets the list:

"name": "Example Store",

"short_name": "Store",

"start_url": "/",

"display": "standalone",

"icons": [

{ "src": "/icons/icon-192.png", "sizes": "192x192", "type": "image/png" },

{ "src": "/icons/icon-512.png", "sizes": "512x512", "type": "image/png" }

4. An icon is missing, the wrong size or fails to load

Check. The Icons section of the Manifest pane shows every icon it could load. A broken path appears in the Installability section. Open each icon URL in a tab and confirm the real pixel size.

Fix. Supply both sizes as real files at the paths the manifest gives.

5. The page is not on HTTPS

MDN: an installable PWA must be served over https , or from localhost or 127.0.0.1 during development. A staging site on plain http or a bare IP address will not qualify.

Check. Look at the address bar. Fix. Put a certificate on the staging domain.

6. The browser cannot install, or the page is inside another app

MDN records that Firefox on desktop does not install PWAs from a manifest. On Android, only Chrome on devices with Google Mobile Services and Samsung Internet on Samsung devices install a full WebAPK; other browsers add a shortcut. web.dev notes that many in-app browsers, such as those in Facebook, Instagram and Gmail, cannot install at all.

Check. Open the same URL directly in Chrome on Android. Google's help page gives the path: More, then "Install and create shortcut", then Install.

Fix. Show an "open in your browser" hint to visitors arriving from social apps.

7. Already installed, or not enough engagement

Chrome's first criterion is that the app is not already installed. Its second is engagement: the user has clicked or tapped the page at least once and has viewed it for at least 30 seconds.

Check. On a computer, look in chrome://apps and uninstall the app. Reload, click once, wait 30 seconds.

8. Your install button waits for an event that never fires

A custom button relies on beforeinstallprompt . MDN's compatibility data shows it in Chromium-based browsers only, not Safari or Firefox. web.dev adds that prompt() can be called once per event.

Check. If Chrome's menu offers installation but your button stays hidden, look under Application, then Service workers. Chrome's December 2023 post says menu installation no longer needs a service worker, but that the prompt logic still required one with a fetch handler at that time.

Fix. Register the listener early in page load, and keep written instructions as the fallback.

When it is not worth fixing

If nobody would open the site daily, installation adds little, and time is better spent on speed. If the site is not a PWA yet, start with converting a website to a PWA or the plain-language definition. Where installation matters to the business and the cause is still unclear, it is part of the PWA development work WavX takes on.

Frequently asked questions

Why is there no install prompt on iPhone?

Because iOS and iPadOS do not have one. As of October 2026 the user opens the Share menu and taps Add to Home Screen, and the beforeinstallprompt event that Chrome uses is not supported on iOS. Show a short instruction on the page instead of waiting for a prompt.

Does a PWA need a service worker to be installable?

Not in Chrome or Edge. Chrome removed the service worker requirement for installing from the menu in version 108 on mobile and 112 on desktop, and Microsoft&#x27;s documentation says Edge does not need one either. You still need a service worker for offline pages and push notifications.

The manifest looks right. Why does Chrome still not offer to install?

Check three things outside the manifest: the app is not already installed on that device, the page is on HTTPS, and you have tapped or clicked the page and kept it open for at least 30 seconds. Chrome waits for that engagement before it treats the page as installable.

Why does my install button work in Chrome but not in Safari or Firefox?

The button depends on the beforeinstallprompt event, which only Chromium-based browsers fire. Safari and Firefox do not support it. Hide the button where the event never arrives and show written instructions for that browser.

Sources

web.dev: What does it take to be installable? (Chrome install criteria) · read 2 October 2026

MDN: Making PWAs installable · read 2 October 2026

Chrome for Developers: Debug Progressive Web Apps (DevTools Application panel) · read 2 October 2026

Chrome for Developers: Revisiting Chrome&#x27;s installability criteria · read 2 October 2026

Microsoft Edge documentation: Get started developing a PWA · read 2 October 2026

web.dev Learn PWA: Installation · read 2 October 2026

web.dev Learn PWA: Progressive Web Apps (platform support and in-app browsers) · read 2 October 2026

web.dev: How to provide your own in-app install experience · read 2 October 2026

Apple iPhone User Guide: Turn a website into an app in Safari on iPhone · read 2 October 2026

WebKit: WebKit Features in Safari 26.0 (every site can be a web app on iOS and iPadOS) · read 2 October 2026

MDN: Web application manifest · read 2 October 2026

MDN: display manifest member · read 2 October 2026

MDN: beforeinstallprompt event (browser compatibility) · read 2 October 2026

Google Chrome Help: Use web apps · read 2 October 2026

Related

Progressive web app development

What works in a PWA on iOS

Progressive web apps: the guide

Build your own software — your way, your pricing.

WavX Solutions is here to create your own software in a fully custom way, built exactly how you work — with a pricing model that fits your business. Connect now and let&#x27;s build it.

Contact Now helpwavx@gmail.com