OUR METHOD

Clear routes start with clear evidence.

No invented compatibility scores. No silent assumptions. Here is how we reach a result.

The direction is the unit of evidence.

“This manager supports passkeys” is not the same as “this manager can import your passkeys from another app.” We evaluate the source, destination, operating system and version together. A documented A → B route does not automatically establish B → A.

Five honest answers

  • Documented: reviewed official guides describe the route and the selected OS meets the requirements. This is not a guarantee of success.
  • Restricted: a specific provider restriction or minimum OS requirement blocks the selected setup under the reviewed guidance.
  • Conflicting guidance: relevant official sources disagree. We surface the conflict instead of guessing.
  • Not verified: we lack sufficient direction-specific evidence. The transfer may still be possible.
  • Same provider: account or device setup is a separate workflow.

What we reviewed, and what we did not

We reviewed the linked public documentation on 11 October 2026. We did not conduct physical-device transfer tests, verify individual accounts, inspect private vaults or certify any provider. The finder applies a curated set of rules locally in your browser. It does not scan your device.

A real example of conflicting guidance: Bitwarden’s export guide and 2026.7.0 release notes mention Android 10+, while its canonical import and passkey guidance specify Android 14+. Routes involving Bitwarden on Android 10–13 are flagged as conflicting. Android 14+ meets the stricter threshold, but still does not override a direction-specific restriction.

Coverage and limits

This edition covers five providers on Android and iOS. It focuses on native Credential Exchange flows. Desktop-only exports, hardware security keys, enterprise-specific deployments, cross-account sync and every credential type are outside its scope. Google’s Android framework announcement is not evidence that every participating app works on every Android version.

Documentation can change after our review. Use the source links, check current app versions and retain working recovery access while verifying a move. There is no automatic daily re-verification service on this site.

The source ledger

Official documents used by the route engine. Each result links to the subset relevant to your selection.

Independence

Passkey Atlas is an independent information tool. Provider names identify compatibility destinations, not endorsements or partnerships. There are no paid rankings, affiliate links or provider-sponsored recommendations in this edition. Optional guide-page advertising helps fund the project and does not change our compatibility assessments, source selection or restrictions.

Passkey Atlas is a KitForma project. To report a documentation change or a problem with this site, contact KitForma. Include the route and source link; never send passwords, passkeys or vault exports.

Your advertising choice

If you allow advertising, Adsterra may show a banner on our guide pages and use cookies and device or page information to deliver and measure ads. The route finder stays free of advertising.

You can continue without ads and use every feature. Your choice is saved in this browser for up to six months; change it here at any time. Global Privacy Control keeps ads off.

Read our privacy notice and Adsterra’s privacy policy.