Browser Feature Support Detector
Live-check which CSS properties, JavaScript APIs, and HTML elements your browser supports via CSS.supports and feature probes.
Loading tool...
What is Browser Feature Support Detector?
Browser Feature Detector scans your current browser and reports which CSS properties, JavaScript APIs, and HTML elements it supports β using the standard CSS.supports() API and live feature probes, all offline.
Key Benefits
- 55+ features checked instantly
- Same techniques as production feature-detection libraries
- Color-coded supported / not-supported results
- One-click copyable support checklist
Common Use Cases
- β’Verifying progressive enhancement fallbacks before release
- β’Debugging layout breaks on specific browsers
- β’Filling in QA browser-matrix reports
- β’Checking whether your browser is ready for modern CSS
How to Check Browser Feature Support
- Open the tool: The detector runs automatically in your browser β no setup needed.
- Review the report: Browse the CSS, JavaScript, and HTML groups to see which features are supported.
- Check the counters: Use the supported and not-supported totals to gauge how modern your browser is.
- Save the report: Copy the checklist or download the report for QA tickets and browser-matrix docs.
Key Features
- Checks 20 CSS capabilities via the standard CSS.supports() API
- Probes 32 JavaScript APIs from Clipboard to WebAssembly
- Verifies HTML elements like dialog, details, and popover
- Color-coded Supported / Not supported badges per feature
- Instant supported vs unsupported counters after each scan
- Copy or download the full report as a checklist
Frequently Asked Questions
How accurate is the detection?
CSS checks use the standard CSS.supports() API, and JavaScript/HTML checks probe for the real objects and interfaces β the same techniques production feature-detection libraries use.
Does it check my device or send data anywhere?
No. Everything runs locally in your browser and nothing is uploaded β the report reflects only the browser you are using right now.
Why does caniuse differ from this result?
caniuse shows global usage statistics across all browsers and versions, while this tool reports what the specific browser window you opened actually supports.
A feature shows supported but my code still fails β why?
Support means the API exists, not that it is bug-free. Some implementations ship partial or buggy behavior, so always test critical features on real target browsers.