Impulsec may earn a commission if you purchase through links on this page. Commercial relationships must not determine our recommendations. Read our Affiliate Disclosure.

How to Recover Passkeys on a New Phone

Illustration: a passkey moves securely from an old phone to a new phone.

Quick Answer: Restore the account and encryption access for the provider that actually holds your passkey, then test a fresh sign-in on the replacement phone. A device-bound credential needs another registered sign-in or the service’s recovery route; a phone backup or password CSV is not a universal passkey restore.

Keep a working old phone until you have verified the replacement. If it is lost or stolen, use the provider’s lost-device protections promptly. Routine migration and securing a missing phone require different priorities.

Find Out Where the Passkey Is Stored

  • Apple Passwords/iCloud Keychain: check the Apple Account and whether password syncing was enabled.
  • Google Password Manager: check which Google Account contains the saved entry.
  • Another password manager: sign back into that provider and the correct vault.
  • A security key or device-only authenticator: the credential may remain tied to that device rather than sync to your phone.

The device you used to create a passkey is not necessarily its only storage location. Look at the saved entry and the provider selected in the sign-in prompt. If you used several Google Accounts or separate personal and work vaults, check each relevant account before concluding the passkey is missing.

Restore Apple Passkeys on an iPhone

For passkeys stored in iCloud Keychain, follow Apple’s current Keychain setup guidance.

  1. Sign in to the same Apple Account on the replacement iPhone and complete its verification prompts.
  2. Open Settings > your name > iCloud and locate the password and Keychain sync setting. Its label and whether you first select See All depend on your iOS version.
  3. Turn on Sync this iPhone and complete any requested approval or passcode checks.
  4. Open Passwords and look for the relevant service. Test a sign-in on the new phone before erasing the old one.

Apple Account access and access to encrypted Keychain data are related but separate checks. Signing in alone may not complete recovery. Follow the official Keychain recovery process if an old passcode or another verification step is required. Do not reset encrypted data as a casual troubleshooting step: read exactly what would be removed first.

An Apple recovery contact can help with supported recovery without receiving ordinary access to your account. That is different from sharing your passwords or appointing a legacy contact.

Restore Google Passkeys on Android

Google explains that passkeys saved in Google Password Manager sync through the Google Account. Set up a screen lock on the replacement phone, sign in to the correct account and open Google Password Manager to check its entries.

Complete the encryption-unlock prompt shown by Google. Depending on your setup and the operation, this may require an earlier device’s screen lock or a Google Password Manager PIN. Your Google Account password is not a universal substitute for those protections. Avoid repeated guesses if you do not recognise the requested code.

If Android offers the wrong provider, search device Settings for passwords. Google’s Android passkey guidance describes selecting and enabling the intended password manager under passwords, passkeys and accounts. Labels can vary by manufacturer.

Illustration: an old phone securely syncing a passkey to a new phone through a cloud.
Image © 2026. All rights reserved.

Check Third-Party Managers and Platform Changes

If you stored a passkey in a separate password manager, install its official app, restore access to your existing account, unlock the correct vault and enable its credential-provider option on the phone. Recovering your Apple or Google account will not necessarily recover a separate manager’s vault.

Moving between Android and iPhone can require an additional transfer or a new passkey. Do not assume that signing into a different ecosystem copies everything. Google now documents direct password and passkey transfers with supported apps on Android. Availability depends on the source, destination and device requirements.

A normal password CSV is not a passkey backup. If a supported transfer is unavailable, use an existing sign-in method to register a new passkey with the service. For broader migrations, see our password-manager switching checklist.

If the Passkey Still Does Not Appear

  1. Try a second trusted device or registered hardware security key that already works.
  2. If the sign-in page offers it, use a nearby phone’s passkey through the QR-code cross-device flow. Follow the proximity and Bluetooth prompts. This signs you in; it does not by itself copy the passkey to the new phone.
  3. Use another method already registered with that service, such as a password, backup code or recovery process. Available options vary.
  4. Once signed in, open the service’s security settings and register a passkey with the intended provider on your new phone.
  5. Test it in a fresh sign-in while preserving a working fallback. For a managed work or school account, ask the administrator before changing required authentication methods.

