VKT Toolkit · September 25, 2026 · 9 min read

Chrome Autofill Not Working? 8 Fixes That Actually Work (2026)

You click the first field, expecting the familiar blue dropdown. Nothing. Or worse: it fills your address from three apartments ago. Autofill failures feel random, but they are not. Seven of the eight causes below are on your side and take two minutes each to check. The eighth is structural — Chrome was never designed to fill the form that is actually annoying you.

Work through them in order. Each fix ends with how to tell whether it was the culprit.

First: Which Autofill Is Broken?

Three different things are called autofill, and the fix depends on which one you are looking at:

• Chrome's built-in autofill — the blue dropdown of saved addresses, names, emails and cards.
• Your password manager's fill — the icon inside the field, or a keyboard shortcut, driven by your vault.
• A form-filling extension — a separate toolbar panel or hover button that replays saved values.

Quick test: open any simple checkout-style page and click a name field. If the built-in dropdown appears there but not on your work form, nothing is broken — you are asking identity autofill to do a job it does not have. That is the case Fix 8 addresses.

Fix 1 — Check That Chrome Has the Data

Autofill cannot offer what it does not store. Open chrome://settings/autofillAndPasswords (or Settings → Autofill and passwords) and look at Addresses and more and Payment methods. Empty lists mean there is nothing to fill.

While you are there, check the other entries. Duplicates and stale addresses are the usual reason autofill fills the wrong value: Chrome takes the first match, and a saved-forgotten apartment can beat your current one. Delete anything you no longer use.

Fix 2 — Turn Autofill Back On

Two toggles matter, and both are easy to switch off while cleaning up privacy settings:

• Save and fill addresses — off means Chrome still stores what you typed but never offers it.
• Save and fill payment methods — the card equivalent, usually off by default.

On a managed work machine, also open chrome://policy and search for AutofillAddressEnabled. If your administrator set it to false, autofill is disabled at the policy level and no setting on your side will bring it back. Ask IT rather than hunting further.

Fix 3 — Sync, Profiles and Guest Windows

Autofill data is per profile. A few situations that look like a bug:

• Signed out of Chrome. Your data stays local to that profile; if the profile was created fresh on this machine, it starts empty.
• More than one profile. Work and personal profiles have separate stores. Your address saved in the personal profile is invisible in the work one.
• Guest window. Guest mode is designed to leave no trace, so it never fills saved values.
• Incognito. Also empty by design, and extensions are off unless you allow them individually.

Test it by opening the same page in your normal window. If it fills there, you were in the wrong window all along.

Fix 4 — The autocomplete Attribute

Field markup decides whether Chrome will even try. The usual blockers:

• autocomplete="off" — modern Chrome often ignores it for identity fields, but some sites combine it with other signals.
• autocomplete="new-password" — explicitly tells Chrome this field must not be filled with a saved value.
• Meaningless names. A field called input_17 with no id and no label gives the heuristic nothing to work with.
• Not an input at all. Custom company pickers and select boxes built from div elements are invisible to autofill, however they look on screen.

How to check: right-click the field → Inspect, and read the name, id and autocomplete attributes. If they are meaningless, no amount of settings fiddling will fix it.

Fix 5 — Fields Inside iframes and Shadow DOM

Some fields are physically outside the page Chrome is filling:

• Cross-origin iframes — payment widgets, embedded booking engines, single sign-on panels. Chrome does not push saved addresses across into a third-party frame.
• Shadow DOM — design-system components that render their inputs in an isolated tree. The field works, looks normal, and stays invisible to autofill heuristics.

Test: click the dead field and check Chrome's element inspector. If the markup sits inside an <iframe> or a #shadow-root, you have found the reason.

Fix 6 — Extensions Fighting Over the Same Form

Two fillers on one page produce chaos: one clears what the other wrote, or a dropdown opens and closes instantly. Suspects are password managers, other form extensions, and aggressive privacy tools that block the APIs fillers rely on.

Test properly: open a fresh profile with no extensions and load the form. If it fills there, re-enable your extensions one at a time until it breaks again.

Fix 7 — SPA Re-Renders and One-Time Fields

• React and Vue re-renders. If a component re-renders after a value is injected, the field can be wiped seconds later. Autofill looks broken; it actually worked and was overwritten.
• Masked inputs. Phone and card fields that reformat as you type sometimes reject a value injected all at once.
• One-time fields. OTP codes, timestamps and today's date are, by definition, not worth remembering — and many sites actively discourage caching them.
• Upload fields. File inputs are outside the reach of any autofill, including extensions.

Fix 8 — When Chrome Is the Wrong Tool

If everything above checks out and the form still refuses to fill, the problem is the category of tool, not the settings. Chrome autofill solves an identity problem: it recognizes "this is a postcode" and offers your postcode. The form eating your Monday solves a repetition problem: the same fourteen fields, filled the same way, every week.

Match the symptom to the cause:

For that last category there is a purpose-built option: VKT Form records the whole state of one form — every field's value — as a local snapshot bound to that form's URL, and replays it in one click. Matching weighs each field's name, id, label and structure, with DOM order as a fallback, so custom and framework-rendered fields are covered as well as plain ones. Snapshots live in chrome.storage.local: no account, no analytics, no upload. The free tier carries 5 snapshots with unlimited fills; Premium removes the cap and adds JSON export/import for $9.99 one-time (lifetime) or $2.99/month.

Honest limits, so you do not expect magic: it does not fill passwords or card numbers (those belong in a password manager), it cannot touch file uploads or drag-and-drop widgets, and it fills fields — it never clicks Submit for you.

Frequently Asked Questions

More VKT tools live in the extensions catalog, or reach us at [email protected].