Chrome password autofill should save time, but when it stops working, login forms become frustrating and slow.
This guide explains how to fix Chrome autofill passwords not working with clear, device-by-device steps that address settings, sync, extensions, permissions, and browser data.
Why Chrome Password Autofill Stops Working
Google Chrome uses its built-in Password Manager to store credentials and populate sign-in fields across websites and apps.
Autofill can fail when the browser is out of sync, site permissions are blocked, saved passwords are missing, or a page uses custom login fields that Chrome does not recognize.
On desktop, the issue is often tied to Chrome settings, profile corruption, browser extensions, or an outdated version of Google Chrome.
On Android and iPhone, system-level autofill settings, Google account sync, or password manager permissions can interfere with automatic fill behavior.
Check Chrome Password Manager Settings
The first fix is to confirm that Chrome is actually allowed to save and fill passwords.
These controls can be disabled accidentally after an update or a privacy change.
On desktop
- Open Chrome and select the three-dot menu.
- Go to Settings > Autofill and passwords > Google Password Manager.
- Turn on Offer to save passwords.
- Turn on Auto Sign-in if you want Chrome to fill and log in automatically.
On Android and iPhone
- Open Chrome and go to Settings.
- Open Password Manager or Passwords.
- Confirm that password saving and autofill are enabled.
- Verify that Chrome is allowed to act as the default autofill service where applicable.
If these settings are off, Chrome may still remember some credentials, but it will not offer them consistently on login pages.
Confirm Your Google Account Is Syncing Properly
Chrome autofill depends heavily on Google account sync.
If passwords are stored in one device but not showing on another, sync is usually the reason.
- Open Chrome and click your profile icon.
- Check whether sync is turned on.
- Make sure Passwords is included in sync data.
- Sign out and back in if sync appears stuck.
Also confirm that you are using the same Google account on every device.
Many autofill issues happen because passwords were saved under a different profile, work account, or personal account.
Update Chrome to the Latest Version
Outdated browser builds can break password filling, especially after website design changes or security updates.
Google frequently patches Autofill, Password Manager, and form detection behavior in Chrome releases.
- Open the three-dot menu.
- Go to Help > About Google Chrome.
- Let Chrome check for updates and restart the browser.
If you are on Android or iOS, update Chrome from the Google Play Store or App Store.
Browser updates often resolve form-detection bugs that users mistake for a password problem.
Remove Problematic Extensions
Ad blockers, privacy tools, password managers, and script blockers can prevent Chrome autofill from reading login fields correctly.
Some extensions also inject code that changes how a sign-in form behaves.
To test this, open an incognito window or temporarily disable extensions:
- Go to chrome://extensions/.
- Disable all extensions.
- Reload the affected login page and test autofill again.
If autofill starts working, re-enable extensions one at a time to identify the one causing the conflict.
Common culprits include privacy-focused browser add-ons and third-party password managers that compete with Google Password Manager.
Clear Cached Form Data and Corrupted Site Storage
Websites sometimes store broken form data in cookies, local storage, or cached scripts.
When that happens, Chrome may know your password but fail to insert it into the page.
Try clearing site data for the affected website rather than wiping all browsing data:
- Open the site in Chrome.
- Select the padlock or site controls next to the address bar.
- Open Site settings and clear data for that website.
- Refresh the page and try signing in again.
If the problem affects many sites, clear cached images and files from Chrome settings, then restart the browser.
Avoid deleting saved passwords unless you know they are backed up in your Google account.
Check Whether Chrome Saved the Correct Password
Sometimes the issue is not autofill itself but an outdated or incorrect saved credential.
If a website changed its password recently, Chrome may still be offering the old entry.
- Open Google Password Manager.
- Search for the website name.
- Review the saved username and password entry.
- Edit or delete outdated credentials and save the current one.
If multiple usernames are saved for the same site, Chrome may fill the wrong account.
Remove duplicate entries where appropriate so the correct login appears first.
Allow Chrome to Access Passwords on Mobile Devices
Mobile autofill depends on both the browser and the operating system.
On Android, the phone may be set to use a different autofill provider.
On iPhone and iPad, Chrome needs permission through iOS password settings.
Android
- Go to Settings > Passwords, passkeys, and autofill or the equivalent on your device.
- Set Google as the preferred autofill service.
- Check that Chrome and Google Password Manager are enabled.
iPhone and iPad
- Open Settings > Passwords or Autofill & Passwords.
- Make sure autofill is enabled.
- Confirm that Chrome is installed and that the Google Password Manager prompt appears when signing in.
If another password manager is selected as the default, Chrome may not offer its own saved passwords in the keyboard or login fields.
Test the Page in a Different Profile or Incognito Window
Chrome profiles can become corrupted, especially after repeated sign-ins, sync errors, or extension conflicts.
An incognito window is a quick way to determine whether the issue is tied to your profile.
- Open an incognito window.
- Visit the login page again.
- Try manually selecting a saved password from the prompt.
If autofill works in incognito but not in your normal window, the main profile likely has a setting, extension, or cache problem.
Creating a new Chrome profile can also help if the current one is damaged.
Make Sure the Website Supports Autofill
Some sites use custom login widgets, iframe-based forms, or dynamically loaded fields that Chrome struggles to detect.
In these cases, the password may be saved correctly, but Chrome does not know where to place it.
Look for these signs:
- The username field fills but the password field stays blank.
- The autofill popup appears only after clicking inside the field.
- The page refreshes or changes after you start typing.
When this happens, click directly inside the username or password field and wait for Chrome’s suggestion bubble.
If the site uses a nonstandard form, you may need to select the saved credential manually instead of relying on automatic fill.
Advanced Fixes for Persistent Chrome Autofill Problems
If the basic checks do not solve the issue, try these deeper troubleshooting steps:
- Restart Chrome and your device to reset background services.
- Reset Chrome settings to restore default behavior without deleting your Google account.
- Create a new Chrome profile to rule out profile corruption.
- Reinstall Chrome if the browser files are damaged.
- Check date and time settings because incorrect system time can disrupt sign-in and sync.
For enterprise-managed devices, group policies or MDM restrictions may also disable password saving or autofill.
In that case, the fix may require administrator changes rather than local browser settings.
Best Practices to Keep Chrome Autofill Working
Once autofill is fixed, a few maintenance habits can reduce the chance of the problem returning:
- Keep Chrome updated on every device.
- Use one primary Google account for password sync.
- Avoid installing multiple password managers that compete with each other.
- Review saved passwords periodically and remove duplicates.
- Enable screen lock and account security features to protect stored credentials.
Chrome Password Manager works best when the browser, account sync, and device autofill settings all point to the same source of truth.
When one layer is misconfigured, the login experience can break even though your passwords are still stored safely.