Skip to content

The reference for installable web apps.

157 entries and 60 compatibility datasets, checked against browser-compat-data and vendor release notes, in English and Chinese. Each support row links its source, and its confidence level is computed from the kind of source.

Support tables come from browser-compat-data and vendor documentation. The demo shows a capability on your own device. Lab pages record what a real device did, with the date, the OS build, and the raw data. The evidence layers page explains how the three relate.

Can I PWA?

All 60 datasets

Support for the capabilities that decide whether a web app ships, in Chrome, Edge, Firefox, Safari on macOS and iOS, Samsung Internet, and Android WebView. Each version is the first release with support; a range shows that support began as partial.

CapabilityChromeBlink · desktopEdgeBlink · desktopFirefoxGecko · desktopSafariWebKit · macOSSafariWebKit · iOSSamsung InternetBlink · AndroidWebViewBlink · Android
Install prompt44795.044
Web Push4217441616.44.0
Service workers40174411.111.34.040
Background Sync49795.0
Periodic Background Sync808013.0
Badging81811716.4
Web Share89→12881→937112.112.28.0
Share target898912.0
File System Access868629.0132
File handlers102102
Window Management10010019.0100
WebGPU113→144113→144141262625.0121
SupportedPartial supportBehind a flagNot supportedUnknown

Will it ship?Where does it work?Does it work on mine?

Browse the reference

Reference overview

Eight sections. An entry on a manifest member or API says what it does, what errors it throws, how each browser handles it, and which part of the specification defines it.

How this reference is kept accurate

Each row of a compatibility dataset covers one browser on one operating system and has exactly one of five statuses: yes, partial, flag, no, or unknown.

Support rows come from MDN browser-compat-data, vendor documentation and release notes, and W3C, WHATWG, and WICG specifications. StatCounter Global Stats browser market shares for September 2026 are used only by the by-country view.

Every entry shows a last-verified date, which moves only when the entry is re-checked against its sources. Entries older than 180 days are queued for re-verification, or after 90 days when their facts depend on store or platform policy. The publishing pipeline is scheduled to run every four hours.

latest content update
2026-10-25
reference entries
157
compatibility datasets
60
latest compatibility verification
2026-10-20