HauntedPalace
Tech & AI

How to Set Up Passkeys—and Retire Your Passwords

A practical guide to creating passkeys on phones and computers, managing them with password managers, recovering lost devices, and retiring passwords safely.

10 min read
How to Set Up Passkeys—and Retire Your Passwords

A fake sign-in page can look convincing right up until the moment your password is stolen. A passkey changes the transaction: the website receives proof from a key held by your device, rather than a secret typed into whatever page happens to be asking for it.

That protection is real, but adopting passkeys does not mean flipping a switch and forgetting every password overnight. A careful setup takes a little planning, especially if you rely on several devices, a password manager or accounts that have not yet added passkey support.

What a passkey actually is

A passkey is a pair of cryptographic keys created by an authenticator and linked to an online account. The private key stays in the authenticator; the service stores the corresponding public key. When you sign in, the service sends a challenge, your device signs it with the private key, and the service checks that signature against the public key it previously registered.

The private key itself does not travel across the web. In practical terms, you may unlock the authenticator with a fingerprint, facial recognition, a PIN or a physical security key, depending on the device and method you chose. That local check confirms that the person using the passkey is the person who enrolled it.

The widely used web implementation is based on WebAuthn, a World Wide Web Consortium standard, and the FIDO2 ecosystem. “Passkey” is the familiar non-technical name for a credential that uses this approach. It is not a single physical object: the credential can live in an operating system, a password manager, a smartphone, a computer or a dedicated security key.

Why passkeys resist phishing

Phishing works by persuading someone to enter a reusable secret into a false page. A passkey authenticator is designed to bind its credentials to the website where they were registered. It offers a credential only for the matching site, so a lookalike address cannot simply collect a passkey intended for the real service.

That origin binding is stronger than merely giving the key a clever name. Even if someone creates a convincing imitation of a bank or email service, the authenticator will not treat it as the registered origin. Public-key cryptography also means that the service never receives the private key, so a copied credential or intercepted request is not the reusable secret that a password would be.

Passkeys are therefore better described as phishing-resistant, not invulnerable. A person can still be tricked into approving the wrong request, and account recovery procedures may still rely on passwords or other factors. The protection comes from how the credential is generated, bound and used—not from passkeys being incapable of mistakes.

A practical passkey setup checklist

Start with an account you use regularly, ideally one where you already have a secure password and a clear recovery route. Changing everything at once makes it harder to tell which setting caused a problem.

  1. Confirm that the service supports passkeys. Many websites still do not offer the option, and most sites that support passkeys continue to use passwords in some capacity.
  2. Sign in using the existing method. Open the account’s security, sign-in or password settings and look for an option to add or create a passkey.
  3. Choose the device or authenticator you want to use. This may be the phone, the computer, an installed password manager or a separate security key.
  4. Follow the local verification prompt. Depending on the authenticator, you may be asked for a fingerprint, facial recognition, PIN or physical confirmation.
  5. Give the passkey a recognizable name. A label such as the service name and device type can help if you later need to distinguish it from other credentials.
  6. Test the passkey. Sign out and use the new option before relying on it. Confirm that it works in the browser and device combination you expect to use most often.
  7. Add a backup route. Register a second passkey on another trusted device or keep the existing password as a temporary fallback.
  8. Record where the account can be recovered. A passkey cannot help if every enrolled device is unavailable and the account has no usable fallback.

Setting one up on a phone

A phone can act as a platform authenticator through its operating system or as a roaming authenticator for another computer. Common platform authenticators include Android, Apple Keychain and Windows Hello. A browser may present a nearby-device flow when the relevant credential is stored on a phone rather than the computer being used.

For a phone-first setup, create the passkey while signed in to the service, choose the phone as the location and complete the requested biometric or PIN check. Then test the sign-in while the phone remains nearby. Before relying on the phone alone, add the same account’s passkey to a second trusted device or retain a working password.

Setting one up on a computer

A computer may use a platform authenticator built into its operating system, or you may use a roaming authenticator such as a dedicated security key. Platform options can make sign-in convenient because the credential is closely connected to the device. A separate key can be useful when you want the credential physically separated from the computer.

Roaming authenticators can connect through USB, Bluetooth Low Energy or near-field communication. If you choose a dedicated key, keep another enrolled method available until the key has been tested. If you choose the computer itself, remember that replacing the device or changing its platform may leave you dependent on credential sync, a password manager or the service’s recovery process.

Using a password manager

Password managers can act as passkey authenticators and can make access across devices easier through cloud sync. Bitwarden and Dashlane support WebAuthn. This approach is useful when you want passkeys separated from individual phones and computers or want them available across browsers and platforms.

