| Issue | Primary Cause | Fastest Fix |
|---|---|---|
| Chrome Login Stuck | Corrupt Cache or Sync Profile | Clear Browser Data |
| Infinite Spinner | Conflicting Extensions | Disable All Extensions |
| White Screen on Login | “Local State” File Corruption | Reset Chrome Settings |
What is Chrome login stuck on loading?
The “Chrome login stuck on loading” error occurs when a user attempts to sign into their Google Account via the browser but is met with an infinite spinning wheel, a blank white screen, or a non-responsive login button. This issue prevents users from syncing bookmarks, passwords, and history across devices.
This technical glitch usually stems from a breakdown in the communication between the local browser client and Google’s authentication servers. It is often caused by outdated cache files, corrupted user profiles, or restrictive network settings that block the sign-in scripts from executing properly.
Step-by-Step Solutions
1. Clear Browser Cache and Cookies
Most login loops are caused by outdated session cookies. Clearing these forces Chrome to request a fresh login token from Google servers.
- Open Chrome and press Ctrl + Shift + Delete.
- Set the Time Range to “All time”.
- Check “Cookies and other site data” and “Cached images and files”.
- Click “Clear data” and restart the browser.
2. Disable Problematic Extensions
Third-party extensions, especially ad-blockers or VPNs, can interfere with the OAuth 2.0 login script used by Google.
- Navigate to
chrome://extensions/. - Toggle off all extensions.
- Attempt to log in again. If it works, enable them one by one to find the culprit.
3. Reset Chrome Local State via Command Line
If the application configuration is corrupt, you can force Chrome to regenerate its core files. You can find the directory using the command line to clear the local state.
# For Windows Users to locate the profile directory
cd %LocalAppData%\Google\Chrome\User Data\
# For Linux/macOS to locate the profile directory
cd ~/Library/Application\ Support/Google/Chrome/
After navigating to the directory, close Chrome and delete or rename the file named Local State. Chrome will recreate this file on the next launch, often fixing the login hang.
4. Check for Network or Proxy Interference
Restrictive firewalls or incorrect proxy settings can block the authentication port.
- Go to Settings > System > Open your computer’s proxy settings.
- Ensure “Automatically detect settings” is turned ON.
- Disable any active VPNs temporarily to rule out IP-based blocking.
5. Create a New Chrome Profile
If your current user profile is deeply corrupted, creating a new one is the most effective solution.
- Click on the Profile icon in the top right corner.
- Click “Add” at the bottom of the menu.
- Sign in using your Google credentials on this new profile.
- If successful, transfer your data and delete the old, stuck profile.