Skip to main content

How many PWAs are actually broken?

TL;DR · Short answer

Most of them, by at least one measure. Across 385 installable web apps loaded in a real browser on 12 August 2026: 235 install and have nothing in their offline cache. Of the 373 manifests we could read, 215 declare no maskable icon, 329 declare no id, and 331 declare no screenshots. 3 apps link to a manifest that no longer responds at all — those cannot be installed by anyone, and nothing in normal browsing reveals it. A second run on 5 November 2026 cut the network on every app in the catalogue and reloaded it; its results are in the November 2026 section below.

The numbers

Offline cache: 150 of 385 installable apps had stored something, 235 had nothing. Manifests: 373 readable of 386. Among those, 215 have no maskable icon (58%), 329 have no id (88%), 331 have no screenshots (89%), 36 have no icon reaching 512px (9.7%), and 32 declare shortcuts (8.6%).

A small but stubborn category: 3 apps declare a manifest URL that returns nothing. Their pages load fine. They look like ordinary websites. But no browser will ever offer to install them, and their authors have no way to notice unless someone tells them.

Why these particular defects survive

Each one is invisible from the developer's chair. The offline failure needs an installed app plus no connection. The missing maskable icon needs a physical Android device — emulators often use a square launcher that hides it. The missing id causes nothing at all until the day you change start_url, and then it orphans every installed user silently.

None of them produce an error. That is the common thread, and it is why the proportions are so high. A defect that announces itself gets fixed in an afternoon; a defect that waits for a specific state stays in production for years.

What this means if you run one

The id is the one to fix today, because it is the only one whose damage is permanent. Add "id": "/" to your manifest while it costs nothing. After you have already moved start_url, the users you orphaned cannot be recovered — the mechanism is here.

Then check offline properly: devtools → Application → Service Workers, tick Offline, reload. Thirty seconds, and it settles whether you are in the 39% or the 61%. For a URL you want read automatically, the checker opens it in a real browser and reports its manifest, its service worker and what the worker cached. It does not cut the network, so keep the airplane-mode test above for that step.

November 2026: we cut the network on the whole catalogue

On 5 November 2026 we repeated the measurement on every listing in the catalogue, 1,073 apps, and added a step the August run did not have: cutting the network. Each URL was opened in a headless Chromium. We waited up to six seconds for a service worker to register and activate, then counted Cache Storage entries. If a worker was active, we switched the browser offline, reloaded the listed URL, and recorded whether the browser displayed a page with at least 20 characters of text. Manifests were fetched separately over HTTP.

45 apps produced no browser reading and are left out of every browser percentage below: 28 navigated away while we were reading the page, and 17 returned a navigation or browser error (timeouts, domains that did not resolve, an expired certificate, an aborted request, a crashed or closed page). That leaves 1,028 apps that loaded. The manifest figures use all 1,073.

Of the 1,028 apps that loaded, **529 had an active service worker** (51.5%), **510 held at least one Cache Storage entry** (49.6%), and **324 displayed a page with the network cut** (31.5%). Among the 529 with an active worker, 324 is 61.2%. The other 205 showed an error or an almost empty page; for 147 of them the browser reported a network error on reload.

Cache entries and offline behaviour do not always agree. 121 apps held cache entries and did not display a page with the network cut, which a cache count alone cannot show. In the other direction, 4 apps displayed a page with no entries in the caches we read. As a sensitivity check, 110 apps that showed no cache in the first pass were opened again with a 20-second wait instead of six, and none of them changed result.

Manifests: **946 of 1,073 were readable** (88.2%). The other 127 are 83 pages with no manifest link in their HTML, and 44 that returned an HTTP error, did not respond, or served something that is not valid JSON. Among the 946, 922 declare a display mode of standalone, fullscreen or minimal-ui; 572 (60.5%) declare a maskable icon, 287 (30.3%) an id, 171 (18.1%) shortcuts, 142 (15.0%) at least one screenshot, 352 (37.2%) a language and 859 (90.8%) an icon of 512 px or more. 38 manifests (4.0%) declare all six: maskable icon, id, shortcuts, screenshot, language and a 512 px icon.

Measure, 5 November 2026CountShareOut of
Apps in the catalogue1,073
Loaded in the browser1,02895.8%1,073
Active service worker52951.5%1,028
At least one cache entry51049.6%1,028
Displayed a page with the network cut32431.5%1,028
Readable manifest94688.2%1,073

November 2026, by category

The table gives, per category, how many of the apps that loaded displayed a page with the network cut. Small categories move several points with one app, so read the order rather than the decimals.

CategoryOpened offlineLoadedShare
Utilities6013544.4%
Health & Fitness327542.7%
Food & Drink82040.0%
Development Tools389938.4%
Games & Entertainment4411937.0%
Education309332.3%
Shopping & Travel103132.3%
News & Reading113531.4%
Music & Audio134429.5%
Productivity2610325.2%
Social & Communication156323.8%
Photography52420.8%
Finance & Business2210820.4%
Design & Creative85016.0%
Video & Streaming2296.9%

What the November run does not see

It visits one URL per app, the one listed here, and it detects service-worker behaviour only. An app that registers its worker on another page, or that keeps its data in local storage, can work offline and still score zero. The reload test accepts any page with 20 or more characters of text, so a custom offline notice counts as a page displayed; 38 of the 324 displayed fewer than 60 characters.

It was also one run from one machine on one day, with a headless browser. The August figures (150 of 385 apps with something in their cache, on 12 August) come from a smaller catalogue and a different set of apps, so the two sets of numbers are two measurements, not a trend. The same goes for manifests: the 373 read in August and the 946 read in November are not the same list.

To repeat the offline step on one app, use the devtools test described above: tick Offline under Application, Service Workers, and reload. Related reading: PWA examples and their offline caches, the manifests we read in August and what installable does and does not mean for offline.

Frequently asked

How many PWAs in this directory open with the network cut?

324 of the 1,028 apps that loaded on 5 November 2026 (31.5%), and 61.2% of the 529 that had an active service worker. The test visits one URL per app and detects service-worker behaviour only, so an app that works offline by other means can score zero.

Does a cache mean an app opens offline?

Not in the 5 November 2026 run. 121 apps held cache entries and did not display a page with the network cut, and 4 displayed a page with no entries in the caches we read.

Where do these numbers come from?

From this directory. Every listed app is opened in a headless Chromium — service worker awaited, Cache Storage read and counted — and every manifest is fetched and parsed. The figures above are the state on 12 August 2026 across 385 installable apps and 373 readable manifests.

Is 58% without a maskable icon really that bad?

It is cosmetic rather than functional: the app works, it just sits in a white circle on Android instead of filling the adaptive shape. But it is the first thing a user sees on their home screen, next to native apps that do it correctly, and it takes one extra PNG to fix.

Also published on Medium. This page is the original.

Apps mentioned

Keep reading

One email a month. Only the apps worth your time.

What they do, what they don't, and whether they actually work offline — we check. No roundup of everything we listed, no affiliate links.

Double opt-in — nothing is sent until you confirm. Unsubscribe any time.
Looking for more apps that work offline?

1240+ Progressive Web Apps with current catalogue evidence — browse and install from your browser, no app store.

Browse the directory →