Passkeys explained: the sign-in with no shared secret
A passkey replaces a password with a cryptographic key pair: the website stores only the public half, and you sign in with the same fingerprint, face or PIN that unlocks your device. What passkeys are, why phishing fails against them, what happens to your existing password and two-factor codes when you add one, and what to check before relying on one - from FIDO, Google, Apple and Microsoft's own documentation, read 21 November 2026.
A growing number of accounts now offer a passkey instead of a password, and the prompt can look like just another popup. It is worth understanding before you tap "create", because a passkey changes what a website holds about you and how you will sign in for years. Everything below comes from the documentation of the FIDO Alliance (the industry body behind the standard), Google, Apple and Microsoft, all read 21 November 2026.
What a passkey actually is
A passkey is a FIDO cryptographic credential tied to your account on one specific website or app, in the FIDO Alliance's definition. When you create one, your device generates a unique key pair for that one account: a public key that goes to the website's server, and a private key that stays on your device. The server never learns the private key. Signing in means approving the sign-in the same way you unlock your device - fingerprint, face scan, PIN or pattern - and the device then signs the site's challenge with the private key, which is never sent. Apple describes the same model: keys are generated by the device, securely and uniquely, for every account, and no shared secret is ever transmitted. passkeys.dev, the developer guidance site maintained by FIDO Alliance members, adds the design consequence: passkeys are automatically unique per service, so there is nothing to reuse across sites.
Why phishing fails against it
A phishing page works because a password can be typed anywhere. A passkey cannot: Google's account help notes that passkeys "can't be shared, copied, written down, or accidentally given to someone else." More fundamentally, passkeys.dev explains that browsers and operating systems enforce that a passkey is only ever used for the service it was created for: the device signs a challenge only for the matching site, so a lookalike site receives no valid signature - the matching check is made by the device, not by your eyes. And passkey credential records on the server hold only public keys, which are not secrets, so a stolen passkey database gives an attacker nothing to replay; other data the server holds is a separate matter. Adoption is why you are seeing the prompts now: in a 2024 independent survey commissioned by the FIDO Alliance, 53% of people reported enabling passkeys on at least one account.
Where the protection stops
Phishing resistance covers the sign-in credential, not the whole account, and the checked documents are careful about that scope. Recovery and fallback paths still exist: Google states that adding a passkey leaves every existing factor untouched, and FIDO describes services falling back to other authentication methods - typically a knowledge-based credential such as a password - when no passkey is available on the device. None of the checked pages claims protection for a session after sign-in, or against someone who can already unlock your device; FIDO's own guidance points people in shared or restricted environments toward device-bound security keys for exactly this reason. The practical reading: a passkey removes the phishable secret from sign-in, while the account remains only as safe as its recovery settings, the device unlock, and the provider account behind the sync.
What changes - and what does not - when you add one
Google's documentation is explicit: adding a passkey to your Google Account does not change or remove any authentication or recovery factors already on the account. Your password, backup codes and recovery options stay exactly as they were. One behavior matters if you use two-step verification: on Google accounts with 2-Step Verification or Advanced Protection, signing in with a passkey bypasses the second step, because the passkey itself verifies that you hold the device and unlocked it. The FIDO Alliance makes the broader claim that a passkey alone is more secure than "password + OTP" or "password + phone approval", since the common second factors remain phishable. Your biometrics are not part of the deal: Google, Apple and FIDO all state that fingerprint or face data stays on the device and is never sent to any server - the server only receives an assurance that the local check passed.
Where passkeys live, and how they follow you
Passkeys are stored by a "passkey provider": a built-in credential manager such as iCloud Keychain, Google Password Manager or Microsoft Password Manager, or a third-party manager such as 1Password or Dashlane, per FIDO and Microsoft documentation. Synced passkeys are copied across your devices through that provider; Apple states iCloud Keychain sync is end-to-end encrypted with keys Apple does not know, and FIDO says passkey syncing generally is end-to-end encrypted. Device-bound passkeys - on a hardware security key, for example - never leave that one piece of hardware. Signing in on a device that does not have your passkey uses cross-device authentication: the site shows a QR code, your phone scans it, and Bluetooth Low Energy verifies the two devices are physically near each other. FIDO notes the BLE link proves proximity only; the sign-in itself is protected by standard cryptography, not by Bluetooth's security.
Losing devices, switching platforms, getting back in
Because synced passkeys live in your provider account, a new device signed into that account receives them. If you lose every device, recovery runs through the provider: Apple describes iCloud Keychain escrow, where recovery needs your Apple Account password, an SMS to your registered number, and your device passcode - with only 10 passcode attempts before the escrow record is destroyed, and an optional recovery contact you can set up in advance. Switching between iPhone and Android works through a cross-platform manager, a security key, or by signing in on the new device with the old one nearby and creating a fresh passkey there, per FIDO's guidance. The practical consequence: your provider account becomes the master key, so it needs strong protection itself - Apple requires two-factor authentication on any Apple Account that uses iCloud Keychain, and registering a passkey without it prompts you to set 2FA up.
What to check before you rely on one
Three checks from the same documents. First, your devices: Google lists minimums of Windows 10, macOS Ventura, ChromeOS 109, Android 9 or iOS 16, or a security key supporting the FIDO2 protocol. Second, the site itself: Microsoft notes you can only create a passkey where the sign-in flow offers one - if you are never prompted, that service does not support it yet, so your password and second factor still matter there. Third, your exits: keep the account's recovery factors current, because Google's model leaves them untouched and they remain your way back when a passkey is unavailable. None of the checked documents suggests deleting your password once a passkey exists.
Sources, all read 21 November 2026: FIDO Alliance, Passkeys (definition; synced vs device-bound passkeys; cross-device authentication over QR and BLE proximity; passkey providers; fallback to other authentication methods; security keys for shared or restricted environments; 2024 commissioned survey figure); passkeys.dev, What are passkeys? (unique per-service by design; servers store only public keys; site enforcement by browser and OS); Google Account Help, Sign in with a passkey instead of a password (existing factors unchanged; second-step bypass with 2-Step Verification or Advanced Protection; device minimums; biometrics stay on device; passkeys cannot be shared or copied); Apple Support, About the security of passkeys (key generation on device; iCloud Keychain end-to-end encryption, escrow recovery, 10-attempt limit, recovery contacts; 2FA requirement); Microsoft Support, Create and save a passkey (save locations including password managers, phones via QR code, security keys and Windows Hello; passkeys offered only where supported).
Frequently asked questions
Is a passkey more secure than a password plus two-factor authentication?
The FIDO Alliance says yes for the common forms: it states that a passkey alone is more secure than "password + OTP" or "password + phone approval", because one-time codes and approval prompts can still be phished while a passkey is bound to the real site by the browser or operating system. This is the standards body's position from its own documentation, not an independent benchmark.
Does adding a passkey remove my password or two-factor codes?
No. Google's account help states that adding a passkey does not change or remove any authentication or recovery factors on the account. One behavior changes: on accounts with 2-Step Verification or Advanced Protection, signing in with a passkey skips the second step, because the passkey already proves you hold and unlocked the device.
Does the website get my fingerprint or face scan?
No. Google, Apple and the FIDO Alliance each state that biometric data stays on your device and is never sent to any server. The website receives only a cryptographic assurance that the local unlock check passed.
What happens if I lose the phone that holds my passkeys?
If your passkeys sync through a provider (iCloud Keychain, Google Password Manager, Microsoft Password Manager or a third-party manager), signing into that provider on a new device restores them - Apple states the sync is end-to-end encrypted. If every device is gone, recovery runs through the provider: Apple's iCloud Keychain escrow, for example, requires your account password, an SMS to your registered number and your device passcode, allows 10 attempts, and offers an optional recovery contact set up in advance. Keeping the provider account's own recovery options current is what makes this survivable.
Does a passkey protect my whole account?
It protects the sign-in credential. The checked documents scope it that way: Google states your existing password and recovery factors remain in place, and FIDO describes services falling back to other sign-in methods when no passkey is at hand - so those paths must stay secured too. None of the checked pages claims protection for a session after sign-in or against someone who can unlock your device; FIDO points users in shared or restricted environments toward device-bound security keys. Recovery security is where the synced versus device-bound distinction matters most: synced passkeys recover through the provider account (with its own encryption and recovery rules, such as Apple's escrow), while a device-bound passkey on a lost security key has no synced copy to fall back on.
Can I use a passkey on any website?
Only where the site supports it. Microsoft's documentation is blunt: if you are not prompted to create or save a passkey when signing in, that website, service or app does not support it at the moment. Your password and second factor remain the sign-in method there.
Do passkeys work if I switch from iPhone to Android, or the reverse?
Yes, through three routes in the FIDO Alliance's guidance: a cross-platform credential manager configured on the new device; a hardware security key, which carries device-bound passkeys between platforms; or signing in on the new device using the old device still in your possession, then creating a new passkey in the new device's provider. Without any of those, the service treats it as a normal account recovery.