Passkey Not Working? A Step-by-Step Troubleshooting Path

A passkey that refuses to work is usually one of a few distinct problems, and they look identical from the outside. Work through them in this order and you will usually find the cause without risking the account.

Name the symptom precisely first

Passkey sign-in crosses four layers: the site, the browser, the operating system, and whatever software holds the credential. Each failure pattern points at a different layer.

The passkey option never appears

The page loads and you can type your email, but nothing on it mentions passkeys — only a password field. That points at the site, or at the sign-in route you landed on, not your device.

The button is there, but no prompt arrives

You click "sign in with a passkey" and nothing happens: no system dialog, no fingerprint or face prompt, no PIN request. The request either never started in the browser or never reached an authenticator.

A generic error after you authenticate

The prompt appears, you approve it, and the site returns "something went wrong". That message is misleading, because it arrives after your device has done its part — the failure is on the account or verification side.

It works on one device and not another

Sign-in succeeds on the laptop and fails on the phone, or the reverse. Often not a bug: a passkey can be bound to a single device or a single security key, so the second device was never going to have a copy.

Symptom, likely cause, first check

Symptom	Likely cause	First thing to check
No passkey option on the sign-in page	Passkeys are not available for this account yet, or this is a different sign-in route	Sign in another way and check the account's security settings
Clicking the button does nothing	The browser could not complete the WebAuthn call, or something intercepted it	Retry in a fresh profile with extensions disabled
Prompt appears, then a generic error	The credential does not match one the site holds for this account	Confirm you are in the account the passkey was registered to
Works on one device, fails on another	Device-bound, or synced but not yet on the second device	Compare the passkey lists on both devices
Prompt demands a security key you do not have	A hardware key is registered and the browser is choosing it	Plug the key in, or pick another method on that screen

The ordered path

Work top to bottom. Every step before the fallbacks is cheap and reversible. Do not jump to "delete the passkey and start over" — that is the one step that can cost you access.

Step 1 — Confirm the OS and browser are current

Passkeys depend on both the operating system and the browser, and the two need to agree. Open the browser's About page and let it update if it offers to, then check the OS update screen. If either is well behind, update and retry.

Step 2 — Check that the site actually supports WebAuthn

WebAuthn is the browser standard passkeys are built on. A site supports it only if it can both create a credential and verify the signature that credential produces later. Support is often rolled out gradually, so "no passkey button for me" is not proof the feature does not exist.

• Look in your account's security settings, not only on the login page.
• Load the sign-in page in a private window, without your account's customisations.
• Check the site's help or status page for whether passkeys are available broadly yet.
• If another account sees the button and yours does not, that is a rollout question, not a device fault.

A page can also offer to create a passkey while failing to verify it later — read passkey saved but login still fails.

Step 3 — Check where the credential is actually stored

Go and look. In your OS settings or password manager, open the saved passkeys list and find the entry for this site. Note the username it is attached to and which device holds it. Many "it does not work" cases turn out to be "the passkey belongs to my personal account and I am signing into my work account".

Step 4 — Decide whether it is synced or device-bound

A synced passkey lives in a keychain or manager that copies it to your other devices; a device-bound one never leaves the hardware that created it. If the failing device is not the one that enrolled, that distinction is often the whole answer.

Step 5 — Rule out browser profile and clutter

Each browser profile keeps its own storage, so a passkey created in one is often invisible in another, and a private window is a third, empty context. Extensions and content blockers can interfere with the prompt, and managed work devices may restrict which authenticators are allowed. One caution: be sceptical of "just clear your browsing data". On some setups the passkey lives inside the browser profile, and clearing it removes the credential you are trying to repair.

Step 6 — Fall back cleanly

If you can reach the account another way, use it: a hardware security key, a one-time code, or your password plus whatever second factor the site wants. Then open the passkey list and register again from settings instead of retrying the login button. If you cannot get in at all, use the password reset or recovery flow before deleting anything; the locked-out sequence is in passkey lost phone, and backup and recovery covers what to set up next.

What not to do

• Do not delete the passkey from the site's settings first. If you cannot sign in another way, you may not be able to add it back.
• Do not wipe browser profile data to "reset" passkeys: that removes credentials without repairing registration.
• Do not skip the hardware key as a fallback. Weigh it against a password manager in passkey versus password manager first, and see password managers with passkey recovery if you would rather have that handled for you.

Where to go next

• Passkey troubleshooting index Grouped by what you actually see on screen.
• Password managers compared for passkeys How they differ on passkey storage, export, and recovery.

Last updated: 2026-10-16