Fix 'Cookies Disabled' in Chrome & Safari (Run the Storage Test)

Confirm cookie status first

Open the Storage Test and Cookie Test. A healthy browser shows green checks for first-party cookies, localStorage, and sessionStorage. If any line is red, keep this tab open and re-run the tests after every change below. This prevents guessing and keeps you within the right word count for a quick fix guide.

Common symptoms when cookies are blocked:

• You log in, refresh, and get signed out again
• Shopping carts empty themselves on the next page
• Consent banners repeat on every visit
• CAPTCHA loops even after solving

Fix 1: Allow cookies for the site

Start by allowing cookies at the site level, then refine third-party settings as needed.

• Chrome / Edge:
  • Click the lock icon in the address bar → Cookies and site data → Allow.
  • Or go to Settings > Privacy and security > Third-party cookies and pick Block third-party cookies in Incognito or Allow all cookies while you test.
• Firefox:
  • Settings > Privacy & Security > Enhanced Tracking Protection → set to Standard.
  • If you previously blocked the site, click the shield icon and choose Turn off protection for this site.
• Safari:
  • Settings (or Preferences) > Privacy → uncheck Block all cookies.
  • If the site needs third-party cookies, uncheck Prevent cross-site tracking temporarily while you test.

Reload the page and rerun the Cookie Test.

Fix 2: Clear corrupted cookies for the site

Bad or expired cookies can cause endless logout loops.

1. Click the lock icon → Cookies → remove cookies for the current site.
2. Or open chrome://settings/siteData (Firefox: about:preferences#privacy → Manage Data) and delete the site's data.
3. Reload, sign in again, and run the tests. If the problem vanishes, the old cookie jar was the culprit.

Fix 3: Check extensions that block cookies

Privacy extensions often block or strip cookies by default.

• Disable strict modes in uBlock Origin, Ghostery, Privacy Badger, DuckDuckGo Privacy Essentials, or AdGuard.
• Cookie consent blockers can stop the consent cookie from ever being set; add the site to their allowlist.
• After adjustments, rerun the Storage Test to confirm storage APIs are no longer blocked.

Fix 4: Use the right third-party setting for the site

Some sites rely on third-party cookies for SSO, payments, or embedded chat widgets.

• Chrome/Edge: Settings > Privacy and security > Third-party cookies → choose Allow third-party cookies while completing the flow. Then add a site exception under Sites that can always use cookies instead of leaving global allow.
• Firefox: under Enhanced Tracking Protection, click Manage Exceptions and add the site that hosts the login or payment iframe.
• Safari: if a payment popup fails, temporarily uncheck Prevent cross-site tracking, finish the payment, then turn it back on.

Fix 5: Make sure storage isn't disabled globally

• Chrome/Edge: Settings > Privacy and security > Site settings > Content > Cookies and site data should Allow sites to save and read cookie data.
• Firefox: in about:config, ensure network.cookie.cookieBehavior is 0 (allow) or 4 (block trackers only), not 2 (block all).
• Brave: lower Shields for the affected site or switch Block third-party cookies to Cross-site only.

Fix 6: Match device time and date

Wrong system clocks cause cookies to expire instantly.

• Sync time automatically in Windows (Settings > Time & language), macOS (System Settings > General > Date & Time), or your Linux distro's date settings.
• After correcting the clock, clear cookies for the site once more and test.

Fix 7: Avoid private modes while testing

Incognito/Private windows delete cookies when closed and often block third-party cookies by default. Test in a normal window to see if the issue disappears. If you must stay private, add a site exception for cookies before closing the tab.

Fix 8: Watch for managed devices

Work or school devices may enforce cookie rules via policy.

• Chrome/Edge: visit chrome://policy and look for CookiesAllowedForUrls, BlockThirdPartyCookies, or CookiesSessionOnlyForUrls.
• If policy blocks what you need, you will need IT to update the rule. Document the failing line from the Cookie Test so they can see the impact.

Verify the fix

Run the Storage Test again and confirm:

• Cookies: yes
• localStorage / sessionStorage: yes
• Third-party cookies: yes (if the site relies on them) Then reload the problem site and try the action that was failing (log in, add to cart, submit form).

Edge cases and quick wins

• Content blockers rewriting URLs: Some blockers strip query parameters that set cookies. Turn them off for the site and retry.
• Profiles and containers: Firefox Multi-Account Containers or Edge profiles may isolate cookies. Use the same profile each time you sign in.
• Disk nearly full: Browsers may refuse to write storage when disk space is low. Free a few hundred MB and retest.