ChatGPT Not Working in Chrome? 9 Fixes (2026) in 10 Min

Quick answer: Clear site data for chat.openai.com (cookies + storage), then test ChatGPT in an Incognito window with all extensions disabled.

If it works in Incognito but not in normal Chrome, the cause is almost always an extension, blocked cookies, or corrupted site storage in your Chrome profile.

Quick Fix Checklist

• 1-minute test (most important): Open Chrome > New Incognito Window and go to https://chat.openai.com. If it works, skip to Extension and Cookies fixes below.
• Hard reload: On the ChatGPT tab press Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (Mac).
• Clear OpenAI site data only: Remove cookies/storage for chat.openai.com (not your entire browsing history).
• Disable extensions (quick isolation): Go to chrome://extensions and toggle off everything (especially ad blockers, privacy tools, script blockers, antivirus web shields, “AI assistant” add-ons).
• Fix cookie blocking: Allow cookies (and third-party cookies if needed) for chat.openai.com and [*.]openai.com.
• Fix “Network error”: Temporarily disable Secure DNS or switch providers, then clear Chrome DNS host cache.

Causes (realistic, not generic)

• Corrupted site storage: Broken cookies, local storage, IndexedDB, or Cache Storage can cause a blank screen, infinite loading, or login loops.
• Extension interference: Ad blockers, tracking protection, script blockers, antivirus web shields, and DOM-modifying extensions can block required scripts, cookies, or WebSockets.
• Chrome cookie/privacy settings: Third-party cookie blocking, “clear cookies on exit,” or strict tracking protection can break authentication and session persistence.
• DNS / Secure DNS filtering: Filtered DNS providers (or Secure DNS mismatches) can intermittently block OpenAI endpoints, causing “Network error” or stuck sends.
• Proxy/VPN/content filtering: Corporate proxies, VPNs, or network filters can block WebSockets/HTTP2 or specific OpenAI domains.
• Chrome profile corruption: A single profile can develop broken permissions/storage that doesn’t affect Incognito or a new profile.
• Managed/enterprise policies: Work/school Chrome can enforce extensions, proxies, or URL blocks that break ChatGPT.
• GPU/rendering issues: Hardware acceleration + driver bugs can cause a white/blank page even when the network is fine.

Cause / Symptom	Best fix (fastest)
Blank page, white screen, endless spinner (bad cache/service worker)	Clear site data for chat.openai.com, then unregister service worker + hard reload
Works in Incognito only	Disable extensions, then re-enable one-by-one; also check cookie exceptions
Login loop / keeps asking to sign in	Allow cookies for chat.openai.com and [*.]openai.com; disable “clear cookies on exit” for these sites
Messages won’t send / “Network error” / streaming stops	Disable blocking extensions, then adjust Secure DNS and clear DNS host cache
Works on mobile but not desktop	Check chrome://policy, proxy/VPN, and antivirus web shield

Step-by-Step Fix

1) Clear ONLY ChatGPT/OpenAI site data (fastest real fix)

This removes corrupted cookies and storage without wiping your whole browser.

1. Open https://chat.openai.com in Chrome.
2. Click the padlock (left of the address bar) > Site settings.
3. Click Clear data (or Delete data depending on Chrome version).
4. Return to the ChatGPT tab and do a hard reload: Ctrl+Shift+R / Cmd+Shift+R.

If you don’t see “Clear data”:

1. Open chrome://settings/siteData.
2. Search for openai and chat.openai.com.
3. Delete those entries, then reload ChatGPT.

2) Identify the extension that breaks ChatGPT (repeatable method)

If ChatGPT works in Incognito, this step usually finds the culprit.

1. Open chrome://extensions.
2. Toggle off all extensions.
3. Reload https://chat.openai.com and try to sign in and send a message.
4. If it works, re-enable extensions one at a time until it breaks again.

Extensions most likely to cause ChatGPT issues:

