
You click sign in, expect the fingerprint or face check, and nothing happens. No prompt appears, the site falls back to asking for a password, or the passkey option is missing entirely. When chrome passkey not working blocks the quick sign-in you set up, it feels like the passkey has vanished — even though you created it only recently and it worked before.
The good news is that passkeys rarely vanish on their own. A passkey sign-in depends on several parts working together: the website must offer passkeys for your account, Chrome must be signed in with sync turned on, the device must have a screen lock set up, and a nearby phone must be reachable over Bluetooth for cross-device approval. This guide checks each part in order, from the simplest account check to the deeper device fixes. Nothing here deletes your saved passwords.
Table of Contents
- Why This Error Happens
- Quick Checks
- Diagnosing the Problem
- Fix 1: Check That the Website Offers Passkey Sign-In for Your Account
- Fix 2: Sign In to Chrome and Turn On Sync
- Fix 3: Turn On Bluetooth and Keep Your Phone Nearby
- Fix 4: Set Up a Screen Lock on the Device
- Fix 5: Allow Passkeys in Chrome Settings and Check Site Permissions
- Fix 6: Update Chrome and Your Operating System
- Fix 7: Delete the Passkey and Create a Fresh One
- Fix 8: Clear the Site Data for the Website and Sign In Again
- Fix 9: Disable Extensions That Block Pop-Ups or Change Sign-In Pages
- Fix 10: Test in a Fresh Chrome Profile and on Another Device
- Fix 11: Check Your Google Account Passkeys and Remove Stale Ones
- What to Avoid
- Frequently Asked Questions
- Conclusion
- Helpful Official Resources
Why This Error Happens
A passkey is a private key stored on your device, protected by your fingerprint, face, or PIN, with a matching public key stored by the website. Signing in means the website asks your device to prove it holds the private key, and your device asks you to confirm with a biometric check or PIN. If any link in that chain is missing, the prompt never appears. These are the missing links found most often.
1. No Passkey Exists Yet for That Account
Many people expect a passkey prompt on a site where they never actually created a passkey. A passkey is created per website and per account, in the security settings of that website, and it is easy to confuse creating a passkey on one site with having passkeys everywhere. If no passkey was ever created for that account, Chrome has nothing to offer, and the site quite correctly asks for a password instead. The fix is not a browser repair — it is creating the passkey in the first place, which Fix 1 and Fix 7 cover step by step.
2. Chrome Is Not Signed In or Sync Is Off
Passkeys created in Chrome are stored in Google Password Manager and synced through your Google Account, so they follow you to your other devices. If Chrome is signed out, or sync is off, the passkeys stored in your account cannot reach the device you are signing in on. The prompt then never appears, because Chrome on that device simply does not know the passkey exists. Signing out of Chrome, switching to a different Google Account, or turning sync off for troubleshooting can all cause chrome passkey not working without any visible error message.
3. Bluetooth Is Off or the Phone Is Too Far Away
When you sign in on a laptop with a passkey stored on your phone, Chrome reaches the phone over Bluetooth and shows a QR code or a prompt on the phone for approval. Bluetooth must be on, on both devices, and the phone must be close by. If Bluetooth is off, the phone is in another room, or the phone is signed in to a different Google Account, the approval never arrives and the sign-in stalls. This cause is easy to miss, because nothing on the laptop screen explains that the phone is the missing piece.
4. The Device Has No Screen Lock Set Up
A passkey is protected by the device lock: a PIN, a fingerprint, or face recognition. If the device has no screen lock at all, there is nothing to confirm the sign-in with, and Chrome cannot create or use a passkey on that device. This happens most often on a new computer or a freshly reset phone where the lock was skipped during setup, or on a shared computer where the lock was removed. Setting up a screen lock is a requirement, not an optional extra, and Fix 4 walks through it.
5. A Permission, Pop-Up Blocker, or Extension Blocks the Prompt
The passkey prompt is a small system dialog that appears over the browser window. A strict pop-up blocker, a privacy extension, or a site permission that denies the sign-in request can swallow the prompt before you ever see it. The page then sits waiting, or falls back to a password, with no clue that a blocker stepped in. Extensions that change sign-in pages or inject their own password prompts are a common cause, especially when the problem started right after an extension was added or updated.
6. The Passkey Is Stale, Duplicated, or Outdated Software Is in the Way
Passkeys can go stale when an account password is changed, when a device is reset, or when the website updates its sign-in system. A stale passkey may still be listed in your account but no longer match the key the website holds, so the sign-in fails silently. Old versions of Chrome or of the operating system can also lack passkey support or carry a passkey bug that was fixed later. A stale passkey and an outdated browser produce the same symptom — a prompt that never appears or fails at once — and Fixes 6, 7, and 11 sort out which one you have.
Quick Checks
Two minutes before the deep fixes.
- Check the website’s security settings — did you actually create a passkey for this account?
- Click the profile icon in Chrome — are you signed in to the right Google Account?
- Check whether sync is on — do your saved passwords show on this device?
- Check Bluetooth — is it on, and is your phone close by and unlocked?
- Check the device lock — does the device ask for a PIN, fingerprint, or face to unlock?
- Think about when it started — did chrome passkey not working begin after a device reset, a new phone, or a browser update?
Diagnosing the Problem
| Symptom | Cause | Go to Fix |
|---|---|---|
| No passkey option on the sign-in page | No passkey created for the account | Fix 1 |
| Passkey works on one device only | Chrome signed out or sync off | Fix 2 |
| Prompt never reaches the phone | Bluetooth off or phone too far away | Fix 3 |
| Error about device lock or PIN | No screen lock set up | Fix 4 |
| Prompt blocked or page stalls | Permission or pop-up blocker | Fix 5 |
| Passkey worked before an update | Outdated Chrome or operating system | Fix 6 |
| Prompt appears then fails at once | Stale or broken passkey | Fix 7 |
| Sign-in loops back to password | Corrupted site data | Fix 8 |
Fix 1: Check That the Website Offers Passkey Sign-In for Your Account
Start here, because the most common cause is also the simplest: the website may not offer passkeys for your account at all, or you may never have created one there. Checking the account settings first saves you from repairing a browser that is not broken.

