Skip to Content
Platform Ontology

Passkey availability checks

A page can ask whether this device can use a passkey, without showing a prompt.

Gets silentlyWhen the page loads

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

APIPublicKeyCredential.isUserVerifyingPlatformAuthenticatorAvailable(); isConditionalMediationAvailable(); getClientCapabilities()
Browser compat keysapi.PublicKeyCredential.isUserVerifyingPlatformAuthenticatorAvailable_static
api.PublicKeyCredential.isConditionalMediationAvailable_static
How access is grantednone
What the user seesNone
Needs a secure context (HTTPS)Yes
Needs a user gestureNo
How long it lastsRead fresh each time
How to take it backNone needed
Inside an iframeNeeds a permissions policy in cross origin frames

Typical flow

  1. Page calls the static check
  2. Browser answers true or false with no prompt
  3. Page picks the sign in screen and may add the answer to a risk score

Data you get

Shape: object
How often: per check

FieldTypeUnitRangePrecision
uvpaabooleanNonetrue when a built in authenticator with user verification existsNot listed
conditionalMediationbooleanNonetrue when passkey autofill is availableNot listed
clientCapabilitiesmapNonenamed features such as hybridTransport and passkeyPlatformAuthenticatorNot 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

TypeExampleApps
securityA login page shows a passkey button only where a built in authenticator exists.None named
bankingA bank offers passkey autofill when it is available.None named
shoppingA store hides a passkey prompt on devices that cannot use one.None named
analyticsA product team measures what share of visitors can use passkeys.None named
enterpriseA fraud team notes that servers and containers answer false.None named
developerA 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

Good uses and abuse

Legitimate uses

  • Better sign in screens
  • Risk hints

Known abuse

  • Penalizing servers and VMs

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits1Rough identifying entropy, when known

History

  • 2018-05, Chrome 67: isUserVerifyingPlatformAuthenticatorAvailable ships
  • 2022-10, Chrome 108: isConditionalMediationAvailable added
  • 2024, Chrome 133: getClientCapabilities added to Chrome

Sources

How well checked: Based on official documentation.

On this page