Do PWAs actually work offline?
Some do, most do not. A browser offers to install a PWA based on its manifest, not on whether a service worker caches anything useful. Of 385 installable web apps we loaded on 12 August 2026, 150 had cached something for offline use and 235 had nothing cached. Caching happens on the first online visit, so open the app once with a connection. To know for sure, install it, turn on airplane mode and open it.
Why installable does not mean offline
Chrome's installability check asks for a manifest, icons and a display mode. It does not ask whether a service worker stores anything: since version 108 on mobile and 112 on desktop it does not even require one to install from the menu (Chrome's documentation, read on 14 November 2026). A worker that registers, activates, and caches nothing changes nothing for installation — and produces an app that installs perfectly then opens blank.
That gap is the whole reason the two numbers differ. Of the 386 apps we measured, 385 are installable and only 150 had anything in their offline cache. Nothing in the install prompt distinguishes them, which is why users learn the difference the hard way.
The three degrees of offline
**The shell only.** The app frame appears — header, navigation, maybe a spinner — and the content never arrives, because the API is excluded from caching. Common, reasonable as a default, and disastrous for anything used in the field. We measured one grocery-list app whose author built it to tick items off in a supermarket aisle; the shell cached, the list did not.
**Shell plus data.** The app opens with your last known content. This is what most people mean by offline, and it needs a deliberate caching strategy for GET responses, not just the app files.
**Full local-first.** The app writes offline and reconciles later. This is the hardest, because it is no longer a caching problem but a merge problem — two people editing the same thing with no connection between them.
How to know before you rely on it
Install the app, turn on airplane mode, and open it. That is the only test that matters and it takes fifteen seconds. Everything else — audits, badges, claims in a listing — is a proxy for this.
A directory listing only carries an offline claim when the current record contains supporting evidence. Because app behaviour changes, rerun the reproducible test before relying on an older result. You can have the same run on your own app.
Frequently asked
No. If the service worker has cached the app, it will load offline in a normal browser tab too. Installing changes the window and the launch icon, not the caching. What installing does change is expectation: people assume an icon on their home screen behaves like a native app.
Because caching happens on first visit. Someone who installed the app and never opened it while online has an empty cache. It is the single most common reason people conclude offline mode is broken when it is not.
A listing only carries an offline claim when its current record contains supporting evidence; because apps change, rerun the test before relying on an older result.
No. If the API is excluded from caching, the frame appears but the content never arrives; offline use with your data needs a deliberate caching strategy for GET responses.
Apps mentioned
Keep reading
1240+ Progressive Web Apps with current catalogue evidence — browse and install from your browser, no app store.
Browse the directory →