- Sign in to the website with your password, the usual way.
- Open the account settings, then the Security or Sign-in section.
- Look for Passkeys, Passwordless sign-in, or Security keys in the list of sign-in methods.
- If no passkey option exists, the website does not support passkeys for your account yet — use your password.
- If the option exists but no passkey is listed, click Create a passkey and follow the prompts.
- Confirm with your fingerprint, face, or PIN when the device asks.
- Sign out and sign in again to test whether the new passkey is offered.
Some websites show the passkey option only after you turn on two-step verification or confirm your identity another way, so check the security section carefully before concluding the site lacks passkey support. Other sites offer passkeys only in their app, not on the website, or only for accounts created after a certain date. The account settings page is the truth — if it lists no passkey and no way to create one, no browser fix will make a prompt appear. When a passkey is listed but the prompt never shows, the problem is the device or the browser, and the next fixes will find it.
Fix 2: Sign In to Chrome and Turn On Sync
Passkeys in Chrome live in Google Password Manager and travel through sync. If Chrome is signed out, or sync is paused, the passkey stored in your account cannot reach the device in your hands. Signing in and turning sync on restores the link between the account and the device.
- Click the profile icon in the top-right corner of Chrome.
- Check which Google Account is shown — it must be the account that holds your passkeys.
- If the wrong account is shown, click Add Chrome profile and sign in with the right account.
- If no account is shown, click Sign in to Chrome and complete the sign-in.
- Open Settings, then You and Google, then Sync and Google services.
- Check that Sync is on, and that Passwords is included in what is synced.
- Open the website again and test the sign-in.
A paused sync looks almost identical to working sync, so open the sync page and read its status rather than trusting the profile icon alone. If sync shows an error, such as a passphrase request or a sign-in problem, resolve that error first — passkeys cannot sync past a broken sync. On a shared computer, check that you are in your own Chrome profile, not someone else’s, because passkeys belong to the signed-in profile. If the password manager itself will not open, or shows no saved items at all, our guide to Chrome password manager not opening covers that problem. After sync is healthy, give it a minute to fetch your passkeys before testing the sign-in.
Fix 3: Turn On Bluetooth and Keep Your Phone Nearby
Cross-device sign-in — a passkey on your phone used to sign in on a laptop — needs Bluetooth to connect the two devices and confirm they are near each other. Without Bluetooth, the laptop cannot reach the phone, and the approval prompt never arrives.

