Client-side passkey support and readiness test

Passkey Readiness Checker

See whether your current browser and device look ready for passkeys. This tool checks browser support, secure context, built-in authenticator availability, and likely sign-in experience.

What this tool can and cannot do

It can tell you whether this browser and device appear capable of using passkeys. It cannot inspect passkeys created for Google, Apple, Amazon, or any other third-party site.

Not Ready Yet

One or more required browser capabilities are missing or blocked, so passkeys may not work in this environment.

Ready checks

0

Capabilities confirmed

Limited or blocked

0

Checks needing attention

Current environment

Browser
Checking...
Operating system
Checking...
Device type
Checking...

Likely passkey provider

Checking...

This is only a best-effort guess based on your device and browser family, not a direct inspection of stored passkeys.

Refresh

Re-run the readiness checks after changing browser settings, switching browsers, or enabling device security.

Last checked: Checking now...

Readiness breakdown

Each check explains one part of the browser and device environment that affects passkey support.

Secure context

Passkeys require HTTPS or localhost in modern browsers.

Checking

Checking secure context...

Modern browsers block passkey APIs on insecure origins.

WebAuthn API

Checks whether the browser exposes the core passkey API.

Checking

Checking WebAuthn support...

The PublicKeyCredential API is the foundation for passkeys.

Credentials API

Checks whether the browser can coordinate credential flows.

Checking

Checking Credentials API support...

Passkey flows depend on navigator.credentials in addition to WebAuthn.

Platform authenticator

Checks whether this device likely supports built-in passkeys.

Checking

Checking platform authenticator availability...

Examples include Face ID, Touch ID, Windows Hello, or Android screen lock.

Passkey autofill

Checks whether passkey sign-in suggestions are likely supported.

Checking

Checking conditional mediation support...

This controls modern passkey autofill style sign-in prompts.

Top-level page context

Checks whether the page is running in the main browsing context.

Checking

Checking browsing context...

Embedded pages can have stricter passkey behavior than top-level pages.

How to use this result

  1. Open the tool in the exact browser and device where you want to use passkeys.
  2. Review the overall status to see whether your environment looks ready, partial, or blocked.
  3. Open the readiness cards to see which requirement is missing or limited.
  4. Fix any blocked checks, then refresh the page and run the test again.
  5. After that, test the specific website or app because every relying party still needs its own passkey implementation.

Recommended next steps

  • Open the site on HTTPS or localhost. Plain HTTP blocks passkey APIs in modern browsers.
  • Switch to a newer browser version that supports WebAuthn and passkeys.
  • Expect passkeys to work with a more manual sign-in flow if autofill-style conditional UI is unavailable.
  • Test from a normal top-level browser tab rather than an embedded frame or in-app browser.

Pro tips

  • Run this tool on the exact browser and device where you want to use passkeys. Results can differ between Chrome, Safari, Firefox, Edge, desktop, and mobile.
  • Use HTTPS in production. Passkey APIs are restricted on insecure origins.
  • A “ready” result does not guarantee that every website has implemented passkeys correctly. It only means your current environment appears capable.
  • If platform authenticator support looks limited, check whether screen lock, Touch ID, Face ID, or Windows Hello is enabled on the device.
  • Safari and Firefox can support passkeys differently from Chromium browsers, especially around autofill and conditional UI.
  • For shared or managed devices, browser policy restrictions can affect passkey availability even if the device normally supports it.

Passkey Readiness Checker FAQ

What does this passkey readiness checker actually test?

It tests whether your current browser and device expose the APIs and secure environment normally needed for passkeys. It checks secure context, WebAuthn support, navigator.credentials support, likely platform authenticator availability, and passkey autofill-related support.

Can this tool see my existing passkeys from Google, Apple, or another site?

No. Browsers do not expose your saved passkeys to random websites. This tool cannot list or inspect passkeys created for other services. It only checks whether your current browser and device look ready to use passkeys in general.

What does “platform authenticator” mean?

A platform authenticator is the built-in passkey capability on your device, such as Face ID, Touch ID, Windows Hello, or an Android device unlock method. If this check passes, the browser reports that a built-in user-verifying authenticator is likely available.

Why can passkeys still fail even if this page says I am ready?

A website still needs to implement passkeys correctly on its own domain. Passkey sign-in also depends on relying party configuration, browser rules, account settings, and whether the specific site has enabled passkeys for your account.

Do passkeys always need biometrics?

No. Biometrics are only one way to unlock the private key on your device. A device PIN, password, or other screen-lock method can also be used depending on your platform and security settings.

Is any of this data uploaded anywhere?

No. This page runs entirely in your browser. It reads browser capabilities locally and does not send passkey or account information to a server.