Conditional UI.
The WebAuthn capability (also called Passkey Autofill) where browsers surface available passkeys directly in the username field — letting users sign in by tapping their account rather than typing anything.
Conditional UI is the UX feature that finally makes passkey adoption feel as easy as the marketing promised. The visible login form looks like a regular username field; passkey-equipped users see their account inline; non-passkey users see the normal password prompt. Same page, both paths, no disruption to either. Production CIAM platforms should enable it by default on their login pages — the conversion uplift over button-based passkey flows is meaningful.
Common questions
What is Passkey Autofill?
How does Conditional UI work for the relying party?
Which browsers support Conditional UI?
Related terms
In the guides
Passkeys Explained: How Synced Credentials Replace Passwords
Passkeys are the user-facing brand for synced WebAuthn credentials. A practical explanation of how they work, sync, recovery, and the deployment patterns that make adoption real.
WebAuthn Explained: How Passkeys Work Under the Hood
WebAuthn is the W3C browser API that powers passkeys. A practical explanation of registration, assertion, RP-IDs, attestation, and the architecture choices that determine adoption.