Browser Feature Support Detector
Detect whether your current browser supports recent web standards such as WebGPU, View Transitions and CSS :has() using real runtime feature checks rather than User-Agent sniffing.
FreeOnline Tool
Loading…
How to Use
- Detection runs automatically when the page opens — there is nothing to configure and no sample data to load, because the subject being tested is the browser you are using right now
- The top of the page shows a "supported / total" summary along with the current User-Agent string for reference
- The list below covers each feature with its name, support status (supported or not supported), a one-line explanation of what it does, and its approximate standardization date
- Open the same page in a different browser or version to compare results, or click "Re-detect" to refresh the current run immediately
Features
- Every check is real runtime detection code (such as
'gpu' in navigator,CSS.supports(...)and'popover' in HTMLElement.prototype) rather than guesswork based on the User-Agent string, so the result reflects what your browser can actually do - Covers 11 recent web standards: WebGPU, the View Transitions API, the CSS :has() selector, CSS container queries, the Popover API, native CSS nesting, the Web Locks API, WebTransport, import maps, the Document Picture-in-Picture API and CSS text-wrap: balance
- Each probe is wrapped in error handling, so an API that throws during detection is simply reported as unsupported instead of breaking the page
- Every entry carries a one-line description and an approximate standardization date (a rough reference only, since vendors ship the same standard at different times)
Use Cases
Evaluating a new feature before adoption
Before committing to a new CSS or JavaScript feature, confirm your development and testing browsers already support it instead of discovering the gap after release.
Cross-browser compatibility triage
Open the page in Chrome, Safari and Firefox to compare results and see exactly where a feature is still unavailable.
Talks and training material
When explaining new web standards to a team, demonstrate live on real machines whether the feature works, which lands better than slides alone.
Planning progressive enhancement
Use the results to decide whether features such as View Transitions or the Popover API need a fallback path or polyfill.
FAQ
Is the result accurate, or is it guessed from my browser version?
It is not guessed. Every entry calls a real runtime interface the browser provides (typeof, the in operator, CSS.supports() and so on) at the moment you load the page, so the result reflects this exact browser instance rather than anything inferred from the User-Agent string.
Why does it say unsupported when I thought this browser version supported it?
The feature may still be experimental and hidden behind a flag you have to enable manually, or the implementation may differ in detail (for example in how CSS.supports() parses the argument) so the probe does not pass. Trust the result on this page — it reflects real availability under your current default configuration.
Why is there no sample data button?
The thing being tested is the browser you opened the page in, so there is no input to prefill. Loading the page already performs a complete real detection run, which is why no sample data feature is offered.
How reliable are the standardization dates?
They are labeled as approximate on purpose, because different vendors ship the same standard at different times and some features are still evolving. Always trust the live detection result on this page over the listed date.