Passkey availability checks
A page can ask whether this device can use a passkey, without showing a prompt.
Static checks such as PublicKeyCredential.isUserVerifyingPlatformAuthenticatorAvailable() and getClientCapabilities() say whether a built in authenticator, passkey autofill or a phone passkey is possible. Sites use them to decide what to show. The answers also reveal a headless server, virtual machine or container, which often has no authenticator.
What it can and can't do
What the user does: Nothing. No prompt appears
It can
- Check for a built in passkey device
- Check for passkey autofill support
- Hide or show passkey buttons
- Notice servers and containers that have no authenticator
It cannot
- See your passkeys
- Prove a person is present
- Use the answer as identity
- Work in an insecure page
How it differs between platforms: The answers vary by operating system and settings, so a false value is only a hint that the device may be a server.
Browser support
Version notes
- Firefox: Version not checked
- Samsung Internet: Version not checked
How a site asks for it
| API | PublicKeyCredential.isUserVerifyingPlatformAuthenticatorAvailable(); isConditionalMediationAvailable(); getClientCapabilities() |
| Browser compat keys | api.PublicKeyCredential.isUserVerifyingPlatformAuthenticatorAvailable_staticapi.PublicKeyCredential.isConditionalMediationAvailable_static |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | Read fresh each time |
| How to take it back | None needed |
| Inside an iframe | Needs a permissions policy in cross origin frames |
Typical flow
- Page calls the static check
- Browser answers true or false with no prompt
- Page picks the sign in screen and may add the answer to a risk score
Data you get
Shape: object
How often: per check
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
uvpaa | boolean | None | true when a built in authenticator with user verification exists | Not listed |
conditionalMediation | boolean | None | true when passkey autofill is available | Not listed |
clientCapabilities | map | None | named features such as hybridTransport and passkeyPlatformAuthenticator | Not listed |
Technical limits
- Varies by OS and settings
- Cannot see credentials
- Not identity
The story
What it is
The page can ask your browser a few quiet yes or no questions about passkeys. It never sees your keys.
For you
You never see it. A site uses the answers to decide whether to show a passkey button for you.
For makers
Use the checks to choose what to show, but never to block a person. Treat a false answer as a weak risk hint only, since many laptops without biometrics also answer false.
Where you see it
| Type | Example | Apps |
|---|---|---|
| security | A login page shows a passkey button only where a built in authenticator exists. | None named |
| banking | A bank offers passkey autofill when it is available. | None named |
| shopping | A store hides a passkey prompt on devices that cannot use one. | None named |
| analytics | A product team measures what share of visitors can use passkeys. | None named |
| enterprise | A fraud team notes that servers and containers answer false. | None named |
| developer | A tester sets up a virtual authenticator to make the checks pass. | Chrome DevTools |
Risks
- Weak bot hint can penalize real users
- Adds a few fingerprint bits
What the platform says
- MDN: PublicKeyCredential. Docs list the static checks used to decide whether to offer passkeys.
Good uses and abuse
Legitimate uses
- Better sign in screens
- Risk hints
Known abuse
- Penalizing servers and VMs
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 1 | Rough identifying entropy, when known |
History
- 2018-05, Chrome 67: isUserVerifyingPlatformAuthenticatorAvailable ships
- 2022-10, Chrome 108: isConditionalMediationAvailable added
- 2024, Chrome 133: getClientCapabilities added to Chrome
Related capabilities
Related
- Passkeys and WebAuthn sign in. Can sign you in with a passkey after your fingerprint, face or PIN
- WebAuthn sign in (get) and conditional mediation. Can sign you in with a passkey, even from the username box suggestions
- WebAuthn passkey registration. Can create a passkey or security key login for one site
- Software passkey for test tools. Lets tests and agents use passkeys without a phone
Sources
How well checked: Based on official documentation.