Why do cookies fail only on third-party embeds?

Most browsers block third-party cookies by default now. Use a first-party embed or move auth to a top-level domain.

IndexedDB works locally but not in production?

Service Worker scope or cross-origin iframes can block IndexedDB. Ensure the app runs on a top-level origin with HTTPS.

How do quotas impact PWA data?

Browsers cap storage per origin. Large caches can be evicted; consider background sync and smaller caches for stability.

Browser Diagnostics

Storage Test

Detect browser storage availability and write-read health

Storage Test

Cookie and storage round-trip checks

0/0 working

Understand your storage results

We attempt real writes and reads to cookies, localStorage, sessionStorage, and IndexedDB. Failures often stem from third-party cookie blocks, storage quotas being exceeded, or hardened privacy settings in Safari, Firefox ETP, and Brave.

If IndexedDB fails, many offline-first apps will not load. Clear site data, disable 'Block all cookies,' then retry. On iOS Safari, storage can be purged in low-memory conditions; pinning the site to the home screen can help persistence.

Quick guides

Enable cookies Third-party cookies Enable localStorage Enable IndexedDB

FAQ

Why do cookies fail only on third-party embeds?: Most browsers block third-party cookies by default now. Use a first-party embed or move auth to a top-level domain.
IndexedDB works locally but not in production?: Service Worker scope or cross-origin iframes can block IndexedDB. Ensure the app runs on a top-level origin with HTTPS.
How do quotas impact PWA data?: Browsers cap storage per origin. Large caches can be evicted; consider background sync and smaller caches for stability.