ChatGPT Not Loading on Chrome — Fix It in 5 Minutes
TL;DR Hard-refresh with Ctrl + Shift + R first — stale cache is the most common cause. Disable browser extensions (especially ad blockers and privacy tools) that block OpenAI’s endpoints.…
- Hard-refresh with Ctrl + Shift + R first — stale cache is the most common cause.
- Disable browser extensions (especially ad blockers and privacy tools) that block OpenAI’s endpoints.
- If the page stays blank, clear site data for
chatgpt.comspecifically — a full cache wipe is usually unnecessary.
- Open Chatgpt in a private/incognito window to rule out a bad browser session.
- Disable extensions, VPN, or strict privacy tools temporarily, then retry the same action.
- Check the official status page or app notice before assuming your account is broken.
- Try the web app and mobile/desktop app separately to isolate the failing surface.
Overview
ChatGPT failing to load on Chrome typically shows up as a blank white page, an infinite loading spinner, or a “Something went wrong” banner that never resolves. The problem is almost always on the browser side — cached scripts, interfering extensions, or network-level blocks — not an account issue.
This guide walks through fixes from fastest to most thorough. Most users resolve it within the first two steps.
- Hard-refresh: Ctrl + Shift + R (Windows/Linux) or ⌘ + Shift + R (Mac).
- Try Incognito mode — Ctrl + Shift + N. If ChatGPT loads there, an extension is the culprit.
- Check OpenAI’s status page for active incidents.
- Clear cookies and site data for
chatgpt.comonly (instructions below). - Disable VPN or proxy temporarily — some block OpenAI’s CDN endpoints.
Symptoms
The exact behavior varies, but these are the patterns Chrome users report most often:
- Blank white screen. The page loads but renders nothing. The tab title may show “ChatGPT” or stay empty. DevTools console often shows
net::ERR_BLOCKED_BY_CLIENTor CORS errors. - Infinite spinner. The ChatGPT logo animates endlessly. No chat interface appears. This usually means the main JavaScript bundle loaded but an API call is failing silently.
- “Something went wrong” banner. The UI partially renders, then displays an error. Refreshing produces the same result.
- Login loop. You authenticate successfully but get redirected back to the login page. The session cookie isn’t persisting.
Why This Happens
Chrome’s aggressive caching and extension ecosystem make it the browser most likely to cause loading failures with single-page apps like ChatGPT. The root causes break down into a few buckets:
Stale cached assets. ChatGPT ships frequent frontend updates. When Chrome serves an outdated JavaScript bundle that expects a newer API contract, the app breaks silently. This is the single most common cause.
Extension interference. Ad blockers (uBlock Origin, AdBlock Plus), privacy extensions (Privacy Badger, Ghostery), and script blockers can strip requests to OpenAI’s API endpoints or block WebSocket connections that ChatGPT uses for streaming responses.
DNS or network filtering. Corporate networks, VPNs, and DNS-level filters (Pi-hole, NextDNS) may block cdn.oaistatic.com or chatgpt.com subdomains without surfacing a clear error.
Corrupted site data. Service workers or IndexedDB entries from a previous ChatGPT session can get into a bad state, especially if a page load was interrupted.
## Check OpenAI Status and Basic Access
Before troubleshooting your browser, rule out a server-side problem.
Visit status.openai.com. If there’s an active incident affecting ChatGPT, no browser fix will help — wait for resolution.
Next, test access from a different context:
– Open ChatGPT on your phone (cellular data, not the same Wi-Fi). If it works there, the issue is your network or browser.
– Try a different browser on the same machine — Firefox or Edge. If those work, the problem is Chrome-specific.
– If nothing works anywhere, the issue is likely your network or an OpenAI-side outage not yet posted to the status page.
status.openai.com. Checking it first saves you from chasing browser ghosts during a genuine outage.## Clear Cache and Site Data for ChatGPT
A full cache wipe nukes saved passwords and preferences across all sites. Target ChatGPT specifically instead.
**Method 1 — Site-specific clear (recommended):**
1. Navigate to `chrome://settings/content/all` in the address bar.
2. Search for `chatgpt.com`.
3. Click the trash icon next to it. This removes cookies, cached scripts, service workers, and IndexedDB data for that origin only.
4. Also search for and clear `oaistatic.com` — ChatGPT’s static asset CDN.
5. Close all ChatGPT tabs, then reopen `chatgpt.com`.
**Method 2 — DevTools clear (for developers):**
1. Open DevTools with F12.
2. Go to the **Application** tab → **Storage** in the left panel.
3. Click **Clear site data**. Check all boxes including “Unregister service workers.”
4. Hard-refresh with Ctrl + Shift + R.
Chrome DevTools → Application
✓ Cookies cleared ✓ Cache storage cleared ✓ Service workers unregistered ✓ IndexedDB cleared
After clearing, you’ll need to log in again. This is expected.
## Disable Extensions and Test in Incognito
Extensions are the second most common cause. The fast way to confirm: open an Incognito window (Ctrl + Shift + N) and load `chatgpt.com`. Incognito disables extensions by default.
**If ChatGPT loads in Incognito**, an extension is interfering. Find it:
1. Go to `chrome://extensions/`.
2. Disable all extensions.
3. Load ChatGPT. It should work.
4. Re-enable extensions one at a time, reloading ChatGPT after each, until the problem returns.
**Usual suspects:**
– **uBlock Origin / AdBlock Plus** — may block requests to `chatgpt.com` API routes. Fix: add `chatgpt.com` and `*.oaistatic.com` to the allowlist rather than disabling the extension entirely.
– **Privacy Badger / Ghostery** — can block third-party requests ChatGPT relies on for authentication (Auth0 endpoints).
– **VPN/proxy extensions** — Windscribe, Hola, and similar in-browser VPNs route traffic through servers that OpenAI may throttle or block.
– **Dark mode / custom CSS extensions** — Stylus or Dark Reader can break ChatGPT’s own dark mode toggle and cause rendering failures.
chatgpt.com specifically — most blockers support per-site exceptions.**If ChatGPT also fails in Incognito**, the problem is not extension-related. Move to Step 04.
## Check Network, DNS, and Chrome Flags
When cache clearing and extension removal don’t help, the issue is usually at the network or browser-engine level.
**DNS resolution check:**
Open a new tab and navigate to `chrome://net-internals/#dns`. Click “Clear host cache.” Then try ChatGPT again. Chrome caches DNS lookups aggressively, and a stale entry for `chatgpt.com` can point to a dead IP.
If you’re on a corporate or school network, the network administrator may be blocking OpenAI domains. Test with mobile hotspot to confirm.
**Try switching DNS:**
1. Go to `chrome://settings/security`.
2. Under “Use secure DNS,” switch to a custom provider: `8.8.8.8` (Google) or `1.1.1.1` (Cloudflare).
3. Reload ChatGPT.
Some ISP DNS resolvers are slow to update records or actively filter AI tool domains.
**Reset Chrome flags:**
If you’ve modified experimental features, they can break site compatibility.
1. Navigate to `chrome://flags`.
2. Click “Reset all” at the top.
3. Relaunch Chrome.
**Check for a corrupted Chrome profile:**
As a last resort, test with a fresh profile:
1. Go to `chrome://settings/manageProfile`.
2. Click “Add” to create a new profile.
3. Try ChatGPT in the new profile without signing into Chrome sync.
If it works in the new profile, your original profile has corrupted data. You can either migrate your bookmarks and passwords to the new profile or reset the old one.
## Update Chrome and Check System-Level Blocks
An outdated Chrome version may lack TLS features or JavaScript engine updates that ChatGPT’s frontend requires.
1. Go to `chrome://settings/help`.
2. Chrome checks for updates automatically. If an update is available, install it and relaunch.
ChatGPT’s frontend uses modern JavaScript features. Chrome versions older than roughly two major releases behind current may silently fail to parse the app bundle.
**System-level checks:**
– **Antivirus / firewall software** — Windows Defender, Norton, Kaspersky, and similar tools sometimes flag `chatgpt.com` WebSocket connections as suspicious. Temporarily disable web protection to test, then add an exception if that resolves it.
– **Hosts file** — Rarely, malware or manual edits to your hosts file can redirect `chatgpt.com`. Check `C:\Windows\System32\drivers\etc\hosts` (Windows) or `/etc/hosts` (macOS/Linux) for entries containing `chatgpt` or `openai`.
– **Date and time** — If your system clock is significantly wrong, TLS certificate validation fails silently. Chrome may show a blank page rather than a clear certificate error.
chatgpt.com or openai.com, run a malware scan before proceeding.If It Still Fails
If none of the above steps resolve the issue:
- Capture the error. Open DevTools (F12), go to the Console tab, reload ChatGPT, and screenshot any red error messages. Also check the Network tab for failed requests (they show in red).
- Try a completely different browser. Firefox and Edge use different rendering engines. If ChatGPT works there, the problem is definitively Chrome-specific.
- Check the OpenAI Community Forum — search for your specific error message. Chrome loading issues are frequently discussed and OpenAI staff respond to widespread problems.
- Contact OpenAI support through the help widget at help.openai.com. Include your Chrome version (
chrome://version), the DevTools console output, and whether Incognito mode made a difference.
Most ChatGPT loading failures on Chrome come down to stale cache or extension interference — the first two steps resolve roughly 80% of cases without touching any system settings.
Isolate the failing surface
Repeat the same chatgpt not loading on chrome check in another browser, private window, or app so you know whether the issue is local or account-wide.
Remove local blockers
Temporarily disable extensions, VPN, custom DNS, or network filters, then refresh the session and try again.
Escalate only after the basics fail
If the issue follows your account across devices, collect the exact error text and contact the vendor support channel with that evidence.