Chrome autofill is one of those features I only notice when it breaks. One morning my login credentials filled in instantly; the next, Chrome stared blankly at an empty field while I dug through a password manager I thought I’d retired. After fixing this on my own machine and a half-dozen family laptops, I’ve found that broken Chrome autofill almost always traces back to one of five settings or sync issues. None of them require reinstalling the browser, and most take under five minutes.
This guide walks through each fix in order, from the quickest toggle check to a full settings reset, so you can stop the blank-form frustration without guessing.
Quick Answer
Open chrome://settings/autofill and confirm that Passwords, Payment methods, and Addresses are all switched on. If they are, clear Chrome’s site data for the affected page, then disable extensions one at a time to find any that block autofill. Re-syncing your Google account fixes most of the cases that remain.
Why does Chrome autofill stop working?
Chrome’s autofill system handles three separate types of saved data — passwords, payment cards, and addresses — and each one is controlled by its own toggle. Any of those can be silently switched off by a browser update, a third-party extension conflict, or a corrupted cache entry. The first time it happened to me, the culprit was a Chrome update that quietly reset my Passwords toggle overnight.
Before diving in, confirm which type of autofill broke: passwords for logins, addresses for checkout forms, or payment cards. That single check narrows your fix straight away.
Autofill rarely breaks site-wide — it usually fails for one data type because one toggle, extension, or cache entry went sideways.
How do I confirm autofill is actually enabled?
Start here, because a flipped toggle is the single most common cause and the fastest to rule out.
- In the Chrome address bar, type chrome://settings/autofill and press Enter.
- Click Passwords and make sure Offer to save passwords and Auto Sign-in are both on.
- Click the back arrow, open Payment methods, and enable Save and fill payment methods.
- Open Addresses and more and enable Save and fill addresses.
If a toggle is already on but passwords still don’t appear, scroll down the Passwords page and check whether Chrome has a saved entry for that site. If the list is empty, Chrome has nothing to fill — save the password manually once, and it will autofill on every later visit. My own “broken” autofill turned out to be exactly this: no entry had ever been saved.
A toggle that’s off, or a site with no saved entry, accounts for more autofill failures than every other cause combined.
Will clearing the cache fix autofill on one site?
Often, yes. A stale or corrupted cache entry can confuse Chrome’s form-detection engine on a single page while every other site fills normally. You don’t need to wipe your entire history — clearing just the affected site is enough.
- Navigate to the site where autofill fails.
- Click the padlock or tune icon in the address bar, then choose Site settings.
- Scroll down, click Delete data, and confirm.
- Reload the page and try the form again.
When the problem spans several sites instead of one, a full cache clear is the better move — my guide to clearing browser cache and cookies covers the cross-browser steps.
Per-site data deletion fixes a single stubborn form without signing you out of every other account you use.
Could a browser extension be blocking autofill?
Frequently. Password managers, ad blockers, and privacy extensions intercept Chrome’s autofill engine, especially when they’re out of date, and an extension conflict is the most common reason autofill suddenly breaks after a Chrome update.
- Go to chrome://extensions and toggle every extension off.
- Reload the page with the form and test autofill.
- If it works, re-enable extensions one at a time, testing after each, until the culprit reappears.
While you’re in there, it’s worth pruning extensions you no longer use — my Chrome memory guide walks through auditing them properly. Note that Dashlane, LastPass, 1Password, and Bitwarden all disable Chrome’s built-in autofill by design; if you run one, its extension, not Chrome, fills your credentials, so make sure it’s enabled and signed into the right account.
If autofill broke right after an update, an outdated extension is the first thing I check.
How do I re-sync my Google account to restore autofill?
Chrome syncs autofill data through your Google account, so a sign-in hiccup can leave the local browser with empty data even when the records still exist online. This is the classic “works on my phone but not my laptop” symptom.
- Click your profile icon at the top-right. If you see a sync error banner, click Fix and sign in again.
- Otherwise go to chrome://settings/syncSetup, toggle sync off, wait 10 seconds, then turn it back on.
- Wait 30 to 60 seconds, reload Chrome, and test the form.
You can verify your saved passwords at Google Password Manager; if they appear there, they should sync back to Chrome within a minute of re-enabling sync.
Re-syncing fixes autofill that works on one device but not another, since the data lives in your account, not the browser.
What if nothing works and I need to reset Chrome?
When every other step fails, a settings reset clears corrupted autofill preferences without touching bookmarks, history, or saved passwords.
- Go to chrome://settings/reset.
- Click Restore settings to their original defaults.
- Confirm the reset; bookmarks and passwords are not affected.
- Return to chrome://settings/autofill and re-enable all three toggles, because the reset turns them off.
I reset only as a last resort, because re-enabling the toggles afterward is easy to forget and looks exactly like the original problem.
A reset wipes corrupted preferences safely, but you must switch the autofill toggles back on yourself.
Which fix matches your symptom?
If you’d rather skip straight to the likely cause, match your exact symptom to the fix below.
| Symptom | Most likely cause | Best fix |
|---|---|---|
| Passwords never suggested on login | Offer to save passwords toggle off | Confirm toggles are on |
| Addresses missing at checkout | Addresses toggle off or no entry saved | Check and add an address |
| Used to work, suddenly stopped | Extension conflict after a Chrome update | Disable extensions |
| Works on one device, not another | Sync error or signed out | Re-sync account |
| All autofill broken at once | Corrupted preferences after update | Reset settings |
Most failures map to one row here, so identify your symptom before working through every step.
Common Mistakes to Avoid
- Assuming the website is broken. Most “this site won’t autofill” problems are a Chrome setting, not a site bug. Check the toggles before blaming the page.
- Wiping all cookies at once. Clearing cookies site-wide signs you out of every account simultaneously. Use per-site data deletion to target only the problem page.
- Running two password managers together. Chrome’s built-in autofill and a third-party extension fighting each other means neither fills reliably. Pick one and disable the other’s autofill feature.
- Forgetting to save the password the first time. If you dismissed Chrome’s “Save password?” prompt, there’s nothing stored to fill. Use my saved passwords guide to add credentials manually.
- Testing in Incognito and expecting autofill. Chrome disables autofill in Incognito by default; the private browsing explainer covers what Incognito does and doesn’t change. Always test in a normal window.
Skip these five traps and you avoid the mistakes that send most people in circles before they find the real toggle.
Frequently Asked Questions
Why does Chrome autofill work on some sites but not others?
Some sites deliberately block autofill with the autocomplete="off" HTML attribute, and Chrome respects it. For example, my bank’s login page never autofills no matter what I change, because the bank set that attribute for security — so I type those credentials manually.
Does clearing the cache delete my saved passwords?
No. Saved passwords live in Chrome’s Password Manager and sync to your Google account, not in the cache. When I cleared a misbehaving shopping site’s data last month, my login still autofilled on the next visit because the password was never stored in the cache to begin with.
Why did autofill stop working after a Chrome update?
Major updates occasionally reset autofill toggles or introduce extension conflicts. After one update my Passwords toggle had flipped off on its own, so I now check the toggles and my extensions first whenever autofill breaks right after Chrome updates.
Can Chrome autofill a username but not a password?
Yes, and it usually means the password wasn’t saved alongside the username or the site uses a two-step login. I hit this on a site that asks for the email first; opening chrome://password-manager/passwords showed the username stored with no password next to it.
Is it safe to let Chrome autofill payment card details?
Generally yes — Chrome encrypts saved card data and fills it only on HTTPS pages. For extra safety I enabled the verification option in chrome://settings/payments, which now asks for my device PIN before any card number fills.
How do I stop Chrome from autofilling on one specific site?
Open the site, click the padlock, choose Site settings, then Delete data. I did this for a coworking-space portal I only use once a year, then dismissed the “Save password?” prompt so Chrome stopped re-saving it.
Conclusion
Chrome autofill breaks for a short, predictable list of reasons — a disabled toggle, a corrupted cache entry, an extension conflict, or a sync hiccup. Work through these fixes in order and you’ll likely be back to one-click logins in a few minutes. To take full control of everything Chrome has stored, read my saved passwords guide next.