Chrome sign-in not working typically presents in one of three ways, and which one you’re seeing points straight to the cause. If Chrome accepts your credentials and then immediately signs you out, it’s almost always a cookie problem — Chrome can’t store the authentication token. If Chrome signs you in but sync never activates (or shows “Sync paused”), the sync state is corrupted. If Chrome won’t complete the sign-in process at all — the button does nothing, or the page loops — there’s something interfering with the Google authentication request itself. You’ll find the complete rundown in our Google Chrome Errors.
The most common root cause across all three: corrupted cookies or cached authentication data. Try this first before anything else — Ctrl + Shift + Delete → All time → tick Cookies and other site data → Clear data → restart Chrome and sign in again. This resolves the majority of sign-in issues that started without any obvious trigger.
Cookies Are the Foundation of Chrome Sign-In
Chrome’s sign-in relies on Google authentication cookies to prove to Chrome that you’ve authenticated. When those cookies become corrupted, Chrome either can’t read them (so it thinks you’re not signed in) or can’t write them (so the sign-in state doesn’t persist). Either way: clearing them and getting fresh cookies from a new sign-in is the fix.
After clearing cookies and signing back in, also check that Chrome is actually allowed to store cookies for Google domains. Settings → Privacy and security → Cookies and other site data → confirm “Block third-party cookies” isn’t blocking Google services. Some configurations block cookies from google.com, accounts.google.com, or googleusercontent.com — which prevents the authentication cookie from being stored. Check the “Sites that can always use cookies” list and add accounts.google.com if Google is listed under blocked sites.
Disable and Re-Enable Sync When It’s Stuck
Chrome Sync stuck in a “paused” state is a separate problem from sign-in failing. This happens when the authentication token Chrome uses for sync becomes invalid — usually after a password change, a Google account security change, or a long period without sync activity. The token is stale but Chrome doesn’t know it needs to be refreshed.
A broken sync state also has knock-on effects on credentials: when the account is signed out or paused, Chrome won’t save your passwords to your Google account even though sign-in looks fine, so the two problems are worth checking together.
Settings → You and Google → Sync and Google services → Turn off sync. Wait 30 seconds. Turn it back on and sign in again. This forces Chrome to request a new authentication token from Google’s servers. It usually works immediately. If sync pauses again within a few minutes, the token is being invalidated by something else — antivirus HTTPS scanning or a proxy is the likely cause (covered below).
Check System Date and Time
This one catches people off guard. Google’s authentication servers use time-based validation — if your system clock is significantly off from actual time, Google’s authentication tokens fail validation because the timestamps don’t match. Chrome will appear to sign in (the UI accepts your credentials) and then immediately sign out, or sync will pause immediately after enabling.
Right-click the clock in the taskbar → Adjust date and time → toggle “Set time automatically” On → click Sync now. Verify the displayed time is correct. Then try signing in to Chrome again. If the clock was significantly off, sign-in will work immediately after syncing.
Antivirus HTTPS Scanning — Particularly Common After Updates
Antivirus products that perform SSL/HTTPS inspection intercept Google’s authentication traffic and substitute their own certificate. When Chrome encounters this substituted certificate for accounts.google.com, it may refuse to accept the authentication response — because the certificate doesn’t match Google’s expected certificate, which Chrome knows from its preloaded certificate pins.
This shows up as sign-in appearing to process and then failing, often with no error message, or with Chrome showing “Sign-in blocked” or a certificate error during the authentication flow.
Temporarily disable your antivirus’s SSL scanning or HTTPS inspection feature (not full protection — just the SSL interception component). Try signing in. If it works, add accounts.google.com and google.com to the antivirus exclusion list for HTTPS scanning, then re-enable full protection. Most antivirus products have a dedicated SSL inspection whitelist for exactly this scenario.
Extensions That Break Authentication
Cookie-blocking extensions, privacy tools that modify request headers, and some developer tools extensions intercept the Google authentication flow in ways that prevent the sign-in from completing. The most common offenders are Privacy Badger (which blocks Google tracking cookies, some of which Chrome sign-in needs), strict cookie-management extensions, and VPN extensions that route Google account requests through a different IP than the authentication token was issued for.
Test in Incognito mode (Ctrl + Shift + N) — Incognito disables all extensions. If Chrome sign-in works in Incognito, an extension is interfering. Go to chrome://extensions, disable all, restart Chrome, try signing in. Re-enable extensions one at a time to find the culprit.
Profile Corruption — The Fix That Works When Nothing Else Does
When Chrome’s sign-in fails persistently despite clean cookies, correct time, no antivirus interference, and no extension conflict, the Chrome profile itself has corruption in the authentication data storage. This is particularly common after a Chrome crash during a sync operation, which can leave the profile’s credential store in a partially written state.
Creating a new profile confirms this quickly. Profile icon (top right) → Add → Continue without signing in. Try signing in from the new profile. If sign-in works immediately in the new profile, the existing profile is corrupted. Sign into your Google account in the new profile — Chrome will sync your bookmarks, passwords, and history from Google’s servers. Reinstall extensions selectively rather than importing from the old profile, which may carry the same corruption.
Google Workspace and Corporate Account Complications
Google Workspace accounts (formerly G Suite) managed by an organisation have additional sign-in constraints set by administrators. If your organisation has configured Chrome to allow only work accounts, or has blocked personal Chrome sign-in through Google Workspace Admin policies, Chrome’s sign-in will fail for personal accounts even though the account credentials are correct. Chrome may show “This account is not allowed on this device” or sign out immediately without explanation.
Check chrome://policy to see what policies are active. If work-related policies appear that restrict sign-in, this is an IT administration issue rather than a Chrome settings problem. Using a separate Chrome profile for work versus personal use allows both to coexist without conflicts.
VPN and Proxy Interference
VPNs that route traffic through a different country sometimes trigger Google’s security systems — if your Google account is normally accessed from the UK and suddenly appears to be signing in from the US (or vice versa), Google may require additional verification or block the sign-in as a suspicious login attempt. Check your email account associated with Google for a security alert about a sign-in being blocked from a new location.
Disconnect the VPN and try signing in from your actual location. If it works, either connect to a VPN server in your usual country, or sign in without the VPN and then connect.
Our guide on Chrome not opening covers the startup failures that sometimes precede sign-in issues when Chrome profile data is severely corrupted. For sync-related issues where sign-in works but data doesn’t appear across devices, the Chrome performance guide covers sync conflicts that cause Chrome sluggishness. Google’s account support pages cover two-factor authentication issues and device trust settings that sometimes prevent Chrome sign-in in ways that look like Chrome problems but are actually Google account security policies.
Chrome’s “Identity Consistency” feature sometimes causes sign-in problems in ways that are confusing. When Identity Consistency is enabled (which it is by default), Chrome tries to keep the browser sign-in state in sync with any active Google account session in the browser. If you’re signed into a Google account in a tab but signed out of Chrome as a browser, Chrome may show a persistent sign-in prompt. Conversely, if you sign out of Chrome but not from Google’s services in a tab, Chrome may re-prompt for sign-in every time you open a new session. Going to chrome://flags/#account-consistency and setting it to “Disabled” can help isolate whether Identity Consistency is creating unexpected sign-in loops, though this is a diagnostic step rather than a permanent fix — Identity Consistency is a useful feature once the underlying sign-in issue is resolved.
Safe Browsing and Enhanced Protection can occasionally affect sign-in in specific circumstances. Chrome’s Enhanced Safe Browsing mode shares more data with Google’s security systems, including authentication request data, to provide stronger phishing protection. In some edge cases, particularly on corporate networks with custom SSL certificates or with aggressive security policies, Enhanced Safe Browsing’s real-time certificate checking conflicts with the authentication flow. Switching from Enhanced Protection to Standard Protection (Settings → Privacy and security → Security → Safe Browsing) and testing sign-in is worth trying if other fixes haven’t worked and you’re on a corporate or custom-certificate network.
Chrome’s password manager is linked to the sign-in state in ways that can create circular dependencies. If Chrome’s saved passwords are stored in an account that Chrome can’t sign into, Chrome may repeatedly prompt for sign-in to access the password manager — which then fails to sign in because a password manager extension (like LastPass or 1Password) is interfering with the authentication form. Temporarily disabling password manager extensions before attempting Chrome sign-in breaks this circular dependency and allows Chrome’s native authentication to complete without interference from the password manager’s form-filling logic.
Windows Credential Manager stores some Chrome authentication data independently of Chrome’s own storage. If Chrome sign-in keeps failing despite clean cookies and no interference, check Windows Credential Manager (search for “Credential Manager” in Start menu → Windows Credentials tab) for any entries related to Google or Chrome. Stale or corrupted entries in Windows Credential Manager can conflict with Chrome’s own authentication storage and cause persistent sign-in failures. Remove any Chrome or Google-related entries from Windows Credentials and retry signing in — Chrome will create fresh credential entries from the new successful authentication.
Two-Factor Authentication (2FA) timeout issues are a specific sign-in failure mode that feels like Chrome not working but is actually a timing problem in the authentication flow. When 2FA is required and the user doesn’t complete it quickly enough — pausing to check the authenticator app, searching for a backup code, or having the 2FA SMS delayed — the authentication session times out before the 2FA is submitted. Chrome receives an incomplete authentication response and either shows an error or appears to sign in but immediately reverts to signed-out state. The fix is simply to start the sign-in process fresh and complete the 2FA step promptly. If 2FA delivery is consistently slow (SMS delays, TOTP code timing issues), switch to a faster 2FA method through Google Account settings — hardware security keys or Google’s on-device prompt notifications typically complete faster than SMS-based codes.
Chrome’s sign-in state has three distinct components that can fail independently: the browser account (Chrome as an application being signed into a Google account), the sync service (Chrome syncing data to that account), and the web sign-in (being signed into Google services in the browser). Problems with each look similar but have different implications. If Chrome shows you as signed in at the top of Settings but sync shows “Sync paused,” the browser account sign-in succeeded but the sync component failed independently. If you’re signed into Google in a tab but Chrome settings show “Sign in to Chrome,” the web session and the browser account are separate. Understanding which component is failing — browser account, sync, or web session — prevents applying sync fixes to a browser account problem or vice versa.
The “Sign in with Google” flow used by third-party websites (signing into a non-Google service using your Google account) is a related but distinct process from signing Chrome itself into a Google account. Issues with third-party Google sign-in often appear alongside Chrome browser sign-in problems because they share the same cookie and authentication infrastructure. If you’re having trouble signing into external services via Google, clearing Chrome’s cookies for google.com and accounts.google.com specifically (rather than all cookies) and retrying usually resolves the authentication token issue without logging you out of everything else. The padlock icon in Chrome’s address bar on any Google page → Cookies and site data → Manage → find and clear google.com entries → reload and sign in again is a targeted approach that addresses third-party Google sign-in failures without the collateral cookie clearing of a global data wipe.
Chrome’s account image not updating after signing in is a minor but frequently reported sign-in symptom that indicates the profile picture sync isn’t completing even though other aspects of sign-in worked. The account image is one of the last things Chrome refreshes after sign-in, and failures in this specific sync step sometimes indicate that the broader sign-in is partially successful but the account data fetch is failing. If everything about Chrome sign-in appears to work except for the profile image not appearing, it usually resolves on its own within a few minutes as Chrome completes the account data sync. If it doesn’t update after five minutes, signing out and signing back in typically completes the account information sync that the initial sign-in left incomplete. See also How to Fix Firefox Sync Not Working for a related case.
