# Passkeys Finally Go Truly Cross-Platform
Table of Contents
Signing in to a site almost always means a password: a string to remember, one you can forget, reuse out of laziness, or hand by mistake to a scam page. Passkeys were created to replace that mechanism. They’ve been around for a few years, but until now they carried a practical limit that held back adoption: a passkey created inside one ecosystem tended to stay there. In January 2025 Google announced a step that eases that limit. Passkeys saved in its manager, Google Password Manager, are now available on iPhone and iPad too, on top of Android, Windows, macOS, Linux, and ChromeOS. It’s worth understanding what a passkey is, and why being able to use it across devices from different vendors changes things.
What a passkey is
A passkey is a way to sign in to a site or an app without typing a password. Instead of a secret word shared with the service, it uses a pair of cryptographic keys: two mathematical values tied to each other. One is the private key, and it stays on the user’s device, protected and never shared with anyone. The other is the public key, handed to the site when you register.
When you sign in, the site sends a small challenge to be signed. The device signs that challenge with the private key, but only after the user has unlocked as usual: fingerprint, face recognition, PIN, or pattern. The site verifies the signature with the public key it had on file and lets you in. For the user, the gesture is the same one already used to unlock the phone.
This design has two practical consequences. First: there’s no longer a password to steal. All the site’s server keeps is the public key, which on its own doesn’t let anyone in; a data breach no longer hands over sign-in credentials. Second: the passkey is bound to the site’s real address. A page that imitates your bank will never get a valid signature, because the address doesn’t match. In practice phishing, the trick that pushes people to type credentials into a fake site, stops working. Passkeys are built on open standards, WebAuthn and FIDO2, maintained by the FIDO Alliance together with the web standards body.
Why syncing was the real obstacle
On paper the mechanism is simpler and safer than a password. The problem, until now, wasn’t the cryptography: it was portability. If the private key stays on the device, what happens when you have more than one device, perhaps from different vendors?
The big providers answered by syncing passkeys, in encrypted form, across their own devices. But each did it inside its own fence. A passkey created on an iPhone ended up in Apple Passwords, the former iCloud Keychain, and stayed usable on Apple devices. A passkey created on Android or a computer, through Google Password Manager, lived in Google’s world and didn’t reach iPhone or iPad. Anyone with a phone from one vendor and a computer from another, or who switched phone brands, could end up without their passkey right where they needed it.
That’s a concrete obstacle. If users fear being locked out, they tend to keep the old password as a safety net, and the site has to keep supporting it. As long as the password stays as a fallback, the benefits of the passkey remain half realized. Syncing across different platforms is therefore the piece that decides whether passkeys become an everyday sign-in method or stay a convenience for people who live inside a single ecosystem.
What Google announced
On January 16, 2025, on the Chrome for Developers blog, Google announced that Google Password Manager passkeys are available on iOS and iPadOS, starting with version 17. From then on, Chrome with the same signed-in profile syncs Google Password Manager passkeys across all platforms and devices: Android, iPhone and iPad, Windows, macOS, Linux, and ChromeOS.
This is the piece that was missing. Syncing between computers and Android had already arrived a few months earlier, in September 2024, for Windows, macOS, Linux, and ChromeOS. iPhone and iPad had been left out: Google Password Manager passkeys weren’t available there, and passkeys created on iOS ended up in Apple Passwords without reaching the other platforms. With this update a single manager, Google’s, covers all the major desktop and mobile operating systems.
One detail worth stressing about the tone: this isn’t a beta or a limited trial. It’s a stable, generally available feature. The requirement is iOS or iPadOS 17 or later; on iOS 16, passkeys are still saved to iCloud Keychain.
How you use it, in practice
On an iPhone or iPad updated to at least iOS 17, a Google Password Manager passkey is used by setting Chrome as an autofill provider in the system settings. From that point on, the passkeys saved in Google’s manager become available in the apps and browsers on the device, not just inside Chrome.
Access to those passkeys is protected by a Google Password Manager PIN. On a new device you need that PIN, or the screen-lock method of an already linked Android device, to restore your passkeys. It’s worth setting up these recovery elements early, because they’re the only way to get your passkeys back.
What to keep in mind
A few clarifications, so the announcement isn’t read as broader than it is.
The cross-platform syncing discussed here concerns one specific provider, Google Password Manager, and it goes through Chrome. On iPhone you have to set Chrome as the autofill provider; Google’s passkeys don’t merge with the ones in Apple Passwords. Anyone who prefers to stay in the Apple ecosystem keeps using Apple Passwords, which in turn syncs across Apple devices. The change is that there’s now at least one manager that spans all the main systems, iOS included.
Google Password Manager passkeys are end-to-end encrypted: they’re readable only on the user’s device, and not even Google can access them. That’s a privacy guarantee, but it has a flip side: if you lose both the PIN and the linked devices, recovery gets hard. That’s why the recovery methods should be set up while everything works, not when you need them.
Finally, it’s worth remembering that a passkey doesn’t erase the others. A site can let you register several passkeys, one per manager or device, and it’s often wise to have more than one as a fallback. And the password, where it’s still offered, is the layer to drop last, not to throw away on day one.
In short, the news isn’t the passkey itself, which already existed, but the fact that one manager now carries it uniformly across all the widespread operating systems. It’s the kind of unshowy detail that decides whether a security technology stays niche or becomes something you use without thinking about it.
