A convincing login page can steal a password and even intercept some forms of one-time code. A passkey changes the mechanics: the user's device proves possession of a credential for the legitimate website rather than typing a reusable secret into a form. That makes common credential-phishing attacks much harder. But account security still depends on device protection, the fallback login methods a service retains and the process for recovering access after a device is lost.
That is a meaningful improvement. It also invites an understandable question. What happens when the phone holding the passkey is lost, replaced or damaged?
Security advice often celebrates the moment when a person signs in with a fingerprint. For someone moving their most important accounts to passkeys, the more consequential moment may arrive six months later, when their old device is gone. A careful transition considers both.
What the website receives during sign-in
A passkey uses public-key cryptography. When an account is registered, the authenticator creates a pair of related cryptographic keys. The service receives the public key. The private key remains under the control of the authenticator rather than being shared as a reusable secret with the website.
During sign-in, the website asks the authenticator to prove possession of the matching private key by signing a challenge. The authenticator checks that the request belongs to the registered website. The user may approve with a device PIN, fingerprint or face recognition. The website can verify the signed response using its public key.
The FIDO Alliance's explanation of passkeys describes this mechanism as a password replacement built on FIDO standards, including WebAuthn. The important property is the connection between the credential and the legitimate website. A fake site with a similar-looking address cannot simply request and reuse the passkey for the real site's domain.
That is why passkeys are described as phishing-resistant. Traditional passwords are strings a person can type into the wrong place. A passkey's private key is not a string the user enters into a form.
A fingerprint is not the account's passkey, and it is not normally sent to the service during this exchange. Biometrics or a PIN unlock the local authenticator. This distinction helps explain why replacing a device's biometric setting does not necessarily require changing every account credential.
Two ways to hold a passkey
Passkeys are often divided into synced and device-bound credentials. Both use the same basic public-key approach, but they solve the portability question differently.
A synced passkey can become available on multiple trusted devices through a passkey provider or password manager, subject to that provider's security design. This makes everyday sign-in and replacing a phone more convenient. A device-bound passkey stays on a particular authenticator, such as a hardware security key. It may be attractive where organizations want stronger guarantees that the credential never leaves one device.
The FIDO Alliance explicitly recognizes both types. The NIST Digital Identity Guidelines, revision 4, published in 2025, address syncable authenticators alongside other forms of authentication. Organizations working under a formal assurance standard need to check the applicable authenticator requirements rather than assuming all passkeys have identical deployment properties.
Neither type eliminates operational trade-offs. A hardware key can be lost. A cloud-synced credential depends on the security and recovery of the account that synchronizes it. Convenient access across devices may be exactly what an individual needs, while a sensitive company system may have reasons to prefer a different arrangement.
There is no universal answer based solely on the word passkey. The right choice depends on the account, threat model, recovery process and how many devices need access.
Phishing-resistant does not mean invulnerable
A passkey prevents several familiar password attacks. An attacker cannot steal a password that is not used. Replaying a password from another breach is ineffective when the account uses a distinct cryptographic credential. Tricking a user into typing a passkey into a fake form is not how passkey authentication works.
But an account can still be compromised through other paths. A stolen and unlocked device may expose an active session. Malware can act through a compromised browser or operating system. A weak fallback sign-in process can give an attacker another way into an account that appears protected by a passkey.
This is why the phrase "phishing-resistant" should be read precisely. It describes the credential's resistance to common phishing methods, not a guarantee that the whole account, device and recovery system are immune to attack.
The distinction matters for compliance too. The PCI Security Standards Council's FAQ 1595 discusses FIDO2-compliant synced passkeys in the context of a particular PCI DSS authentication requirement. That is a narrowly scoped standards interpretation, not a blanket statement that any passkey implementation satisfies every security or multifactor policy.
A good account-security review therefore checks the surrounding system. How are new devices trusted? Can email-based recovery override the passkey? Does the account offer alerting when security settings change? Can the user revoke an unfamiliar device or session? A strong front door is valuable only if the side doors receive attention.
The migration trap: the old password may still work
Adding a passkey and removing password-based risk are not always the same event. Some services let users sign in with either a passkey or a traditional password. Others keep a password for account recovery. A person who registers a passkey and stops thinking about the existing credentials may retain much of the old exposure.
After adding a passkey, inspect the account's security settings. Confirm which sign-in methods remain enabled, how recovery works and whether old sessions are still active. If a password continues to be supported, it should remain unique and strong, ideally stored in a reputable password manager.
Do not casually remove every recovery mechanism. That can leave an account inaccessible after device failure. Instead, find out which recovery paths the service actually supports and keep those paths secure. For sensitive accounts, the recovery email may deserve as much protection as the account itself.
A second trusted device or a separately stored device-bound security key may provide resilience, provided the service permits it. The goal is to avoid a situation in which one stolen or broken phone becomes the only path to your essential records.
A practical account-recovery rehearsal
The safest time to discover a recovery problem is while the account still works. Choose one noncritical service that supports passkeys and walk through the setup carefully. Sign out. Sign in with the passkey. Then consider how you would proceed if your primary device disappeared.
Do you have another trusted device? Does the credential synchronize through an account you can recover? Can you use a hardware key? Does the service provide recovery codes? Where are those codes stored, and could someone who steals your phone also access them?
Write down a recovery map rather than the actual secret material. The map might say, "Recovery codes are stored in a secure offline location," without copying sensitive codes into a casual note or shared document. Protect backup routes with the same care as the primary account.
A simple rehearsal also helps reveal usability problems. If a family member shares an account, passkey setup may alter how that person signs in. If an organization rotates devices frequently, an unplanned move to device-bound credentials may create unnecessary support requests.
A sensible order for making the change
Start with high-value accounts that support passkeys and have clear recovery instructions: primary email, your password manager if applicable, and the services that control payments or other important information. Before changing anything, secure the account that will synchronize credentials and verify a recovery route.
Set up the passkey on a trusted, updated device. Test sign-in from that device, and, where supported, test a second legitimate path. Review existing password and multifactor settings. Keep account notifications enabled. Repeat for additional services only after you understand the recovery behavior of the first.
Companies face an extra step: document what happens when an employee leaves, loses a device or changes jobs. Administrators should avoid using shared personal credentials as a shortcut. An account-lifecycle policy is part of the authentication decision.
Passkeys reduce exposure to password theft and conventional phishing. Their wider benefit comes when people can use them confidently without creating a new single point of failure. The login screen becomes simpler; recovery deserves the more careful plan.
References and background
Our explainers link to source documents so readers can explore the evidence and interpret it in context. Websites and policies may change after publication.
- FIDO Alliance, *Passkeys*fidoalliance.org
- NIST, *Digital Identity Guidelines*, revision 4pages.nist.gov
- PCI Security Standards Council, FAQ 1595www.pcisecuritystandards.org