- Turn on Bluetooth on the laptop or computer you are signing in on.
- Turn on Bluetooth on the phone that holds the passkey.
- Place the phone next to the computer, within arm’s reach.
- Unlock the phone and keep its screen awake during the sign-in.
- Check that the phone is signed in to the same Google Account as the computer.
- On the computer, start the sign-in and choose the passkey option.
- When the prompt or QR code appears, approve it on the phone with your fingerprint, face, or PIN.
The phone does not need to be paired with the computer in the Bluetooth settings — Chrome handles the connection itself — but Bluetooth must be switched on for the handshake to happen. Airplane mode on the phone turns Bluetooth off along with everything else, so check that first if the phone never receives the prompt. A phone with a dead battery, a phone left in another room, and a phone signed in to a different account all produce the same silent failure, so check each one in turn. If the QR code appears but the phone camera will not scan it, open the camera app directly and point it at the code, or approve the prompt from the phone notification instead.
Fix 4: Set Up a Screen Lock on the Device
A passkey cannot be created or used on a device with no lock screen, because the lock is what proves the person signing in is the device owner. If the device opens straight to the home screen with no PIN, fingerprint, or face check, passkeys will fail or refuse to be created.
- On Windows, open Settings, then Accounts, then Sign-in options.
- Set up a PIN, and add fingerprint or face recognition if the device supports it.
- On a Mac, open System Settings, then Touch ID and Password, and add a fingerprint or password.
- On Android, open Settings, then Security, then Screen lock, and choose a PIN, pattern, or biometric.
- On an iPhone, open Settings, then Face ID and Passcode or Touch ID and Passcode, and turn the lock on.
- Lock the device and unlock it once to confirm the new lock works.
- Try creating or using the passkey again.
The lock must be a real lock, not a swipe with no check — a swipe-only lock proves nothing about who is holding the device, so passkeys refuse to use it. On Windows, the Windows Hello setup covers the PIN and biometric options in one place, and Chrome uses whatever Windows Hello provides. If the device is managed by an employer or a school, the lock settings may be controlled by policy, in which case the administrator may need to allow biometric sign-in. After the lock is set up, Chrome may need a restart before it offers passkey creation, so close and reopen the browser before testing again.
Fix 5: Allow Passkeys in Chrome Settings and Check Site Permissions
Chrome and the operating system must both allow the passkey prompt to appear. A denied permission, a blocked pop-up, or a site setting that refuses the sign-in request can swallow the prompt silently, leaving the page waiting or falling back to a password.
- Open Settings in Chrome, then Privacy and security, then Site settings.
- Check Pop-ups and redirects — the website must be allowed, not blocked.
- Check the Additional permissions section for any sign-in or device options the browser lists.
- Open the website, click the tune icon or padlock icon in the address bar, and review Site settings.
- Make sure nothing on that page is set to Block for the sign-in features the site needs.
- Reload the website and try the passkey sign-in again.
- If the prompt appears but vanishes at once, check whether a second browser window is hiding behind the first.
The passkey prompt is a system dialog, not a web page element, so it can appear behind the browser window or on a second monitor — look around before assuming it never appeared. A strict pop-up blocker is the usual suspect when the prompt never shows on one site but works on others, because the block is per-site. Sign-in state also depends on cookies, and a site that cannot save its sign-in cookie may loop back to the password screen even when the passkey itself worked. If cookies behave strangely on the site, our guide to Chrome cookies not working covers the cookie side. Keep the permission changes narrow: allow the one site you trust, rather than loosening pop-up rules for the whole web.
Fix 6: Update Chrome and Your Operating System
Passkey support is relatively new, and both Chrome and the operating system must be recent enough to handle it. An outdated browser or an old operating system can lack the pieces passkeys need, or carry a passkey bug that was fixed in a later release.

