Support in current browsers

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

BrowserMinimumOutcomeReason
Chrome150WorksEvery required mapped BCD feature is available without a recorded qualification.
Edge150WorksEvery required mapped BCD feature is available without a recorded qualification.
Firefox152WorksEvery required mapped BCD feature is available without a recorded qualification.
Safari26.5WorksEvery required mapped BCD feature is available without a recorded qualification.
Chrome for Android150WorksEvery required mapped BCD feature is available without a recorded qualification.
Firefox for Android152WorksEvery required mapped BCD feature is available without a recorded qualification.
Safari on iOS26.5WorksEvery required mapped BCD feature is available without a recorded qualification.
Android WebView150Not supportedAt least one required mapped feature is not available at this browser baseline.
Samsung Internet29.0WorksEvery required mapped BCD feature is available without a recorded qualification.

What this feature can and cannot do

Helps protect against

  • Phishing-prone password dependence
  • Credential reuse

Does not guarantee

  • Account recovery weaknesses
  • Server-side authentication flaws
  • Every phishing and social-engineering path

What you need before using it

  • A complete WebAuthn flow
  • Secure account recovery
  • User-verification policy

Fallback to keep in place

Offer an explicit WebAuthn action and a carefully protected recovery path.