When Gmail won’t let you log in, confirm password, clear cookies, check 2-Step or passkeys, and rule out outages on Google’s status page.
Locked out of Gmail and staring at a loop, error, or a blank page? You’re not alone. Sign-in trouble usually comes from a few recurring culprits: browser data that’s gone stale, cookies blocked, a prompt stuck in 2-Step Verification, or a temporary service hiccup. This guide walks you through quick checks that fix most login blocks, then moves into deeper fixes for phones and email apps.
Quick triage: get back in, step by step
Start with the fast wins below. If one step doesn’t help, move to the next. For outages or broad incidents, check the Google Workspace Status Dashboard to confirm it’s not on Google’s side.
Use this mini-map to match what you see with the fastest fix.
| Symptom | Likely cause | First step |
|---|---|---|
| Password accepted, page loops back | Corrupt cookies or cache; blocked third-party cookies | Clear cookies and cache for google.com and accounts.google.com, then retry in a private window |
| “Couldn’t sign you in” after code | Stuck 2-Step flow or prompt not reaching your phone | Pick “Try another way” and use backup codes or a security key |
| No verification code arrives | Carrier delay, spam filtering, or recovery number out of date | Use a Google prompt on a signed-in phone, then update recovery info |
| “This browser or app may not be secure” | Old app or embedded webview using an outdated sign-in method | Open a full browser and add the account with the Google option |
| App asks for IMAP password over and over | Password changed or app now needs OAuth or an app password | Remove and re-add the account with the Google option, or use an app password |
| “Something went wrong, try again later” | Temporary service issue or network filter | Check the Workspace Status Dashboard and try another network |
| Your account was disabled message | Security hold or policy violation | Follow the link provided to start the review or recovery steps |
| Traveling and can’t pass the check | Extra risk checks from a new location or device | Sign in on a known device and network, then approve the new login |
Fix web browser sign-ins
Most web sign-in loops trace back to cookie or cache problems, or a cranky extension. Here’s how to get a clean sign-in in a few minutes.
Clear stale data
Close extra tabs. In your browser, clear cookies and cache for all time, then restart the browser. If you prefer a lighter touch, clear data only for google.com and accounts.google.com. Try a fresh sign-in after the restart.
Allow cookies and JavaScript
Gmail needs cookies and JavaScript to complete sign-in. Make sure third-party cookies aren’t blocked, especially in private or incognito windows where they’re often disabled by default.
Disable extensions and content blockers
Turn off password managers, content blockers, script blockers, and privacy add-ons for a moment. If sign-in works with extensions off, turn them back on one by one to spot the offender.
Use a supported browser
Update Chrome, Edge, Firefox, or Safari to the current version. If you see “This browser or app may not be secure,” switch to a full browser window instead of an embedded webview.
Gmail login not working: common causes
Different errors tend to point to specific root causes. Matching the message to the likely fix saves time. Watch for phrases like “wrong password,” “couldn’t sign you in,” “try again later,” or prompts that never reach your phone.
Fix two-step or passkey roadblocks
If you turned on 2-Step Verification or passkeys, the extra check must complete before Gmail lets you in. When a prompt or code never arrives, use the backup options you set up earlier.
Use “Try another way”
On the verification screen, pick “Try another way” to switch to a different method: a Google prompt on a signed-in phone, a hardware security key, backup codes, or a code sent to your recovery email or phone.
Get prompts on a signed-in phone
Prompts appear on phones that are signed in to the same Google Account and have a screen lock. Turn on screen lock, connect to the internet, and keep Google Play Services up to date on Android.
Use backup codes or a security key
If your phone is lost or offline, enter one of your one-time backup codes. If you registered a USB or NFC security key, plug it in or tap to verify.
App passwords for old mail apps
If you still use an older mail app that doesn’t support modern sign-in, generate an app password in your Google Account security settings. Use that 16-character password in the mail app instead of your normal one.
Device and app fixes
If the Gmail app, Apple Mail, Outlook, or another client keeps failing, work through the checks below. They handle most sign-in errors after a password change or a security update.
Android and iPhone
Update the Gmail app. Reboot the phone. Confirm the time and date are set to automatic. Remove the Google Account from the device, restart, then add it again. Avoid captive Wi-Fi portals until after sign-in completes.
Outlook, Apple Mail, and Thunderbird
Remove and re-add the account using the Google or OAuth option, not manual IMAP. If you changed your password or turned on 2-Step Verification, delete the old saved credentials. Make sure IMAP is enabled in Gmail settings if your client needs it.
If you use an app, this quick table points you to the right menu or toggle.
| App or device | Check | Where |
|---|---|---|
| Gmail app (Android) | Update Gmail and Google Play Services; turn on screen lock; check prompts | Play Store and Settings > Security |
| Gmail app (iPhone) | Update Gmail; allow notifications; restart; remove and re-add account | App Store and iOS Settings |
| Outlook desktop | Add account via Google; remove old stored credentials; restart Outlook | File > Add Account |
| Apple Mail (macOS) | Internet Accounts > Google; re-add using Google; confirm IMAP is on in Gmail | System Settings > Internet Accounts |
| Thunderbird | Add Mail Account with OAuth; delete saved password and reconnect | Account Settings > Server Settings |
| Browsers | Allow cookies; clear cache; disable extensions; test a private window | Settings > Privacy |
Account recovery if you’re locked out
If you can’t remember the password or can’t pass verification, use Google’s account recovery flow. Provide the most precise answers you can, use a device and location you’ve used before, and keep trying daily if you add better info.
Recovery tips that raise your odds
Use a familiar device on your home Wi-Fi. Enter the last password you recall, even if it seems slightly wrong. Submit recovery once per day with any new details, then wait for the follow-up email.
Prevent the next lockout
Once you’re back in, spend a few minutes hardening your setup so login stays smooth.
- Add or update a recovery email and phone in your Google Account.
- Turn on passkeys or 2-Step Verification and store backup codes somewhere safe.
- Keep one extra signed-in device for prompts, like a tablet at home.
- Review third-party access and remove apps you no longer use.
- Keep your browser and phone fully updated.
Before you try again: short checklist
- Password works on another device or in a private window.
- Cookies allowed and cache cleared; extensions off for the test.
- No outage on the Workspace Status Dashboard.
- Phone is online with screen lock on for prompts.
- Backup code or security key is ready if the prompt fails.
Deep fixes for stubborn loops
If a clean browser still fails, try a new browser profile. On Chrome, add a new profile, skip sync, then sign in to Gmail. A fresh profile avoids broken settings that carry over during updates. You can also reset browser settings to default and retest. Reboot once.
Check time and SSL warnings
If your device time is off by hours, sign-in can fail. Set time and date to automatic and restart. If the address bar shows certificate or security warnings, update the browser and try again on a different network.
VPNs, firewalls, and school networks
Some networks block Google sign-in pages or needed scripts. Temporarily turn off a VPN, switch to mobile data, or try another Wi-Fi. If you’re on a school or work network, test at home to compare.
Conflicting sessions
If you juggle many Google Accounts, a stuck cookie can mix them up. Sign out of all accounts, close the browser, start a private window, then sign in only to the account you need. Add others later.
Security holds and suspicious activity
Unusual sign-ins can trigger extra checks or a temporary hold. If you see a message about unusual activity, follow the on-screen steps. You may be asked to confirm a phone number, verify a code, or wait for a review to finish.
Work or school accounts
For Google Workspace accounts, admins can block older apps, limit IMAP, or require security keys. If you use a company laptop, policies may also limit embedded sign-in windows. If nothing here works, check with your admin about current sign-in rules.
When waiting is the right move
After several failed attempts, the system can slow down new tries. If recovery says to try again later, give it a day. Use the same device, the same browser, and the same network next time to improve your odds.