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

Confirm storage in 10 seconds

Open the Storage Test. It checks localStorage, sessionStorage, cookies, and quota. A passing result shows green checks for localStorage and quota > 0 MB. Leave the tab open and re-run after each change below so you know which fix worked.

Typical signs local storage is blocked:

• Web apps forget preferences after every refresh
• Games never save progress or settings
• PWAs refuse to install or work offline
• "QuotaExceededError" shows in the console

Fix 1: Allow site data for this site

Start by letting the site store data, then dial privacy back down once it works.

• Chrome / Edge: Settings > Privacy and security > Cookies and site data → ensure Allow sites to save and read data is on. Click Sites that can always use cookies and add the affected domain (this covers storage too).
• Firefox: Settings > Privacy & Security > Enhanced Tracking Protection → set to Standard. Click Manage Exceptions and allow the domain.
• Safari: Settings/Preferences > Privacy → uncheck Block all cookies. Safari ties storage and cookies together.
• Brave: Click the Shields icon → set Block cross-site cookies to Cross-site only for the site.

Reload and rerun the Storage Test. If localStorage is still blocked, continue.

Fix 2: Leave private browsing for testing

Incognito/Private windows wipe storage when closed and often block third-party storage. Open a normal window, sign in, and see if the Storage Test passes. If you must stay private, add a site exception before closing the tab so the browser keeps storage for that session.

Fix 3: Relax strict tracking protection temporarily

Aggressive tracker blocking can sandbox or clear localStorage.

• Firefox Strict mode and Brave Aggressive mode can break embedded login widgets. Switch to Standard while you complete the action, then add per-site exceptions.
• In Edge with tracking prevention on Strict, add the domain to Exceptions under Privacy, search, and services.

Fix 4: Clear corrupted site data

If storage exists but fails to write, a corrupt entry may be blocking new data.

1. Open Site settings for the domain (Chrome/Edge: lock icon → Cookies and site data → Manage; Firefox: shield icon → Clear cookies and site data).
2. Remove data for the site.
3. Reload, sign in, and rerun the Storage Test.

Fix 5: Check disk space and quota

Browsers stop writing when the profile or disk is nearly full.

• Free several hundred MB on your system drive.
• In DevTools Application > Storage (Chrome) or Storage Inspector (Firefox), verify Usage is below quota. If Quota exceeded, delete old cached data or large IndexedDB databases you no longer need.

Fix 6: Ensure JavaScript and storage APIs are allowed

localStorage needs JavaScript.

• Chrome/Edge: Settings > Privacy and security > Site settings > JavaScript → Allowed. Also ensure Additional content settings > On-device site data is allowed.
• Firefox: in about:config, confirm dom.storage.enabled is true.

Fix 7: Disable interfering extensions

Some privacy or sandboxing extensions wipe storage on every navigation.

• Turn off add-ons like Temp Containers, Cookie AutoDelete, ClearURLs, or strict modes in uBlock Origin.
• Try in a clean profile. If the Storage Test passes there, re-enable extensions one by one to find the blocker.

Fix 8: Account for Safari and ITP limits

Safari's Intelligent Tracking Prevention can purge storage for sites you do not interact with often.

• Add the site to your Favorites and interact with it (click, scroll, play a video). ITP treats engaged sites more leniently.
• If you are testing a PWA, visit it at least once a week so Safari keeps its storage.

Fix 9: Managed device policies

Enterprise policies can disable storage.

• Chrome/Edge: check chrome://policy for DefaultCookiesSetting or CookiesAllowedForUrls. If set to block, only IT can change it.
• Firefox ESR under management may set DisableStorage or enforce Strict ETP. Ask IT to create an exception for the affected domain.

Verify the fix

Run the Storage Test again. You want:

• localStorage: yes
• sessionStorage: yes
• Quota: non-zero If all green, reload the web app and try the action that was failing (save, toggle theme, progress a level). If localStorage still fails, open DevTools → Console and look for errors mentioning QuotaExceededError or SecurityError to narrow the cause.