When saved passwords stop autofilling, it can feel like everything is broken at once—especially if it works in one browser but not another. The good news: most fixes are settings-level and don’t require resetting your whole browser.
This guide focuses on differences between Chrome, Safari, and Firefox, so you can fix the right thing quickly.
Before you start: don’t keep retrying logins if a site is showing warnings like “too many attempts.” Fix autofill first, then try again.
1. Confirm you’re not in Private/Incognito mode (autofill rules change)
All three browsers treat private windows differently, and that’s a common reason autofill “mysteriously” disappears.
- Chrome: Incognito usually won’t use some form data, and extensions (including password managers) may be disabled unless you allowed them in Incognito.
- Safari: Private Browsing is stricter about remembering site state. Autofill can appear inconsistent if the site relies on cookies or cross-site logins.
- Firefox: Private windows can block logins/cookies more aggressively depending on Enhanced Tracking Protection settings.
Switch back to a normal window and try again on the same sign-in page.
2. Check the browser’s built-in password/autofill toggles (they’re different)
If autofill stopped after an update, a settings toggle is often the culprit—especially if you use the built-in password manager.
- Chrome: Settings → Autofill and passwords → Google Password Manager. Make sure password saving and auto sign-in/autofill are enabled.
- Safari (Mac/iPhone): Safari settings → Autofill. Ensure “User names and passwords” is enabled. Also check iCloud Keychain is enabled if you rely on it.
- Firefox: Settings → Privacy & Security → Logins and Passwords. Confirm “Ask to save logins and passwords” and “Autofill logins and passwords” are on.
Small detail that matters: Safari’s autofill is closely tied to Keychain/iCloud settings, while Chrome/Firefox can operate more independently.
3. Look for a password manager conflict (two systems fighting each other)
If you have a third-party password manager (1Password, Bitwarden, LastPass, etc.), you can end up with no autofill prompts because the browser’s built-in manager and the extension both try to “own” the field.
- Temporarily disable the password manager extension and test browser autofill.
- Or do the opposite: disable the browser’s built-in password saving/autofill and rely on the extension.
- In Chrome, also check the extension is allowed on that site and (if relevant) allowed in Incognito.
- In Safari, check Safari Extensions and ensure the password manager extension is enabled and has permissions.
- In Firefox, confirm the extension is enabled and not blocked by Enhanced Tracking Protection on the login page.
You’re aiming for one “source of truth” for autofill: either the browser or the password manager, not both.
4. Site-specific blockers: cookies, tracking protection, and “remember me” logic
Many login forms won’t trigger autofill correctly if the site can’t set the right cookies, or if a cross-site login flow gets blocked.
- Firefox: Enhanced Tracking Protection can block scripts that control the login form. Try clicking the shield icon and temporarily relaxing protection for that site.
- Safari: “Prevent cross-site tracking” can break certain identity providers (especially “Continue with…” buttons). Temporarily try turning it off for testing, then turn it back on.
- Chrome: Third-party cookie restrictions (and related privacy features) can affect sign-in flows, especially if the login happens in an embedded frame.
If autofill works on the site’s direct login page but not inside an in-app embedded window or popup, it’s often this.
5. Fix the “wrong account keeps filling” problem (it can look like autofill is broken)
Sometimes autofill is working—but it’s filling an old username, a hidden field, or a different subdomain’s login.
- On the login page, click the username/email field and look for a dropdown of saved logins. Choose the right one manually once.
- If the site uses multiple domains (for example, login.example.com vs www.example.com), you may have a saved password attached to the “other” domain.
- If you recently changed your password, delete the outdated saved entry and save the new one fresh.
Browser differences here: Safari often groups credentials differently via Keychain, while Chrome/Firefox may store separate entries per domain and form structure.
6. Last-resort, low-risk resets (avoid the nuclear options)
If nothing above helps, try these in order. Each one is reversible or limited in scope.
- Reload the page and try the field again (some login pages load the real form after scripts run).
- Try a different profile (Chrome) or a fresh browser profile (Firefox) to rule out corruption—without deleting anything.
- Clear site data for just that website (not full history). This often fixes stuck login states that interfere with autofill prompts.
- Update the browser, then fully quit and reopen it (not just close the window).
If you’re using iCloud Keychain (Safari) or Google Password Manager (Chrome), make sure sync is on and currently healthy before making major changes.
Final thoughts
Chrome, Safari, and Firefox can all “lose” autofill for different reasons—Safari tends to be Keychain- and privacy-setting-sensitive, Firefox is often tracking-protection-related, and Chrome commonly runs into profile/extension conflicts.
If you fix it in one browser but not the others, treat that as a clue: it’s usually a browser setting or privacy feature, not your account password itself.