Passkeys vs Passwords: How Passkeys Work and How to Switch Without Getting Locked Out
Learn how passkeys work, where they are saved, and how to set up and test your first passkey while protecting access to your accounts.

A passkey lets you sign in to a compatible account by approving a request on a device. You might use a fingerprint, facial recognition, your device PIN, or a compatible security key, depending on your setup. Behind that approval, the device uses a cryptographic credential linked to the specific service. You avoid typing a shared password into the website. That feature is especially useful when a convincing fake login page tries to look like the real thing.
The FIDO Alliance estimated in October 2026 that seven billion passkeys were in use worldwide. The estimate is about passkeys, which is different from a count of individual people. One person can have several passkeys across accounts and providers. For someone making the switch, the more immediate question is what happens the day their main phone goes missing. You can answer that before you rely on your first passkey. FIDO Alliance’s October 2026 update
How a passkey signs you in
When you register a passkey with a service, your credential provider generates a pair of cryptographic keys. The service receives a public key and associated registration information. Your device, password manager, or compatible security key controls the private key. When you return to sign in, the service sends a challenge. Your authenticator proves it controls the matching private key by signing the challenge. The service verifies the response with the public key it recorded.
Depending on how the credential is created, the authenticator may verify you locally with the method you use to unlock your device. The website receives the sign-in response. Your fingerprint image and device PIN are handled by your authenticator and are separate from what the service receives. A short PIN used on a locked device has a different role from a short account password submitted to a website. The surrounding device protections are part of how that PIN is used.
Passkeys are bound to the service identity used at registration. A fake sign-in site at a different domain generally cannot use your passkey for the genuine domain. This is called phishing resistance. You still need to protect your devices, keep recovery details current, and scrutinize requests for approvals or access. A scam can ask for money directly, request that you install software, or steer you toward a weaker sign-in method. Those are separate risks from stealing a typed password. FIDO Alliance passkey resources
How is that different from a password?
A password is a secret you submit to prove you know it. A strong, unique password stored by a reputable password manager can be very effective. Each account should have its own. A second factor makes many password-based accounts harder to compromise. Which second factor you use matters because some methods can be tricked into relaying an approval or a code.
A passkey also needs protection, but the sign-in protocol changes what the user gives to the site. Approving the use of a private key to sign a challenge avoids disclosing it to the relying service. The service has the public key used to verify the proof. That website-specific design helps with a common failure of ordinary password entry: a human can type the right password into the wrong page.
You may see a passkey offered as a primary sign-in method, as another option alongside passwords, or in a flow that also asks for a separate check. Some services enforce an organization’s security policies before they let you create one. Read the settings for the account in front of you. The presence of a “Create passkey” button alone tells you little about how its other sign-in and recovery methods work.
Where your passkey lives
A synced passkey can be available on supported devices through the provider you selected. If you create it with a password manager or built-in credential service, eligibility depends on the devices, browsers, apps, account settings, and synchronization options that provider supports. A passkey saved under your personal account may be separate from a passkey saved under your work account. Write down the provider name somewhere you can check later.
A device-bound passkey remains tied to a particular authenticator, such as a compatible physical security key. This can be a clear choice for people with managed devices or a policy requiring hardware-backed credentials. To prepare for hardware loss, check whether the account can register a second security key. Store the spare away from the first and test it independently.
Cross-device sign-in is another option some services support. A computer may display a QR code that a nearby phone scans, then the phone can approve sign-in using its existing credential. The exact pairing and proximity requirements depend on the platform. Selecting this flow can sign you into a session without saving a permanent credential on the computer. Use it only when you initiated the login on a service and computer you trust.
A common source of confusion is having several providers. Your browser may have one credential store, your operating system another, and your work password manager a third. Some prompts default to the most recently used option. Before approving creation, check the provider name and account shown. Before leaving a job or changing a managed device, ask your IT team how business credentials should be transferred or recreated.
Before creating a passkey, plan your recovery
Start with one account you can still access. Open its security settings from the service’s own app or the known website. Confirm that the current recovery email and phone number are yours. If the account offers backup codes, follow the provider’s instructions for storing them securely and privately. Avoid saving your only recovery instructions inside the same account you are trying to protect.
Write a short inventory for yourself. Include C for the credential provider account, S for the service account, and D for the devices you can use. If C and S are the same account, review how you would get back in on a replacement device. If your phone is the only trusted device for C, losing it could make recovering S more complicated. A spare security key, another trusted device, or a documented recovery path might make sense. Which one works depends on your accounts.
Your email is worth special care because it can be the recovery destination for other services. A backup address that you never check may be accessible to somebody else or may no longer exist. Update it while you can sign in. Business accounts should have a support route you can reach without the original computer, plus clarity on who can approve recovery.
Physical access matters too. Turn on a secure screen lock, update your devices, and use the device provider’s lost-device features if you have them. Think about travel. If you keep your main phone and your backup security key in the same bag, one theft can affect both. Store the recovery materials where you can retrieve them when needed without making them easy for another person to obtain.
Set up and test your first passkey
1. Choose the right device. Start on your own updated phone or computer. Check that you can unlock it reliably and that the intended credential provider is signed in. If you are using a work account, first check its enrollment rules. Keep your current session open as you test.
2. Go to the account’s security settings. Look for labels such as “Passkeys,” “Sign-in methods,” or “Password and security.” Services use different names. Follow the prompt started by the service you intended to visit. If a message sends you an unexpected QR code, go to the service through your normal route and initiate the operation there.
3. Create a passkey and confirm its destination. Your system may let you choose a phone, a security key, a built-in credential store, or a password manager. Check the provider and account name shown before approval. When the service lets you give the passkey a label, use a meaningful name such as “Personal password manager” or “Spare USB key.”
4. Keep the original session open and test another session. Use a supported second browser profile, a separate device, or an ordinary private window if your provider supports it there. Open the legitimate service and choose its passkey sign-in option. Check that the correct account appears and that you get to the correct account after approving the prompt.
5. Test a second route. If your provider says the credential is synced, see whether it is available on another supported device. If you registered a physical backup key, use it to sign in once. A test you can complete today is more useful than discovering a missing setting after you lose a device.
6. Record what worked. Save the service, the provider used, the device or spare key tested, and where to find the official recovery instructions. The inventory should never contain the actual device PIN or a list of recovery codes in plain view. Keep recovery codes in the secure location recommended for your setup.
7. Review fallback sign-in options. Keep a safe, tested fallback while you are making the transition. If the service offers passwordless account settings, learn the trade-offs before removing a recovery path. For work accounts, ask the administrator who handles recovery before changing policies on your own.
For a Google Account, the company provides its own steps for creating, choosing, and removing passkeys. Menu details can change, so use the service’s documentation if your screen differs from a tutorial. Google Account passkey help
What to do when you change phones or computers
Set up your replacement while the old device remains available, if possible. Sign in to your credential provider on the replacement and confirm which credentials appear. Test access to your main email, password manager, work account, and any service you need urgently. If the account uses a device-bound passkey, register a separate credential from the newly trusted device or re-enroll a security key as allowed.
Once the replacement works, review the service’s registered credentials and device list. Remove entries you no longer need, following the service’s instructions. Check whether the credential is synced before assuming the label identifies only one physical device. Confirm that you still have at least one usable sign-in and recovery route after removing old entries.
If a phone was stolen, use the official device and account recovery tools from a trusted device. Review recent sign-ins, active sessions, and registered credentials where the service shows them. Business users should follow their organization’s incident reporting steps. Secure your primary email early if other accounts rely on it for recovery. The exact order can depend on which devices and backup methods are still available.
If several people manage a business account
Where a service offers named users or delegated access, give each person their own sign-in. That makes it easier to add a passkey to the right account and remove access when a role changes. Keep a named recovery contact for the team. Check that a second authorized administrator can actually sign in while the primary administrator is available. A shared note telling staff to ask for a phone approval creates another dependency on the device you may be trying to protect.
Troubleshooting passkey prompts
The prompt says no passkey is available. Check that you are using the intended account name and the same credential provider used when you enrolled. Verify that the device and browser support the selected flow. If you saved the passkey to a physical key, connect that key. Switch to a tested recovery or alternate sign-in method when needed, then inspect the account’s passkey list from a device you control.
The passkey opens a different account. Look at the username displayed by the service and the provider. Credentials can share a service name even when they belong to separate accounts. Clear labels in the settings can reduce repeat mix-ups. Sign out and choose the intended username before trying again.
The nearby-device QR flow fails. Verify you started the sign-in on the correct site, bring your devices near each other, and follow the provider’s instructions for the required settings. Check for work policies that restrict pairings. If you can use another supported method, finish that way and test the cross-device route later with both devices available.
A passkey stopped appearing after a browser change. Credential availability depends on which provider the new browser can access. Find out where the passkey was saved first. Some browsers can use the operating system’s provider, and some third-party managers need their extension or app configured. A passkey created in the old browser may need a supported sync path or separate enrollment on the new device.
Your password is still offered. Many services leave several sign-in options available. Review the account’s settings and support documentation to understand which methods can be disabled and what role email or other recovery options play. Protect those other routes as carefully as the regular sign-in.
Frequently asked questions
Does a passkey let the website see my fingerprint?
A biometric check used by your authenticator happens on your device. The site gets a cryptographic response as part of the sign-in process. The authenticating device and the account service have different roles. If your device uses a PIN instead of a fingerprint, that can still fit the passkey flow your platform supports.
Should I delete all my passwords once I turn on passkeys?
Keep tested access while you move accounts one at a time. Some sites do not yet offer passkeys, and some passkey-enabled sites still use passwords or other methods during recovery. Check the provider’s guidance before changing a working sign-in. Use strong unique passwords wherever a password remains part of your setup.
Can I use one passkey for every website?
You can use the same credential provider to hold several passkeys, and a physical key can often hold credentials for different services depending on capacity and policy. Each passkey registration is tied to a particular service and account. A password manager full of different passkeys is normal. The provider’s name tells you where they are managed, while the registration tells you where each credential works.
Can I use passkeys on a shared computer?
Some services support using your own device or security key for a sign-in on another computer. A shared computer can still pose risks after sign-in because it handles the active session and sees the account pages you open. For sensitive accounts, use a trusted device you control. If your workplace provides a managed shared workstation, follow its sign-in and sign-out policy.
What should I do if I receive a passkey prompt I did not initiate?
Cancel it. Go directly to the official service to review your sign-in activity or account settings. Report suspicious prompts through your organization’s process when it is a work account. Treat the details on an unexpected screen as information to check. Use the recovery or support route you already know.
A manageable first session
Choose one account with an existing sign-in and known recovery options. Create a passkey, sign in independently on a supported second session, and check the spare route while your current device still works. Repeat with your most important email or financial accounts only after you understand what each service lets you test and how it handles recovery.
For more everyday tech utilities, see FixHubLab’s Developer Tools. Its QR Code Generator is for creating ordinary links you intend to share. When a sign-in service requires a QR code, use the one it generates within the official login process.
