---
url: 'https://www.corbado.com/passkey-benchmark-2026/webauthn-client-capabilities'
title: 'WebAuthn Client Capabilities Benchmark'
description: 'WebAuthn client capabilities benchmark for conditional mediation, hybrid transport and passkey UX readiness.'
lang: 'en'
dir: 'ltr'
keywords: 'WebAuthn client capabilities, conditional mediation, hybrid transport, passkey UX readiness'
---

# WebAuthn Client Capabilities

[← all benchmarks](https://www.corbado.com/passkey-benchmark-2026.md)

WebAuthn client capabilities show which browser-side features create the ceiling for advanced passkey experiences. Conditional mediation, hybrid transport, related origins and signal support shape how much of the passkey journey can be made seamless.

## WebAuthn client capabilities

*Q1 2026 · browser API support*

The bars below check the **browser only**. They show the share of web sessions whose browser advertises (or is known to) support the WebAuthn capability. They do not check the underlying authenticator or credential provider, which has to support the capability too. Mature capabilities sit near saturation. The WebAuthn Signal API is the main remaining gap after the Safari reporting adjustment.

| Capability | Benchmark range | Observed |
| --- | --- | --- |
| Conditional Create | 83%–92% | 84% |
| Conditional Get | 97%–100% | 97% |
| Hybrid Transport | 97%–100% | 97% |
| Related Origins | 95%–100% | 96% |
| Signal API | 48%–87% | 79% |

### Browser Split

The table keeps the browser split focused on the two most decision-relevant columns: Conditional Create and Signal API. Browser support is the first prerequisite. The authenticator or credential provider must support the capability as well. See the [Corbado Conditional Create analysis](https://www.corbado.com/blog/conditional-create-passkeys).

| Browser | Conditional Create | Signal API |
| --- | --- | --- |
| Chrome | 97% | 84% |
| Safari | 95% | 72% |
| Edge | 7% | 96% |
| Samsung Internet | 0% | 100% |
| Firefox | 5% | 0% |

### Notes

1. Safari Signal API is adjusted: Safari 26+ on iOS/macOS is counted as supported because Safari supports Signal API there, although the capability flag does not reliably report it. Based on the Safari OS-version mix, adjusted Safari Signal API support is 72%. See the [Corbado Signal API analysis](https://www.corbado.com/blog/webauthn-signal-api).
2. Google App traffic is excluded from this browser benchmark because it is not a normal browser context for relying-party WebAuthn capability reporting.

## Bring your numbers to the benchmark.

*Q1 2026 · beyond the public report*

**Asking yourself:**

- *How does this look in **your** country?*
- *Is your customer mix older or younger than the average we publish?*
- *Want the per-segment breakdown we cannot publish?*

The public report is a slice. Corbado Research holds the full picture — by country, vertical and cohort. Tell us your context and we will run the comparison against your deployment.

[Contact us for the full picture →](https://www.corbado.com/contact-sales)

## Further Reading

Curated Corbado research and primary references.

- **Capability guide · Corbado blog** — [WebAuthn Client Capabilities](https://www.corbado.com/blog/webauthn-client-capabilities) — Corbado guide to browser-side capability detection for advanced passkey experiences.
- **Browser API · web.dev** — [WebAuthn client capabilities](https://web.dev/articles/webauthn-client-capabilities) — Google’s implementation guide for reading WebAuthn client support from the browser.
- **API reference · MDN** — [getClientCapabilities()](https://developer.mozilla.org/en-US/docs/Web/API/PublicKeyCredential/getClientCapabilities_static) — Reference for the capability strings that determine advanced passkey UX availability.

[← all benchmarks](https://www.corbado.com/passkey-benchmark-2026.md)

---

*Annual benchmark for passkey readiness, creation, usage and adoption strategy by Corbado, the passkey intelligence platform for CIAM teams. [Learn more →](https://www.corbado.com).*