Passkey Sync - Cross-Device Credential Sharing
About 2 min read
Passkey sync is a mechanism that distributes the credential (private key) of a passkey to multiple devices via the cloud. With traditional FIDO2 authentication, the private key was bound to a single device, so the effort of re-registering credentials when a device was lost or replaced was a barrier to adoption. Apple announced passkey sync in the iCloud Keychain in 2022, and Google followed suit.
Why Sync Became Necessary
Device-bound FIDO2 authentication, such as a security key, was hard for ordinary users to handle. If you lose the key, you can no longer access your account, and every time you buy a new device you have to re-register with each service you use. The sync feature was designed as a remedy for this "inconvenience."
Sync Methods by Platform
| Platform | Sync infrastructure | Encryption method | Sync scope |
|---|---|---|---|
| Apple | iCloud Keychain | E2EE (inaccessible even to Apple) | Devices on the same Apple Account |
| Google Password Manager | E2EE (rolled out in stages from 2024) | Android / Chrome on the same Google account |
Both Apple and Google apply end-to-end encryption during synchronization. In Apple's case, the encryption key for the iCloud Keychain is generated on the device, and only encrypted data is stored on Apple's servers. In other words, the design ensures that even Apple itself cannot read the contents of the passkey.
How Sync Works - End-to-End Encryption
Even if a cloud provider's server is compromised, the private key cannot be extracted from the encrypted passkey data. Apple states that it designed iCloud Keychain so that passkeys remain protected even if the Apple Account used with iCloud is compromised.
Challenges of Cross-Platform Sync
As of 2025, the biggest challenge is that sync across platforms is not possible. A passkey created on an iPhone is not synced to Android, and vice versa. The FIDO Alliance is promoting the interoperability of "multi-device credentials."
As a workaround for this problem, third-party password managers such as 1Password and Dashlane support cross-platform passkey sync. Because these tools operate independently of the OS's passkey infrastructure, they can share passkeys even between Apple devices and Android devices. The article password sync across multiple devices explains the specific setup steps.
The Trade-Off with Device-Bound Types
Highly convenient, and recoverable from the cloud even when a device is lost. Suited to consumer-facing services. However, it depends on the security of the cloud account.
Because the private key never leaves the physical device, it is unaffected by cloud breaches. Suited to high-security enterprise environments. Recovery after loss is a challenge.
Corporate security policies can also adopt hybrid operations in which synced passkeys are permitted for general employees while security keys are mandated for administrator accounts. The article challenges of passkey migration explains the details of this operational design.
Misconceptions About Sync
One concern is, "If passkeys are synced, don't they carry the same leakage risk as passwords?" However, passkey sync and password sync work differently. A password is a "shared secret" sent to the service's server, but a passkey's private key is never sent to the service's server. Sync takes place among the user's devices, and at authentication time only the signature for the challenge is sent to the server. Even if the sync path were compromised, the private key cannot be extracted from data encrypted with E2EE.
Adoption Decisions in Practice
When introducing passkey sync, an organization standardized on the Apple ecosystem can rely on the iCloud Keychain, but in a BYOD (bring-your-own-device) environment the cross-platform problem becomes apparent. Evaluate the risks of biometric authentication as well, and consider whether biometric authentication is appropriate as the identity verification method for synced passkeys.
Frequently Asked Questions
- Does passkey sync work between Apple and Google devices?
- The OS-standard sync foundations (iCloud Keychain and Google Password Manager) are independent of each other, so a passkey created on an iPhone is not automatically synced to Android. Across platforms, the options are signing in each time via QR-code proximity authentication, or storing passkeys in a cross-platform password manager such as 1Password to share them.
Was this article helpful?
Related Terms
- How Password Managers Keep Your Accounts SafePassword managers generate, encrypt, and auto-fill unique credentials for every login. Learn how an encrypted vault simplifies security across all devices.
- Recovery Codes - Backup Access for MFARecovery codes are one-time backup codes for regaining account access when the primary MFA device is lost. They should be stored securely, for example printed or in a password manager, as they bypass normal authentication.
- Social Login - Sign In with Google, Apple, and MoreSocial login lets users sign in to third-party services with a Google, Apple, or other social account via OAuth 2.0 or OpenID Connect. It boosts convenience but carries risks of over-permissioning and privacy exposure.
- Passkeys - FIDO2 Passwordless AuthenticationPasskeys replace passwords with public-key cryptography stored on your device. See which platforms support passkeys and how to enable passwordless login.