- In Chrome, click the three-dot menu, then Help, then About Google Chrome.
- Wait for Chrome to check for an update, and click Relaunch if one is offered.
- On Windows, open Settings, then Windows Update, and install any waiting updates.
- On a Mac, open System Settings, then General, then Software Update, and install waiting updates.
- On Android, open Settings, then System, then System update, and install waiting updates.
- Restart the device after the updates finish.
- Test the passkey sign-in again on the website.
Update the operating system as well as Chrome, because the passkey prompt itself is drawn by the operating system — Windows Hello on Windows, the system keychain prompt on a Mac, and the system biometric prompt on a phone. If the operating system is too old to show that prompt, no browser update can fix the sign-in. On a work or school device, updates may be controlled by an administrator, so the update page may show that updates are managed — ask the administrator whether a newer version is available. After updating, chrome passkey not working often clears on the first test, because the update restores the missing passkey pieces in one step.
Fix 7: Delete the Passkey and Create a Fresh One
A stale or corrupted passkey can sit in your account looking normal while failing every sign-in. Deleting it and creating a fresh one replaces both halves of the key pair — the private key on the device and the public key on the website — and clears any mismatch between them.
- Sign in to the website with your password.
- Open the account Security settings and find the list of passkeys.
- Delete the passkey for the device that will not sign in. Keep a working passkey on another device if you have one.
- Sign out of the website completely.
- Sign in again with your password and return to the Security settings.
- Click Create a passkey and confirm with your fingerprint, face, or PIN.
- Sign out and sign in again to test the fresh passkey.
Do not delete every passkey at once. If you have a working passkey on your phone, keep it until the fresh passkey on the computer proves itself — deleting all of them leaves only the password, and a forgotten password then means account recovery. The fresh passkey must be created on the device that will use it, or on the phone that will approve sign-ins for that device, because the private key is stored where it is created. If creation fails with an error about the device or the lock screen, go back to Fix 4 and confirm the screen lock is set up and working. A fresh passkey that works at once proves the old one was stale, and no further fix is needed.
Fix 8: Clear the Site Data for the Website and Sign In Again
Stored data for one website — cookies, cached files, and saved permissions — can corrupt in a way that breaks sign-in for that site alone. Clearing the data for just that site gives it a clean start without signing you out of every other website.
- Open the website in Chrome.
- Click the tune icon or padlock icon in the address bar, then Site settings.
- Click Delete data or Clear data for the site, if the option is shown.
- Alternatively, open Settings, then Privacy and security, then Delete browsing data.
- Choose Cookies and other site data and Cached images and files, with a short time range first.
- Close the website tab completely, then reopen the website.
- Sign in with your password first, then test the passkey sign-in.
Clearing data for one site is safer than clearing everything, because it leaves your other sign-ins untouched. If the single-site clear does not help, repeat with the full Delete browsing data flow and the All time range — but know that this signs you out of most websites, so check that your passwords are saved before you start. A sign-in that loops back to the password screen, or a passkey prompt that appears and then returns you to the same page, is the classic sign of corrupted site data. If saved passwords themselves have vanished from Chrome, that is a wider problem, and our guide to Chrome saved passwords disappeared covers recovering them.
Fix 9: Disable Extensions That Block Pop-Ups or Change Sign-In Pages
Extensions that manage passwords, block pop-ups, or reshape web pages can intercept the passkey prompt before you see it. A password manager extension, in particular, may show its own sign-in prompt and hide the browser’s passkey prompt behind it.
- Click the three-dot menu, then Extensions, then Manage extensions.
- Look for password managers, pop-up blockers, privacy tools, and script blockers.
- Turn off the most suspicious extension first, using its switch.
- Reload the sign-in page and try the passkey sign-in again.
- If the prompt appears, you have found the culprit — keep it off for sign-ins, or adjust its settings.
- If the prompt stays missing, turn extensions off one at a time, testing after each one.
- When the culprit is found, check whether it has an allow-list for the website.
Test one extension at a time, because turning them all off at once fixes the symptom without naming the cause, and the problem returns when they are all turned back on. Password manager extensions deserve the first look: many of them take over the sign-in form, and their prompt can cover or replace the passkey dialog. If you use a password manager you trust, check its settings for a passkey or WebAuthn option, and let the browser handle passkeys while the manager handles passwords. Remove any extension you do not recognise, because unknown extensions that touch sign-in pages are a security risk as well as a source of faults.
Fix 10: Test in a Fresh Chrome Profile and on Another Device
A fresh profile has default settings, no extensions, and no stored site data. If passkeys work there, your main profile is the cause. Testing on another device answers the same question for the device itself: if the passkey works on the phone but not on the laptop, the laptop setup is at fault.

