How to use Browser capability checker
Check whether common browser APIs are exposed, including Web Crypto, WebAssembly, WebGPU and workers. The check runs when you submit the form. Its inputs are processed in this browser.
How the check works
The checker inspects API presence in the current execution context. It does not request camera, microphone, location or graphics-device access.
The Overview tab explains the findings. Measured data lets you search individual fields and values, while JSON report shows the complete export. Export JSON to retain a baseline, or print the findings for your own records. Review the report before sharing it: browser characteristics, token claims, and file names can reveal information about your setup.
Read the result in context
An exposed API is a starting point for feature detection. Secure context, permissions and runtime conditions can still prevent a particular operation.
Understand the limits
Presence is not a performance benchmark or a guarantee that every feature of an API works. No high-entropy client hints are requested.
Common questions
Where is the input processed?
In this browser tab. This tool does not submit its input to the site server or a third-party service.
What should I keep with a result?
Record the selected options, browser and time. Review exported values before sharing them. Generated passwords, tokens and HMAC secret keys are excluded from report exports.