Passkey Adoption · Android
How high is passkey adoption on Android in 2026?
100%
WebAuthn available
97%
Passkey-ready
100%
Synced passkeys
Android passkey readiness in Mar 2026, with the preceding three months of history available below.
Passkey Adoption · Android
Android passkey readiness in Mar 2026, with the preceding three months of history available below.
As of Mar 2026, passkey adoption on Android is measurable across Chrome (WebAuthn 100%, passkey-ready 97%, synced passkeys 100%). Based on Corbado's passkey intelligence, these figures cover the last three months (Jan 2026–Mar 2026). On Android, passkeys live by default in Google Password Manager and are protected by device biometrics.
Chrome is the dominant browser for passkey traffic on Android and is what this page focuses on. Samsung Internet and Firefox also implement WebAuthn on Android; we keep the headline view on Chrome for readability, with higher-resolution per-browser breakdowns available through Corbado's enterprise tooling. Android 14 and later ship with Credential Manager as the system entry point, which unifies passkey and password UI across supporting apps.
In Mar 2026, Chrome on Android had WebAuthn available to 100% of users and was passkey-ready (via Google Password Manager with device biometrics) for 97%, and 100% of created passkeys synced across the user's devices. Chrome on Android uses Google Password Manager as the passkey store and offers hybrid transport, so an Android phone can also sign in to sites open on a Windows or macOS computer.
| Month | WebAuthn | Passkey-ready | Synced passkeys |
|---|---|---|---|
| Jan 2026 | 100% | 97% | 100% |
| Feb 2026 | 100% | 97% | 100% |
| Mar 2026 | 100% | 97% | 100% |
This page focuses on the biggest chunk of Android traffic: Chrome. For higher-resolution, per-browser and per-version breakdowns, use Corbado's passkey observability and enterprise products.
Synced passkeys have been available on Android 9 and later since the October 2022 Google Password Manager rollout. WebAuthn itself reached Android 7 and later earlier, via a Google Play Services update. The experience improved substantially in Android 14 with Credential Manager, which unifies passkey and password sign-in under one system UI. Our Android figures cover all supported versions as encountered across many sites and customers.
When a user scans a QR code shown by a site open on a laptop, Chrome on Android uses Bluetooth to prove the phone is physically near the laptop, then asks the user to approve with biometrics or the screen lock. The passkey stays on the phone; the laptop only receives the signed assertion. This flow works across ecosystems, including signing into Windows or macOS sites from an Android phone.
Passkeys stored in Google Password Manager sync across a user's Android devices and to Chrome on desktop when the user is signed into the same Google account with sync enabled. Cross-ecosystem sync (for example to Safari on macOS) is not direct and is usually handled through hybrid transport rather than a shared credential store.
The same three-month window for the other major operating systems, with their latest passkey-ready and sync figures.
Each percentage represents the share of Android visitors in that month for whom the feature was technically available, not the share who actually used a passkey. Numbers are drawn from many sites so they reflect what the average Android visitor sees today. Inputs combine Corbado's internal data with public demo and tooling surfaces such as the Passkeys Debugger. See the full operating system and browser matrix on the homepage.