• Ad blockers and tracker blockers (including “privacy” extensions)
• Script blockers / content security tools
• Antivirus “web protection” extensions
• “Dark mode for every site” / DOM rewriters / reader modes
• Autofill, clipboard, and form-injection tools

Fix without uninstalling: Add an allowlist/exception for chat.openai.com and [*.]openai.com (wording varies by extension). If the extension has a “block WebSockets” or “advanced tracking protection” toggle, disable it for ChatGPT.

3) Fix cookie blocking and sign-in loops (Chrome settings that matter)

If ChatGPT loads but you can’t stay signed in, or it keeps redirecting to login, cookies are being blocked or cleared.

1. Open chrome://settings/cookies.
2. Under cookie settings, check whether Block third-party cookies is enabled.
3. Add exceptions under Sites allowed to use third-party cookies (or similar):
   • chat.openai.com
   • [*.]openai.com
4. Also check Clear cookies and site data when you close all windows. If enabled, add ChatGPT/OpenAI to the “Always keep” / exception list.

Tip: If you use multiple Google accounts/profiles, confirm you’re signing into ChatGPT in the same Chrome profile where you changed cookie settings.

4) Advanced fix: Reset service worker + Cache Storage (fixes stubborn blank screens)

Use this when clearing site data didn’t help, or when Chrome keeps serving a broken cached app shell.

1. Open https://chat.openai.com.
2. Open DevTools: F12 or Ctrl+Shift+I (Windows/Linux) / Cmd+Option+I (Mac).
3. Go to Application.
4. In the left sidebar:
   • Service Workers > click Unregister (if present).
   • Storage > click Clear site data (ensure Cache Storage is included).
5. Close DevTools and hard reload: Ctrl+Shift+R / Cmd+Shift+R.

5) Fix “Network error” and stuck sends (DNS + WebSockets)

If messages fail to send, streaming stops mid-answer, or you see intermittent connection errors, DNS filtering or blocked WebSockets is common.

1. First, disable extensions that can block network requests (ad/privacy/script blockers), then retest.
2. Open chrome://settings/security.
3. Under Use secure DNS:
   • Temporarily set it to Off, or
   • Switch to a different provider if your current one filters traffic.
4. Clear Chrome’s DNS cache:
   • Open chrome://net-internals/#dns (if available) > click Clear host cache, or
   • Open chrome://dns (newer Chrome) > clear host cache.
5. Reload ChatGPT and send a short test message (e.g., “ping”).

If you’re on a work/school network: Try a different network (mobile hotspot) to confirm whether a firewall/proxy is blocking ChatGPT.

6) Non-obvious fix: Clear Chrome network state (fixes weird connectivity)

If ChatGPT fails only in Chrome (but works in other browsers) and DNS changes didn’t help, reset Chrome’s network state.

1. Open chrome://net-internals/#sockets (if available) and click Flush socket pools.
2. Open chrome://net-internals/#hsts and remove any custom entries only if you previously added them (most users can skip this).
3. Restart Chrome and test ChatGPT again.

If those pages aren’t available in your Chrome version, simply restart Chrome and reboot your computer after changing DNS/Secure DNS.

7) Check for Chrome policies/proxy (managed devices)

If you’re on a managed browser, local fixes may be blocked by policy.

1. Open chrome://policy and look for policies related to extensions, proxies, DNS, or URL blocking.
2. Open chrome://settings/system and check whether a proxy is configured (or forced).
3. If policies exist, you’ll need your admin to allow OpenAI/ChatGPT domains or remove the blocking extension/filter.

8) Fix rare blank/white screen: disable hardware acceleration

This helps when the page renders blank but DevTools shows the site is loading.

1. Open chrome://settings/system.
2. Toggle Use graphics acceleration when available to Off.
3. Click Relaunch, then open ChatGPT again.

9) Last-resort (but effective): Use a clean Chrome profile

