Chrome Autofill Stopped Working? Here Is Why

You start typing your address, and nothing drops down. Or the dropdown appears and fills one field out of six. Or it worked last week on this exact form and stopped.

Autofill fails in four distinguishable ways, and the most common one is not anything you did. Chrome has to recognise a form before it can fill it, and a site that builds its fields unconventionally is invisible to that matching regardless of what is in your settings.

Work out which case you have before changing anything.

Which failure is yours

Confirm the data exists

Open chrome://settings/autofill. Chrome splits this into separate stores, and people frequently assume one covers all three:

• Addresses and more — names, addresses, phone numbers, email.
• Payment methods — cards, with the number encrypted.
• Passwords, which now live at chrome://password-manager.

Each has its own on/off toggle. Check that Save and fill addresses (and the payment equivalent) is actually on, and then check that the entry you expect is in the list.

This is the step that resolves a surprising share of cases. Chrome only saves an address after you have submitted a form and accepted the save prompt, and a prompt dismissed once is not offered again for that entry. If the address is not listed, autofill was never going to offer it. Click Add and enter it manually.

Same for cards. A card saved to your Google account rather than locally shows with a cloud marker and may require confirmation each time, which some people read as autofill being broken.

When the site is the problem

If autofill works everywhere except one site, the site is why. Chrome identifies fields by their name, type and autocomplete attributes, and three common patterns defeat it:

• autocomplete="off" on the form or fields. Banks and payment pages do this deliberately. Chrome ignores the attribute for passwords but still honours it in places for addresses and cards.
• Non-standard field names. A field named field_7b carries no clue about what belongs in it. Chrome does a reasonable job of inference from labels and surrounding text, but it is inference and it fails.
• Fields built by JavaScript after load, or split into several boxes — a phone number across three inputs, a card number across four. Chrome fills the first and leaves the rest.

There is no setting that fixes any of this, and that is the honest limit of this guide. What you can do instead:

• Double-click an empty field. This sometimes triggers the dropdown when typing does not.
• Type the first two characters of the value rather than clicking in and waiting. Matching is prefix-based.
• Paste from your saved entry. Open chrome://settings/autofill in a second tab and copy from there for a long form.
• Use a password manager extension for sites Chrome will not handle. Most handle hostile forms more aggressively than Chrome does, because they are willing to ignore autocomplete="off" in cases Chrome will not.

When it stopped suddenly

Check sync is actually running

Addresses, cards and passwords travel through Chrome sync. If sync has paused — commonly after a password change, an account security event, or a long gap between uses — new entries stop appearing on other devices while existing ones remain.

Click your profile icon. A paused sync shows an explicit message there. Sign in again when prompted.

If the data is missing on one device and present on another, that is sync rather than autofill, and the entries are safe. Checking where your Google account is signed in is useful if you suspect something ended the session.

Check you did not clear it

The delete-browsing-data dialog has an Autofill form data checkbox on its Advanced tab. It is easy to tick while clearing something else, and it takes addresses and card entries with it.

Clearing the cache alone never affects autofill. If you are not sure what you cleared, what each browsing-data checkbox destroys sets out the boundaries.

Cleared autofill data that was synced may still be recoverable from another signed-in device that has not yet synced the deletion, but do not count on it — sync propagates deletions quickly.

Test in a Guest window

Profile icon → Guest. Autofill will be empty there, so this test is only useful for one thing: checking whether a form that refuses to fill in your profile offers to save a new entry in Guest. If it does, your profile has a problem rather than the site.

An extension can also suppress the dropdown. Form fillers, password managers and privacy extensions all interact with the same fields, and two of them competing on one form produces exactly the “nothing appears” symptom. The systematic way through that is in how to find which Chrome extension is slowing you down, which uses the same halving method for any extension-caused misbehaviour.

Removing bad entries

A typo saved into autofill will be offered forever. Two ways to remove one:

• From the dropdown: highlight the bad suggestion with the arrow keys, then press Shift+Delete.
• Properly: chrome://settings/autofill → Addresses and more → the ⋮ beside the entry → Delete.

Do the second for anything containing an old address or a card you no longer hold. Entries persist across devices through sync, so removing it once removes it everywhere.

About saved cards

Worth being clear about the risk, because it is physical rather than technical. Card numbers are stored encrypted, and Chrome requires your device password, PIN or fingerprint before filling the security code.

What that protects against is someone reading the profile files. What it does not protect against is someone using your unlocked computer — on sites that do not require the CVC, a saved card fills and submits with no challenge at all. If you share a machine, do not save cards to it.

What to expect

Checking chrome://settings/autofill and finding the entry simply absent accounts for a large share of cases, and adding it manually takes a minute.

Site-specific failures are the category with no fix. A checkout that refuses to autofill will keep refusing, and a password manager extension is the practical answer rather than any Chrome setting. That is unsatisfying, and it is nonetheless where that line sits.