Fix Claude Google Sign-In Not Working: Step-by-Step

Using Google Sign-In is a convenient way to access Claude, but authentication loops, blank screens, and generic errors can sometimes lock you out of your account. These sign-in issues are rarely caused by system-wide Claude outages; instead, they typically stem from local browser settings, cookie restrictions, or misconfigured account profiles.

Follow this guide to troubleshoot and fix Google Sign-In failures on Claude.ai.

Why Google Sign-In Fails on Claude

When you click "Continue with Google," your browser initiates a secure handshake between Google's authentication servers and Anthropic. This process can break if: 1. Cross-Site Tracking is Blocked: Your browser blocks the cookies required to pass authentication data between google.com and claude.ai. 2. Stale Session Data: Old, corrupt cookies from previous sessions interfere with the login handshake. 3. Account Conflicts: You originally registered your account using your email address and passwordless login link, and the system is struggling to link your Google profile to that existing account.

1. Enable Third-Party Cookies and Cross-Site Tracking

Most Google Sign-In failures are caused by privacy settings that prevent different domains from sharing authentication tokens.

• In Google Chrome: Go to Settings > Privacy and security > Third-party cookies. Ensure that "Block third-party cookies" is turned off, or add [*.]claude.ai and [*.]google.com to your allowed sites.
• In Apple Safari: Go to Settings > Privacy (or Safari > Settings > Advanced on macOS) and uncheck Prevent Cross-Site Tracking.
• In Brave Browser: Click the Brave Shield icon in the address bar while on Claude.ai and toggle the shields to Down temporarily to see if the authentication completes.

2. Clear Google and Claude Cache Data

Corrupted cache files can lock you into a continuous redirect loop where Claude asks you to sign in over and over.

1. Open your browser settings and navigate to your history or privacy section.
2. Choose to clear browsing data, but select only Cookies and other site data and Cached images and files.
3. To avoid losing all your saved logins, you can clear data specifically for Claude and Google:
4. In Chrome, click the padlock/settings icon to the left of claude.ai in your address bar.
5. Click Site settings, then click Clear data.
6. Restart your browser and attempt to sign in again.

3. Try an Incognito or Private Window

Browser extensions (especially password managers, ad-blockers, and script-blockers) frequently interfere with authentication scripts.

1. Open a private/incognito window in your browser.
2. Go directly to [claude.ai](https://claude.ai/).
3. Click Continue with Google.
4. If this works, the issue is caused by one of your browser extensions. Temporarily disable your extensions one by one in your main browser window to identify the culprit.

4. Check for Account Link Mismatch

If you created your Claude account by typing your Gmail address and clicking "Send Login Link," you established a passwordless email-based account. Sometimes, clicking "Continue with Google" afterward triggers a conflict error.

1. If Google Sign-In fails, go back to the main login screen.
2. Type your Gmail address directly into the email field and click Continue with email.
3. Open your inbox, click the temporary login link sent to you, and see if you gain access.
4. Once inside, you can navigate to your profile settings to see if you can link your Google account for future logins.

When to Escalate

If you have cleared your cache, enabled cookies, disabled all extensions, tried multiple browsers, and still receive an error message (such as "Authentication failed" or a developer error page from Google), check the official Anthropic status page at status.anthropic.com to see if there is an ongoing login outage. If the status page is green, contact support via the help widget on the login screen. Specify whether you are using a workspace or personal Google account, as corporate Google Workspace policies can sometimes block external API authentication.