Passkeys guide: prepare, configure, and verify the result
A passkey uses public-key cryptography: the service keeps a public key while the secret needed to sign in remains with your device or credential provider. The sign-in is tied to the real site, which makes it resistant to ordinary credential phishing.
Passkeys do not remove the need for recovery planning. Security depends on how the credential syncs, how devices are unlocked, which fallback methods remain, and what happens when a phone, computer, or account is lost.
Passkeys are not reusable secrets
A server breach does not reveal a password that can simply be replayed on another site.
The unlock stays local
A fingerprint, face, or device PIN generally unlocks use of the credential; the biometric is not sent to every website.
Synced and hardware-bound models differ
A platform credential can follow a protected account; a security key may require a spare physical key and deliberate enrolment.
Fallback can become the weak path
A phishable password, SMS reset, or poorly protected email may still bypass the stronger everyday sign-in.
Make one deliberate change at a time
Inspect the account's full sign-in menu
Identify existing passwords, SMS, authenticator, security keys, recovery contacts, trusted devices, and codes before adding a passkey.
Choose the credential location
Decide whether trusted platform sync, a password manager, or a hardware security key fits your device mix and recovery needs.
Create and test the passkey
Enroll from the official account settings, sign out in a low-risk moment, and confirm sign-in on the devices you actually use.
Strengthen recovery
Store recovery codes offline, protect the credential provider with strong authentication, and remove fallback methods that are no longer needed.
Practice loss response
Know how to remove a passkey associated with a lost device and how to regain access if every primary device is unavailable.
Check behavior, not just the toggle
| What you see | What to check | Safer adjustment |
|---|---|---|
| Browser displays a QR code | It may be offering cross-device passkey sign-in | Confirm the site and nearby device before scanning; do not scan a code sent by a stranger |
| Passkey is on a lost phone | Screen lock protects it but the device remains trusted | Use another trusted device to lock it and remove the relevant credential |
| New device has no passkey | Sync, account, platform, or waiting-period limits may apply | Use an approved alternate method and review credential-provider status |
| Account still accepts a password | The legacy method may remain the easier attack path | Strengthen it and its recovery or remove it when the service safely supports that choice |
Practice passkey recovery before replacing a trusted device
Confirm where the credential is stored or synced, how a missing device is removed, and which tested fallback remains. Enroll a replacement or spare before wiping the only device or security key that can complete sign-in.
Sources for Passkeys guide
Confirm current instructions and limits for this specific task before acting.
Judge a passkey by its recovery path as well as its sign-in strength
Draw the sign-in path for the account after enrollment. Include the passkey provider, device unlock, synced devices, hardware keys, recovery codes, account contacts, and any password or SMS fallback that remains. The everyday sign-in may resist phishing while an older recovery route still permits a weaker reset.
Choose between synced credentials and device-bound security keys according to the devices and people involved. A synced passkey can make ordinary access and device replacement easier. A hardware key can provide deliberate physical control but needs a spare and a secure enrollment plan. Test the selected model on the browsers and devices that will actually be used.
Practice one safe loss scenario before relying on the setup. Confirm how to lock a missing device, remove its credential, use an approved alternate method, and regain access when the primary device is unavailable. Do not remove the last tested fallback merely to make the settings page look stronger.
Questions to answer before relying on it
Can someone use my passkey if they steal my phone?+
They would normally also need to unlock the device or credential store. Remote-lock the device promptly and remove its credential from account settings.
Do passkeys work across Apple, Android, and Windows?+
Cross-platform use is supported in several ways, but the smoothest path depends on the service, browser, device ecosystem, and credential provider. Test before depending on it.
Should I delete every password after adding a passkey?+
Only when the service supports a safe passwordless mode and you have tested recovery. Otherwise secure the remaining password because it still affects the account.
Connect this setup to the controls around it
A dependable security stack connects prevention, detection, and a tested route back to access. Use the Cybersecurity tools & services hub for the complete topic pathway, then continue with Two-factor authentication guide, Password managers, and Lost or stolen phone plan.
Document the fallback routes behind each passkey in an account recovery inventory.
