Passkeys

Person approving a passkey sign-in on a smartphone beside a laptop

Passkeys Explainer

A passkey is a digital credential tied to a user account and a specific website or application. Instead of typing a reusable password, the user approves sign-in with a device unlock such as a PIN, fingerprint, or face scan. Passkeys are built on public-key cryptography and web standards including WebAuthn, allowing compatible browsers, operating systems, and password managers to participate in the same authentication process.

When a passkey is created, the device produces a public-private key pair. The service stores the public key, while the private key remains under the control of the user’s authenticator or passkey provider. During sign-in, the server sends a fresh challenge. The authenticator signs it after local user verification, and the server checks that signature with the stored public key.

This design reduces two common password risks. A server breach does not expose a reusable secret that can be entered elsewhere, and the credential is bound to the legitimate site identity, making it resistant to phishing pages on look-alike domains. The biometric or PIN normally unlocks the authenticator locally; the website does not receive a copy of the fingerprint, face, or device PIN.

Passkeys still require careful account design. Users may lose devices, switch ecosystems, use shared computers, or need recovery. Synced passkeys depend on provider security, while device-bound credentials require another way to regain access. Services should explain where credentials are stored, support management and revocation, protect recovery flows, and maintain suitable alternatives during the transition from passwords.

Passkeys replace password entry with a cryptographic credential. Key terms include relying party, authenticator, public key, private key, challenge, WebAuthn, synchronization, and recovery.

A device PIN or biometric unlocks use of the credential; it is not sent to the website as the login secret. Source: Google for Developers — Passkeys.

The service sends a unique challenge, the authenticator signs it with the private key, and the server verifies the result using the public key.

Because the credential is bound to the correct domain or app identity, a deceptive site cannot request a valid signature for another service.

Passkeys reduce password reuse, credential phishing, and the value of stolen server authentication databases.

Account recovery remains security-critical, and cross-device support varies by platform, provider, and whether the credential is synced or device-bound.

Explore more "Explainers"

Discover additional explainers across politics, science, business, technology, and other fields. Each explainer breaks down a complex idea into clear, everyday language—helping you better understand how major concepts, systems, and debates shape the world around us.