---
url: 'https://www.corbado.com/passkey-benchmark-2026/conditional-create'
title: 'Conditional Create Rate Benchmark'
description: 'Conditional Create benchmark showing where password sign-ins can upgrade into passkeys automatically.'
lang: 'en'
dir: 'ltr'
keywords: 'conditional create, automatic passkey upgrade, passkey creation benchmark, credential provider support'
---

# Conditional Create Rate

[← all benchmarks](https://www.corbado.com/passkey-benchmark-2026.md)

Conditional Create Rate measures where browser, authenticator and credential-provider support make passkey creation automatic: silently after a successful password sign-in, with no extra prompt. It is best read as an adoption accelerator for mature passkey rollouts, not as a standalone replacement for enrollment strategy.

## Conditional Create

*Q1 2026 · ecosystem readiness*

Conditional Create makes passkey creation automatic after a successful password sign-in, when the right ecosystem stack is in place (see the Prerequisite Stack below for the full gating logic). The four platform tiles below assume the the following credential managers for each OS: iCloud Keychain (Apple Passwords) on iOS / macOS, Google Password Manager on Android and the Chrome / Google Password Manager on Windows. The range is an add-on benchmark for mature deployments where explicit enrollment prompts already exist; standalone deployments can differ materially.

| Platform | Browser ready | Authenticator | Add-on contribution | Ecosystem readiness |
| --- | --- | --- | --- | --- |
| iOS web | 83%–92% | Yes | 42%–62% | Very strong |
| macOS web | 83%–92% | Mostly yes | 28%–43% | Strong |
| Android web | 83%–92% | Fragmented | 7%–11% | Fragmented |
| Windows web | 83%–92% | Partial | 12%–18% | Constrained |

### Ecosystem Interpretation

iOS is the strongest environment because browser, authenticator, password manager and passkey autofill behavior are tightly integrated. macOS is also viable, but more mixed. Windows and Android currently show the most friction: Windows Hello is not a Conditional Create path, while Android depends heavily on the selected credential provider, the manufacturer and the resulting default settings. In Samsung-heavy markets, Google Password Manager availability alone is not enough if the preferred service path is not set for the user.

- **iOS web** — Apple keeps browser, authenticator and password manager tightly integrated; passkey autofill is already familiar.
- **macOS web** — Chrome and Safari cover the browser side well; desktop password-manager choice is more mixed than iOS.
- **Android web** — Chrome / Google Password Manager can work; Samsung Internet, Samsung Pass and default-provider setup fragment readiness.
- **Windows web** — Chrome / Google Password Manager can work; Windows Hello is not a Conditional Create path and Edge lowers readiness.

### Prerequisite Stack

Browser support is only the first gate. Conditional Create also requires provider / authenticator support, a recent saved-password autofill login and no existing passkey in the active credential provider. See the [Corbado Conditional Create analysis](https://www.corbado.com/blog/conditional-create-passkeys).

1. Browser/client reports Conditional Create support.
2. The selected authenticator or credential provider supports Conditional Create.
3. The user has a saved password and uses autofill recently enough for the browser/provider timing window.
4. The account does not already have a passkey in the active credential provider.

### Browser Capability Split

December 2025 capability support explains the browser-side ceiling, aggregated across operating systems. This table is purely about whether the browser exposes Conditional Create, not about the underlying authenticator or OS. iOS Chrome, Edge and Firefox are split out as WebKit contexts; non-iOS Firefox does not show Conditional Create support in this data. This still does not measure saved-password autofill share.

| Browser | Support |
| --- | --- |
| Chrome | 96% |
| Safari | 95% |
| Edge | 4% |
| Chrome iOS WebKit | 98% |
| Samsung Internet | 0% |
| Firefox | 0% |

### Notes

1. Browser support is reported separately because it is necessary but not sufficient. The selected credential provider and authenticator must support Conditional Create too.
2. Autofill share is not published here. Older high-returning-user sites with correctly implemented password fields can have a higher saved-password autofill ceiling.

## Bring your numbers to the benchmark.

*Q1 2026 · beyond the public report*

**Asking yourself:**

- *How does this look in **your** country?*
- *Is your customer mix older or younger than the average we publish?*
- *Want the per-segment breakdown we cannot publish?*

The public report is a slice. Corbado Research holds the full picture — by country, vertical and cohort. Tell us your context and we will run the comparison against your deployment.

[Contact us for the full picture →](https://www.corbado.com/contact-sales)

## Further Reading

Curated Corbado research and primary references.

- **Case study · web.dev** — [How adidas improved sign-in with passkeys](https://web.dev/case-studies/adidas-passkeys) — Case study showing how passkeys and passkey prompts changed account sign-in and creation flows.
- **Adoption accelerator · Corbado blog** — [Conditional Create for Passkeys: Support & Effectiveness](https://www.corbado.com/blog/conditional-create-passkeys) — Platform support, prerequisites and strategic value of upgrading saved-password users into passkey users.
- **Automatic upgrades · passkeys.eu** — [Automatic Passkey Upgrade](https://passkeys.eu/automatic-passkey-upgrade) — Overview of automatic passkey upgrade patterns for moving saved-password users into passkeys.

[← all benchmarks](https://www.corbado.com/passkey-benchmark-2026.md)

---

*Annual benchmark for passkey readiness, creation, usage and adoption strategy by Corbado, the passkey intelligence platform for CIAM teams. [Learn more →](https://www.corbado.com).*