Password Autofill Not Working: What to Check

Password autofill not working usually means one of four layers has failed: the password is saved in a different vault or account, the device or browser is asking the wrong autofill provider, a private window or extension permission is blocking suggestions, or the site's form or domain does not qualify. Do not begin by resetting the password. Find the failed layer first, because each one needs a different fix.

Do not paste a password into notes, chat, search, or another untrusted field while testing. A refusal to fill on a mismatched domain can be a security protection rather than a defect.

Key Takeaways

• Confirm that the saved credential exists in the vault you actually use.
• Check the signed-in account and the system's selected autofill provider.
• Separate a problem on every site from one unusual form or app.
• Treat passkeys and passwords as different sign-in methods.
• Resetting a vault, extension, or browser profile is a last resort.

The device and app troubleshooting guide provides a broader method when several unrelated features are failing at the same time.

Where exactly is password autofill not working?

Start with a small scope table. Test one familiar account whose exact website address you can verify, then compare the result in another normal browser window or the service's official app.

Observation	Most useful next check
No saved entry appears in the password manager	Vault, account, or password synchronization
Entry exists but no suggestion appears anywhere	Selected provider, autofill switch, extension, or permission
Suggestions work except on one site	Domain match, form design, declined list, or site policy
Username fills but password does not	Field eligibility, split login flow, or stale saved entry
A passkey prompt appears instead	Sign-in method selection, not necessarily password failure
Work profile behaves differently	Administrator policy or managed-browser restrictions

Record the browser or app, the exact domain, whether the page is a normal window or private window, and whether the username and password fields appear on the same screen. Do not repeatedly save new copies of the same credential while diagnosing it. Duplicate entries can make the provider choose an old domain or username and hide the real cause.

If the password manager itself cannot open, search, or unlock, fix that first. If the vault works and the saved item is visible, continue at the provider and field layers.

Is the credential in the correct vault and account?

Open the password manager directly rather than relying on the suggestion pop-up. Search for the service by its verified domain and inspect the saved username. The credential may be in a personal account while the browser uses a work account, or in one provider while the operating system has selected another.

Apple explains that iCloud Keychain items synchronize separately from a general device backup and that AutoFill depends on the relevant Passwords and Keychain settings. It also notes that Safari may not save or fill on some sites and that Private Browsing changes expected behavior.［1］ This makes the vault view a better checkpoint than guessing from a missing prompt.

Check these items without revealing the password:

1. The password entry is present under the expected account or vault.
2. The stored website matches the real sign-in domain, including a legitimate regional or organization subdomain.
3. The saved username matches the account you intend to use.
4. The item is not only in an archived, deleted, shared, or work vault that the current profile cannot access.
5. A recent password change reached the device on which autofill is failing.

Do not edit the stored domain merely to force a match. Verify the service's official address independently. A lookalike domain should not receive a real credential.

Is the intended password manager autofill provider enabled?

Modern phones and browsers can have several password providers installed. The provider whose app contains the credential is not automatically the provider the operating system or browser asks for suggestions.

On iPhone and iPad, the switch currently sits under Settings > General > AutoFill & Passwords, where AutoFill Passwords and Passkeys must be on; in iOS 17 or earlier it was under Settings > Passwords > Password Options.［1］ Since iOS 18, iPadOS 18, and macOS Sequoia, Apple's Passwords app holds the items AutoFill uses and syncs them through iCloud Keychain.［2］ Menu names can move between operating-system versions, so follow the current labels on the device rather than an old screenshot.

On Android and Chrome, check the selected autofill service or provider, the Google account or third-party manager account, and the browser profile. Google's setup guide for Android asks you to sign in with your Google Account and set Google as the autofill provider; saved passwords follow that account, so the intended provider and profile still matter.［3］

For a browser extension, check that it is installed, enabled, unlocked, and allowed on the current site. On a Mac, Apple's saved passwords fill in supported third-party browsers only after you enable Apple's extension for that browser.［2］ Private windows often require a separate extension permission. A work or school administrator may prohibit extensions, external password providers, or filling into certain applications. Do not bypass that policy; ask the administrator which provider is supported.

After changing one switch, return to a fresh normal tab and test once. Changing several providers, permissions, and profiles together removes the evidence needed to identify the failed layer.

Does the website or app qualify for autofill?

Autofill providers use context, not only the presence of two text boxes. They may consider the website domain, app-to-domain association, field type, selected browser profile, and whether the page is embedded inside another app.

Check the visible address before interacting. A service may use a separate, legitimate identity domain for sign-in, but you should confirm that from the service's own homepage or support material. If the domain looks unfamiliar, stop instead of weakening protections.

Some common form-specific cases are:

