Explainer
Passkeys explained: how they replace passwords
A passkey is a sign-in credential built on FIDO standards that you unlock with your fingerprint, face, PIN or pattern instead of typing a password.[1] It works by public-key cryptography, so the website holds only a public key and never learns the secret, and it works only on the site it was made for, which blocks phishing.[2][3]
This explainer describes how passkeys work and what standards bodies and platform makers say about them. We did not test any product. Setup steps differ by device and service, so follow your provider’s own instructions.
What a passkey is
A passkey replaces a password. Instead of typing a secret, you approve the sign-in the same way you unlock your phone or laptop: with a fingerprint, a face scan, a PIN or a pattern.[1] Your fingerprint or face data stays on your device and is never sent to the website.[4]
Passkeys can live on your phone or computer, or on a separate hardware security key.[1]
The FIDO Alliance defines a passkey as an authentication credential based on FIDO standards, stored on a phone, computer or hardware security key, and unlocked with the same user verification as the device.[1] Passkeys use the FIDO2 specifications: WebAuthn, the browser API that creates and uses passkeys, and CTAP, the Client to Authenticator Protocol.[5] Biometric matching happens locally, and the relying party never receives the biometric.[4]
How the cryptography works
When you create a passkey, your device makes two linked keys. One is public and goes to the website. The other is private and stays with you. To sign in, your device proves it holds the private key without ever sending it.[2] No shared secret is sent, and the website stores only a public key, so its servers hold no password to steal.[6][3]
Apple describes the flow: at registration the operating system generates a unique key pair for that account. The server stores the public key, and the private key, which is needed to authenticate, is never revealed to the server.[2] No shared secret crosses the wire, and the server does not need to protect the public key.[6]
Why passkeys resist phishing
Unlike a password, a passkey can’t be typed into a fake site: Google says passkeys work only on the websites and apps they were registered with, because the browser or operating system checks the site, so a user cannot be tricked into authenticating on a deceptive site.[3] Google adds that services store only a public key rather than a password.[3]
Security agencies recommend this kind of “phishing-resistant” sign-in. The #StopRansomware Guide from CISA and its partners recommends phishing-resistant multi-factor authentication for email, VPNs and accounts that reach critical systems.[7] Compromised credentials are one of the initial access vectors the guide covers.[8] See how ransomware works and how to spot phishing.
Synced and device-bound passkeys
Passkeys copied between a user’s devices through a cloud service are called synced passkeys. Those that never leave one device, including passkeys on FIDO security keys, are called device-bound passkeys.[9] Apple syncs passkeys with iCloud Keychain, which it says is end-to-end encrypted with keys Apple does not know.[10]
Apple, Google and Microsoft
On 10 October 2023 Google made passkeys the default option for personal Google Accounts and switched on a “Skip password when possible” setting.[11] In May 2025 Microsoft said brand-new Microsoft accounts would be “passwordless by default”.[12] At the same time, citing the FIDO Alliance, Microsoft said more than 15 billion user accounts could sign in with passkeys; that is an industry figure we have not seen independently verified.[13]
In a 2024 survey commissioned by the FIDO Alliance, 53% of people said they had turned on passkeys for at least one account, and 22% on every account they could. These are self-reported answers, not measured usage.[14] For company background, see apple, alphabet and microsoft.
What NIST’s 2025 guidelines say
The US National Institute of Standards and Technology published the fourth revision of its authentication guidelines, SP 800-63B-4, in July 2025. It replaced the 2020 version.[15] The guidelines recognize “syncable authenticators”, whose keys are managed through a sync fabric such as a cloud provider, and set extra requirements for them.[16] Because synced keys must be exportable, they are not allowed at the highest assurance level, AAL3, which requires a non-exportable private key.[17]
NIST also requires services at the middle level, AAL2, to offer at least one phishing-resistant option, and federal agencies to require phishing-resistant authentication for their staff, contractors and partners.[18] For passwords that remain, the same document sets a 15-character minimum for single-factor use and bans composition rules and forced periodic changes.[19]
Read next
Next in the crash course
How VPNs work: tunnels, encryption and their limits
How a VPN tunnels and encrypts your traffic, what it does and doesn't protect according to NIST, NCSC and FTC guidance, and what Ofcom found about UK VPN use.
Questions readers ask
What is a passkey?
A sign-in credential based on FIDO standards, stored on a phone, computer or hardware security key, that you use by unlocking your device with a biometric, PIN or pattern.[1]
Does the website get my fingerprint or face scan?
No. According to the FIDO Alliance, biometric information stays on your device and is never sent to a remote server.[4]
Why are passkeys harder to phish than passwords?
A passkey works only on the website or app it was registered with, so you can't be tricked into using it on a fake site, and the site stores only a public key rather than a password.[3]
What happens if I lose my phone?
Synced passkeys are copied between your devices through a cloud service. Apple, for example, syncs them with end-to-end encrypted iCloud Keychain. Device-bound passkeys, such as those on a security key, never leave that one device.[9][10]
What are FIDO2 and WebAuthn?
FIDO2 is the set of standards passkeys are built on. It has two parts, WebAuthn, the browser API that manages passkeys, and CTAP, which connects devices and security keys.[5]
Sources
· 19 claims from 7 publishers
Each numbered claim is a statement we checked against the sources listed with it. Tap a number in the text to see its sources in place.
- [1]
The FIDO Alliance defines a passkey as an authentication credential based on FIDO standards, stored on a phone, computer or hardware security key, that lets a user sign in with the same method used to unlock the device, such as a biometric, PIN or pattern. confirmedas of 2026-11-07
- Passkeys · FIDO Alliance · Primary source (retrieved 2026-11-07)
- [2]
Apple says passkeys use public key cryptography under the WebAuthn standard - the device creates a unique key pair for each account, the public key is stored on the server and the private key, needed to sign in, is never learned by the server. confirmedas of 2026-11-07
- About the security of passkeys · Apple · Primary source · Credential security (retrieved 2026-11-07)
- About the security of passkeys · Apple · Primary source · Credential security (retrieved 2026-11-07)
- [3]
Google says passkeys work only on the websites and apps they were registered with, so a user cannot be tricked into authenticating on a deceptive site, and developers store only a public key rather than a password. confirmedas of 2026-11-07
- Passkeys (Google for Developers) · Google · Primary source · Passkeys are safer (retrieved 2026-11-07)
- [4]
According to the FIDO Alliance, biometric information used to unlock a passkey stays on the user's device and is never sent to any remote server. confirmedas of 2026-11-07
- Passkeys · FIDO Alliance · Primary source · FAQ: Is the user's biometric information safe when signing in with a passkey? (retrieved 2026-11-07)
- [5]
Passkeys are built on the FIDO2 specifications, WebAuthn and CTAP; the WebAuthn standard covers the browser API that manages passkeys. confirmedas of 2026-11-07
- Passkeys · FIDO Alliance · Primary source · FAQ (retrieved 2026-11-07)
- [7]
The #StopRansomware Guide advises implementing phishing-resistant multi-factor authentication for all services, particularly email, VPNs and accounts that access critical systems. confirmedas of 2026-11-07
- #StopRansomware Guide · CISA, MS-ISAC, NSA and FBI · Primary source · Initial Access Vector: Compromised Credentials (retrieved 2026-11-07)
- [8]
The #StopRansomware Guide groups its prevention advice by six common initial access vectors: internet-facing vulnerabilities and misconfigurations, compromised credentials, phishing, precursor malware infection, advanced forms of social engineering, and third parties and managed service providers. confirmedas of 2026-11-07
- #StopRansomware Guide · CISA, MS-ISAC, NSA and FBI · Primary source · Part 1, section headings (other vectors are later headings) (retrieved 2026-11-07)
- [9]
Passkeys synced between a user's devices through a cloud service are called synced passkeys, while those that never leave a single device, including those on FIDO security keys, are called device-bound passkeys. confirmedas of 2026-11-07
- Passkeys · FIDO Alliance · Primary source · FAQ (retrieved 2026-11-07)
- [10]
Apple syncs passkeys across a user's devices with iCloud Keychain, which it says is end-to-end encrypted with keys not known to Apple. confirmedas of 2026-11-07
- About the security of passkeys · Apple · Primary source · Synchronization security (retrieved 2026-11-07)
- [11]
On 10 October 2023 Google made passkeys the default sign-in option across personal Google Accounts, turning on a "Skip password when possible" setting. confirmedas of 2023-10-10
- Passwordless by default: Make the switch to passkeys · Google · Primary source · 2023-10-10 (retrieved 2026-11-07)
- Passwordless by default: Make the switch to passkeys · Google · Primary source · 2023-10-10 (retrieved 2026-11-07)
- [12]
In May 2025 Microsoft said brand-new Microsoft accounts would be "passwordless by default". confirmedas of 2025-05-01
- Pushing passkeys forward: Microsoft's latest updates for simpler, safer sign-ins · Microsoft Security Blog · Primary source · 2025-05-01 (retrieved 2026-11-07)
- [13]
Microsoft, citing the FIDO Alliance, said in May 2025 that more than 15 billion user accounts could sign in with passkeys instead of passwords. confirmedas of 2025-05-01
- Pushing passkeys forward: Microsoft's latest updates for simpler, safer sign-ins · Microsoft Security Blog · Primary source · 2025-05-01 (retrieved 2026-11-07)
- [14]
In a 2024 survey commissioned by the FIDO Alliance, 53% of people said they had enabled passkeys on at least one account and 22% on every account they could. confirmedas of 2026-11-07
- Passkeys · FIDO Alliance · Primary source · Passkey Adoption (retrieved 2026-11-07)
- [15]
NIST published SP 800-63B-4, its digital identity guidelines for authentication, in July 2025, superseding the 2020 version of SP 800-63B. confirmedas of 2026-11-07
- SP 800-63B-4, Digital Identity Guidelines: Authentication and Authenticator Management (publication page) · NIST Computer Security Resource Center · Primary source (retrieved 2026-11-07)
- [16]
NIST SP 800-63B-4 recognizes "syncable authenticators" that manage authentication keys through a sync fabric such as a cloud provider, and sets additional requirements for them in a normative appendix. confirmedas of 2026-11-07
- NIST SP 800-63B-4: Digital Identity Guidelines, Authentication and Authenticator Management · NIST · Primary source · 2025-07-01 (retrieved 2026-11-07)
- [17]
Because syncable authenticators require an exportable private key, NIST SP 800-63B-4 says they shall not be used at its highest assurance level, AAL3, which requires a non-exportable private key. confirmedas of 2026-11-07
- NIST SP 800-63B-4: Digital Identity Guidelines, Authentication and Authenticator Management · NIST · Primary source · 2025-07-01 (retrieved 2026-11-07)
- [18]
NIST SP 800-63B-4 requires verifiers to offer at least one phishing-resistant authentication option at AAL2, and requires federal agencies to make staff, contractors and partners use phishing-resistant authentication for federal systems. confirmedas of 2026-11-07
- NIST SP 800-63B-4: Digital Identity Guidelines, Authentication and Authenticator Management · NIST · Primary source · 2025-07-01 (retrieved 2026-11-07)
- [19]
NIST SP 800-63B-4 requires single-factor passwords to be at least 15 characters, bars composition rules such as mixing character types, and bars forcing periodic password changes. confirmedas of 2026-11-07
- NIST SP 800-63B-4: Digital Identity Guidelines, Authentication and Authenticator Management · NIST · Primary source · 2025-07-01 (retrieved 2026-11-07)
- NIST SP 800-63B-4: Digital Identity Guidelines, Authentication and Authenticator Management · NIST · Primary source · 2025-07-01 (retrieved 2026-11-07)
Revision history (1)
- Page created.
Created Nov 7, 2026. Last reviewed by an editor on Nov 8, 2026. Next scheduled review: Apr 7, 2027.
Cite this page
"Passkeys explained: how they replace passwords." ContentLora, updated Nov 7, 2026. https://contentlora.com/explain/passkeys-explained
Spotted an error? Suggest a correction or emailcorrections@contentlora.com.