← Back to Blog
Illustration of an app store listing being sorted into four separate policy categories

PWA Browser Support: What Each Browser Installs in 2026

What "PWA browser" actually means

Search results for "pwa browser" usually mean one of two things: which browsers can install a Progressive Web App, or whether you need a special browser to run one. You do not. A PWA is still a website, delivered over HTTPS, that a supporting browser can promote and install. The "PWA browser" is simply the browser that installed it and later launches it.

That last point matters more than it sounds. MDN's install guide is explicit: a PWA stays tied to the browser that installed it. The same site installed from Chrome and from Edge becomes two separate apps, and they do not share data. If you treat "install" as a single product event, your numbers will be wrong.

The engine decides more than the browser brand

Three engines sit underneath almost every PWA browser you will test:

  • Blink, used by Chrome, Edge, Samsung Internet, Opera, Brave, and most other Chromium browsers on Windows, macOS, Linux, ChromeOS, and Android.
  • WebKit, used by Safari on every Apple platform, and by every browser on iPhone and iPad. Chrome or Firefox on iOS is still WebKit in a different shell.
  • Gecko, used by Firefox on platforms other than iOS.

Feature support follows the engine and the OS, not the logo on the icon. An install button that works in Chrome on Android will not automatically work in Safari, and it will not work the same way in Chrome on iPhone.

PWA browser support in 2026: what each browser installs

Installation is available on modern desktop and mobile systems, but the path, the prompt, and the result are not the same. The table below is the practical matrix teams should design against. Details follow MDN's installability and installing guides.

PWA browser / OS

How the user installs

Browser promotion

beforeinstallprompt

What the install produces

Chrome on desktop

Address-bar install icon, or the browser menu to install the page as an app

Yes, when installability checks pass

Yes

An OS-integrated app window (Start menu, Dock, or a desktop entry, depending on the OS)

Edge on desktop

App available control, or install this site as an app

Yes, when checks pass

Yes

An OS-integrated app window

Chrome on Android with Google Mobile Services

Menu: Add to home screen, then Install (labels vary by version)

Yes, but Chrome rate-limits its own install UI

Yes

A WebAPK: a real launcher entry, app switcher entry, and a row in system settings

Samsung Internet on Samsung devices

Install icon in the URL bar, or add the page from the menu

Yes

Yes, in current Samsung Internet releases

A WebAPK on Samsung devices

Edge, Opera, Firefox, and Chrome without Google Mobile Services on Android

Menu: Add to home screen or Install

Little or no promotion

Usually no

A browser-badged home-screen shortcut that opens the site in that browser

Safari on iOS and iPadOS

Share, then Add to Home Screen

No

No

A Home Screen web app

Chrome, Edge, Firefox, and other browsers on iOS 16.4 and later

Share menu, then Add to Home Screen

No

No

A Home Screen web app that still runs on WebKit

Safari on macOS 14 (Sonoma, Safari 17) and later

File, then Add to Dock, or Share, then Add to Dock

No

No

A Dock web app. Safari can do this for sites with or without a manifest

Firefox on desktop

No manifest-based PWA install in the Chromium sense; MDN still describes a PWA extension for Firefox

No

No

Do not plan a Chrome-like install prompt here

Two Android facts are easy to miss and expensive to discover in production:

  1. Only some Android installs are WebAPKs. Per MDN, the browsers that install PWAs as WebAPKs are Chrome on devices with Google Mobile Services, and Samsung Internet on Samsung devices. Everything else on Android, including Chrome on devices without GMS, tends to add a badged shortcut.
  2. A shortcut is not a WebAPK. A WebAPK shows up like an app. A badged shortcut still belongs to the browser. If your ads, onboarding, or analytics assume every Android install looks like a store-installed app, a large slice of real users will not match that picture.

On Apple platforms the rules flipped historically and then settled into a different shape. Before iOS 16.4, only Safari could add a PWA to the Home Screen. From iOS 16.4 onward, other browsers can offer Add to Home Screen from the Share menu, but the installed app still runs on WebKit. Before macOS 14, the desktop pattern was the opposite of early iOS: other browsers could install, Safari could not. From Safari 17 on macOS 14, Add to Dock is the Safari path.

Promotion is not the same as installation

Chrome and Edge will also let a user install almost any page from a menu, even when the site fails the checks that unlock promotion. Those checks decide whether the address-bar icon appears and whether beforeinstallprompt fires. They are not a gate that makes installation impossible.

If you need the icon and the prompt, start with a valid web app manifest and a secure context, then debug in DevTools under Application, Manifest. Chrome's own installability errors are more reliable than guessing from a user-agent string.

For Chrome-specific timing and cases where the prompt is not showing, use the dedicated guide on Chrome install prompt optimization rather than copying that material into this article.

What you can automate, and what you have to explain

