How to Fix Google Password Manager Passkeys Not Showing on Android?
Android can show “No passkeys available” even while the credential remains visible at passwords.google.com. Chrome may also skip the passkey prompt and show only a password field.
Neither symptom proves that the credential was deleted. The phone or browser may be looking in a different account or password manager.
Two separate records are involved. The website keeps a registration showing that a passkey was created. The password manager holds the private credential needed to sign in.
The website can therefore list an old passkey even when that credential is no longer available on this phone.
Use the closest match below before changing any settings.
| What you can see | Where to start |
|---|---|
| The passkey appears at passwords.google.com but not on the phone | Check the Google Account and Android passkey provider in Methods 1 and 2 |
| The passkey is in Google Password Manager, but Chrome never offers it | Match Chrome’s autofill provider and open the picker manually in Method 3 |
| The website lists a passkey, but Google Password Manager does not | Look for the original device or password manager, then use Method 6 |
| The old passkey works, but the site will not offer to create a new one | Check the save-offer and declined-site settings in Method 5 |
1. Confirm Which Account or Password Manager Still Holds the Passkey
Passkeys saved in Google Password Manager belong to the Google Account selected when they were created. A phone with several Google Accounts can therefore show an otherwise healthy passkey in one account and an empty list in another.
This check also prevents a common mistake: a passkey shown on the website’s own Security page is not proof that Google Password Manager still holds the usable credential.
- Open the Passwords app and select Passkeys. If that app is unavailable, open Chrome > More > Settings > Google Password Manager instead.
The fastest first check is whether the passkey is actually present in Google Password Manager rather than missing from Android entirely. - Switch between the Google Accounts on the phone and search for the website or app name.
- Sign in to passwords.google.com with the same account and search again.
A passkey that exists under another signed-in Google Account will look missing on Android until you check the account that actually owns it. - If you use Samsung Pass, 1Password, Bitwarden, Dashlane, or another manager, check that app too. A passkey stays with the provider that saved it unless it is deliberately transferred or recreated.
If the passkey appears on the web but not in Android’s sign-in sheet, continue to Method 2. If it appears only in another manager, select that manager rather than forcing Google Password Manager. If only the website lists it, skip to Method 6.
2. Make Android Offer the Password Manager That Owns the Passkey
Android can use Google Password Manager and compatible third-party managers as passkey providers. If the passkey is in Google Password Manager but Android is asking another provider for credentials, the sign-in sheet can be empty even though the passkey still exists.
- Open Settings > Passwords, passkeys & accounts. On some phones, search Settings for Password if the wording differs.
Android keeps the active passkey provider in the Passwords passkeys and accounts screen rather than inside every individual app. - Tap the current password manager and select the provider that actually contains the passkey. Choose Google Password Manager only when Method 1 confirmed the entry is there.
- Enable the suggestion toggle beside that provider, then close and reopen the affected app or website.
If another provider owns the passkey flow or Google Password Manager is disabled the sign-in prompt can appear empty or not show its passkeys at all.
Google documents both the provider selector and suggestion toggle in its Android passkey guidance.
If Android now offers the passkey, the wrong provider caused the gap. If the problem occurs only in Chrome, continue below.
3. Make Chrome Use the Same Provider and Open the Passkey Picker Manually
Chrome on Android has its own autofill-provider setting. If it points elsewhere, Chrome requests credentials from that vault and never asks Google Password Manager for the passkey.
This section applies when Method 1 found the passkey but websites opened in Chrome do not offer it. If no password manager contains the credential, changing Chrome cannot recover it.
- Open Chrome > More > Settings > Autofill services.
- Select Autofill with Google for Google Password Manager. If the passkey is stored in a third-party manager, choose Autofill using another service instead.
If Chrome is sourcing autofill data from another service Google Password Manager can look empty even when the passkeys still exist. - Tap Restart Chrome when prompted.
- Return to the sign-in page. If no prompt appears, touch and hold the username or password field, then select Select passkey or Use passkey.
- If the page offers Sign-in options, Other ways to sign in, or Use a different device, open it and choose the passkey route explicitly.
Google’s current Chrome autofill instructions confirm that turning off autofill prevents Chrome from saving or filling Google Password Manager passkeys.
If Chrome also fails to save and fill ordinary passwords, use this Chrome password-saving guide for that broader problem.
If the passkey appears after restarting Chrome or opening the picker manually, the browser handoff was the problem. If passkeys still fail in both websites and apps, continue to Method 4.
4. Restore the Screen Lock and Unlock the Synced Passkey Vault
Android refuses passkey creation and sign-in without a secure device lock. Google Password Manager also encrypts synced passkeys behind the Android lock or a Google Password Manager PIN.
Check the lock when passkeys fail across websites and apps, or when a new device sees the account but cannot unlock its credentials. A device-lock problem does not explain one rejected website while other passkeys keep working.
- Open the phone’s Security, Security & privacy, or Lock screen settings.
- If the lock is set to None or Swipe, create a PIN, pattern, or password.
Google Password Manager depends on the device screen lock so passkeys can stop showing if the phone is not protected by a real unlock method. - Lock and unlock the phone once, then reopen the site or app and try again.
- If Google asks for a Google Password Manager PIN or the PIN from an Android device that already used these passkeys, complete that verification. Do not choose an option that resets or deletes all passkeys merely to bypass a forgotten PIN.
Google explains how the Android lock and Google Password Manager PIN protect synced credentials in its passkey management guide.
If the credential can now be unlocked, the vault was intact. If an existing passkey works but the site will not offer to save a new one, continue to Method 5.
5. Restore the Save Prompt Only When a New Passkey Cannot Be Created
The save-offer toggle lets Google Password Manager respond when a site requests a new credential. Removing a service from the declined list reverses an earlier decision not to save there. Together, those changes allow the site’s creation request to reach the password manager again.
These settings matter only when a supported website or app will not offer to create a new passkey. They cannot retrieve an existing credential that has disappeared.
- Open Passwords > Settings, or open Chrome > Settings > Google Password Manager > Settings.
- Turn on Offer to save passwords and passkeys.
If save offers are disabled Google Password Manager may never surface new passkeys for supported sites or apps. - Open Declined sites and apps and remove the affected service if it is listed.
- Return to that service’s account-security settings and choose its own Create a passkey or Add passkey option.
If a service sits in the declined list Google Password Manager can stay silent for that site until you unblock it.
If the creation prompt returns, the site had been suppressed. On a managed work or school device, the setting may be controlled by an administrator. If the original passkey is absent from every provider, continue to Method 6.
6. Use the Original Device or Replace a Missing Passkey Safely
This recovery path is for a passkey that is absent from Google Password Manager and every other manager you checked. It is not a repair for a credential that remains visible in the correct vault.
Provider changes cannot reconstruct a missing credential. Using the original device lets the website verify the private key where it still exists; creating a replacement establishes a new working key pair when no usable copy remains.
The old passkey may still live on the phone, computer, security key, Chrome profile, or password manager where it was created. The website may also be retaining an old registration for a credential that no longer exists.
- Try the original device or password manager first. On a computer, choose Use a phone or tablet or Use a different device if the site offers it.
- If no usable copy remains, sign in with the account password, recovery code, another passkey, or the service’s account-recovery process.
- Open the service’s Security, Passkey, or Sign-in settings and create a new passkey in the password manager you intend to keep using.
- Test the replacement in a new sign-in session. Only after it works should you remove the stale passkey registration from the website.
- If the original passkey still exists on another phone, use the site’s QR-code flow to sign in from that phone. Keep Bluetooth enabled on both nearby devices and scan the code with the phone’s camera.
A QR-code sign-in uses the passkey from the other device for that session. It does not copy the credential into Google Password Manager.
If every other passkey works and only one service still rejects or hides its credential, contact that service. Its passkey registration or sign-in implementation is now the remaining point of failure.
