Gemini Not Loading on Chrome — Fix Blank Screen, Timeouts, and Connection Errors

Overview

Gemini failing to load in Chrome typically presents as a blank white page, an infinite spinner, or a generic “Something went wrong” message. The root cause is almost always on the client side: stale cache, conflicting extensions, or account/region restrictions.

This guide covers the most common causes in order of likelihood and walks through each fix. If you’re seeing a specific error code, skip to the step that matches. If the page simply never renders, start from the top.

Symptoms

What you may see when Gemini fails to load in Chrome:

• Blank white page — the URL resolves but the app shell never renders. The page title may show “Gemini” but the body stays empty.
• Infinite loading spinner — the page partially loads but the chat interface never appears.
• “Something went wrong” banner — a generic error with no actionable detail. Sometimes accompanied by a “Try again” button that changes nothing.
• ERR_CONNECTION_TIMED_OUT or ERR_CONNECTION_RESET — Chrome can’t reach Google’s servers at all. Usually a network or DNS issue rather than a Gemini-specific problem.
• 403 / “Gemini isn’t available” — your account or region doesn’t have access. This is an access restriction, not a bug.

If Gemini loads but responses fail mid-generation, that’s a different issue — .

Why This Happens

Gemini’s web client is a single-page application that relies on multiple Google API endpoints to initialize. If any of these requests fail — due to stale authentication tokens, blocked network calls, or corrupted cache — the entire interface can fail silently.

The most common causes, ranked by frequency:

1. Stale cookies or cached state — Chrome aggressively caches service worker data. A bad cached state can prevent the app from bootstrapping.
2. Extension interference — Ad blockers, privacy extensions (uBlock Origin, Privacy Badger), and script blockers routinely block the API calls Gemini needs.
3. Account restrictions — Google Workspace admins can disable Gemini for an entire organization. Personal accounts in unsupported regions may also be blocked.
4. Network issues — VPNs, corporate proxies, and DNS misconfigurations can block or slow Google API traffic.
5. Outdated Chrome — Gemini’s frontend uses modern web APIs. Chrome versions significantly behind current stable may fail to render the app.

Check Status and Account Access

Verify the service is up. Visit the Google Cloud Status Dashboard. If there’s an active incident affecting Gemini or Google AI services, no client-side fix will help — wait for resolution.

Confirm your account has access. Sign in at gemini.google.com with your personal Google account first. If you’re using a Google Workspace account, Gemini may require your organization’s admin to enable it under Admin Console → Apps → Additional Google services.

Check region availability. Gemini isn’t available in all countries. If you’re traveling or using a VPN that routes through an unsupported region, switch to a server in a supported country or disconnect the VPN entirely.

Try another browser. Open gemini.google.com in Firefox or Edge. If it loads there, the problem is Chrome-specific — continue to step 02. If it fails everywhere, the issue is account- or network-level.

Clear Cache and Cookies

This is the fix that resolves the majority of cases. Don’t skip it even if you think your cache is fine.

Targeted clear (recommended):

1. Navigate to chrome://settings/content/all in Chrome’s address bar.
2. Search for gemini.google.com.
3. Click the trash icon next to it to remove all stored data for that site.
4. Also clear accounts.google.com if you suspect a stale auth token.
5. Close all Chrome tabs, reopen Chrome, and navigate to gemini.google.com.

Nuclear option — full clear:

1. Press Ctrl + Shift + Delete (or ⌘ + Shift + Delete on Mac).
2. Set time range to All time.
3. Check Cookies and other site data and Cached images and files.
4. Click Clear data.

Clear the service worker separately. Gemini registers a service worker that can hold onto stale state even after a cache clear:

1. Open chrome://serviceworker-internals/.
2. Find any entry for gemini.google.com.
3. Click Unregister.
4. Hard-refresh Gemini.

Disable Conflicting Extensions

Extensions are the second most common cause. Here’s how to identify the culprit efficiently rather than disabling everything at once.

Quick test: Open an Incognito window (extensions are disabled by default in Incognito unless you’ve explicitly allowed them). If Gemini loads in Incognito, an extension is interfering.

Common offenders:

• uBlock Origin — may block Google’s API endpoints used by Gemini. Try adding @@||gemini.google.com^ to your custom filter list instead of disabling it entirely.
• Privacy Badger — can block third-party Google domains that Gemini depends on.
• NoScript / ScriptSafe — Gemini requires JavaScript from multiple Google-owned domains.
• Dark Reader — occasionally causes rendering issues where the page loads but content is invisible (white text on white background).
• Grammarly — known to interfere with text input areas in SPA frameworks.

Binary search method: If you have many extensions, disable half at a time, reload Gemini, and narrow down which half contains the problem. Faster than disabling one by one.

Navigate to chrome://extensions/ and toggle extensions off. After identifying the conflicting extension, check if it has an update available or add Gemini to its allowlist.

Chrome-Specific Diagnostics

Update Chrome. Gemini’s frontend relies on modern JavaScript features. Open chrome://settings/help — Chrome should auto-update. Restart after updating.

Check for corrupt profile. A corrupted Chrome profile can cause site-specific failures:

1. Open chrome://version/ and note your Profile Path.
2. Close Chrome completely.
3. Rename that profile folder (e.g., Default → Default_backup).
4. Reopen Chrome — it creates a fresh profile.
5. Try Gemini. If it works, migrate your bookmarks and extensions to the new profile.

Check DNS resolution. Open Chrome DevTools (F12) → Network tab → reload Gemini. Look for failed requests. If requests to gemini.google.com or alkalimetal-pa.clients6.google.com fail:

• Try switching DNS to 8.8.8.8 / 8.8.4.4 (Google DNS) or 1.1.1.1 (Cloudflare).
• On Windows: Settings → Network → Change adapter options → IPv4 → DNS.
• On Mac: System Settings → Network → Advanced → DNS.

Check Chrome flags. Some experimental flags can break Google apps. Navigate to chrome://flags/ and click Reset all if you’ve modified flags previously.

Disable hardware acceleration if you see a blank page with no console errors:

1. Go to chrome://settings/system.
2. Toggle off Use hardware acceleration when available.
3. Relaunch Chrome.

This resolves rendering issues caused by outdated or buggy GPU drivers — more common on older machines or Linux desktops.

If It Still Fails

If none of the above steps work:

1. Capture the exact error. Open DevTools (F12), reload Gemini, and screenshot both the Console and Network tabs (filter Network to failed requests). This is the most useful information for any support interaction.
2. Try a completely different network. Tether to your phone’s mobile data. If Gemini loads, your ISP, router, or corporate firewall is blocking something.
3. Test in a different browser. If Gemini fails in all browsers, the problem isn’t Chrome — it’s your account, network, or region.
4. Report the issue. Use the Send feedback option inside Gemini (if the page loads partially) or visit the Google Gemini Help Center for account and access issues.
5. Check community forums. The Google Gemini Community on Google’s support forums often surfaces emerging issues faster than official status pages.

FAQ