# Passkeys vs passwords: what changes and what doesn't

Source: https://passwordgeneratorlab.com/guides/passkeys-vs-passwords/

> How passkeys work, why they resist phishing, how they compare with passwords and 2FA, their limits, and why you still need strong passwords.

Updated 9 November 2026 · 7 min read

## Key takeaways

- A passkey is a FIDO2/WebAuthn key pair: the website stores only a public key, and the private key stays with your device or passkey provider.
- Passkeys resist phishing because each one is bound to the website it was created for, so a lookalike site gets nothing it can use.
- NIST SP 800-63B-4 accepts synced passkeys up to AAL2; its highest level, AAL3, requires a non-exportable, device-bound key.
- Moving passkeys between providers is starting to work: FIDO's Credential Exchange Format is a Proposed Standard, used by Apple's OS 26 releases and an Android API.
- Strong, unique passwords are still needed for sites without passkeys, for accounts that keep a password as a fallback, and for the accounts that hold your passkeys.

Last reviewed 9 November 2026

A passkey lets you sign in by unlocking your phone or computer, with your fingerprint, face, PIN or screen lock, instead of typing a password. More and more sites offer them, and some new accounts no longer ask for a password at all. This guide explains what a passkey actually is, why it stops the phishing attacks that defeat passwords and most two-factor codes, where it still falls short, and why a strong password remains part of the picture.

## What a passkey is

A passkey is a sign-in credential built on the FIDO Alliance's FIDO2 standards and the W3C's Web Authentication API (WebAuthn), which browsers and operating systems implement. Instead of a shared secret that you and the website both know, a passkey is a **key pair**:

- The **private key** stays in your passkey provider: your phone, computer, password manager or a hardware security key. It is never sent to the website.
- The **public key** is stored by the website. It can check a signature made by the private key, but it can't be used to create one.

When you sign in, the site sends a fresh random challenge. Your device asks you to unlock it, signs the challenge with the private key, and returns the signature. The site verifies it with the public key it has on file. Your fingerprint or face only unlocks the key on your device; Google and the FIDO Alliance both state that biometric data stays on the device and is never sent to a remote server.

## Synced and device-bound passkeys

Passkeys come in two kinds, and the difference matters for both convenience and recovery:

- **Synced passkeys** are stored by a passkey provider such as Apple Passwords (iCloud Keychain), Google Password Manager or a third-party password manager, and copied to your other devices. Apple and Google both describe this sync as end-to-end encrypted. Lose your phone and the passkey is still on your laptop or comes back when you sign in to a new device.
- **Device-bound passkeys** never leave one piece of hardware, typically a FIDO2 security key. They are the strongest option, but losing the key means losing that passkey, and some keys have limited room: a YubiKey 5 holds 25 passkeys, or 100 on firmware 5.7.4 and later.

NIST's current digital identity guidelines (SP 800-63B-4) accept synced passkeys up to its middle assurance level (AAL2), which covers most everyday accounts. Its highest level (AAL3) requires a key that can't be exported, so only device-bound authenticators qualify there.

You can also use a passkey stored on your phone to sign in on a nearby computer. The computer shows a QR code, you scan it with your phone, and the two devices confirm they're physically close (over Bluetooth) before your phone approves the sign-in. This is the FIDO "hybrid" cross-device flow.

## Why passkeys resist phishing

A phishing page works by getting you to type a secret into the wrong site. A password, or a one-time code from SMS or an authenticator app, is just text: whoever receives it can replay it on the real site within seconds.

A passkey is created for one specific website (the WebAuthn "relying party"), and the browser enforces that link. A lookalike domain asking for your passkey gets nothing, because your device has no passkey for that domain, and a signature made for one site isn't valid on another. There is also nothing for you to read out or copy, so you can't be talked into handing it over. That is why Google describes passkeys as working "only on their registered websites and apps" and why CISA names FIDO/WebAuthn as the widely available form of phishing-resistant MFA.

