Chrome’s autofill is more capable than most users take advantage of — it stores addresses, payment cards, and form data across devices if you’re signed in, and lets you manage exactly what it saves. The problem is that most of the controls are buried three menus deep, and when autofill stops working, the cause is almost never where people look first. For the bigger picture, our Chrome How-To Guides pulls everything together.
The management page you need is chrome://settings/autofill — bookmark it. From there you can view every saved address and card, delete outdated entries that cause wrong suggestions, and troubleshoot why a specific site isn’t triggering autofill.
What Chrome’s form filling Stores and How It Learns
autofill functionality stores three categories of information: addresses (name, street address, city, state, postal code, country, phone number, and email address — each configured as a named address profile), payment methods (credit and debit card numbers, cardholder names, expiration dates, and CVV codes — stored optionally with or without Google account association), and personal information like full name and email address that appears in single-field forms. The storage of these three categories is configurable independently — addresses can be saved without saving payment cards, and vice versa — through the Settings → Autofill and passwords section which contains separate management interfaces for “Address and more” and “Payment methods.”
autofill learns new address data in two ways. First, when a checkout or registration form is completed manually, Chrome detects the address fields and offers to save the entered information as a new address profile. Accepting the save prompt adds the address to the Chrome Autofill store for future use. Second, Chrome may import address information from the signed-in Google account, where address data entered in other Google services (Google Pay, Google Shopping, Google Maps saved addresses) is available to Chrome Autofill without requiring manual entry in a browser form. For payment cards, Chrome Autofill also integrates with Google Pay — cards saved in Google Pay appear in Chrome’s payment method autofill without requiring separate entry in the browser’s settings, and they are filled using the Google Pay virtual card system that protects the actual card number from the merchant.
The precision of Chrome Autofill‘s field detection affects how accurately it fills forms. Chrome analyses the HTML attributes of form fields — the name, autocomplete, id, and placeholder attributes specifically — to identify which type of information belongs in each field. Well-implemented forms with proper HTML autocomplete attributes (such as autocomplete="given-name", autocomplete="street-address", autocomplete="cc-number") trigger precise field-by-field filling where the correct Chrome Autofill data goes into each matching field automatically. Forms with poor or missing autocomplete attributes may receive incorrect field matching — the name field filled with an email address, for example — because Chrome is inferring the field type from context rather than reading an explicit declaration. The accuracy of Chrome Autofill on any specific website depends primarily on how well that website’s forms are coded, not on Chrome’s capabilities.
Imported autofill data from browser history — addresses that Chrome has detected from previously visited and completed forms — appears in the Chrome Autofill suggestions even if the user has not explicitly saved the data. This “local autofill” data is distinct from the named address profiles in the Address and more settings — it is stored transiently and can be cleared through the Clear browsing data dialog by selecting “Autofill form data” in the data type list. Users who prefer that Chrome Autofill only suggest explicitly saved profiles rather than inferred data from form history should clear the autofill form data periodically and add their addresses as explicit named profiles in the Settings interface.
Chrome Autofill Data Types — What Is Stored and Where
| Data Type | Where Managed | Syncs with Account | Clears with Browsing Data |
|---|---|---|---|
| Named address profiles | Settings → Autofill → Addresses and more | Yes — when Autofill sync is on | No — explicit delete required |
| Payment cards (local) | Settings → Autofill → Payment methods | No — device-local only | No — explicit delete required |
| Payment cards (Google account) | pay.google.com | Yes — account-level storage | No — managed via Google account |
| Form history (transient) | Not directly viewable | No | Yes — “Autofill form data” in Clear data |
| Passwords | Password manager (separate) | Yes — when Passwords sync is on | No — explicit delete required |
Payment cards in Chrome Autofill have two distinct storage modes that affect both security and cross-device availability. Cards saved as “local cards” are stored only on the specific device they were entered on and are not synced to other devices through the Chrome account. Cards saved to the Google account — which Chrome prompts to do when a new card is entered, asking “Save card to Google?” — are stored securely with Google and are available across all devices signed in to the same account. The Google-stored cards benefit from Google Pay’s virtual card feature on participating websites, where the actual card number is replaced with a single-use virtual number that the merchant charges — the actual card number is never exposed to the merchant, which is a meaningful fraud prevention benefit. Choosing to save Chrome Autofill payment cards to Google rather than locally is the higher-security option for most users.
Managing and Editing Chrome Autofill Saved Data
Managing Chrome Autofill addresses: Settings → Autofill and passwords → Addresses and more shows all named address profiles. Each profile can be edited by clicking the three-dot menu → Edit, which opens a full address form for modifying any field. Common reasons to edit a saved address profile include a change of residence, a change of phone number, or a correction to a field that was captured incorrectly when Chrome offered to save a completed form. Deleting outdated address profiles removes them from autofill suggestions — the menu for each profile includes Delete alongside Edit. Multiple address profiles for different shipping and billing addresses are supported, and Chrome offers to select among them when multiple saved profiles match the form fields being filled.
Chrome Autofill for payment methods: Settings → Autofill and passwords → Payment methods shows all saved cards and the IBAN (bank account) entries if any are saved. Local cards (not synced to Google account) show with a small “local” indicator; account cards show with the Google Pay association. Adding a new card manually is done through the Add button in this interface rather than requiring a checkout form to initiate the save prompt. The CVV code for saved cards is not stored by Chrome Autofill by default for locally saved cards — Chrome may prompt for the CVV at checkout even when the card number and expiry are filled automatically, which is a deliberate security design that prevents a stored CVV from being exposed alongside the card number in the autofill data store.
- Open Chrome Settings → Autofill and passwords → Payment methods.
- To add a new card: click Add → enter the card number, cardholder name, and expiration date → choose whether to save locally or to Google account → Save.
- To edit an existing card: click the three-dot menu on the card entry → Edit → modify the card details → Save. Only name and expiry are editable for locally stored cards; Google account cards are edited via pay.google.com.
- To delete a card from Chrome Autofill: click the three-dot menu → Remove. For Google account cards, removal from Chrome removes them from Chrome’s local cache but the card may still appear if it remains in the Google account — manage Google account cards at pay.google.com.
- To disable Chrome Autofill for payment cards entirely: toggle off “Save and fill payment methods” in Settings → Autofill and passwords → Payment methods. This prevents Chrome from offering to fill or save payment card information while leaving address autofill active.
- To disable Chrome Autofill for addresses: toggle off “Save and fill addresses” in Settings → Autofill and passwords → Addresses and more. Existing saved addresses are retained and can still be manually accessed; new addresses are not saved and the autofill dropdown does not appear.
The privacy consideration for Chrome Autofill payment cards is worth explicit attention: any application that can access Chrome’s profile data on the device can potentially access locally stored card information. Chrome encrypts the stored payment data, and on Windows it uses the system’s credential protection to further secure the data. Nevertheless, users who want to ensure payment card data is never stored in the browser can disable payment autofill entirely and manage cards exclusively through a dedicated password manager with payment card support, or through their bank’s own mobile payment system. Our guide on Chrome password manager covers the separate credential storage that handles passwords alongside Chrome Autofill, and our Chrome sync guide explains how Chrome Autofill data syncs through the account. The Google Chrome support documentation covers the specific encryption mechanisms used for payment card storage in Chrome Autofill and the Google Pay integration that provides virtual card protection.
When Chrome Autofill Does Not Work — Diagnosis and Fixes
The most common reason Chrome Autofill does not appear on a form where it should is that the website’s form fields lack the standard HTML autocomplete attributes that Chrome uses to identify field types. When Chrome cannot determine what type of information belongs in a field, it does not offer Chrome Autofill suggestions for that field — it leaves the field unfilled rather than guessing incorrectly. This is the website’s implementation limitation rather than a Chrome issue, and it cannot be resolved through Chrome settings. The workaround is to right-click any form field and check whether “Autofill” appears in the context menu — if it does, Chrome has identified the field type but is not showing the dropdown automatically, and clicking Autofill from the context menu manually triggers the suggestion.
If Chrome Autofill is not firing at all across multiple sites, the first check is whether the “Save and fill addresses” and “Save and fill payment methods” toggles are enabled in Settings → Autofill and passwords. Chrome updates occasionally reset autofill toggles, and a Chrome profile sync issue can cause autofill data to appear missing when the sync conflict has removed locally visible profiles. Signing out of Chrome and signing back in, which triggers a fresh sync of autofill data from the Google account, resolves the missing-data-after-update scenario. Clearing autofill form data (not addresses or payment methods) through the Clear browsing data dialog occasionally resolves situations where corrupted transient autofill data is interfering with Chrome Autofill normal operation.
Chrome Autofill filling the wrong data into a form field — an email address in a name field, a city in a phone number field — is almost always caused by mismatched autocomplete attributes in the website’s form HTML. Chrome is reading the field’s declared type and filling accordingly; when the declared type does not match what is visually presented as the field’s purpose, the result is an incorrect fill. This type of mismatched fill is immediately obvious, can be cleared with a single Delete keystroke, and is best addressed by the website’s developers rather than by Chrome configuration. The developer tools inspect panel (F12 → Elements → click the problematic field) shows the field’s actual autocomplete attribute value, which confirms whether the field declaration matches its visual purpose. Our guide on Chrome DevTools covers the elements inspection workflow relevant to diagnosing form attribute issues.
Chrome Autofill on Mobile and Across Different Chrome Contexts
On Chrome for Android, Chrome Autofill integrates with Android’s system autofill framework, which means that addresses and payment cards saved in Chrome are available not only in Chrome’s own form fields but potentially in other Android applications that request autofill data through Android’s system autofill service. To use Chrome as the system autofill provider on Android: Android Settings → General management (or System) → Language and input → Autofill service → select Chrome. With Chrome set as the system autofill provider, Chrome Autofill data appears in app login forms, checkout screens in shopping apps, and registration forms in native Android applications — extending the browser-based credential store across the full Android application ecosystem. The same address profiles and payment cards managed through Chrome’s Settings interface are then available as Chrome Autofill suggestions throughout the device.
The autofill experience across different Chrome profiles is fully isolated — address profiles and payment cards saved in a work Chrome profile are not accessible when using the personal profile, and vice versa. This profile isolation is correct behaviour for the common scenario of maintaining separate professional and personal browsing environments, but it means that addresses needed in both contexts (a home address for personal deliveries and for work-from-home correspondence, for example) must be added to the Chrome Autofill address store in each profile separately. There is no cross-profile sharing or import function for autofill data — each profile’s autofill store is treated as belonging to the account signed into that specific profile.
Why has Chrome autofill stopped suggesting my saved information?
Two common causes: the website uses autocomplete=”off” to intentionally disable autofill on its forms (banking sites often do this for security), or your autofill data exists but a sync issue has disconnected it from the local browser. Check chrome://settings/autofill first to confirm your data is still there — if it is, the website is likely suppressing it.
Where does Chrome manage autofill passwords separately?
Passwords are separate from addresses and cards — they live at chrome://password-manager/ or passwords.google.com if you use Google sync. The main autofill settings page only shows addresses and payment methods, not login credentials.
Because they are handled separately, password problems need a separate fix — if password autofill has stopped working while addresses and cards still fill normally, the cause lives in the password manager rather than autofill itself.
Why does Chrome autofill the wrong address?
Chrome may have multiple saved addresses and default to an outdated one. Go to chrome://settings/addresses, delete any old or duplicate entries, and keep only the current correct address. Chrome tends to use the most recently used entry rather than a fixed default, so using the correct one consistently corrects the autofill order over time.
Can I use Chrome autofill on a site that has disabled it?
Not without a browser extension. Sites that use autocomplete=”off” tell Chrome to suppress autofill for their forms. Chrome respects this for address and payment fields. Some password manager extensions can override it for login fields, but not for address or card fields.
Does Chrome autofill sync across devices?
Yes, if you’re signed into Chrome with a Google account and sync is enabled. Check that sync is active at chrome://settings/syncSetup. Addresses and payment methods sync across all Chrome instances signed into the same account, including mobile.
