Browser security
Compatibility & evidence
Authentication

WebAuthn platform authenticator detection

Detects whether a user-verifying platform authenticator is available.

Support in current browsers

Checked against the current browser versions recorded in MDN browser data 8.1.5.

BrowserMinimumOutcomeReason
Chrome155WorksEvery required mapped BCD feature is available without a recorded qualification.
Edge154WorksEvery required mapped BCD feature is available without a recorded qualification.
Firefox157Works with limitsEvery required mapped feature is available, but BCD records one or more qualifications.
Safari27WorksEvery required mapped BCD feature is available without a recorded qualification.
Chrome for Android155WorksEvery required mapped BCD feature is available without a recorded qualification.
Firefox for Android157WorksEvery required mapped BCD feature is available without a recorded qualification.
Safari on iOS27WorksEvery required mapped BCD feature is available without a recorded qualification.
Android WebView155WorksEvery required mapped BCD feature is available without a recorded qualification.
Samsung Internet30.0WorksEvery required mapped BCD feature is available without a recorded qualification.
The release trace

How support changed

Each segment groups recorded releases with the same result. Gaps between recorded versions are not filled in. This is support at each release, rather than the planner’s check of every release above a minimum.

Chrome

api.PublicKeyCredential.isUserVerifyingPlatformAuthenticatorAvailable_static
  1. 1 – 6666 recorded releases
    Not supported
  2. 67 – 15588 recorded releases
    Works

Edge

api.PublicKeyCredential.isUserVerifyingPlatformAuthenticatorAvailable_static
  1. 12 – 176 recorded releases
    Not supported
  2. 18 – 15476 recorded releases
    Works

Firefox

api.PublicKeyCredential.isUserVerifyingPlatformAuthenticatorAvailable_static
  1. 1 – 5962 recorded releases
    Not supported
    • Only supports USB U2F tokens.
  2. 60 – 15798 recorded releases
    Works with limits
    • Only supports USB U2F tokens.

Safari

api.PublicKeyCredential.isUserVerifyingPlatformAuthenticatorAvailable_static
  1. 1 – 12.121 recorded releases
    Not supported
  2. 13 – 2740 recorded releases
    Works

Chrome for Android

api.PublicKeyCredential.isUserVerifyingPlatformAuthenticatorAvailable_static
  1. 18 – 6946 recorded releases
    Not supported
  2. 70 – 15585 recorded releases
    Works

Firefox for Android

api.PublicKeyCredential.isUserVerifyingPlatformAuthenticatorAvailable_static
  1. 4 – 5953 recorded releases
    Not supported
    • Partial implementation
    • Only supports USB U2F tokens.
  2. 60 – 9122 recorded releases
    Works with limits
    • Partial implementation
    • Only supports USB U2F tokens.
  3. 92 – 15766 recorded releases
    Works

Safari on iOS

api.PublicKeyCredential.isUserVerifyingPlatformAuthenticatorAvailable_static
  1. 1 – 12.218 recorded releases
    Not supported
  2. 13 – 2740 recorded releases
    Works

Android WebView

api.PublicKeyCredential.isUserVerifyingPlatformAuthenticatorAvailable_static
  1. 1 – 6941 recorded releases
    Not supported
  2. 70 – 15585 recorded releases
    Works

Samsung Internet

api.PublicKeyCredential.isUserVerifyingPlatformAuthenticatorAvailable_static
  1. 1.0 – 9.423 recorded releases
    Not supported
  2. 10.0 – 30.029 recorded releases
    Works

BCD 8.1.5 · catalogue 2.3.0. Source corrections can change this trace without a new browser release.

What this feature can and cannot do

Helps protect against

  • Phishing-prone password dependence
  • Credential reuse

Does not guarantee

  • Account recovery weaknesses
  • Server verification defects
  • Authenticator policy

What you need before using it

  • A complete WebAuthn registration and authentication flow

Fallback to keep in place

Offer standards-based roaming authenticators and a carefully protected recovery path.