Browser Feature Detector

Instantly test your browser's support for 40+ Web APIs and get a compatibility score.

Last reviewed: June 2026
Reviewed by , software engineer - last updated June 2026

New to this tool? Click here for instructions

0/0
APIs supported
Running feature detection...

How to Use Browser Feature Detector

The detector runs as soon as the page loads. Use the filter chips to narrow the grid to supported APIs, missing APIs, security APIs, media and graphics APIs, or storage APIs. The score at the top is the number of APIs detected in this browser divided by the total set tested on the page.

Copy Report produces a plain-text summary that includes the current user agent and every probe result. Export Report downloads the same summary so you can attach it to a bug report, QA note, or compatibility ticket.

When to Use Browser Feature Detector in Real Workflows

Use this page when you need to decide whether a progressive enhancement can run in the current browser. It is especially useful for APIs that depend on secure contexts, browser settings, experimental flags, or hardware availability, such as Web Crypto, Service Workers, WebGPU, MediaDevices, Web Bluetooth, Web Serial, the Clipboard API, and File System Access.

The report is also useful when a user says a feature is unavailable but the browser name alone is not enough. Instead of relying on user-agent sniffing, you can capture the exact runtime capabilities visible to the page.

How It Works

Every probe runs locally in JavaScript. Most checks are direct property tests such as 'serviceWorker' in navigator, typeof WebSocket !== 'undefined', or window.crypto && window.crypto.subtle. A few checks create a temporary canvas or test local storage because those APIs can exist while still failing in restricted contexts.

The tool does not send browser capability results to a server. Network access is only used for the page itself, third-party consent/advertising scripts allowed by site policy, and any external documentation links you choose to open.

Tips, Edge Cases, and Limitations

Feature detection answers what this page can see right now; it does not promise that every sub-feature, permission prompt, codec, GPU adapter, or device will work in production. Some APIs appear only on HTTPS, some are blocked in iframes, and some require a user gesture or a permission grant before real use.

Use these results as guardrail input. If a required API is missing, code a fallback. If an API is present but high-risk, still handle runtime errors around the actual call.

Sources Checked

Reference guidance was checked against MDN's feature detection guide, the Web Crypto API, and the Service Worker API.

Frequently Asked Questions

The feature detection score is the number of detected APIs divided by the total APIs tested. It provides a quick overview of your browser's compatibility with various Web APIs.
Some APIs require HTTPS, permissions, hardware support, browser flags, or a top-level browsing context. Extensions and privacy settings can also hide or disable interfaces.
Feature detection involves testing the actual capability at runtime, while user agent sniffing relies on parsing the User-Agent string to identify the browser and version. Feature detection is more reliable and accurate.
WebGPU is a high-performance 3D graphics API that may be unsupported in some browsers due to lack of hardware support or specific browser settings.
Yes, you can use the Export Report button to generate a plain-text document listing every tested API, its support status, your user agent string, and your final score. This is useful when filing browser compatibility bug reports with development teams.