WebAuthn
What Is WebAuthn?
WebAuthn, short for Web Authentication, is a web standard that lets websites and apps verify users with cryptographic credentials instead of passwords. It is a W3C-backed browser API for passwordless sign-in and stronger multi-factor authentication. WebAuthn is not a biometric system or password manager. A fingerprint or face scan may unlock a credential on a device, but biometric data is not sent to the website.
How WebAuthn Works
A relying party is the website or app requesting sign-in. An authenticator is a device feature or security key that holds the credential.
- The server creates a one-time random challenge to prevent replay attacks.
- The browser sends the request to an authenticator, such as a phone, laptop, or hardware security key.
- During registration, the authenticator creates a private and public key pair for the site's origin, or verified web address.
- The private key stays on the authenticator, while the server stores the public key with the user's account.
- At sign-in, the authenticator approves the request and signs the new challenge with its private key.
- The server verifies the signature with the public key before creating a session.
WebAuthn vs. Passkeys vs. Passwords
Passkeys use WebAuthn, but the terms describe different parts of the sign-in experience.
| Item | What it is | What the service receives |
|---|---|---|
| WebAuthn | The technical browser standard and API | Public-key credentials and signed challenges |
| Passkey | A user-friendly credential built with WebAuthn | A public key, not a reusable secret |
| Password | A shared secret chosen by the user | A password-derived verifier that attackers may target |
Benefits of WebAuthn
Its design improves security and sign-in convenience.
- Credentials are bound to a site origin, helping block lookalike phishing sites.
- The service does not need to store a reusable password.
- Users can authenticate with built-in device authenticators or physical security keys.
- WebAuthn can protect high-risk actions, such as changing payment details, through step-up authentication.
Practical Limits and Implementation Considerations
WebAuthn needs account lifecycle planning, not just a login button.
- Let users enroll more than one authenticator before they lose or replace a device.
- Protect account recovery with identity checks and rate limits, since weak recovery can defeat strong sign-in.
- Test cross-device sign-in and provide clear instructions for users unfamiliar with passkeys.
- Keep a compatible fallback where needed, but avoid automatically falling back to an easily phished password.
When to Use WebAuthn in an Application
WebAuthn suits consumer logins, workforce tools, administrator dashboards, and sensitive account actions. It proves who a user is, while authorization decides what that user can access. It can work alongside sessions, OAuth, and other multi-factor authentication controls rather than replacing permission checks.
Building Secure Sign-In Flows with Emergent
Teams building with an AI app builder can plan WebAuthn registration, server-side signature validation, session handling, and protected recovery flows as part of product architecture. Learn more about app design and development, then use an AI web app builder to turn a designed sign-in flow into a full-stack application. Build phishing-resistant sign-ins with Emergent.
on Emergent today

