Skip to content
>_KernelBrief
Cybersecurity

Passkeys Explained: How They Work, Why They Beat Passwords, and How to Start Using Them

Passkeys replace passwords with cryptography that can't be phished or reused. How they work, synced vs device-bound passkeys, and how to start.

By Published 7 min read
// SECURITY
Table of contents

A passkey is a replacement for a password that you never have to type, remember or reset. Instead of a secret you share with a website, a passkey is a cryptographic key pair: the website stores a public key, and your device keeps the private key and unlocks it with your fingerprint, face, PIN or screen lock.

The result is sign-in that is both easier and much harder to attack. Passkeys can't be phished, guessed or reused across sites, and a breach of a website's database doesn't expose anything an attacker can log in with. They are built on open standards from the FIDO Alliance and the W3C, and are supported by Apple, Google and Microsoft platforms and all major browsers.

This guide explains how passkeys work, the trade-offs you should understand, and how to start using them.

What problem do passkeys solve?

Passwords fail in predictable ways:

  • Phishing. A convincing fake login page collects your password, and the attacker uses it on the real site.
  • Reuse. One breached site exposes every account where you used the same password.
  • Server breaches. Websites store password hashes; weak passwords can be cracked offline.
  • Weak secrets. People choose memorable passwords, which are also guessable.

Traditional two-factor authentication helps, but one-time codes sent by SMS or shown in an authenticator app can still be typed into a phishing page. Passkeys are designed so that there is no shared secret to steal and nothing to type.

How passkeys work

Passkeys use the WebAuthn standard, published by the W3C, together with FIDO protocols for talking to authenticators.

Creating a passkey

  1. You sign in to a website the usual way and choose "Create a passkey".
  2. Your device generates a brand-new key pair just for that website.
  3. The private key stays on your device (or in your password manager); the public key is sent to the website.
  4. Your device records which website — technically, which domain — the passkey belongs to.

Signing in with a passkey

  1. The website sends a random challenge.
  2. Your device asks you to verify yourself with a fingerprint, face scan, PIN or device password. This unlocks the private key locally.
  3. The device signs the challenge with the private key and sends back the signature.
  4. The website checks the signature with the public key it stored. If it matches, you're in.

Your biometric data never leaves your device and is never sent to the website. The website only ever sees a public key and signatures.

Why phishing doesn't work

The browser binds each passkey to the domain it was created on. If you land on examp1e-login.com instead of example.com, your browser simply won't offer the example.com passkey — there is nothing for you to be tricked into handing over. This origin binding is what makes passkeys "phishing-resistant", the property that agencies such as CISA recommend as the strongest form of multi-factor authentication.

Why a database breach doesn't expose you

A website that supports passkeys stores only public keys. A public key can't be used to sign in, so stealing the database gives an attacker nothing they can replay elsewhere.

Synced passkeys vs device-bound passkeys

There are two main kinds of passkeys, and the difference matters for recovery and for security policy.

Synced passkeys Device-bound passkeys
Where the private key lives In a credential manager that syncs across your devices (e.g. iCloud Keychain, Google Password Manager, or a third-party password manager) On one physical device, typically a hardware security key
If you lose a device Restored when you sign in to the credential manager on a new device Lost; you need another registered passkey or a recovery method
Typical use Consumers and most workforce accounts High-security accounts and regulated environments

Synced passkeys are what made passkeys mainstream: you create one on your phone and it is available on your laptop and tablet. The security of synced passkeys depends partly on the security of the account that syncs them, so protect that account well.

The U.S. National Institute of Standards and Technology first addressed this in an April 2024 supplement, and its current digital identity guidelines include an appendix on syncable authenticators. NIST says synced passkeys can support its AAL2 assurance level when the sync service meets its requirements; because syncing means the key can be exported, they don't meet AAL3, which requires non-exportable keys such as those on hardware security keys.

Using a passkey on someone else's computer

You don't need your passkey stored on every device. When you sign in on a computer that doesn't have your passkey, most browsers offer a QR code. Scan it with your phone, verify with your fingerprint or face, and the phone completes the sign-in. The protocol uses Bluetooth to check that your phone is physically near the computer, which stops a remote attacker from relaying the request.

How to start using passkeys

1. Secure your credential manager first