A passkey also removes two other password problems. There is no shared secret on the server, so a database breach exposes only public keys, which can't be used to sign in. And each passkey is unique to its site, so there is nothing to reuse and nothing for credential-stuffing attacks to try elsewhere.

## Passwords, passwords plus 2FA, and passkeys compared

| Question | Password only | Password + code (SMS or app) | Passkey |
| --- | --- | --- | --- |
| Can a fake site steal what it needs? | Yes | Yes, if it relays the code in real time | No: the passkey is bound to the real site |
| What does a server breach expose? | Password hashes, which can be cracked if the password is weak | Password hashes; the server also stores the shared secret behind app codes | Public keys, which can't be used to sign in |
| Risk from reuse across sites | High if you reuse it | Reduced: the code is still needed | None: each passkey is unique to one site |
| What you have to remember or type | The password | The password and a code | Nothing; you unlock your device |
| Works everywhere today? | Almost everywhere | Most major services | A growing but still partial list of services |

If you want the details on codes, push prompts and security keys, see our [two-factor authentication guide](https://passwordgeneratorlab.com/guides/two-factor-authentication/). Depending on the service, a passkey is used either as a complete sign-in on its own or as a phishing-resistant second factor.

## Where you can use passkeys

Support is built into current versions of the major platforms. According to the industry reference site passkeys.dev, synced passkeys work out of the box on iOS and iPadOS 16 or later, macOS 13 or later, Android 9 or later and ChromeOS 129 or later, and Windows (23H2 or later) can use a passkey from a nearby phone. Third-party password managers can also store and sync passkeys across platforms.

On the website side, adoption has moved past early adopters. Microsoft, for example, made new consumer Microsoft accounts passwordless by default in May 2025, and the FIDO Alliance reports that billions of accounts can now sign in with a passkey. Still, a passkey only helps on sites that support it, and many sites, especially smaller ones, don't yet.

## The limitations to know about

- **Account recovery is the weak point.** If you lose every device with your passkeys, you depend on your provider's recovery process, or the website's. Many sites fall back to email, SMS or a password, and an attacker can target that fallback instead of the passkey.
- **Passwords often stay switched on.** Adding a passkey usually doesn't remove your password. As long as the account still accepts it, that password can be phished, guessed or reused, so it still needs to be strong and unique.
- **Ecosystem lock-in is easing, slowly.** Passkeys used to be hard to move between providers. The FIDO Alliance published the Credential Exchange Format (CXF) as a Proposed Standard in August 2025, with an errata update in March 2026. Apple's iOS, iPadOS, macOS and visionOS 26 support direct, user-initiated transfers between participating credential managers, and Android offers a same-device credential transfer API built on CXF. The companion transfer protocol (CXP) is still a draft, and both sides of a transfer must support it, so check before you switch managers.
- **Sharing is uneven.** A password can be shared, for better or worse. Some providers, such as Apple Passwords, let you share passkeys with a trusted group or over AirDrop; others don't. For shared household or team accounts, a password in a shared password-manager vault is often still the practical answer.
- **Your device becomes the key.** Anyone who can unlock your phone or computer can use its passkeys, and malware on an unlocked device can misuse your sessions. A strong screen lock matters more than ever.

## Why you still need strong passwords

Passkeys are the better sign-in method where they're offered, but passwords aren't going away yet:

- **Sites without passkey support** still need a unique, random password, ideally with the strongest second factor they offer.
- **Accounts that keep a password alongside the passkey** are only as safe as that password.
- **The accounts that hold your passkeys**, such as your Apple, Google or Microsoft account or your password manager, are often protected or recovered with a password or passphrase. That one deserves the most care: long, unique and memorable, protected with two-factor authentication.
- **Devices and encrypted backups** still rely on PINs, passcodes and passphrases.

A password manager handles both worlds: many now store passkeys as well as passwords, and they make a unique password for every remaining account effortless. See [do you need a password manager?](https://passwordgeneratorlab.com/guides/do-you-need-a-password-manager/) For the passwords you still need, our [password generator](https://passwordgeneratorlab.com/) creates them in your browser with the Web Crypto API, and nothing is sent anywhere.

## A practical plan

1. Turn on a passkey for your main email, Apple, Google or Microsoft account, and your password manager first.
2. Add a passkey wherever a site offers one, and register it on two devices or providers where you can, so losing one isn't a crisis.
3. Keep a strong, unique password (or long passphrase) on every account that still has one.
4. Store recovery codes safely, and check that each account's recovery path isn't weaker than its sign-in.

## Sources

- [FIDO Alliance: Passkeys](https://fidoalliance.org/passkeys/)
- [W3C: Web Authentication — An API for accessing Public Key Credentials, Level 3 (Recommendation, August 2026)](https://www.w3.org/TR/webauthn-3/)
- [passkeys.dev: Terminology (synced and device-bound passkeys, cross-device authentication)](https://passkeys.dev/docs/reference/terms/)
- [passkeys.dev: Device support](https://passkeys.dev/device-support/)
- [NIST SP 800-63B-4, Digital Identity Guidelines: Authentication and Authenticator Management (2025)](https://pages.nist.gov/800-63-4/sp800-63b.html)
- [CISA: Implementing Phishing-Resistant MFA (fact sheet)](https://www.cisa.gov/sites/default/files/publications/fact-sheet-implementing-phishing-resistant-mfa-508c.pdf)
- [Google for Developers: Passkeys](https://developers.google.com/identity/passkeys)
- [Google Account Help: Sign in with a passkey instead of a password](https://support.google.com/accounts/answer/13548313)
- [Apple Support: About the security of passkeys](https://support.apple.com/en-us/102195)
- [FIDO Alliance: Credential Exchange Format v1.0 (Proposed Standard, errata March 2026)](https://fidoalliance.org/specs/cx/cxf-v1.0-ps-errata-20260309.html)
- [Apple Developer, WWDC25: What's new in passkeys (credential import and export)](https://developer.apple.com/videos/play/wwdc2025/279/)
- [Android Developers: Credential transfer between credential providers (FIDO CXF)](https://developer.android.com/identity/sign-in/credential-transfer)
- [Apple Support: Share passwords and passkeys with people you trust on iPhone](https://support.apple.com/guide/iphone/share-passwords-iphe6b2b7043/ios)
- [Microsoft Security Blog: Pushing passkeys forward (May 2025)](https://www.microsoft.com/en-us/security/blog/2025/05/01/pushing-passkeys-forward-microsofts-latest-updates-for-simpler-safer-sign-ins/)
- [Yubico Support: How many accounts can I register my YubiKey with?](https://support.yubico.com/s/article/How-many-accounts-can-I-register-my-YubiKey-with)

## Keep reading

- [Has my password been leaked? How to check safely](https://passwordgeneratorlab.com/guides/has-my-password-been-leaked/) — How to check if your email or password appeared in a data breach without exposing it, what a “not found” result really means, and what to do if it leaked.
- [Do you need a password manager?](https://passwordgeneratorlab.com/guides/do-you-need-a-password-manager/) — Why password reuse is the real risk, how password managers protect your vault, the honest tradeoffs, and how to choose one and set it up safely.
- [Two-factor authentication (2FA) explained](https://passwordgeneratorlab.com/guides/two-factor-authentication/) — What 2FA is, which methods resist phishing, whether SMS codes are safe, how to handle MFA fatigue and recovery codes, and where to turn it on first.
- [How often should you change your password?](https://passwordgeneratorlab.com/guides/how-often-should-you-change-your-password/) — Why security agencies no longer recommend changing passwords on a schedule, the situations where you should change one right away, and what to do instead.
