WebAuthn passkey registration
Creates a passkey or security key credential for the site.
In one line
Can create a passkey or security key login for one site
Creates a passkey or security key credential for the site.
Makes a public key login bound to the site's domain. The site never sees the private key or biometrics.
What it can and can't do
What the user does: You tap Create a passkey and confirm with your fingerprint, face, phone or key
It can
- Ask your device to make a new key pair tied to that site
- Save the public half on its servers so you can sign in later
- Let you use a phone or a USB security key instead
It cannot
- See the private key; it stays on your device or password manager
- Get your fingerprint or face data
- Use that passkey on another site
- Create it without your confirmation
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 67 | 2018-05-29 | None |
| Edge | Supported | 18 | 2018-10-02 | None |
| Firefox | Supported | 60 | 2018-05-09 | Only supports USB U2F tokens. |
| Safari | Supported | 13 | 2019-09-19 | None |
| Safari on iPhone | Supported | 13 | 2019-09-19 | None |
| Chrome on Android | Supported | 70 | 2018-10-17 | None |
| Samsung Internet | Supported | 10.0 | 2019-08-22 | None |
How a site asks for it
| API | navigator.credentials.create({publicKey:{rp,user,challenge,pubKeyCredParams,authenticatorSelection,attestation}}) |
| Permissions policy | publickey-credentials-create |
| Browser compat keys | api.PublicKeyCredential |
| How access is granted | prompt |
| What the user sees | OS or browser sheet: use Touch ID, Face ID, Windows Hello, phone or security key |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | Yes |
| How long it lasts | Credential persists on authenticator or cloud keychain |
| How to take it back | Delete passkey in OS password manager; signalUnknownCredential from the site |
| Inside an iframe | Same as top level; cross-origin iframes need a permissions policy where listed |
Typical flow
- Call the API
- Browser applies its access rules
- Page receives the result
Data you get
What comes back: Creates a passkey or security key credential for the site.
Shape: object
How often: on demand
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
id / rawId | binary | bytes | 16 to 1023 bytes | credential id |
response.attestationObject | binary | bytes | format: none, packed, tpm, android-key, apple, fido-u2f | enterprise only attestation |
response.getPublicKey() | binary | bytes | COSE key (ES256 -7, RS256 -257, EdDSA -8) | Not listed |
authenticatorAttachment | enum | None | platform or cross-platform | Not listed |
transports | list | None | usb, nfc, ble, internal, hybrid | Not listed |
Technical limits
- Credential is bound to rpId; phishing sites cannot reuse it
- Cannot read private key or biometric data
- Attestation shown to the site only if user consents; most browsers default to none
- Needs HTTPS (or localhost) and a user gesture on most browsers
The story
What it is
Makes a new passkey for a site, tied to its domain.
For you
A prompt says something like 'Save a passkey for this site?' and you confirm with your face, fingerprint or PIN. After that you can skip the password. The site never sees your fingerprint or face.
For makers
Makers get a safe way to sign people in without a password database to leak. It cuts reset support and stops phishing, and it is a selling point for security minded customers.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A console or game account site invites a player to create a passkey after sign in, so a stolen password cannot take over the account. | PlayStation, Roblox, Nintendo Account |
| banking | A bank prompts a customer to add a passkey to replace text message codes. | None named |
| shopping | A store offers 'Create passkey' on the order confirmation page so the next purchase is faster. | Amazon, eBay |
| productivity | A code host or work app asks a new user to create a passkey in their password manager. | GitHub, Google Workspace |
| payments | A payments app uses a new passkey to bind the browser as a trusted device for transfers. | PayPal |
| security | A security team grows passkey enrollment as a measure of fewer account takeovers. | None named |
Risks
- Lose the device, lose the passkey if not synced
- Prompt looks like others
What the platform says
- Apple: Passkeys. Apple presents creating a passkey as saving a Face ID or Touch ID login that syncs across devices.
- Google: Passkeys. Google sells passkeys as sign in with your fingerprint, face or screen lock, saved in your account.
- MDN (standards docs): Web Authentication API. Describes a way for sites to sign people in with public key credentials held on a device, instead of passwords.
Good uses and abuse
Legitimate uses
- Passwordless login
- Phishing resistant MFA
Known abuse
- Attestation can fingerprint authenticator model
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 4 of 5 | How revealing the data is |
| Utility | 5 of 5 | How useful it is to honest apps |
| Friction | 2 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2018-04, Chrome 67: WebAuthn ships (Safari 13, Firefox 60)
- 2022-09, Safari 16: Passkeys sync via iCloud Keychain
- 2024-04, Chrome 133: getClientCapabilities (Firefox 135, Safari 17.4)
- 2024-12, Chrome 129: PublicKeyCredential.toJSON and parse*OptionsFromJSON (Safari 18.4)
Sources
How well checked: Checked against real behavior.