If Chrome is not saving passwords the way it used to, the browser itself is rarely the problem — the fix is almost always a setting you can flip back in under a minute.
Chrome’s built-in password manager stopped saving, filling, or showing passwords — new logins aren’t being prompted to save, existing passwords aren’t autofilling when you need them, or saved passwords have disappeared. Usually fixable in under 5 minutes once you know which layer is actually broken. For a broader walkthrough, our Google Chrome Errors is a good next read.
The fastest check: type chrome://password-manager/passwords directly in the address bar. This takes you straight to Chrome’s password list. If your passwords are there but not autofilling: autofill is broken but data is intact. If the list is empty when you know you had saved passwords: sync or a clear-data event removed them. If the “Save passwords” toggle at the top of chrome://settings/passwords is Off: turn it back on — that’s likely everything.
Chrome Not Saving Passwords? Start Here
The symptoms people search for all trace back to the same short list. Maybe Chrome won’t save passwords at all and the “Save password?” prompt never appears. Maybe new logins save fine but your saved passwords are not showing on another device. Or maybe Chrome stops offering autofill for credentials it clearly has stored. Each points to a different layer, so it is worth pinning down which one you are seeing before changing any settings.
The usual culprits, in the order worth checking them: the Save passwords toggle quietly switching off after an update, your account dropping out of sync so saved entries stay on a device you are no longer signed into, and a per-site “Never save” exception set long ago and forgotten. Work through the sections below in that sequence — toggle first, then sync, then exceptions — and you will clear the overwhelming majority of cases where Chrome stopped saving passwords, without disabling things that were never broken.
Save passwords toggle and autofill toggle
Two separate switches control Chrome’s password behaviour. Both need to be On:
- chrome://settings/passwords → “Offer to save passwords”: when Off, Chrome never asks if you want to save. When On, Chrome prompts after successful login.
- chrome://settings/passwords → “Auto Sign-in”: when On, Chrome signs in automatically to sites with one saved password. When Off, Chrome fills the form but doesn’t submit.
These are the two most-toggled settings that users accidentally turn off, often through privacy extension configuration or by clicking “Never” on a save prompt one too many times and forgetting they did it.
Site-specific “Never save” exceptions
Clicking “Never” on a password save prompt adds that site to a “Never saved” list — Chrome stops asking for that domain forever. This is easy to trigger accidentally and harder to remember doing.
Check: chrome://settings/passwords → scroll past the saved passwords list → “Never saved” section at the bottom → if the site where autofill isn’t working is listed there: click the X to remove it → Chrome will start offering to save passwords for that site again. You may need to log in once manually after removing the exception to get Chrome to save the credential.
Sync state — where passwords actually live
With Chrome Sync enabled, passwords are stored in your Google account and sync to all signed-in devices. If sync is paused or broken: passwords might exist in one place but not another.
Check sync state: click your profile picture in Chrome → look at the sync status. If it says “Sync is paused”: click through to sign back in. After sync resumes, passwords that exist in the Google account re-appear in Chrome within a minute or two.
Authoritative source for what’s actually in your account: visit passwords.google.com → sign in → see your saved passwords. If they’re visible there but missing in Chrome: sync isn’t pulling them through. If they’re not visible there either: they were deleted (from this account’s device, or deliberately).
A third-party password manager taking over
Grammarly, Dashlane, 1Password, Bitwarden, and LastPass all install browser extensions that sometimes intercept Chrome’s password autofill. When active, Chrome’s native password prompt may not appear because the extension captured the login event first.
Test: chrome://extensions → disable all extensions → visit a site → log in → does Chrome now prompt to save the password? If yes: an extension was intercepting it. Re-enable one at a time to find which, then configure that extension to allow Chrome’s native saving, or decide which password manager to use exclusively and disable the other.
Our guide on Chrome autofill troubleshooting covers the broader autofill issues including addresses and payment cards, and our Chrome stability and profile issues covers deeper profile corruption scenarios. For password import/export and the Google Password Manager web app, passwords.google.com provides direct access to your synced credentials and lets you export them to a CSV file as a backup.
Password autofill not triggering on specific sites
Chrome matches saved passwords to sites by URL. If a site changed its login page URL (moved from /login to /signin, added a subdomain, migrated from http to https), Chrome may not recognise the new URL as matching the saved credential.
Fix: chrome://settings/passwords → find the saved credential → click the three-dot menu → Edit → update the URL field to match the current login page. Or delete the old credential → log in manually → save when Chrome prompts.
Multi-step logins (username on one page, password on a separate page) confuse Chrome’s autofill. Chrome sometimes doesn’t recognise the password field until you’ve filled the username. Try: fill in the username → Tab to password field → right-click → see if “Autofill” option appears in the context menu. If it does but doesn’t auto-trigger: this is Chrome recognising the multi-step flow but not automatically filling it.
Site blocking Chrome’s autofill
Websites can use the autocomplete="off" or autocomplete="new-password" attribute to tell Chrome not to autofill password fields. This is common on banking sites, employee portals, and some enterprise applications. Chrome has gotten better at ignoring this attribute when it recognises a standard login flow, but some sites still successfully prevent autofill.
Workaround: right-click the password field → if “Autofill” appears in the context menu → click through Chrome’s own autofill menu even though the field blocked automatic filling. Chrome’s context-menu autofill can bypass the attribute block that prevents the automatic trigger. This doesn’t always work but succeeds on many sites that have technically blocked autofill.
A browser extension intercepting the login form
Password manager extensions — LastPass, 1Password, Bitwarden, Dashlane and the like — often rewrite login forms in ways that confuse Chrome’s own detection. Chrome sees the submission but never registers it as a credential being entered, so the save prompt never fires. The cleanest test is an Incognito window (Ctrl+Shift+N), where extensions are disabled by default: log in somewhere with credentials you know are not already stored. If the prompt appears in Incognito but not in a normal window, an extension is the cause — disable your password-manager extensions one at a time in regular Chrome to find which one.
Two-factor sites and multi-page logins
Sites that split sign-in across separate pages — username and password on one screen, a 2FA code on the next — frequently trip up Chrome’s detection, which never sees a complete login to offer saving. This is common with Microsoft accounts, banking portals, and enterprise SSO. The manual route works here: open chrome://password-manager/passwords and use Add to store the entry yourself. A dedicated password manager built around multi-step authentication will also handle these flows more reliably than Chrome’s built-in detector.
A site’s “Remember me” is not the same as a saved password
Some sites never show Chrome’s save bubble at all — instead they offer their own “Remember me” checkbox. That is entirely separate from Chrome’s password manager: ticking it sets a cookie or session token, it does not create a saved password. To check what actually happened, log in and then search the site at chrome://password-manager/passwords. If there is no entry, Chrome did not save anything, regardless of what the site’s own prompt implied.
Recovering lost passwords
If passwords were deleted (by clearing Chrome data, by someone else using your PC, or through Chrome Sync overwriting local data with an older state): recovery depends on the timeline.
Check Google account activity: myaccount.google.com → Security → Recent security activity → look for any “password sync deleted” type events. More useful: passwords.google.com → there’s a “Recently deleted” section that retains passwords for 30 days after deletion. Passwords deleted within the last month can be restored from there.
If more than 30 days have passed: no cloud recovery path exists. If you had local backups (Chrome export to CSV done previously): import via chrome://settings/passwords → three-dot menu → Import passwords → select the CSV file. This is why periodic exports are worth doing.
Enterprise managed Chrome and password restrictions
On corporate Chrome: IT policies can disable password saving, disable sync, or require passwords to be managed through a corporate credential store (like Microsoft Entra ID or a corporate SSO). If chrome://settings/passwords shows “Some settings are managed by your administrator” and the toggle is locked: IT has disabled it by policy.
There’s no local workaround for this. The password manager being disabled on a managed device is intentional (common in environments where credentials must flow through SSO, not local browser storage). Use your corporate password manager or SSO as intended.
Profile corruption affecting passwords
If passwords are visible in passwords.google.com but missing in Chrome, and sync appears connected: the local profile’s password store may be corrupted. Test in a new Chrome profile (profile icon → Add → continue without account → visit a site). If Chrome can save passwords in the new profile: the main profile is corrupted.
Fix for corrupted profile: chrome://settings/reset → “Restore settings to their original defaults” → this doesn’t delete passwords from Google but does clear the local sync state, forcing Chrome to re-download passwords from the cloud. After reset: re-enable Chrome Sync by signing back in → passwords repopulate within minutes.
| Issue | Most likely cause | Fix |
| Chrome never asks to save | “Offer to save passwords” is Off | chrome://settings/passwords → toggle On |
| Won’t save one specific site | Site in “Never saved” list | Remove from Never saved section in password settings |
| Saved but not autofilling | URL mismatch or site blocking | Edit saved credential URL; use right-click autofill |
| Passwords disappeared | Sync issue or clear data event | Check passwords.google.com; recently deleted; sync state |
| Save prompt not appearing | Extension intercepting | Disable extensions; identify which is capturing the event |
| Settings locked/greyed out | Enterprise policy | Managed device — contact IT |
The toggle check and the “Never saved” site list together resolve the majority of password saving issues in under 2 minutes. The sync check and passwords.google.com visit resolves most “passwords disappeared” scenarios. These are the right first steps before considering anything more involved like profile resets or extension audits.
Chrome’s password generator
Chrome offers to generate strong passwords when you’re creating a new account. If the password generator isn’t appearing: right-click a password field → Chrome should show “Suggest strong password.” If it doesn’t appear: the page may have a non-standard password field, or the feature may be disabled.
Enable: chrome://settings/passwords → “Offer to save passwords” must be On (generator won’t appear if saving is disabled). For sites where it doesn’t trigger: chrome://flags → search “Password” → there are experimental password generation flags that may affect this on some Chrome versions.
The generator creates a unique complex password and automatically saves it — you don’t need to remember or write it down. The critical step: ensure “Offer to save passwords” is on before using the generator, or Chrome generates a password it then can’t save, and you’re locked out of the new account immediately.
Biometric unlock for password manager
On Windows 11 with Windows Hello configured: Chrome can optionally require biometric verification (fingerprint or PIN) before autofilling passwords. Settings → chrome://settings/passwords → “Use your screen lock to verify it’s you” → when enabled, Chrome asks for your Windows Hello authentication before filling a password.
If Chrome is asking for your screen unlock before autofilling and you don’t want this friction: that toggle is the setting to disable. If Chrome is NOT asking and you want it to (for additional security on a shared machine): enable it. It’s a security preference, not a requirement.
Exporting and backing up saved passwords
Chrome has a built-in password export feature: chrome://password-manager/passwords → three-dot menu (top right) → “Export passwords” → downloads a CSV file with all saved credentials in plaintext. Store this file somewhere secure — it contains every saved username and password in readable form.
Do this periodically (monthly is reasonable) and keep the file in encrypted cloud storage or a password manager that itself handles the CSV. This export serves as recovery if Chrome data is lost, if you switch browsers, or if sync breaks and cloud passwords are unavailable. Once exported: import into any major password manager (1Password, Bitwarden, Dashlane, or another browser) by selecting “Import from CSV” and mapping the column fields.
Migration to a dedicated password manager
Chrome’s password manager is convenient but has limitations: no secure notes, no two-factor authentication storage, limited sharing, no breach monitoring on the free tier. If you’re having recurring password issues and use many sites: a dedicated password manager is worth considering.
Bitwarden (free tier excellent), 1Password (~£3/month), and Dashlane cover the gaps. They all import from Chrome’s exported CSV directly and install as Chrome extensions that replace Chrome’s native autofill. The transition takes about 30 minutes total; after that, passwords are managed more robustly with better cross-platform support and actual security features around the credential store.
For users who want to stay with Chrome’s password manager: it works well for most everyday needs. The main maintenance habit is periodic export-to-CSV as backup, and keeping Chrome synced to a Google account so credentials survive any single device failure or Chrome profile corruption.
Password import from another browser
If you’re moving from Firefox, Edge, Safari, or another browser to Chrome and expected your passwords to carry over: they don’t automatically. Chrome prompts once during first setup; if you skipped it, passwords stayed in the other browser.
Import now: chrome://settings/passwords → three-dot menu → “Import passwords” → “Select file” if you’ve already exported a CSV. Or use the dropdown to import directly from another browser on the same machine (Chrome reads Firefox and Edge’s local password databases directly, no export needed). The imported passwords appear immediately in Chrome’s password list and are available for autofill right away.
Using the Password Checkup feature
chrome://settings/passwords → “Check passwords” (or “Go to Password Checkup”) → Chrome checks your saved passwords against known data breach databases. Passwords found in leaks are flagged as “Compromised,” weak passwords show separately, and reused passwords get their own category.
This is one of Chrome’s more useful password manager features and runs locally with a privacy-preserving protocol (your actual passwords don’t get sent to Google’s servers — only a partial hash). Running this once after setting up the password manager gives you a prioritised list of passwords to change. Focus on the Compromised ones first; those credentials are actively in circulation and need immediate replacement.
The practical bottom line for Chrome password manager issues: check the save toggle, check the Never saved list, verify sync is connected, and visit passwords.google.com to confirm what the cloud actually has. These four quick checks explain and resolve the great majority of password saving and autofill failures, usually in under 3 minutes. If this sounds familiar, How to Fix Firefox Sync Not Working is worth a look.