If every registered authenticator and recovery route is unavailable, account recovery may fail. No generic passkey-recovery tool can promise to unlock every service. Use official support rather than paying an unknown person who claims to extract missing credentials.

Handle a Lost Phone and Finish the Move

For a missing device, follow Apple’s lost-iPhone steps or Google’s lost-Android guidance from a trusted device. Mark or lock it as lost where supported, assess account exposure and use the official recovery process if needed. Do not leave an exposed device unsecured while waiting to complete a migration.

For an ordinary replacement, check important services individually, including your email and password manager. Review obsolete device sessions and passkeys in each service after confirming the new route works. A synced passkey may be shared across your approved devices, so deleting it without understanding its scope could remove access you still need.

Keep an independent recovery route for essential accounts. If restoring the password-manager account is the obstacle, use our master-password recovery checklist.

Identify the PIN Before Entering It

A replacement phone can ask for several different codes during setup and sign-in. Read which account or device the prompt names. The screen lock for the new phone, an older device’s passcode, a password-manager encryption PIN and a carrier account PIN serve different jobs. Repeatedly trying one in every prompt can create another lockout without restoring the credential.

Prompt or protectionWhat it concernsWhat to check
Current phone screen lockLocal device authentication.Use the code for the phone named in the prompt.
Earlier device’s passcodeA provider’s encrypted-data recovery check.Identify the old device rather than guessing the new phone’s code.
Google Password Manager PINProtection for passkeys in supported Google Password Manager workflows.Use the provider’s PIN instructions, not the carrier’s account-reset process.
Carrier account PINChanges to the mobile account or number.Recover mobile service separately from the credential vault.

Google’s PIN guidance says Android uses its screen lock for saved credentials; the separate Google Password Manager PIN cannot be created or reset on Android. For a forgotten PIN created on another supported device, use Google’s instructions on a non-Android device where you previously used Google Password Manager. Check that it is signed in to the right Google Account before concluding that a missing change-PIN option means the data is gone.

Do not choose Reset passkeys simply to clear a confusing prompt. Google says that reset deletes all the passkeys concerned and requires new ones at the services. Preserve working devices and registered alternatives, read the exact reset warning, and use the supported recovery route first. A failed PIN attempt does not by itself establish that the passkeys are corrupt or that deletion is necessary.

Keep Phone-Number Recovery Separate From Vault Recovery

A new SIM or restored phone number can help receive an account’s text messages, but it does not recreate a device-bound passkey or automatically unlock encrypted cloud credentials. Conversely, Wi-Fi access to your password manager does not prove that mobile service and text delivery have been restored. Work out which dependency is actually preventing sign-in before changing more accounts.

If the phone was stolen or you received an unrequested SIM-change alert, contact the carrier promptly through a trusted route and secure the device with official lost-device controls. See how to protect against SIM swapping for the difference between carrier safeguards and online-account authentication. Do not give an unsolicited caller a device passcode, carrier PIN or verification code in exchange for promised recovery.

For an essential account, make a short record of the account name, credential provider and the recovery option that remains available. Keep secret values out of an ordinary support message. If a work or school policy controls the credential, ask that administrator to confirm the permitted replacement method before deleting a registered authenticator. Where no method remains, use that service’s official recovery process; no universal recovery app can guarantee a bypass.

Once a replacement credential works, review the missing phone’s access separately from routine tidying. Remove or secure device sessions through the relevant provider, and review the service’s registered credentials with care. A synced passkey may be usable on several approved devices; deleting it can affect more than the missing phone. Preserve a confirmed alternative while you make those changes.

Diagnose the Missing Step, Not Just the Missing Entry