If ChatGPT works in Incognito but not in normal Chrome even after the steps above, your profile may be corrupted.

1. In Chrome, click your profile icon (top right).
2. Click Add to create a new profile.
3. In the new profile, go to https://chat.openai.com and sign in.
4. If it works, migrate bookmarks/passwords and keep the new profile for ChatGPT, or remove the problematic extension/settings from the old profile.

Still Not Working

• Check for an OpenAI outage first: https://status.openai.com. If there’s an incident, local fixes won’t help until it’s resolved.
• Try a known-clean environment:
  • Different network (mobile hotspot) to rule out firewall/DNS filtering
  • Different browser (Edge/Firefox) to confirm it’s Chrome-specific
  • New Chrome profile (no extensions) to rule out profile corruption
• Collect evidence in 60 seconds (pinpoints the blocker):
  • Open DevTools > Console and copy the first 3–5 red errors.
  • DevTools > Network > reload and look for failed requests (status 401/403/429 or (blocked)).
  • If you see 429, you may be rate-limited; wait a bit, reduce rapid refreshes, and retry.
• Confirm your system clock is correct: Incorrect date/time can break secure sessions and cause login loops. Set time to automatic, then restart Chrome.
• Disable VPN/antivirus web shield temporarily: Some security products intercept HTTPS/WebSockets and break ChatGPT even when extensions are off.
• Update Chrome: Go to chrome://settings/help and update. Outdated Chrome can fail modern web app features.
• Escalation options:
  • If you’re managed (work/school): send your admin the failing domain and the policy list from chrome://policy.
  • If you need OpenAI support: include your symptom, whether Incognito works, your Chrome version, and Console/Network errors.
  • If nothing works: uninstall/reinstall Chrome (or reset settings) after exporting bookmarks/passwords.

If you want the fastest pinpoint: share (1) your symptom (blank page, stuck loading, login loop, messages not sending), (2) whether Incognito works, and (3) the top Console error line.

Fixes for Chrome

This section covers a specific troubleshooting angle related to chatgpt not working on chrome solution. Use it to narrow the issue before moving to deeper fixes.

Why this happens

Problems like this often come from one of three areas: local app state, network conditions, or a recent configuration change.

How to fix it

1. Confirm the exact symptom before changing multiple settings at once.
2. Restart the app and the device before trying advanced fixes.
3. Test on a different network or device if possible.
4. Keep note of any exact error message because it often points to the real cause.

Important notes

• If the basic checks change the behavior, that usually tells you where the issue really lives.
• Move to stronger fixes only after the quick isolation steps above.

If the Problem Started After an Update

If the problem started right after an update, the timing strongly suggests a compatibility or local data issue.

Why this happens

Updates can change permissions, invalidate saved sessions, or leave behind temporary cached data that no longer matches the latest app or system version.

How to fix it

1. Restart the device first to clear temporary glitches triggered by the update.
2. Check whether a follow-up patch is already available for the app or system.
3. Sign out and sign back in if the app still opens but a specific function fails.
4. Clear cache or reinstall the app if the issue appears tied to corrupted local data.
5. Look for reports from other users to confirm whether the update introduced a wider bug.

Important notes

• If many users report the same issue after the same update, a vendor-side patch may be required.
• Do not reset the whole device too early if simpler update-related fixes have not been tested yet.

How to Check for a Temporary Outage

Before changing device settings, confirm that the problem is not caused by a temporary outage.

Why this happens

Service interruptions can make normal accounts, apps, and networks appear broken even when nothing is wrong locally.

How to fix it

1. Try the web version to see whether the same action fails outside the app.
2. Check official status pages or recent outage discussions if available.
3. Avoid repeated retries if the platform appears unstable.
4. Wait a few minutes and test again from the same trusted network.

Important notes

• If both the app and browser fail in the same way, the issue is much more likely to be service-side.
• Changing passwords or reinstalling apps will not help during a real outage.

Frequently Asked Questions