What should I prepare so I can recover accounts that use passkeys?

Make a short recovery plan for each important account, rather than one general plan for every service. Start with the provider’s own recovery instructions and note when you checked them. Then record which devices can access the passkey, which recovery methods are configured, and what the provider says to do if your usual device is unavailable.

A passkey’s behavior and recovery path depend on the provider and where it is stored. For example, Google says adding a passkey does not remove existing authentication or recovery factors from a Google Account. Google also says its passkey requires access to and the ability to unlock the device. [S1] These are Google-specific details, not rules for every service.

List devices you have actually checked, and describe what each one can do. For example: “Personal phone — passkey available; screen lock works; last checked [date].” If you have another device, note whether it can access the same account or passkey instead of assuming it can.

Also note whether you can unlock each device and whether you can reach it if your main phone is lost. Google’s stated requirement to access and unlock the device applies to its passkeys. [S1] Apple says passkeys stored in iCloud Keychain sync across a user’s devices, and describes Keychain recovery involving account and recovery factors such as a trusted phone number and device passcode. [S2] These details are specific to Apple; check your own setup and instructions.

While signed in, review the provider’s account security or recovery settings. Record the names of available methods in your private plan; don’t copy passwords, one-time codes, or other secrets into a document that might be exposed. If a method is missing, use the provider’s setup guidance to decide whether and how to add it.

Keep the plan usable if your phone is unavailable. It can point to the official recovery instructions and list the methods you have configured. Don’t treat one provider’s example as universal: Apple’s described Keychain recovery depends on its own account and recovery factors, while Google’s article explains Google Account behavior. [S1] [S2] The supplied information does not establish recovery steps for other providers or every account configuration.

Use placeholders until you verify each detail. For example:

1. Account/provider: Google — instructions checked: [date]. Passkey-capable device(s): [device and whether it unlocks]. Existing recovery methods: [method names only]. If usual device is unavailable: [provider’s stated next step].
2. Account/provider: Apple — instructions checked: [date]. Devices using iCloud Keychain: [verify each device]. Recovery details to confirm: [trusted phone number and device passcode requirements, as applicable]. If usual device is unavailable: [provider’s stated next step].
3. Other accounts: [provider] — repeat the fields using that provider’s own instructions.

These are prompts to verify, not claims about how your accounts are configured. Google says adding a passkey does not remove existing recovery factors. [S1] Apple describes Keychain syncing and recovery within its ecosystem. [S2] Neither source establishes a universal passkey recovery procedure.

Treat a device change as a reason to review the plan: check the new device’s access, confirm which passkeys and recovery methods are available, and consult the provider’s instructions before you stop using the old device. You can set a reminder to review the notes periodically; the sources here do not establish a single review interval.

A useful stopping check is: Can I find the provider’s recovery instructions? Do I know which device I can unlock to use the passkey? Have I recorded the recovery methods actually configured, without recording secrets? If any answer is no, keep your existing account access available while you investigate through the provider. The cited guidance is specific to Google and Apple; it does not verify what another provider will require. [S1] [S2]