The trade-off is that access to the passkey depends on reaching and unlocking the password manager. Keep the manager’s own master password protected, and make sure you understand how its sync and recovery options work before moving important accounts over. Test a synced passkey on a second device before deleting the account password.

Make sign-in work across your devices

The smoothest passkey setup is not necessarily the one with the fewest credentials; it is the one you can still use on the day you need it. Consider which devices you normally carry, which browser you prefer and where the password manager lives. Then enroll the account on more than one of those paths.

Platform authenticators often sync credentials between devices, while password managers can provide another cross-device route. A WebAuthn Hybrid Transport flow can also access a credential stored on another authenticator, such as a smartphone. Support and wording vary across browsers and services, so the useful test is practical: can you open the relevant account on the combination you would actually use?

Do not assume every passkey moves automatically. The Web Authentication Framework described in the facts stores its private key directly on a physical device such as a smartphone, so that credential cannot be backed up or transferred to another device. A roaming hardware key is also physically separate, but it can be enrolled as a second method for the same account.

What to do if you lose a device

The answer depends on where the passkey was stored. If it lives in a synced platform authenticator or a password manager with cloud sync, you may be able to sign in on another device and approve the request there. If it lives on a device-bound authenticator or a physical security key, losing that item may mean losing access to that particular passkey.

Before it happens, add a backup passkey on another trusted device and keep the account’s password or other recovery method working. Make a simple inventory of important accounts and where each passkey is stored. Include details of the password manager that holds any synced credentials.

If a device disappears, use the service from another trusted device and look for its passkey or account-recovery options. If no alternative passkey was enrolled, rely on the service’s fallback process. There is no universal recovery method that every site provides, so the password you are trying to retire may still be your safety net for a while.

The honest drawbacks

Passkeys are useful, but they are not yet a complete replacement for passwords across the web. Many websites still do not support them, and many services ask for a password or another verification method alongside a passkey. A passwordless sign-in can therefore coexist with a password-based fallback.

They can also be less intuitive across browsers, operating systems and devices. The same credential may sync through one route but require a nearby-device flow through another. Naming, moving and identifying passkeys takes some practice, particularly if you use several accounts and authenticators.

Device dependence is another drawback. A synced passkey avoids some device-loss problems, but it also introduces dependence on the platform or password manager that stores it. A device-bound credential avoids that particular sync dependency, but it must be replaced if the device is lost.

Biometrics should also not be confused with the passkey itself. A fingerprint or face may unlock the authenticator, while the passkey remains the cryptographic credential. A PIN serves a different local role, and neither changes the need to protect the device, its account and the recovery alternatives.

Retire passwords without locking yourself out

Begin with one account, not the whole address book. Add a passkey, sign out, test it and confirm that you can still reach the account through a fallback. Only then consider removing the password from the account’s password list.

Next, prioritize accounts for which a reused or weak password creates the greatest concern. Keep unique passwords in a reputable password manager, especially for any account that does not support passkeys or still needs a password for recovery. Avoid deleting a password merely because a passkey appears in the account settings; test the actual sign-in flow first.

Finally, update your inventory. Note which accounts are passwordless, which still require both methods, where backup passkeys live and which password manager holds them. Revisit accounts when you replace a phone, computer or password manager. A well-planned retirement is gradual: the passkey becomes the usual route, while one dependable fallback remains until the service’s support and your own setup make it safe to remove.

Frequently asked questions

Are passkeys safe?

Passkeys are designed to resist phishing because they are bound to the site where they were registered, and the private key remains inside the authenticator. They are not a cure for every form of account abuse, so device security and account-recovery settings still matter.

Can I use one passkey on all my devices?

Sometimes, but it depends on where the credential is stored. Platform authenticators and password managers can sync passkeys, while device-bound credentials cannot be transferred. Adding a backup passkey on another trusted device is the most reliable way to preserve access.

What if I lose my phone?

First, try the service on another device if the passkey was synced through the operating system or password manager. If it was device-bound or stored only on a physical key, you may need the backup passkey, password or another recovery method.

Can I delete all my passwords now?

Not yet as a blanket rule. Many websites do not offer passkeys, and many sites still need passwords for fallback or multi-factor sign-in. Retire passwords account by account after testing the passkey and preserving a dependable recovery route.

The sensible goal is not to erase every password on the same afternoon. It is to replace fragile, reusable secrets with stronger credentials one account at a time, while making sure that losing a device does not mean losing an account. Passkeys work best as part of a recovery plan, not as a substitute for one.

Sources: Wikipedia — Passkey; WebAuthn; FIDO Alliance. Facts checked against the article text before publication.

J

Julian Reed

Julian Reed covers technology, money and the ideas moving both. He has a weakness for a clearly explained concept.