Help centre
Answer
What are the storage limits for a PWA?
Short answer
A PWA typically gets 60% of the device disk space on Chrome and Edge (up to hundreds of GB), 20% of total quota on Firefox, and around 1 GB on Safari. Cache Storage, IndexedDB and OPFS share the same quota. Browsers evict least-recently-used origins under pressure unless the site requests persistent storage.
By InstantPWA engineering·Reviewed July 7, 2026
Per-browser limits
Chrome/Edge: 60% of disk. Firefox: 20% of free space with a 10 GB per-group cap. Safari 17+: ~1 GB per origin with promptless eviction after 7 days of inactivity.
Check the current quota
Call navigator.storage.estimate() — it returns { quota, usage } in bytes.
Request persistent storage
navigator.storage.persist() returns true if the browser grants it. Persistent storage is not evicted under pressure and is only cleared when the user explicitly deletes site data.
Related
What is a PWA?
A PWA (Progressive Web App) is a regular website that meets three technical criteria — HTTPS, a Web App Manifest and a service worker — so browsers let visitors install it on their home screen. Once installed, it launches like a native app, works offline and can send push notifications.
Do PWAs work offline?
PWAs can work offline, but only for content their service worker has explicitly cached. Registering a service worker does not automatically make a site offline-capable — you decide what to cache (app shell, API responses, images) and what strategy to use (cache-first, network-first, stale-while-revalidate).