Passkey
About 4 min read
Last updated: 2026-03-28
What Are Passkeys
Passkeys are a new authentication method that replaces passwords, based on the FIDO2/WebAuthn standard. They allow you to log in to websites and apps using biometric authentication on your smartphone (fingerprint or face recognition) or Windows Hello on your PC.
The core of passkeys is public key cryptography. When you register with a service, a private key is stored on your device and a public key is stored on the server. During login, your device generates a signature with the private key, and the server verifies it with the public key. Since no "shared secret" like a password travels over the network, passkeys are fundamentally resistant to phishing and data breaches.
Why Passkeys Are More Secure Than Passwords
- Phishing Resistance: Passkeys verify the domain during authentication. A passkey created on a legitimate site won't work on a phishing site, making it structurally impossible to accidentally enter credentials on a fake site.
- Elimination of Leak Risk: Only the public key is stored on the server. Even if the server is compromised, it's cryptographically impossible to reconstruct the passkey from the public key. Credential stuffing attacks also become infeasible.
- Impossible to Guess: Passkeys are cryptographically generated key pairs, making them virtually impossible to guess through brute force attacks.
- No Reuse Problem: A unique key pair is generated for each service, so even if one service is compromised, other services remain unaffected.
Passkey Sync and Management
There are two types of passkeys: "device-bound" and "synced."
Device-bound passkeys are tied to specific hardware like security keys (YubiKey, etc.) and cannot be copied externally. They are the most secure but access is lost if the device is lost.
Synced passkeys are synchronized across multiple devices through Apple's iCloud Keychain, Google Password Manager, or password managers (1Password, Bitwarden, etc.). They offer high convenience and allow access from another device if one is lost.
The security of synced passkeys depends on the security of the sync account (Apple ID, Google Account, etc.). Always set up strong two-factor authentication on your sync accounts.
Adoption Status and Migration Tips
As of 2026, passkeys are rapidly gaining adoption. Major services including Google, Apple, Microsoft, Amazon, GitHub, and PayPal already support them.
A gradual approach to migrating to passkeys is practical.
- First, set up passkeys on your most important accounts (email, financial, cloud storage)
- After setting up passkeys, keep password + 2FA as a backup method for a while
- Once comfortable with passkey usage, gradually expand to more services
- Managing passkeys centrally with a password manager makes multi-device usage smoother
For services that don't yet support passkeys, the best approach remains using strong passwords generated by a password manager combined with 2FA.
FIDO2/WebAuthn Technical Architecture and Cross-Device Authentication
FIDO2, the foundation of passkeys, consists of two specifications: WebAuthn (Web Authentication API) and CTAP (Client to Authenticator Protocol).
Registration Flow: When a user creates a passkey, the browser's WebAuthn API requests the authenticator (the device's biometric module or security key) to generate a key pair. The authenticator stores the private key in a secure area (TPM, Secure Enclave) and sends the public key to the server. The service's origin (domain) is bound to the key at this point.
Authentication Flow: The server generates a random challenge (nonce) and sends it to the browser. The browser passes the challenge to the authenticator via the WebAuthn API, and when the user completes biometric verification, the private key signs the challenge. The server verifies the signature with the stored public key, completing authentication. No secret information ever travels over the network.
Cross-Device Authentication (Hybrid Transport): When you want to log in on a PC but your passkey is on your smartphone, CTAP 2.2's hybrid transport can be used. A QR code is displayed on the PC screen, and scanning it with your smartphone triggers proximity verification via Bluetooth Low Energy (BLE), completing the PC login through biometric authentication on the smartphone.
Platform Support: iOS 16+ and macOS Ventura+ sync passkeys via iCloud Keychain. Android supports them through Google Password Manager, integrated with Chrome. Windows provides device-bound passkeys via Windows Hello, while synced passkeys are supported through third-party password managers like 1Password and Bitwarden. Linux currently focuses on security key support via browsers.
Organizational Migration Strategy: When enterprises migrate from passwords to passkeys, a phased approach is more effective than a company-wide switch. Start with a pilot deployment in IT and security teams to identify operational challenges. Then establish a coexistence period for passkeys and passwords, allowing users to migrate at their own pace. Finally, transition to mandatory passkey use, but always maintain security key backup options.
To learn more about this topic, see What Are Passkeys? How Passwordless Authentication Works.
Common Misconceptions
- Passkeys send biometric data to the server
- Biometric authentication is completed entirely on the device, and fingerprint or facial data is never sent to the server. Biometrics are only used to authorize access to the private key stored on the device.
- If I set up passkeys and lose my smartphone, I won't be able to log in
- Synced passkeys are backed up to the cloud through iCloud Keychain or Google Password Manager. Logging into your account on a new device will restore your passkeys.
Passkeys vs. Password + 2FA
Passkeys
Public key cryptography. Phishing resistant. No secrets stored on the server. One-step login via biometrics. Impossible to leak or guess.
Password + 2FA
Shared secret model. Risk of entering password and code on phishing sites. Password hash stored on server. Requires two-step operation.