• The site asks for the username first and creates the password field only on the next page.
• The login form is inside an embedded web view that does not expose fields normally.
• The app has not associated itself with the saved website.
• A site requested that browsers not save a password.
• The provider remembers that you declined to save or fill on this site.
• The field is a one-time code, PIN, recovery code, or passkey prompt rather than a password.

Try the provider's explicit fill action from the field, keyboard accessory, browser toolbar, or extension menu. If the credential appears there but not automatically, the vault and account are probably healthy; the remaining scope is automatic suggestion eligibility.

Could browser password autofill be limited by mode, permissions, or policy?

Test in a normal window with extensions limited to the password provider. Private or incognito windows intentionally reduce stored state and may disable extensions unless separately allowed. Clearing cookies is not a first-line autofill fix because cookies manage sessions, while a password vault manages credentials. It can also sign you out of unrelated sites.

Check whether the browser or password app has been updated, then restart only that app. If an extension recently updated, unlock it again and verify site access. On mobile, confirm the app can display autofill suggestions and operate in the background where the platform requires it. Do not grant accessibility, screen-reading, or broad device-management privileges to an unknown helper that promises to force autofill.

Managed devices need an extra boundary check. A company may require its own password manager, browser profile, identity provider, or single sign-on flow. If autofill works in the personal profile but not the work profile, that difference is useful evidence. It is not permission to copy a work password into a personal vault.

Also distinguish autofill from staying signed in. If the password fills successfully but the site asks again after every restart, use the guide for a browser that keeps signing you out. That problem usually concerns cookies, sessions, or account policy rather than the password suggestion pipeline.

What should you try last?

Before a reset, verify that the vault is synchronized or exported through the provider's supported backup method and that you can unlock it on another trusted device. Never assume a browser reset preserves locally stored passwords.

Then use the narrowest reversible action:

1. Restart the affected browser or app.
2. Disable and re-enable only the intended password extension or autofill switch.
3. Remove a clearly stale duplicate entry after confirming the current credential.
4. Sign out of and back into the password provider only after recovery access is confirmed.
5. Reinstall an extension or app only when the vault is known to exist remotely.

Do not reset the account password merely because a suggestion is absent. Test a manual sign-in only on the verified official domain and avoid storing the password in the clipboard longer than necessary. If the credential is rejected when entered correctly, switch to the service's official account-recovery process; that is no longer an autofill problem.

Summary

• Locate the credential in the correct vault before changing anything.
• Match the provider, account, browser profile, domain, and field type.
• Use a normal window to separate private-mode and extension restrictions.
• Respect domain mismatch and managed-device protections.
• Back up or confirm synchronization before reinstalling or signing out.

FAQ

Why is a saved password not showing in autofill?

It may be stored in a different account or provider, attached to another domain, excluded by the site's form, or unavailable in the current browser profile. Open the vault directly and verify the entry before changing the password.

Why does autofill work on some websites but not one site?

The remaining site may use a different sign-in domain, a multi-step form, an embedded web view, or a policy that limits saving and filling. A one-site failure usually does not justify resetting the whole vault.

Does private browsing disable password autofill?

Behavior varies by platform and extension. Private windows can suppress normal suggestions or require explicit permission for the password extension, so compare with a normal window on the same verified domain.

Why does my phone use the wrong password manager?

Installing a manager does not always select it as the system provider. Check the platform's autofill provider setting and the active account, then test again after changing only that choice.

Is a passkey the same as an autofilled password?

No. A passkey uses a different authentication credential and may present a biometric or device-unlock prompt. Choose another sign-in method only if the service officially offers password sign-in for that account.

Should I clear browser data to fix autofill?

Not first. Clearing data can remove sessions and local state without fixing the vault, provider, or domain match. Use it only after identifying browser-profile corruption and confirming important local data is protected.

Is it safe to copy and paste the password manually?

Only on the verified official sign-in page and only when necessary. Avoid notes, chat, search fields, remote-support sessions, and unknown clipboard tools, and clear the clipboard if the platform does not do so automatically.

When should I reset or reinstall the password manager?

Only after confirming that the vault is synchronized or recoverable and that you have the correct account and recovery method. Reinstallation should be the last provider-level test, not the opening step.

Sources

1. Apple Support - If iCloud Keychain won't turn on or sync — https://support.apple.com/en-us/102441
2. Apple Support - Use the Passwords app to create, manage, and share passwords and passkeys across Apple devices — https://support.apple.com/en-la/120758
3. Google Account Help - Get started with Google Password Manager — https://support.google.com/accounts/answer/6208650?hl=en

Sources checked 4 October 2026.

Related Articles

• A structured method for device and app problems
• What to check when a browser keeps signing you out
• How to judge whether password managers are safe
• How to check for leaked passwords
• When a password change is actually warranted