← all benchmarks

Conditional Create Rate

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.

Q1 2026 · ecosystem readiness

Conditional Create

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.

iOS web Very strong

Apple keeps browser, authenticator and password manager tightly integrated; passkey autofill is already familiar.

Browser ready 83%–92% range

Authenticator ready YES

Add-on contribution range 42%-62%

macOS web Strong

Chrome and Safari cover the browser side well; desktop password-manager choice is more mixed than iOS.

Browser ready 83%–92% range

Authenticator ready MOSTLY YES

Add-on contribution range 28%-43%

Android web Fragmented

Chrome / Google Password Manager can work; Samsung Internet, Samsung Pass and default-provider setup fragment readiness.

Browser ready 83%–92% range

Authenticator ready FRAGMENTED

Add-on contribution range 7%-11%

Windows web Constrained

Chrome / Google Password Manager can work; Windows Hello is not a Conditional Create path and Edge lowers readiness.

Browser ready 83%–92% range

Authenticator ready PARTIAL

Add-on contribution range 12%-18%

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.

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.

1Browser/client reports Conditional Create support. 2The selected authenticator or credential provider supports Conditional Create. 3The user has a saved password and uses autofill recently enough for the browser/provider timing window. 4The 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%

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

Related sources

Conditional Create Rate