beforeinstallprompt is the only widely used way for your page to trigger a native install dialog. It is a Chromium feature. Safari on iOS and macOS, and Firefox, do not fire it. On those PWA browsers, the install path is always user-initiated, so the product UI has to explain the menu path instead of rendering a button that does nothing.

A practical pattern:

  • Listen for beforeinstallprompt and show a custom install button only after it fires.
  • On Safari and Firefox, replace that button with short, platform-specific instructions: Share, then Add to Home Screen on iPhone; File, then Add to Dock on recent Macs.
  • Never hide the fallback behind a generic "Install" control that only works in Chrome.

The mechanics of the prompt itself, including iOS and Android differences, are covered in Add to Home Screen prompt.

Why the PWA browser you ship against changes user acquisition

If you run ads or an install funnel to a PWA, the browser mix is part of the offer, not a downstream detail.

  • The event is not one event. A WebAPK install, a badged Android shortcut, a Safari Home Screen add, and a desktop Dock app are four different outcomes. Folding them into one "PWA install" KPI hides where the funnel actually breaks. See how to measure Add to Home Screen conversions and PWA funnel optimization.
  • Installs do not travel across browsers. A Chrome install will not appear in Edge, and the two copies will not share login or local data.
  • In-app browsers are a separate hole. Many social and messenger in-app browsers will not promote or complete a PWA install. If a large share of paid clicks opens there, send people into a system browser or expect the install CTA to fail.
  • Store packaging is a different path. If you need a Play Store listing, a TWA or APK wrapper is not the same PWA with a different button. Compare PWA vs TWA and PWA vs APK, or start from a PWA maker if you do not want to wire the install surface yourself.

A practical checklist

  1. Ship a manifest, icons, and a sensible display mode, and confirm the file is actually linked. Details live in PWA manifest requirements.
  2. Test at least five surfaces: Chrome desktop, Chrome on an Android device with Google Mobile Services, one Android browser that only creates a shortcut, Safari on iOS, and Safari on a recent macOS.
  3. Show a custom install button only where beforeinstallprompt fires. Everywhere else, show instructions.
  4. Record the installing browser and OS with the conversion, not only a generic "installed" flag.
  5. Do not promise a single install experience in ad creative if a large share of traffic is iOS or an in-app browser.
  6. If production behavior surprises you, check serving and service-worker updates in the PWA deployment guide before rewriting the install UI.

Common mistakes

  • Building the entire install UX around Chrome's address-bar icon, then discovering Safari traffic cannot press it.
  • Treating every Android "Add to home screen" as a WebAPK.
  • Assuming Chrome on iPhone behaves like Chrome on Android.
  • Counting every home-screen add as a store-equivalent app install in UA reports.
  • Skipping in-app browsers in QA, even when they drive a large share of paid sessions.

FAQ

What is a PWA browser?

A PWA browser is the browser that installs and later hosts a Progressive Web App. There is no separate browser you have to download just to use PWAs. Chrome, Edge, Safari, Samsung Internet, and Firefox all participate, but they do not install the same result or offer the same prompt.

Which browsers support PWA install in 2026?

Chrome and Edge on desktop, Chrome on Android with Google Mobile Services, and Samsung Internet on Samsung devices offer the strongest install and promotion paths, including beforeinstallprompt where the criteria pass. Safari installs via Add to Home Screen on iOS and Add to Dock on macOS 14 and later, with no install prompt. Other iOS browsers can add to the Home Screen from iOS 16.4, still on WebKit. Firefox does not offer a manifest-based, Chromium-style install prompt.

Does Firefox support PWA?

Firefox supports core web platform pieces used by PWAs, such as service workers, but it does not promote manifest-based installation the way Chrome does, and it does not fire beforeinstallprompt. MDN still describes Firefox as requiring a PWA extension for installation. Do not design your primary install CTA around Firefox.

Can I install a PWA in Chrome on iPhone?

From iOS 16.4 onward, Chrome and other iOS browsers can add a site to the Home Screen from the Share menu. The result is still a Home Screen web app running on WebKit, not a Chromium WebAPK. There is no beforeinstallprompt on iOS.

Why does the install button not show in Safari?

Safari never fires beforeinstallprompt, so a custom install button that depends on that event will never appear. The user path is Share, then Add to Home Screen on iOS, or Add to Dock on recent macOS. Explain that path in the product; do not wait for a prompt that will not come.

Is a home-screen shortcut the same as a WebAPK?

No. A WebAPK, created by Chrome on Android with Google Mobile Services or by Samsung Internet on Samsung devices, is a signed package with a real launcher and settings entry. A browser-badged shortcut is closer to a home-screen bookmark that still opens through that browser. Measure and QA them separately.

ROIBest

Build your next growth engine with ROIBest

Talk to our team about a stable, high-converting Android PWA solution.