Padlock caught in a circular refresh loop icon
If you enter your password on a Mac and the page just refreshes (or you get dumped right back to “Sign in”), you’re probably stuck in a login loop. It’s common across Safari/Chrome/Firefox and many apps that open an embedded web sign-in.

It’s usually fixable without changing your password.

Before you start: if this is a work/school account, your admin policies (device compliance, VPN, security keys) can also cause loops—so note which step changes the behavior.

1. Check the obvious: date/time, network, and VPN

Login sessions rely on accurate time and a stable route to the auth server. If your Mac’s clock is off or your connection is bouncing, logins can “succeed” but the session cookie never sticks.

  • Go to System Settings > General > Date & Time and enable Set time and date automatically.
  • Temporarily turn off VPN, iCloud Private Relay (if you use it), and any “secure DNS” tools, then try signing in again.
  • Try a different network (hotspot is fine) to rule out a captive portal or filtering.

If it works on another network, the fix is usually VPN/DNS/filtering—not your account.

2. Confirm cookies aren’t blocked (and allow cross-site cookies if needed)

Cookie with shield symbolizing blocked or limited cookies
A login loop is often a cookie issue: the site sets a session cookie, but the browser blocks it, so you get sent back to sign-in.

  • Safari: Settings > Privacy
    • Turn off Block all cookies.
    • If you use “Prevent cross-site tracking,” try turning it off briefly to test (some identity providers rely on cross-site cookies).
  • Chrome: Settings > Privacy and security > Third-party cookies
    • Try allowing third-party cookies for the sign-in flow, or add the site as an exception.
  • Firefox: Settings > Privacy & Security
    • Set Enhanced Tracking Protection to Standard for a test, or add an exception for the site.

After changing cookie settings, completely close the tab and restart the sign-in flow from the site’s main page.

3. Clear site data for just the affected service (not your whole browser)

Corrupted or conflicting site storage can keep sending you back to the beginning. Clearing data for only the problem domain is usually enough.

  • Safari: Settings > Privacy > Manage Website Data
    • Search for the site and its login provider (often a separate domain), then Remove.
  • Chrome: Settings > Privacy and security > Site settings > View permissions and data stored across sites
    • Search the domain and delete stored data.
  • Firefox: Settings > Privacy & Security > Cookies and Site Data > Manage Data

If the service uses “Sign in with…” (Google/Microsoft/Apple), clear both the service domain and the identity provider domain involved.

4. Disable content blockers, ad blockers, and “privacy” extensions (temporarily)

Browser extension puzzle piece with a toggle switch icon
Some blockers remove key redirect parameters or block a script that writes the session cookie—classic cause of a refresh loop.

  • Try an incognito/private window (many extensions are disabled there unless you allow them).
  • Or temporarily disable blockers for the sign-in domain and the identity provider domain.
  • In Safari, also check Safari > Settings > Extensions and disable anything that alters pages, cookies, redirects, or headers.

If disabling the blocker fixes it, re-enable the blocker and add a site exception rather than leaving it off globally.

5. Try a clean browser profile (or another browser) to isolate the cause

This is a fast way to tell whether the issue is the site/account or your local browser state.

  • Test in a different browser you don’t normally use (Safari vs Chrome vs Firefox).
  • Or create a new browser profile (Chrome/Edge) and try signing in there.

If it works in a fresh profile, the culprit is usually an extension, cookie policy, cached data, or a damaged local browser database.

6. If the login happens inside an app: reset the in-app web login state

Many Mac apps sign you in through an embedded web view. Those can keep stale tokens even when your main browser is fine.

  • Quit the app completely (not just close the window), then reopen and try again.
  • If the app has an option like Reset sign-in, Clear cache, or Remove account, use it and sign in fresh.
  • Update the app (and macOS) to ensure the embedded web components are current.

If the app offers “Open in browser to sign in,” choose that—it’s often more reliable.

7. Check Keychain for repeated old passwords or stuck prompts

Sometimes the login is fine, but a background sync component keeps reusing an old credential, causing repeated auth failures and loops.

  • Open Keychain Access (Spotlight search it).
  • Search for the service name (or the identity provider, like “Microsoft,” “Google,” etc.).
  • If you see multiple similar entries, look for ones with old usernames or outdated “Internet password” items.
  • Delete only items you’re confident belong to the broken login, then try signing in again so macOS can recreate them.

If you’re unsure, don’t mass-delete Keychain items—remove one suspicious entry, retest, and repeat.

Final thoughts

Most Mac sign-in loops come down to cookies/site data, blockers, or a stale embedded web session. Work from the smallest change (site data + blockers) outward.

If none of the steps change anything, try the same account on another device—if it loops there too, the problem is likely account-side (security policy, required re-verification, or a service outage).