Fix IndexedDB Blocked in Chrome & Firefox (Run the Storage Test)

Confirm IndexedDB availability

Open the Storage Test. Look for a line indicating IndexedDB: available and Quota: non-zero. If your test does not show IndexedDB explicitly, click Advanced details in DevTools: Application > Storage (Chrome) or Storage Inspector (Firefox) and try to create a sample database. Keep the tab open and rerun after every fix.

Symptoms when IndexedDB is blocked:

• Gmail Offline fails to enable or shows a storage error
• PWAs install but never sync offline content
• Design tools like Figma/Canva fail to load assets after refresh
• Games show "database error" or reset progress to zero

Fix 1: Allow site data and cookies for the domain

IndexedDB follows the same storage permission bucket as cookies and localStorage.

• Chrome / Edge: Settings > Privacy and security > Cookies and site data → keep Allow sites to save and read data on. Add the domain under Sites that can always use cookies.
• Firefox: Settings > Privacy & Security > Enhanced Tracking Protection → Standard. Add the domain under Manage Exceptions with Allow.
• Safari: Settings/Preferences > Privacy → uncheck Block all cookies and keep Prevent cross-site tracking off while testing complex app embeds.

Reload the app and rerun the Storage Test.

Fix 2: Use a normal window, not private browsing

Incognito/Private windows usually provide temporary IndexedDB that clears on close, and some browsers block it entirely. Test in a normal window to confirm whether the restriction is tied to private mode.

Fix 3: Relax strict tracking protection during setup

Aggressive tracking modes can block storage in embedded iframes used by SSO, payments, or asset CDNs.

• Firefox Strict and Brave Aggressive often block third-party IndexedDB calls. Switch to Standard, sign in, then add site exceptions so you can return to stricter settings.
• Edge tracking prevention on Strict: add the domain under Exceptions in Privacy, search, and services.

Fix 4: Clear corrupted IndexedDB databases

If one site fails while others work, its database may be corrupt.

• Chrome/Edge DevTools: Application > IndexedDB. Right-click the problematic database → Delete database. Reload and let the app recreate it.
• Firefox: Tools > Browser Tools > Storage Inspector, right-click the database → Delete All.

After deleting, rerun the Storage Test and try the app again.

Fix 5: Check disk space and quota

IndexedDB writes fail silently when the profile or disk is full.

• Free several GB on the system drive.
• In DevTools Application > Storage (Chrome) or Storage Inspector (Firefox), check Usage and Quota. If usage hits quota, delete old databases you no longer need.
• On Android/ChromeOS, clear older downloads to free space for the browser profile.

Fix 6: Confirm JavaScript and storage APIs are enabled

• Chrome/Edge: Settings > Privacy and security > Site settings > JavaScript → Allowed. Ensure Additional content settings > On-device site data is allowed.
• Firefox: about:config → dom.indexedDB.enabled should be true. If you toggled it off previously, set it back and restart.

Fix 7: Disable extensions that wipe storage

Extensions that auto-delete site data can empty IndexedDB on each navigation.

• Turn off Cookie AutoDelete, Temp Containers, ClearURLs, or aggressive privacy suites.
• Test in a fresh profile with no extensions. If the app works, re-enable extensions one at a time.

Fix 8: Safari and iOS specifics

• iOS/iPadOS WebKit historically capped IndexedDB sizes. Update to the latest iOS, then retry.
• Add the site to your Home Screen (PWA) to grant a more generous storage bucket.
• Interact with the site weekly so ITP does not evict data it sees as unused.

Fix 9: Managed device policies

Enterprise policies can turn off storage for compliance.

• Chrome/Edge: chrome://policy → look for DefaultCookiesSetting, CookiesSessionOnlyForUrls, or DefaultFileSystemWriteGuardSetting. If set to block, IT must change it.
• Firefox ESR: check if your organization applies a policy disabling dom.indexedDB.enabled. Request an exception for the affected domain.

Verify the fix

Run the Storage Test again. Confirm that IndexedDB can be created and quota is available. Then reload the web app and perform the action that failed (enable offline, save a design, download a playlist). If errors persist, open DevTools Console and look for SecurityError or QuotaExceededError messages to guide the next step.