Chrome autofill not working covers several different problems — addresses not filling, passwords not suggesting, credit cards not appearing, or form fields not getting detected at all. The fix for each is different, so it’s worth spending 10 seconds identifying which type of autofill isn’t working before trying anything. We go deeper on the whole subject in our Google Chrome Errors.
The password side has its own deeper guide: when Chrome stops saving or filling your passwords specifically, the causes (the save toggle, sync state, login-form detection) differ from why an address or card fails to fill.
Passwords not suggesting → chrome://password-manager/settings → confirm “Offer to save passwords” and “Auto sign-in” are both on.
Addresses not filling → chrome://settings/addresses → check whether addresses are saved and whether autofill is enabled there.
Payment methods not appearing → chrome://settings/payments → verify cards are saved and the toggle is enabled.
If all three are enabled but autofill still doesn’t work: continue to the fixes below.
The Incognito test
Open an Incognito window (Ctrl+Shift+N) and try the same form. If autofill works in Incognito: an extension is interfering with autofill in regular Chrome. Commonly: password manager extensions (LastPass, 1Password, Bitwarden) that replace Chrome’s native autofill, form-filling extensions, or privacy extensions blocking form field detection.
Disable extensions one at a time in chrome://extensions, reloading the form after each, until autofill starts working. The extension that broke it when enabled is the one to remove or reconfigure.
Site-specific autofill failure
When autofill works on most sites but fails on a specific one: that site may have autocomplete="off" on its form fields, which tells browsers not to autofill. Chrome has been progressively ignoring this for passwords (since it’s often set for the wrong reasons), but still respects it for addresses and payment fields on many sites.
Banks, government portals, and financial sites commonly use this. There’s no Chrome-side setting to override it for addresses — it’s the site’s choice. For passwords: Chrome generally fills them anyway now, but older Chrome versions and some specific site configurations still block it.
Autofill suggestions appear but don’t fill
You see the autofill dropdown, click a suggestion, and nothing fills in: the form field might not accept the format Chrome is sending. Common with custom form implementations (JavaScript-driven forms, SPA frameworks like React/Vue where form fields don’t behave like standard HTML inputs).
Try: click on the suggestion, then immediately press Tab to move to the next field. This sometimes completes the fill that clicking alone doesn’t trigger. Also try the keyboard: press down arrow to select the autofill suggestion rather than clicking.
No autofill dropdown appearing at all
This is usually one of three things:
- The form field isn’t recognised as an autofill-eligible field (no name, id, or autocomplete attribute that Chrome recognises)
- Autofill is completely disabled in Chrome settings
- A corrupted Chrome profile is preventing autofill from initialising
Check chrome://settings/autofill — the master switch for all autofill. If it’s off: enable it. If it’s on but still not working: test in a new Chrome profile (click the profile icon → Add → Continue without signing in → test the same form).
Clearing stale autofill data
Chrome remembers form inputs separately from saved addresses/passwords. These free-form cached inputs (the generic autocomplete suggestions based on what you’ve typed before) can become corrupted or contain wrong data that appears when autofill should be suggesting saved structured data instead.
Ctrl+Shift+Delete → change Time range to “All time” → check “Autofill form data” (not “Cookies” or “Passwords” — those are separate) → Clear data. After clearing, the cached form suggestions are gone. Structured data (saved addresses, passwords, payment methods) stays in place since it’s stored separately.
Google Pay and payment autofill
Payment method autofill requires the card to be saved either locally in Chrome or in Google Pay (if signed into a Google account). If a card shows in Google Pay on your phone but not in Chrome’s payment autofill: ensure Chrome is signed in with the same Google account → chrome://settings/payments → “Payment methods from Google Pay” toggle should be On.
Google Pay payment autofill also requires the “Allow sites to check if you have payment methods saved” to be on: chrome://settings/content/paymentHandler → On.
Address format mismatch
Chrome stores addresses with specific field mapping (Street, City, State, Zip, Country). When a form has non-standard field labelling — “Address Line 1/2” instead of “Street,” or “Postcode” instead of “Zip” — Chrome doesn’t recognise the mapping and skips those fields. The suggestion dropdown appears but only fills some fields.
This is a site and browser compatibility issue. Nothing in Chrome settings fixes it — the form designer needs to use standard autocomplete attribute values (autocomplete=”address-line1″, autocomplete=”postal-code”, etc.) for Chrome to map correctly. As a workaround: trigger autofill on one field, then manually copy the remaining data from the suggestion that appeared.
Our guide on Chrome cookies and data persistence covers the related Chrome data storage issues — corrupted data stores affect both cookies and autofill similarly. For password-specific autofill problems, the Chrome password saving guide covers the password manager diagnostics in detail. Google’s Chrome autofill documentation covers the autocomplete attribute values that site developers should use for Chrome to correctly recognise and map form fields to saved data.
Multiple Google accounts and autofill conflict
When Chrome is signed into one Google account but the autofill data was saved under a different account, Chrome shows no suggestions because the wrong profile’s data is loaded. Check the profile icon in the top right — which account is currently active? If Chrome shows “Person 1” without an account name, or shows a different email than expected, the autofill data from the old account isn’t accessible in this session.
Sign out → sign in with the correct account → the autofill data from that account loads. Chrome maintains separate autofill stores per profile, so switching profiles is the solution rather than looking for a settings fix.
Enterprise policy restrictions on autofill
Corporate Chrome deployments can disable specific autofill features through Group Policy. Navigate to chrome://policy/ — if “AutofillAddressEnabled,” “AutofillCreditCardEnabled,” or “PasswordManagerEnabled” appear with disabled values: IT has restricted autofill. Users can’t override these policies through Chrome settings. Report to IT if autofill is needed for legitimate business purposes.
Autofill stopped working after Chrome update
Specific Chrome versions occasionally regress autofill behaviour — particularly for specific field types or sites. If autofill stopped working immediately after Chrome updated: check whether there’s a newer Chrome update available (chrome://settings/help) that may have already addressed the regression. Also check the Chrome Help Community or Reddit for the specific Chrome version number alongside “autofill not working” — known regressions are documented within days of release and usually patched quickly.
Touch and mobile-style forms on desktop
Web applications designed primarily for mobile (responsive designs, PWAs) sometimes implement touch-optimised form inputs that don’t trigger Chrome’s autofill on desktop. These forms handle input differently from standard HTML inputs, and Chrome’s autofill detection doesn’t recognise them as autofill candidates.
There’s no Chrome-side fix for this. The developer needs to implement standard autocomplete attributes. As a workaround: right-click the form field → Chrome’s context menu sometimes shows “Autofill” even when the standard dropdown doesn’t appear — this context menu option uses a different autofill trigger that sometimes works where the automatic detection doesn’t.
Autofill and iframes
Forms embedded in iframes (a common implementation for payment widgets, address lookup tools, and third-party form processors) have limited autofill support. Chrome restricts autofill in cross-origin iframes for security reasons — a malicious iframe could try to steal autofill data by triggering autofill on hidden fields. This means payment widgets from payment processors (Stripe, PayPal, Square) embedded in a site often don’t show credit card autofill through Chrome’s normal mechanism.
Many payment processors implement their own autofill triggers that work with their proprietary iframe setup. If Chrome’s native autofill doesn’t work for a payment widget: the payment processor may have their own save/autofill capability within the iframe that’s separate from Chrome’s. Look for a save option within the payment form itself.
Resetting Chrome autofill data
If autofill data appears corrupted — Chrome autofills wrong addresses, inserts old data that should have been updated, or shows duplicate suggestions — the autofill database may need a targeted reset. chrome://settings/addresses → for each saved address → click the three-dot menu → Edit → verify the data → Delete any incorrect entries. Similarly for chrome://settings/payments.
Rather than clearing all autofill data (which loses everything), selectively deleting corrupted entries preserves the data that’s working correctly. Re-enter the correct information after deletion and Chrome saves it freshly without the corruption.
Checking whether Chrome recognises a field
Developers and curious users can check what Chrome “sees” in a form: F12 → DevTools → right-click on the form field → Inspect → look at the element. The name, id, type, and autocomplete attributes on the input element determine how Chrome handles it. An input with autocomplete="off" or no name attribute often won’t receive autofill. This inspection helps confirm whether the issue is Chrome’s settings or the site’s implementation.
Autofill keyboard shortcuts
A lesser-known Chrome behaviour: pressing the down arrow key in an empty form field shows saved autofill options without waiting for you to start typing. If clicking in a field doesn’t show suggestions but pressing down arrow does: Chrome is waiting for input before showing suggestions for that specific field type, and the keyboard trigger bypasses this delay. This works for both address and password fields.
When none of this works: reset the Chrome profile
If autofill is confirmed enabled in all settings, no extensions are blocking it, the profile is signed in correctly, and it still doesn’t work: a corrupted Chrome profile state is the most likely remaining cause. Creating a new profile (profile icon → Add → sign in with Google account) and testing autofill in the new profile confirms this — autofill works in the new profile but not the old one. Migrating to the new profile resolves the issue; the corrupted autofill state in the old profile can’t typically be repaired without a complete profile rebuild.
Signing into the new profile with the same Google account restores all synced autofill data — addresses, passwords, and payment methods that were synced to Google’s servers come back automatically without needing to re-enter them manually.
One important nuance about autofill: there are three separate autofill systems in Chrome that are each independently configurable: (1) Form autofill — addresses and miscellaneous form data, (2) Password autofill — saved credentials, and (3) Payment autofill — credit cards and payment methods. They share the same on/off toggle in Settings → Autofill and passwords, but each has its own storage, its own error states, and its own fixes. When “autofill isn’t working,” the affected type determines everything about the diagnosis — troubleshooting payment autofill with fixes designed for address autofill wastes time. The three-line check at the start of this guide (checking the specific settings page for the specific autofill type) matters more than the specific fixes themselves.
Autofill on login pages after Chrome’s redesign
Chrome’s unified sign-in and Passwords experience changed significantly in Chrome 120+. The password manager was moved to a standalone page (chrome://password-manager/) and the sign-in experience on Google’s own pages changed. If password autofill stopped working specifically on Google-owned sites (gmail.com, google.com, youtube.com sign-in pages) after an update: this is often a result of Chrome’s own authentication state, not a general autofill problem. Sign out of the Chrome profile → sign back in → this refreshes the authentication state that Google-property autofill depends on.
Accessibility features and autofill interaction
Screen readers and accessibility tools that hook into Chrome’s rendering can interfere with autofill dropdown visibility without preventing it from working — you trigger autofill, it runs, but the visual dropdown isn’t shown. The data fills (or partially fills) without visible feedback. If this is occurring: check whether the form fields that “don’t autofill” actually have been filled — sometimes the fill is invisible in the UI but the data is there when you submit or look at the field value.
Accessibility-aware autofill configuration in Chrome is accessible at chrome://settings/accessibility — the “Live captions,” “Focus mode,” and “Accessibility features” settings don’t directly affect autofill, but third-party accessibility tools that inject JavaScript into pages can. If using such tools: test autofill with the accessibility tool disabled to confirm whether it’s the variable.
Synced autofill data not appearing on a new device
When setting up Chrome on a new device and synced autofill data doesn’t appear: the sync process may not have completed. chrome://settings/help → confirm Chrome is signed in → chrome://sync-internals/ → check the sync status for “Autofill” data type. If it shows errors or hasn’t synced recently: sign out of Chrome → sign back in → allow 5 minutes for sync to complete before testing autofill.
Also check whether autofill is included in what’s being synced: chrome://settings/syncSetup → “Manage what you sync” → confirm “Autofill” is checked. If it was unchecked before the device migration, autofill was never synced and isn’t available on the new device from the cloud — it only exists on the original device’s local storage. You might also run into Chrome Autofill Stopped Working.
