If a sign-in page in Chrome turns white/blank, keeps spinning, or never finishes loading, it’s usually a cookies/cache issue, an extension conflict, or a network/privacy setting blocking the page scripts.
Work through the steps below in order—most people get it fixed by step 3.
1. Confirm it’s not the site (quick isolation test)
Before changing anything, check whether the problem is specific to Chrome.
- Open the same login link in an Incognito window (Ctrl+Shift+N / Cmd+Shift+N).
- Try another browser (Edge, Safari, Firefox) on the same device.
- Try the same Chrome login on your phone using mobile data (not Wi‑Fi).
If it fails everywhere, the service may be down or your account could be temporarily blocked. If it works elsewhere but not Chrome, continue below.
2. Hard refresh and reload without cached files
A blank login page can happen when an outdated script is stuck in cache.
- Windows: press Ctrl+F5 (or Ctrl+Shift+R) on the login page.
- Mac: press Cmd+Shift+R.
- If you’re redirected in a loop, copy the login URL, close the tab, and paste it into a new tab.
This is fast and fixes more cases than you’d think.
3. Clear cookies for that site (best fix for blank/looping logins)
Most sign-in pages rely on cookies. If they’re corrupted or blocked, the page may load empty or spin forever.
- Open Chrome Settings → Privacy and security → Third-party cookies.
- Click See all site data and permissions (or search for “site data”).
- Search for the site’s domain (for example: accounts.example.com).
- Delete cookies/storage for that domain only.
Then reopen the login page and try again.
4. Disable extensions (especially ad blockers, script blockers, password tools)
Extensions that filter scripts, block trackers, inject password fields, or rewrite pages can break login flows and cause blank screens.
- Open chrome://extensions.
- Toggle off extensions (start with ad blocker/privacy/script extensions).
- Retry the login page.
If it works after disabling extensions, re-enable them one by one to find the culprit. Then whitelist the login domain or replace that extension.
5. Check Chrome cookie settings and “Block all cookies” pitfalls
If cookies are blocked too aggressively, the page may load but authentication never completes.
- Chrome Settings → Privacy and security → Third-party cookies.
- Avoid using Block all cookies for normal sign-ins.
- If the site uses embedded sign-in (common with “Continue with Google/Microsoft”), try allowing third-party cookies for that site.
- Also check Site settings → Pop-ups and redirects and allow the site temporarily if the login uses a redirect window.
After changing settings, fully close Chrome and reopen it.
6. Reset network “middlemen”: VPN, proxy, DNS, and captive portals
Some logins fail when a VPN, proxy, or filtered DNS blocks authentication endpoints, or when Wi‑Fi requires a captive portal sign-in.
- Turn off VPN/proxy temporarily and retry.
- Switch networks (Wi‑Fi ↔ mobile hotspot) to test quickly.
- If you’re on public Wi‑Fi, open any non-HTTPS site (example.com) to trigger a captive portal, then retry login.
- If you use a “family filter” or ad-blocking DNS, try standard DNS temporarily.
If the login works on a different network, the fix is usually in the VPN/proxy/DNS layer—not your account.
Final thoughts
Blank or endlessly loading sign-in pages in Chrome are almost always caused by bad site cookies/storage or an extension blocking scripts. Clearing site data and testing with extensions off is the fastest path.
If none of the steps help, try updating Chrome (or testing a fresh Chrome profile) and note any error in DevTools Console—support teams can often pinpoint the blocked request from that.