Chrome autofill is one of those features you only notice when it stops working. Suddenly you’re typing your name and address into every form, or your saved passwords aren’t filling, or the form field suggestions just disappeared. The cause is almost always one of: autofill got disabled in settings, the site is preventing autofill via HTML attributes, or your Chrome profile’s sync is out of state. For the bigger picture, our Google Chrome Errors pulls everything together.
Start here: open chrome://settings/autofill. You’ll see three sections — Passwords, Payment methods, and Addresses. If any of those have been toggled off, Chrome won’t fill for that data type. The toggle for passwords (“Offer to save passwords”) and the toggle for addresses (“Save and fill addresses”) are completely independent — you can have one on and the other off. Check all three sections and re-enable anything that’s off.
Why autofill silently breaks
The most common trigger: Chrome updated and reset a setting. This is rarer than it used to be but still happens occasionally. Second most common: a sync conflict where your profile on one device had autofill off, and that setting propagated through Chrome Sync to overwrite all your devices. Third: an extension (particularly ad blockers or privacy tools) is blocking the autofill script that fills the form.
One thing most users don’t know: Chrome autofill has a separate enable switch from the password manager. You can have saved passwords that don’t autofill, and separate address autofill that works or doesn’t independently. “Autofill isn’t working” usually means one specific data type — passwords, addresses, or payment cards — rather than all three simultaneously failing.
Site-specific autofill blocks
Many websites deliberately prevent autofill using autocomplete="off" attributes on form fields. Banks, government sites, and authentication forms especially. The reason varies: security concerns about autofilled data on shared machines, preventing users from saving wrong data, or just legacy implementation choices.
When a site blocks autofill: Chrome respects it and doesn’t fill, even if autofill is globally enabled. You’ll notice the dropdown doesn’t appear, nothing fills when you click into the field, and there’s no autofill icon in the field corner.
Workaround: right-click the form field → the context menu sometimes still shows “Autofill” even when the field has autocomplete=off, and clicking through Chrome’s own menu can override the site’s attribute. This isn’t guaranteed to work but does sometimes. The more reliable workaround: save the data in a password manager (Bitwarden, 1Password) and use its fill keyboard shortcut instead of relying on Chrome’s native autofill.
Extensions interfering
This is the second most common real-world cause. Privacy extensions like uBlock Origin, Privacy Badger, and Ghostery can block the JavaScript events that Chrome autofill uses to detect fillable fields. Some ad blockers are configured to block form detection scripts wholesale.
Test: open a site where autofill fails → try in Incognito (Ctrl+Shift+N, which runs without extensions by default) → try typing the first letter of your address. Does autofill appear in Incognito? If yes, an extension is blocking it in normal Chrome.
Find which: chrome://extensions → toggle off extensions one by one → reload the site between each → autofill appears when you’ve disabled the offender. Then adjust that extension’s settings (whitelist the site) rather than disabling it entirely.
Google account sync issues
If Chrome Sync is enabled, your autofill data (passwords, addresses, payment methods) lives in your Google account and syncs to all your devices. If sync is paused, broken, or in a conflict state, Chrome may show empty autofill fields even though data exists.
Check sync: click your profile picture in Chrome → look for the sync status. If it says “Sync is paused” or shows an error → click it → sign back in. After re-establishing sync, Chrome downloads your saved autofill data again and fills should work.
Also: chrome://settings/syncSetup → check that “Autofill” and “Passwords” are both checked under what syncs. If “Autofill” was unchecked on any device and that unchecked state propagated: re-enable it.
Our guide on Chrome loading problems covers the broader profile and sync issues, and our Chrome crash diagnosis covers cases where autofill fails because Chrome itself is unstable. For password manager configuration including how to export and re-import saved passwords, Google’s Chrome autofill documentation covers the password and address data management tools.
Passwords specifically not autofilling
Password autofill is managed separately from address/payment autofill. When passwords stop filling but everything else works: chrome://passwords (or chrome://settings/passwords) → check the saved passwords list. Is the site’s password there? Click the eye icon to verify the saved password is correct.
Common reasons passwords stop autofilling even when saved:
- The site changed its URL structure (login moved from /login to /signin) and Chrome doesn’t match the new path to the old saved credential
- The site uses a two-step login where username and password are on separate pages — Chrome sometimes doesn’t recognise the password field until you’ve filled the username
- The form uses dynamically generated field names, which fool Chrome’s matching logic
- The site flags the password field as
autocomplete="current-password"inconsistently across pages
For URL mismatches: in chrome://passwords, click the credential → edit → update the URL to match the current login page path. For two-step logins: click into the password field after the username step, then use Ctrl+Shift+F (fill autofill shortcut) or right-click → Autofill.
Payment cards not filling
Credit card autofill in Chrome works through Google Pay integration. Cards are stored either locally or in your Google account. If cards aren’t filling: chrome://settings/payments → check if any cards are listed. If none: they haven’t been saved yet.
Adding a card: next time you make a purchase, Chrome prompts to save it. Or: chrome://settings/payments → “Add payment method” → enter card details manually. Cards saved to your Google account sync across devices; cards saved locally (not to Google) stay on just that browser.
Some users find Chrome prompts to fill cards but the form then rejects the autofilled data (especially CVV, which many sites re-verify for security). Chrome fills what it can; the site sometimes clears specific fields for security reasons immediately after. This looks like “autofill didn’t work” but Chrome actually did its job — the site’s script cleared the sensitive field intentionally.
Clear autofill data for specific entries
Sometimes autofill offers wrong suggestions — old addresses, former email addresses, outdated names. Clearing specific entries (rather than all autofill data) is cleaner than a full reset:
- Click into a form field where the bad suggestion appears
- Chrome shows a dropdown with autofill suggestions
- Hover over the unwanted entry → click the X or three-dot menu → “Remove”
- For addresses saved in your Google account: chrome://settings/addresses → edit or delete individual entries
This is much better than clearing all autofill data (which loses every address and payment card) when you just need to remove specific outdated entries. One less frustrating use case: Chrome sometimes remembers old autocomplete suggestions from text you’ve previously typed (not from the formal address book) — these appear as lighter-coloured suggestions vs the card-icon suggestions from your saved addresses. They can be deleted the same way.
Autofill on mobile forms visited from desktop
If Chrome autofill works on desktop but not on mobile (or vice versa), it’s usually a sync state rather than the autofill feature itself. Ensure you’re signed into the same Google account on both, and that autofill types are set to sync in both directions.
Chrome on Android specifically: Settings → Google Password Manager → settings → “Offer to save passwords” must be on. Same for addresses and payment methods. Mobile Chrome has its own settings page that isn’t always reflected in the desktop chrome://settings/autofill view.
When autofill data seems to disappear
Users occasionally report all their saved addresses and passwords vanishing overnight. The actual causes are usually one of:
- Chrome’s “Clear browsing data” was run with “Autofill data” and/or “Passwords and other sign-in data” checked — easy to do accidentally with “All time” selected
- Another Chrome user profile on the same machine cleared data
- A sync conflict resolved by deleting the local data and re-downloading, but sync itself wasn’t working so data didn’t restore
- A child account or managed profile with restricted autofill was selected by mistake
If passwords vanished: check passwords.google.com — Google’s account stores your Chrome-synced passwords independently. If they’re visible there, they just haven’t synced back to Chrome yet. Sign out of Chrome → sign back in → sync re-runs → passwords restore.
Reset autofill settings without losing data
chrome://settings/reset → “Restore settings to their original defaults” → this resets Chrome settings including autofill configuration, but does NOT delete saved passwords or addresses from your Google account (they’re account-side, not settings-side). After reset, go back to chrome://settings/autofill and re-enable what you want. This resolves settings-state corruption without data loss.
| Autofill type failing | First check | Likely fix |
| Passwords | chrome://passwords — is credential saved? | Verify saved URL matches login page; check sync |
| Addresses | chrome://settings/addresses — are entries there? | Re-enable “Save and fill addresses” toggle |
| Payment cards | chrome://settings/payments — cards listed? | Add card if missing; check Google Pay integration |
| Nothing autofills anywhere | Incognito test (does it work there?) | Extension blocking if Incognito works; settings if not |
| Works on some sites, not others | Is the site blocking with autocomplete=”off”? | Check site HTML; use password manager as fallback |
Chrome autofill is one of those features where the fix is almost always in settings or an extension, not in Chrome’s underlying code. The diagnostic path is: check the settings page first, test in Incognito second, then review sync state. Those three steps resolve the overwhelming majority of autofill complaints quickly.
Third-party password managers and Chrome autofill conflict
If you use 1Password, Bitwarden, Dashlane, or LastPass alongside Chrome’s built-in autofill, you have two separate fill systems competing. Sometimes they interfere: Chrome tries to fill, the extension overrides it; or the extension fills a field and Chrome immediately overwrites with its own suggestion.
The pragmatic approach: pick one system and disable the other. Either turn off Chrome’s saved passwords (chrome://settings/passwords → toggle “Offer to save passwords” to off, and clear existing saved passwords) and rely entirely on the third-party manager. Or remove the third-party extension and use Chrome’s built-in only.
Most security-conscious users prefer dedicated password managers for their stronger encryption and cross-browser/cross-device support. Chrome’s built-in autofill is fine for casual use. The important thing is not running both simultaneously with the same credentials saved in both — inconsistent fills, update conflicts, and general confusion follow.
Enterprise-managed Chrome restrictions
On corporate-managed Chrome installations, IT can restrict autofill via Chrome policy. Signs: chrome://settings/autofill shows “This setting is managed by your administrator.” You can’t re-enable autofill for the restricted category.
This is a policy choice, not a bug. Corporate IT often disables payment card autofill specifically (PCI compliance concerns) while allowing address and password autofill. Speak to IT if you need an exception — it’s a legitimate ask for roles that frequently use web forms professionally.
When to export your autofill data
Good practice regardless: export your Chrome passwords periodically. chrome://passwords → top-right three-dot menu → “Export passwords” → saves a .csv file. Store it somewhere secure (not in your Downloads folder).
Same for addresses: chrome://settings/addresses shows what Chrome has saved, but there’s no direct export UI. You can screenshot or manually record important entries.
Password export specifically protects you against the scenario where Chrome sync breaks and local data is lost without a Google-side backup. With an exported .csv, you can import into any password manager and start fresh. Not something you’ll need often, but having done it once means a sync catastrophe doesn’t also mean losing all your saved credentials.
Overall, Chrome autofill problems are rarely about the feature being genuinely broken — they’re almost always configuration, extension conflict, or site-side blocking. Fifteen minutes of systematic troubleshooting (check settings, test in Incognito, verify sync) resolves most issues without needing to touch anything more complicated.
One habit worth building: when Chrome asks “Would you like to save this password?” — actually click “Save.” The number of users who dismiss this prompt every time and then wonder why nothing autofills is surprisingly high. Chrome’s autofill is opt-in per credential; it won’t save anything you haven’t explicitly allowed. If you’ve been declining the save prompt for years, your password list is empty by design, not by accident. Enable auto-save (chrome://settings/passwords → “Offer to save passwords” → On) and start accepting the prompts going forward.
Similarly for addresses: Chrome only saves an address when you complete a form and accept the “Save your info?” offer. It doesn’t mine your contact book or guess your address. The first time you fill in a form with your current address and accept the save prompt, autofill has it for future use. After that it’s automatic — until something resets the settings or clears the saved data. If this sounds familiar, Fix Chrome Microphone Not Working is worth a look.