Your passkeys will live in Apple's iCloud Keychain, Google Password Manager, Microsoft's Windows Hello / Microsoft account, or a third-party password manager. Make sure that account has a strong unique password, a recovery method you control, and its own strong second factor.

2. Add passkeys to your most important accounts

Start with the accounts that unlock everything else:

  • Your primary email account (it can reset all your other passwords).
  • Your Apple, Google or Microsoft account.
  • Your password manager, if it supports passkey sign-in.
  • Code hosting (GitHub, GitLab) and cloud accounts if you're a developer.
  • Financial services that offer passkeys.

Look for a "Passkeys" or "Security keys" option in each account's security settings. The passkeys.dev community site maintains information on supporting services.

3. Register a backup

For critical accounts, register at least two passkeys — for example, one synced passkey and one hardware security key kept somewhere safe — or make sure you have a working recovery method. Websites differ in how they handle account recovery, and a forgotten recovery path is the most common way people get locked out.

4. Keep your old methods tidy

Many sites keep your password as a fallback after you add a passkey. Where a service allows it, removing or strengthening weaker fallbacks (like SMS codes) improves security, because an attacker will always target the weakest option available.

Limitations and honest trade-offs

Passkeys are a major improvement, but they are not magic:

  • Account recovery is still the weak spot. If a service lets anyone reset access with a simple email link or SMS code, attackers will target that instead.
  • Ecosystem lock-in has been a real concern. The FIDO Alliance has been developing standard formats for securely moving passkeys between credential managers; until those are universally supported, check how your chosen manager handles export before committing.
  • Shared accounts are awkward. Passkeys are designed around individuals; sharing access works best through password managers that support sharing passkeys within families or teams.
  • Malware on your unlocked device can still abuse an active session. Passkeys protect the sign-in step, not a compromised computer.

For developers: adding passkey support

If you build web applications, passkey support is implemented with the browser's WebAuthn API (navigator.credentials.create() and navigator.credentials.get()), plus server-side verification of attestation and assertion responses. Use a well-maintained, audited WebAuthn library for your server language rather than implementing the cryptographic verification yourself, and offer passkeys alongside existing sign-in methods while users migrate. The W3C WebAuthn specification and passkeys.dev are the authoritative references.

Developers who manage servers can apply the same public-key principle to infrastructure access — our guide to generating Ed25519 SSH keys covers hardware-backed keys too.

The bottom line

Passkeys remove the password from the most common attacks — phishing, reuse and database breaches — while making sign-in faster. Turn them on for your email, your platform account and your password manager first, register a backup for anything critical, and you will have removed the biggest risks most people face online.

Frequently asked questions

+Are passkeys safer than passwords?

Yes, for the most common attacks. A passkey can't be reused across sites, can't be guessed, isn't stored on the website's server in a usable form, and only works on the real website it was created for — which defeats phishing pages.

+What happens to my passkeys if I lose my phone?

If you use synced passkeys (for example in iCloud Keychain, Google Password Manager or a third-party password manager), they are restored when you sign in to that account on a new device. Device-bound passkeys on a lost security key are gone, which is why you should register more than one.

+Does the website get my fingerprint or face data?

No. Biometrics are only used locally to unlock the passkey on your device. The website receives a cryptographic signature, not your biometric data.

+Can I use a passkey on a computer that doesn't have it?

Usually yes. Most browsers can show a QR code that you scan with your phone; the phone then signs you in, using Bluetooth to confirm it is physically nearby.

Sources & references

  1. FIDO Alliance — Passkeys
  2. W3C — Web Authentication: An API for accessing Public Key Credentials (WebAuthn)
  3. passkeys.dev — Passkeys developer resources (FIDO Alliance and W3C community)
  4. NIST — SP 800-63B (rev. 4), Appendix B: Syncable Authenticators
  5. CISA — Implementing Phishing-Resistant MFA (fact sheet)

Spotted an error? See our Corrections Policy.

  • #passkeys
  • #webauthn
  • #fido2
  • #authentication
  • #phishing
  • #passwords
KB

KernelBrief Editorial

The KernelBrief editorial desk researches, writes and fact-checks every article published on this site. Every article is checked against primary sources (official documentation, vendor announcements, standards bodies and original research) before publication. Every factual claim is linked to its source, and corrections are handled under our published Corrections Policy.