Browser Feature Detector

Find out which modern web features work in the browser you are using right now. The detector tests image formats such as WebP and AVIF by actually decoding tiny sample images, checks graphics (WebGL, WebGL 2, WebGPU), device APIs (Web Share, clipboard, geolocation, gamepad), storage, workers, media codecs and newer CSS features, and lists each result in plain words.

Device & Browser Info Runs in your browser

Check Which Web Features Your Browser Supports

JavaScript is required. This tool runs in your browser, so please enable JavaScript to use it. The instructions below are still available.

How to Use the Feature Detector

Open the page; the checks run automatically in a second or two.
Read the summary, then scan the table grouped by category. Each row says Supported or Not supported in words.
Press Copy results to share them, or Check again after changing a browser setting.

About This Tool

Web developers deciding whether a feature needs a fallback, support staff diagnosing why a site misbehaves, and users checking whether their browser is up to date.

Input: Nothing to enter · Output: Supported / not supported list.

Features and Limitations

Features

Over 60 checks across images, graphics, media, storage, device, security and CSS.
Image formats are verified by decoding real samples, not just by browser name.
No permission prompts: device APIs are detected without being used.
Plain-text results that do not rely on colour.

Limitations

“Supported” means the API exists. A feature can still be turned off by a policy, a permission setting or missing hardware (for example WebGPU on an old graphics card).
Some APIs only exist on secure (HTTPS) pages or with specific server headers, which can make them appear unsupported on other sites.
Results are computed in your browser; nothing you enter is sent to a server.

Frequently Asked Questions

How is image format support tested?

The page creates a tiny image in each format from built-in data and asks the browser to decode it. If decoding succeeds, the format is reported as supported.

Why is SharedArrayBuffer shown as unavailable?

Browsers only enable it on pages that are cross-origin isolated (served with special COOP and COEP headers). Most websites, including this one, do not need it.

Does this ask for any permissions?

No. It only checks whether features exist; it does not request your location, camera, notifications or clipboard.

My browser is up to date but shows some features as unsupported. Why?

Not every browser implements every API. Web Bluetooth and WebUSB, for example, are only in Chromium-based browsers, and some features are behind flags.