- Click the profile icon in the top-right corner of Chrome, then Add Chrome profile.
- Create the new profile and sign in with the same Google Account that holds your passkeys.
- Wait a minute for sync to fetch your passkeys into the new profile.
- Open the website in the new profile and try the passkey sign-in.
- On another device, open the same website and try the same passkey sign-in.
- Compare the results: working in the new profile points at the old profile; working on the other device points at the first device.
- If the passkey fails everywhere, the passkey itself or the website is the cause — move on to Fix 11.
The two tests together narrow the fault to one of three places: the profile, the device, or the passkey. A new profile that works means the old profile carries a bad setting, a bad extension, or corrupted data, and moving to a fresh profile is a reasonable long-term answer. A second device that works means the first device needs the Bluetooth, lock screen, or update fixes from earlier in this guide. If Chrome keeps signing you out between tests, so the profile never stays signed in long enough to test, our guide to Chrome keeps logging me out covers the sign-in persistence problem.
Fix 11: Check Your Google Account Passkeys and Remove Stale Ones
Your Google Account holds the master list of passkeys synced through Chrome. A stale, duplicated, or orphaned entry there can confuse sign-in, especially after a device reset, a phone change, or a passkey created twice for the same site. Cleaning the list leaves only passkeys that match real devices.
- Open your Google Account settings in the browser and sign in.
- Open the Security section, then find Passkeys or How you sign in to Google.
- Review the list of passkeys, noting which device each one belongs to.
- Remove passkeys for devices you no longer own, and remove duplicates for the same site.
- Keep at least one working passkey, or confirm your password and recovery options still work, before removing anything.
- On the device, open Chrome and wait for sync to pick up the cleaned list.
- Create a fresh passkey for the website with Fix 7, and test the sign-in.
Never remove every sign-in method at once. Before deleting a passkey, confirm you can still sign in with your password and that your recovery email and recovery phone are current — a locked account with no working sign-in method is a much harder problem than a broken passkey. Duplicates are common after a phone change: the old phone’s passkey and the new phone’s passkey sit side by side, and the website may try the dead one first. If chrome passkey not working survives a cleaned account list, a fresh passkey, and a fresh profile, the website’s passkey support itself may be at fault — use the password sign-in, and check the website’s help pages for a known passkey problem.
What to Avoid
- Do not delete every passkey at once — keep one working sign-in method until the replacement proves itself.
- Do not turn off sync to “fix” passkeys — sync is how passkeys reach your other devices.
- Do not share passkeys, QR codes, or approval prompts with anyone — a real sign-in approval is only ever for you, on your own device.
- Do not install unknown “passkey manager” extensions — they touch your sign-ins and can steal account access.
- Do not use pirated, cracked, or “free premium” security tools — they are a common source of malware and stolen credentials.
- Do not remove the device screen lock — passkeys cannot work without a PIN, fingerprint, or face check.
- Do not approve a passkey prompt you did not start — an unexpected prompt can mean someone else is trying to sign in as you.
Frequently Asked Questions
Why does the passkey prompt appear on my phone but not on my laptop?
The prompt appears where the passkey lives. If the passkey is stored on the phone, the laptop must reach the phone over Bluetooth to ask for approval, and the phone must be nearby, unlocked, and signed in to the same account. If Bluetooth is off or the phone is far away, nothing appears on the laptop. Fix 3 covers the Bluetooth and proximity checks, and Fix 2 covers the sync that lets the laptop know the passkey exists at all.
Do I still need my password after I create a passkey?
Yes, keep your password safe even after passkeys work well. The password is the fallback when a device is lost, reset, or unavailable, and some sites still ask for it for sensitive changes such as updating recovery options. Store the password in a password manager you trust, and keep your recovery email and recovery phone current. A passkey is a faster way to sign in, not a replacement for account recovery.
Can I use the same passkey on more than one device?
Yes, when the passkey is synced through your Google Account. A passkey created in Chrome is stored in Google Password Manager and synced to your other devices signed in to the same account, so it can be used on each of them. A passkey stored only on a security key or only on one phone, without sync, stays on that device. When chrome passkey not working affects only one device, sync is the first thing to check, as Fix 2 explains.
Why does the site ask for a password even though I have a passkey?
The site falls back to a password when it cannot reach the passkey: the prompt was blocked, Bluetooth could not reach the phone, sync had not fetched the passkey, or the passkey is stale. The fallback is normal behaviour, not a fault in itself — it means the site tried the passkey path and gave up. Work through Fixes 2, 3, and 5 to find which link failed, and the prompt should return on the next sign-in.
Is it safe to approve a passkey prompt on a public or shared computer?
Be careful. Approving a sign-in on a shared computer signs you in on that computer, and the session may stay active after you leave. If you must sign in on a shared computer, use a private browsing window, sign out fully when you finish, and never save the passkey on a computer you do not own. On your own devices, passkeys are safer than passwords, because there is no typed password for anyone to see or steal.
What happens to my passkeys if I lose my phone?
Passkeys synced through your Google Account survive a lost phone, because a copy is stored in your account and synced to your other devices. Sign in to your Google Account on another device, review the passkey list as Fix 11 describes, and remove the passkey for the lost phone. If the passkey was stored only on the lost phone with no sync, it is gone with the phone, and you must sign in with your password and create a fresh passkey. This is why keeping sync on and keeping a second sign-in method matters.
Conclusion
When chrome passkey not working blocks a sign-in, the cause is usually a missing passkey, a signed-out browser, silent sync, switched-off Bluetooth, or a device with no lock screen — not a lost passkey. Check the account settings first, then sign in and turn on sync, then confirm Bluetooth and the screen lock, and finally refresh a stale passkey with a clean replacement. Finish by signing out and signing in again on the same website, with the fingerprint, face, or PIN prompt appearing on its own — that is the only proof that counts. Set it, test it, and sign in without typing a password.
