Welcome to KnowHow Daily!
Practical guides, money-saving tips, tech solutions, government benefits, and useful information for everyday life.
Welcome to KnowHow Daily!
Practical guides, money-saving tips, tech solutions, government benefits, and useful information for everyday life.

Learn how to set up passkeys safely, protect your accounts when switching devices, and build a recovery plan for lost phones, shared devices, and account lockouts.

Passkeys replace the part of a password that attackers can steal or trick you into revealing. Instead of typing a secret into a website, your phone, computer, or security key proves that it holds a private cryptographic credential. You then unlock that device with a fingerprint, face scan, PIN, or screen lock.
The important distinction is where the passkey is saved. A synced passkey is managed by a credential manager such as Google Password Manager, Apple iCloud Keychain, or Microsoft Password Manager and can become available on other compatible devices. A device-bound passkey stays on one device or physical security key. It can be highly useful, but losing that device can also mean losing that particular sign-in method.
Passkeys make phishing harder because the credential is tied to the legitimate website or app. They do not, however, remove every account-recovery risk. If someone can unlock your phone or computer, they may be able to use passkeys stored there. That is why setup and recovery planning matter as much as the passkey itself.

The exact buttons vary by account, but the process is usually similar:
For a Google Account, the direct setup page is the account’s passkey and security-key management screen. Google advises creating passkeys only on devices you personally own and regularly use.
On Apple devices, passkeys are stored in iCloud Keychain when the required Apple account security settings are enabled. On Windows and Microsoft accounts, the passkey may be saved in Microsoft Password Manager, Windows Hello, a phone, another credential manager, or a FIDO2 security key.
Read Apple’s passkey setup instructions Create and save a Microsoft passkeyCreating a passkey does not always delete your password. In many services, the password remains available as another sign-in method unless you deliberately change the account’s settings. That gives you time to confirm that the passkey works.
Before switching to a passkey-first setup, make sure you have at least two practical ways back into the account:
Do not create a passkey on a family tablet, work computer that other people can unlock, library computer, or shared household device. Anyone who can unlock that device may be able to use the passkey. If you accidentally create one on a shared device, remove it from the account and from the device’s credential manager.
If the passkey was synced through a credential manager, signing in to the same manager on a replacement device may restore access after the provider’s verification process is complete. This is one reason synced passkeys are convenient for everyday accounts.
If the passkey was stored only on the old phone, it may not transfer. Use another registered passkey, a security key, the account’s recovery process, or an existing signed-in session to add a new passkey. Do not erase or trade in the old phone until you have tested the replacement device.
When a phone is lost or stolen, treat the passkey as an account-access issue rather than merely a missing-device problem. From a device you still control:
For Google Accounts, a newly added sign-in method may not be fully trusted immediately. Google says some new passkeys or recovery changes can take up to seven days to become available, although an existing trusted passkey or security key may speed up certain changes. Plan device replacements before the old device disappears.
Neither type is automatically right for every account. The better choice depends on how much convenience, portability, and physical control you need.
| Passkey type | Best fit | Main advantage | Main trade-off |
|---|---|---|---|
| Synced passkey | Email, shopping, social media, and everyday services | Can be available across compatible devices through a credential manager | Access depends on the credential manager and its recovery process |
| Device-bound passkey | High-value accounts or tightly controlled devices | Remains tied to one device or security key | You need a backup method if that device or key is lost |
| Phone-based passkey used with another computer | Occasional sign-in on a computer you do not own | Lets the phone approve the sign-in through a QR code and nearby-device check | Usually requires the phone, camera, Bluetooth, and an active connection between devices |
A physical security key can be a strong backup, but it should not be your only route into an account. Consider registering two keys and storing them separately if the service supports multiple keys.
The safest order is to add first and remove later:
If the account offers a QR-code option such as “Use another device” or “Passkey from nearby device,” the old phone can sometimes approve a sign-in on the new computer. This does not necessarily copy every passkey to the new device; it may simply let the old device authenticate that one sign-in.
A passkey saved through one provider may not automatically appear in a different provider’s credential manager. Check the save-location prompt instead of accepting the default without reading it.
A replacement device may appear ready while the account still relies on the old passkey. Test a complete sign-in before wiping, selling, or returning the old device.
One phone, one passkey, and one recovery number create a single point of failure. Add a second trusted method for important accounts.
The passkey protects a specific account, while your credential manager has its own account, device security, and recovery requirements. Protect both layers.
The simplest decision rule is this: use a synced passkey for convenience, add a second recovery route for resilience, and use device-bound keys when you specifically want credentials kept off cloud-synced systems. A passkey is safer when it is part of a recovery plan—not when it becomes your only door into the account.
A. Usually, yes. Many services keep the password available unless you change the account’s sign-in settings. Keep it or another recovery method until you have tested the passkey on more than one trusted route.
A. Not necessarily. A passkey may sync within the credential manager that created it, but cross-platform availability depends on the provider, operating system, browser, and account. A QR-code sign-in can sometimes let one device approve access on another without transferring the passkey itself.
A. Check that the device has a screen lock, that you are using the same credential manager account, and that the website or app supports passkeys. Try another sign-in method, then review the account’s registered passkeys and add a new one if necessary.
A. No. Anyone who can unlock that device may be able to use the passkey. Remove the passkey from the account and the device’s credential manager, then create one on a device that only you control.