What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Passkeys are sign-in credentials built on public-key cryptography: your device or security key keeps a private key, while the website stores only a matching public key. At login, the service sends a one-time challenge; after you approve it with a device PIN, face scan, fingerprint or similar gesture, the authenticator signs that challenge and the service verifies the signature. The private key and your biometric data are not sent to the website. This design removes the reusable secret that phishing pages usually try to steal, although device compromise, stolen sessions, weak recovery and a compromised credential-manager account can still put an account at risk.
This guide follows a passkey from enrollment through everyday and cross-device sign-in, explains what “encrypted” means for synced credentials, and gives a practical plan for setup and recovery.
As an Amazon Associate I earn from qualifying purchases.
What exactly is a passkey?
A passkey is a discoverable FIDO credential: a cryptographic key pair created for a particular service. The authenticator—such as a phone, computer, tablet or FIDO2 security key—retains the private key. The service, called the relying party, stores the corresponding public key. Because the public key cannot be used to impersonate you without the private key, the service does not need to store a password that could be reused elsewhere. The FIDO Alliance describes passkeys as passwordless credentials based on this public-key model.
Passkeys use the FIDO2 family of standards. WebAuthn is the browser-facing API that a website uses, while CTAP defines communication between an authenticator and a client such as a browser or operating system. Your face, fingerprint or device PIN is only a local authorization method. It unlocks or approves use of the private key; it is not the passkey transmitted to the service.
Popular on Amazon
“Discoverable” means the authenticator can identify a credential for the site without you first typing a username. A service can still ask for an account identifier or offer several credentials, but the cryptographic proof remains the important part.
How does passkey sign-in work from enrollment to verification?
Passkey sign-in is a challenge-and-response exchange. The service never receives the private key; it receives a signature that can be checked with the public key it already has.
- Enrollment starts at the account. Choose the service’s option to add a passkey. The service sends registration data that identifies the site and the account.
- Your authenticator creates a key pair. The private key is generated and kept under the authenticator’s control. The public key and credential metadata are returned to the service for storage.
- You authorize locally. The operating system asks for the gesture configured on that device, such as a PIN, fingerprint or face recognition. This confirms that someone with local access is approving creation of the credential.
- The service issues a fresh challenge at every login. A challenge is a random, one-time value tied to the expected site and request.
- The authenticator signs the challenge. After local approval, it uses the private key to create a digital signature over the challenge and the relevant origin data.
- The service verifies the signature. The server uses the stored public key. A valid signature for the expected origin and current challenge proves control of the authenticator without exposing the private key.
A captured signature cannot simply be replayed because the next login uses a different challenge. Correct origin checks also prevent a credential created for the real site from being accepted by an unrelated lookalike domain.
Are passkeys encrypted, and does a website get my fingerprint?
The cryptographic credential is protected by the authenticator, and synced passkeys are designed to be end-to-end encrypted while being synchronized by a credential provider. The FIDO Alliance explains that a synced passkey becomes available on devices signed in to the same provider account, while the synchronization data is protected end to end. That is general FIDO guidance, not a guarantee that every provider has identical account-recovery or implementation details.
A website does not receive your fingerprint, face image or PIN. FIDO’s model keeps biometric processing on the device; the remote service receives an indication that local user verification succeeded. A biometric match is therefore an unlock or approval event, not a biometric password uploaded to the account.
Also popular on Amazon
Encryption does not eliminate all trust decisions. If someone takes over the account used to synchronize passkeys, defeats its recovery controls or obtains an already-unlocked device, the attacker may gain access to credentials that are available through that account. Protect the provider account with its strongest available safeguards and keep its recovery information current.
Recommended Free Tools
Do passkeys sync across devices?
They can, but there are two different models. A synced passkey is made available on additional devices through a credential provider. A device-bound passkey stays on one device or a hardware security key. The choice is a trade-off between availability and independence from a synchronization account.
| Characteristic | Synced passkey | Device-bound passkey |
|---|---|---|
| Availability after replacing a device | Usually available on devices signed in to the same provider account, subject to that provider’s setup and recovery process. | Not automatically copied; you need the original authenticator or another registered credential. |
| Main dependency | The security and recovery of the credential-provider account. | Physical possession and protection of the specific device or security key. |
| Assurance profile | Convenient for everyday use across a person’s devices. | Useful when an organization or individual specifically needs a hardware-bound credential. |
| Typical fit | Most consumers and users who value easy device replacement. | Highly regulated environments, elevated-privilege accounts or a separately stored recovery authenticator. |
Microsoft’s enterprise guidance describes synced passkeys as a convenient, low-cost choice for most users outside elevated-risk settings, while recommending FIDO2 security keys for highly regulated environments or users with elevated privileges. That is Microsoft’s guidance for its environment, not a universal rule that every person needs a security key.
Provider names commonly associated with passkey synchronization include iCloud Keychain, Google Password Manager, 1Password and Dashlane; Apple also refers to Apple Passwords, and Samsung offers Samsung Pass. Features, portability and recovery behavior can change, so check the current documentation for the provider you actually use rather than assuming that two providers work identically.
How does cross-device sign-in work?
Cross-device authentication lets a nearby phone authorize a login on another computer when the passkey is not stored on that computer. It is a system-supported handoff, not a manual export of the private key.
Also popular on Amazon
- On the computer, choose the option to use a passkey from another device. A QR code or equivalent handoff prompt appears.
- Open the camera or passkey prompt on the nearby phone and scan or approve the request.
- The devices use Bluetooth proximity checks and an encrypted exchange to confirm that the phone is nearby and is authorizing this session. Apple’s developer explanation of passkeys describes this QR-and-Bluetooth flow.
- Approve the passkey with the phone’s local gesture. The computer receives the signed response, not a copy of the private key.
Because the exact screens are supplied by the operating system and browser, labels differ. Look for wording such as “use another device,” “use a phone” or “security key,” and avoid typing a passkey into a webpage or sending it to someone who asks for it.
Why are passkeys resistant to ordinary phishing?
Passkeys are resistant to ordinary credential phishing because the signature is bound to the legitimate relying-party identifier and the specific origin. A phishing page at a different origin cannot normally obtain a valid signature for the real site, even if its design looks identical. This verifier-name binding means you do not have to recognize a fake domain and type a reusable secret into it. The OWASP Passkey Security Cheat Sheet explains this origin and challenge binding.
The protection works in a typical attack sequence:
- A fake site can display a convincing login form, but it cannot ask your authenticator to produce a credential for the legitimate origin while pretending to be that origin.
- A real-site challenge is signed only after local approval, so a copied password or intercepted one-time code is not part of the passkey exchange.
- A signature captured from one login is tied to that challenge and is not a standing secret that can be replayed for the next login.
Phishing resistance is not the same as total account security. A malicious site can still trick you into authorizing an action on the real site if you are already on the real origin and approve a prompt you did not intend. Services must also implement WebAuthn correctly and protect credential-management operations.
What can still go wrong with a passkey?
Passkeys remove a major class of password attacks, but they do not protect every layer around an account. OWASP identifies several remaining risks:
- Compromised active sessions: malware or an attacker who steals a valid session cookie may act without performing a new passkey login.
- Weak account recovery: an email-only reset, support process or fallback method can become the easiest route around a strong authenticator.
- Device or authenticator compromise: an unlocked phone, infected computer or exposed security key can authorize actions.
- Credential-provider takeover: control of the account that synchronizes passkeys may expose the attacker to the same credentials on other devices.
- Server or implementation errors: incorrect origin validation, challenge handling or credential-management logic can undermine the protocol’s protections.
Keep operating-system updates current, lock devices with a strong local method, review active sessions, and treat unexpected passkey prompts as suspicious. A passkey is strongest when the account’s recovery and session controls are designed with the same care.
Also popular on Amazon
What happens if I lose my phone or security key?
There is no single universal outcome. A synced passkey may be restored on a replacement device after you recover the provider account, while a device-bound credential generally remains unavailable when its device or key is lost. The service’s own recovery policy determines what happens next.
Before removing an old device, add a second trusted authenticator wherever the service allows it. That can be another passkey, a separate security key or another supported method. OWASP recommends supporting more than one authenticator and designing recovery carefully; having two independent routes reduces dependence on one piece of hardware.
Make a written recovery plan:
- Record which credential provider stores your synced passkeys.
- Confirm that you can recover that provider account using current, protected recovery methods.
- For important services, register a second authenticator before the first device is lost.
- Store any spare hardware key according to your organization’s security policy, not attached to the everyday device.
- After a loss, revoke the missing device or credential and review account sessions and recent activity.
Do not assume that a provider’s backup or recovery process gives the same assurance as the original device. Convenience and recoverability must be weighed against the security of the account that enables synchronization.
How fast are passkey logins?
Published figures indicate a speed and completion advantage, but they are not universal benchmarks. The UK National Cyber Security Centre says passkey logins can be up to eight times faster than entering a username, password and two-step-verification code in its 2026 guidance. Microsoft Learn reports, for Microsoft account users, 99% successful registration, registration 14 times faster (three seconds versus 69 seconds), and 95% versus 30% sign-in success for the compared flows. Those Microsoft figures describe Microsoft’s user population and experience; they should not be treated as independent results for every service or device.
The practical benefit is fewer typed secrets and fewer code-entry steps. Actual time still depends on the device gesture, browser, network, service implementation and whether cross-device approval is required.
Also popular on Amazon
How should I start using passkeys safely?
Use passkeys on services that offer them, while keeping a recovery path until you have verified that the passkey works on your devices. The NCSC recommends opting for passkeys over passwords wherever they are available. When a service does not support passkeys, the NCSC advises a strong, password-manager-generated password and two-step verification.
- Choose a primary authenticator. Decide which built-in credential manager or compatible provider you trust and understand how its account recovery works.
- Enroll from the real service. Open the service by typing its known address or using a trusted app, then select its passkey setup control. Do not enroll from a link in an unexpected message.
- Label the credential. If the service shows a device or provider name, use a label that will help you recognize it later.
- Test a second route. Sign out and sign back in, then add another passkey or authenticator for important accounts if the service supports it.
- Secure the surrounding accounts. Protect the credential-provider account, email account and devices that can recover or synchronize credentials.
- Keep fallback methods deliberate. Retain a strong password or approved recovery method where the service requires one, and remove weak or unused recovery options.
For an organization, separate ordinary users from administrators and other elevated-privilege roles. Consider whether the convenience of synced passkeys fits the organization’s threat model, and whether regulated or high-impact accounts warrant device-bound FIDO2 security keys. Document enrollment, replacement, revocation and help-desk verification before making passkeys mandatory.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallWhat is the bottom line on passkeys?
Passkeys replace a reusable password with a private key held by an authenticator and a public key held by the service. Local device verification authorizes a signature over a fresh, origin-bound challenge, which is why a normal phishing page cannot simply collect and replay the credential. Synced passkeys make replacement and multi-device use easier but increase reliance on the provider account and its recovery controls; device-bound credentials provide a more physically anchored option at the cost of convenience. Use multiple trusted authenticators for important accounts, protect sessions and recovery paths, and keep strong passwords plus two-step verification for services that have not adopted passkeys.
Frequently Asked Questions
Can I copy a passkey to a USB drive or email it to myself?
No. A passkey is not a text string to export. Use the provider’s supported synchronization, a system cross-device flow, or a compatible FIDO2 security key; never send a private key or credential file through email or chat.
Should I delete my password immediately after adding a passkey?
Only after confirming the passkey works and checking the service’s recovery requirements. Some accounts still need a password or another fallback, and removing every recovery route before testing a replacement can lock you out.
Can a passkey protect an administrator account as well as a personal account?
Yes, but the assurance choice may differ. Microsoft guidance points highly regulated environments and elevated-privilege users toward FIDO2 security keys, while synced passkeys are presented as a convenience option for most other users.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What should I do after a passkey login prompt appears unexpectedly?
Cancel it and inspect which service and device requested the approval. An unexpected prompt can indicate an attempted login or an account problem; review active sessions and recovery settings instead of approving a request just to make the alert disappear.