Treat a new-phone problem as three separate checks: can you open the correct provider account, can you decrypt its saved credentials, and will the website accept the particular credential? Write down the service name and provider, without copying the secret into an email or support ticket. That small inventory helps you avoid resetting the wrong account while a working copy still exists.

Apple restore completed, but Passwords is empty: check Keychain syncing separately from the phone backup. Apple explains that Keychain items sync separately from iCloud Backup. Verify the same Apple Account and approved-device checks before treating a successful backup restore as proof that credentials have returned. If the entries exist but do not fill, inspect the AutoFill setting separately rather than deleting the vault.

Google Account works, but a passkey will not unlock: distinguish the account sign-in from the device’s encryption check. On Android, Google Password Manager uses a device screen lock; Google documents recovery on a replacement using the lost device’s PIN, pattern or password. A Google Password Manager PIN is a separate prompt used in supported cross-platform situations, not a setting you can create or change on Android. Read the exact prompt before entering a code.

The credential is visible, but the website rejects it: confirm the service account and username. A stored entry does not prove the service still accepts that credential. Use an already-registered fallback or the service’s official recovery, then register a replacement in the intended manager. Do not delete the remaining working authenticator just to see whether that forces a repair.

Choose the recovery route before resetting anythingA synced credential needs provider access and encryption approval. A device-bound or unavailable credential needs an existing service sign-in or recovery before registering a replacement.Where is the passkey saved?SYNCED PROVIDERRestore the correct accountComplete encryption checksEntry present and usable?Yes: test a fresh sign-inNo: follow the route belowDEVICE-BOUND / UNAVAILABLEUse another registered methodor official service recoveryRegister a replacement passkeyTest it before retiring access
Choose the recovery route before resetting anything.

Moving Between Platforms Without Mistaking Sign-In for Transfer

First decide whether you are continuing to use the same credential provider or changing it. The former needs access to that provider on the replacement device; the latter needs an explicitly supported transfer or registration of a new passkey. A cross-device QR sign-in can get you into a service without placing a credential in the destination vault. Afterward, inspect the destination’s saved entry and perform a separate sign-in with the other device unavailable.

For a supported Android transfer into Google Password Manager, open its settings and choose Import passwords and passkeys, select the source app, authenticate and approve the export there. If that option or source is absent, do not substitute a CSV and assume it carries passkeys. Check the exact source app and operating-system requirements, or sign in with an existing method and register a replacement instead. Keep any working source until verification succeeds.

Finish With Two Working Ways In

For each essential account, confirm the replacement phone can sign in and retain an independent recovery method the service supports. Secure a lost phone immediately through official lost-device controls. On iPhone, removing a missing device from Find My also removes Activation Lock; Apple advises keeping it in Find My even after a remote erase. Treat that security decision separately from tidying a password-manager device list.

Frequently Asked Questions

Will all my passkeys appear automatically on a new phone?

No. Synced passkeys depend on access to the right provider account and completion of its encryption checks. Device-bound passkeys and unsupported migrations need another sign-in or recovery route.

Does scanning a sign-in QR code transfer my passkey?

Not by itself. A cross-device sign-in uses the passkey on the other device to authenticate you. Register or transfer a passkey separately if you need it stored on the new phone.

Can a password CSV restore passkeys?

No. Use a specifically supported passkey transfer or restore the original credential provider. Ordinary password CSV files do not contain the required passkey credentials.

Is my carrier PIN the same as my passkey recovery PIN?

No. A carrier account PIN protects mobile-account changes. A phone passcode and a password-manager encryption PIN serve different purposes. Read the prompt to identify which provider and device it refers to.

Should I reset all passkeys if I forget my Google Password Manager PIN?

Do not use deletion as the first troubleshooting step. Google says resetting passkeys deletes them and requires new credentials at the services. Check its supported PIN recovery instructions and preserve working devices and alternative sign-in methods first.

Sources and Image Credits

Sources: Google passkey management; Google Password Manager PIN; Google credential transfers; Apple Keychain across devices; Apple lost-device security.

Illustrations: Impulsec.