A passkey is a login credential made of two mathematically linked keys: a private key that never leaves your device, and a public key stored by the website you're signing into. You unlock the private key with your fingerprint, face, or device PIN, so no password is typed, sent, or stored. That design removes two of the most exploited weak points in online accounts: reused passwords and codes that phishing pages can capture.
The Two-Key Pair That Replaces Your Password
Every passkey begins as a generated pair of keys created by your device's secure hardware or operating system. The private key stays inside that device's protected storage. The public key travels to the service and sits in its user database, where it's useless to anyone who steals it, because it can only verify signatures, not create them.
When you sign in, the service sends a random challenge. Your device signs that challenge with the private key and returns the signature. The service checks the signature against the stored public key. Neither key crosses the network in a form an attacker can replay, and nothing password-like ever exists to be typed into a fake login page.
The cryptography underneath uses public-key signature schemes standardized by the FIDO Alliance and the W3C's Web Authentication specification. Those standards are what let a passkey work across a Safari browser on an iPhone, a Chrome browser on Windows, and a native Android app, all verifying against the same account. The signing math is identical; only the way you unlock the key differs.
A useful comparison is a signature stamp held in a locked drawer. The bank keeps a copy of the stamp's imprint, not the stamp. Anyone can verify a document came from you, but stealing the imprint lets no one forge new documents. That asymmetry is the whole security argument for passkeys, and it's also why losing the device becomes the critical risk to plan for.
What Actually Happens During a Passkey Sign-In
The sequence below follows the same order you'll see on screen with a typical platform authenticator, such as Windows Hello, Touch ID on a Mac, or Google Password Manager on Android. Exact prompts differ by vendor and browser, but the order holds.
1: You open the sign-in page and choose the passkey option, usually labeled "Sign in with a passkey" or shown as an icon of a key or fingerprint. 2: The browser asks the operating system for an available authenticator, which may be the device itself or a synced password manager. 3: Your device displays the account and service name and asks you to verify with biometrics or the device PIN. 4: The private key signs the service's challenge, and the browser returns the signed response. 5: The service verifies the signature against your stored public key and grants access.
If the prompt never appears, the most common causes are a browser that doesn't support the Web Authentication API, a passkey stored in a different profile or password manager than the one currently active, or a service that has passkeys disabled for your account type. Check the browser version first, then confirm which password manager holds the credential. On shared machines, verify you're signing into your own browser profile before retrying.
Why Phishing Sites Can't Capture a Passkey
A passkey is scoped to a specific domain at creation time. When you register one on your bank's site, the credential is bound to that exact domain, and the browser will only release it to a matching origin. A lookalike domain, even one with a valid certificate, receives nothing usable, because the browser won't offer the credential to it.
This is a structural difference from one-time codes. A code sent by SMS or generated in an app can be typed into any page that asks for it, including a convincing fake. Passkeys can't be relayed that way. The FIDO Alliance, which publishes the passkey specifications, describes this origin binding as the core defense against credential phishing.
The protection has limits worth knowing. A passkey stops credential theft at the login step. It won't stop a malicious browser extension that can act inside your already-authenticated session, and it won't stop someone who has your unlocked device and your fingerprint. Real-world attacks on passkey accounts tend to target account recovery flows, not the passkey itself.
Device-Bound vs. Synced Passkeys
There are two practical flavors, and the distinction decides what happens when hardware fails. A device-bound passkey lives in one piece of hardware, such as a security key or a phone's secure enclave, and cannot be copied. A synced passkey is encrypted and replicated through a platform account, so it appears on every device signed into that account.
| Feature | Device-bound passkey | Synced passkey |
|---|---|---|
| Stored where | One security key or device chip | Encrypted in a platform or password manager account |
| Survives device loss | No | Yes, if the sync account is recoverable |
| Works on a new phone | Only with the original key | Signs in after sync completes |
| Typical example | A USB or NFC security key | iCloud Keychain, Google Password Manager |
| Best for | High-value accounts, shared devices | Everyday accounts across several devices |
Pick device-bound credentials for the accounts where you want a physical token required, such as a primary email or financial login. Choose synced passkeys for the long tail of everyday accounts where convenience outweighs the loss of a hardware gate. If you want both, most major services let you register several passkeys per account, so a synced passkey can serve daily use while a security key stays in a drawer as the recovery path.
What Happens When You Lose the Device Holding Your Passkey
Loss or theft of a device is the failure case that separates passkey guidance from password advice. A synced passkey usually survives, because the encrypted copy lives in your platform account and reappears after you sign into a new device. A device-bound passkey does not survive, and you're locked out unless the service offers another route.
That's why you should register at least two passkeys per important account and keep one on hardware you store separately. Services differ in how they handle lockout. Some allow a recovery code generated at setup, some fall back to email verification, and some require identity proofing through support. Check the recovery options before you rely on any single credential.
Sign out of lost devices remotely where the platform offers it. Apple, Google, and Microsoft each provide a device management page that can remove a lost device from the account, which stops synced passkeys from unlocking on it. That's a step worth knowing before you need it, because it requires access to the account you're trying to protect.
Passkeys Across Apple, Google, and Microsoft
Each major platform implements passkeys with its own storage and sync behavior, and the differences matter when you switch phones or mix ecosystems. Apple stores passkeys in iCloud Keychain, which syncs across devices signed into the same Apple Account. Google Password Manager syncs passkeys across Android and Chrome when you're signed in. Microsoft supports passkeys through Windows Hello and its Microsoft account, and Windows 11 handles them natively.
Cross-platform use is partial. A passkey created in iCloud Keychain won't appear in Google Password Manager unless you export or move it, which not every platform permits. Some password managers now support passkey storage independent of the platform, which eases switching, but availability varies by manager and version. Verify support on the maker's site before committing.
Regulatory pressure has pushed adoption. The FIDO Alliance has published guidance aimed at making passkeys portable across providers, and the European Union's eIDAS regulation and the United States' federal identity standards both reference phishing-resistant authentication. Those frameworks don't mandate passkeys specifically, but they raise the profile of the technology for banks and government services. Individual services still decide their own rollout timelines.
Where Passkeys Fit in Your Existing Security Setup
Passkeys replace passwords for login, not for everything else. Your account still has a profile, recovery contacts, and usually a second authentication factor for sensitive actions like changing an email address. Removing the password doesn't remove the need to protect the account recovery path, and attackers who can't phish a passkey may try to reset it.
Some services keep a password alongside a passkey as a fallback. In that case, the password remains a weak point, so use a unique generated one stored in a password manager. Others let you remove the password entirely once a passkey is registered, which closes the door on password-based attacks. Check which mode a service uses in its account security settings.
Shared devices need a plan. A passkey on a family tablet synced to one person's account is reachable by anyone who unlocks that device. Set a separate device PIN for each user, use separate browser profiles, and avoid registering high-value passkeys on hardware that others use. Those habits matter more with passkeys than with passwords, because the credential follows the device.
How to Register Your First Passkey and Test It Works
Registration takes under a minute on most services if you have the right device ready. The steps below follow the flow most sites use; exact labels vary, so look for the passkey option in the security or sign-in settings.
1: Sign in to the account with your existing password. 2: Open the security settings and find the sign-in, authentication, or passkey section. 3: Choose "Add passkey" or "Create a passkey." 4: Verify with your device biometrics or PIN when prompted. 5: Name the passkey after the device so you can identify it later. 6: Sign out and back in using only the passkey to confirm it works. 7: Register a second passkey on a different device or security key.
If the sign-in test fails, delete the passkey from the service and re-register it, checking that you're using the same browser profile or password manager that created it. On browsers with multiple profiles, the credential is often stored per profile, so a different profile won't see it. Confirm the device's biometric or PIN prompt actually appears during registration; if it doesn't, the operating system isn't handing the request to an authenticator.
The Cost of Passkeys: Time, Hardware, and Recovery
Passkeys are free on most platforms, but the true cost sits in hardware and recovery. A hardware security key typically costs between $25 and $90 depending on certification level, brand, and connector type, based on current retail listings from major vendors. You'll want a second key for backup, which doubles that outlay for accounts you protect with device-bound credentials.
Time cost is modest. Registering a passkey takes about a minute per account, so securing twenty accounts is roughly twenty minutes of setup plus a few minutes to test. Recovery, when it goes badly, is where the expense lands: a lost phone with the only synced passkey to a critical account can mean hours on support lines. Registering two passkeys per account avoids that scenario.
The trade-off against passwords is real but lopsided. Passwords cost nothing at setup and enormous sums at breach, while passkeys front-load a small hardware and setup cost and shrink the ongoing risk. For an individual with a handful of accounts, the practical spend is zero if you rely on phone and laptop sync, rising to roughly $50 to $180 if you add two hardware keys.
Common Passkey Misconceptions and the Limits Nobody Mentions
Several myths persist, and correcting them changes how you deploy passkeys. The first is that passkeys eliminate account takeover entirely. They don't: recovery flows, session hijacking, and malicious extensions remain live threats. The second is that passkeys are a single credential you can copy anywhere. Most can't be exported, and that's the point.
A third myth is that passkeys only work on phones. They work in browsers and desktop operating systems too, and hardware keys give desktop users a device-bound option. A fourth is that passkeys replace two-factor authentication entirely. They often count as one strong factor, but high-value services may still require a second factor for sensitive actions.
The limits are less discussed. A passkey tied to a browser profile disappears if you delete that profile. A synced passkey depends on the security of the platform account that syncs it, so a weak platform password undermines the whole setup. And a service that mishandles passkey registration can leave you with a credential that no longer matches, which is why testing immediately after setup is worth the minute it takes.
FAQ
Do passkeys work without internet access?
Most passkey sign-ins need a connection for the service to issue the challenge and verify the response. A synced passkey that hasn't reached a new device can't be used offline, and device-bound passkeys on a security key still require the service to be reachable. Local unlock with biometrics happens offline, but the login exchange does not.
Can I use the same passkey on my phone and my laptop?
Only through sync. A synced passkey stored in iCloud Keychain, Google Password Manager, or a compatible password manager will appear on every device signed into the same account. A device-bound passkey stays on the hardware it was created on, so you need to register a second passkey for the other device.
Are passkeys less secure than a password plus two-factor authentication?
For phishing resistance, passkeys are stronger because the credential is bound to the site's origin. For loss recovery, password-plus-two-factor can be easier to restore through emailed codes or backup codes. The strongest setup combines a passkey with a second registered device and printed recovery codes stored offline.
What happens if I delete my browser profile that held a passkey?
The passkey is typically removed with the profile, and you'll need another registered passkey or the service's recovery flow to regain access. Before deleting a browser profile, check its saved passkeys and re-register on another device if needed. Some password managers store passkeys outside the browser profile, which sidesteps this problem.
Can someone clone my passkey from my phone?
Device-bound passkeys are designed to resist extraction, and the private key stays inside protected hardware. Synced passkeys are encrypted end to end by the platform provider, but their security depends on the strength of the platform account that syncs them. A compromised platform account is the realistic cloning risk, not the phone itself.
Do all websites support passkeys yet?
No. Adoption varies by service, and some sites support passkeys only in specific regions or on specific platforms. Banks and government portals have been slower than consumer platforms. Check the service's security settings for a passkey option; if it's missing, the site may still be password-only.
How many passkeys should I register per account?
Register at least two: a primary on your everyday device and a backup on a separate device or hardware key. For a primary email or financial account, three is reasonable if the service allows it. More registrations widen recovery options without adding meaningful cost.
Is a passkey the same as a password manager?
No. A password manager stores secrets you type; a passkey is a cryptographic key pair that signs challenges. Some password managers now store passkeys alongside passwords, which blurs the categories, but the underlying mechanism differs. A password manager without passkey support cannot hold one.