Browser Feature Checker
Which web APIs, CSS features and codecs your browser supports, with a report.
About this tool
Open the page and it tests this browser straight away. It lists support for core JavaScript APIs, graphics such as WebGL, WebGL 2 and WebGPU, device APIs like Bluetooth, USB, the clipboard and speech, modern CSS such as container queries, :has() and nesting, and video and audio codecs including AV1, HEVC and Opus. It also shows your screen, viewport, CPU threads, language, time zone and preference settings. Copy the report to attach to a bug or a support request.
How feature detection works
Version numbers are a poor guide to what a browser can do, because features ship behind flags, arrive at different times on different platforms and can be switched off by policy. Feature detection asks the browser directly. JavaScript APIs are detected by checking whether their objects exist, such as navigator.gpu for WebGPU or window.EyeDropper. CSS features are tested with CSS.supports(), which reports whether a property and value would be understood, and selector support uses CSS.supports("selector(...)"). Media codecs are tested with canPlayType(), which answers "probably", "maybe" or nothing. Graphics contexts are created on a hidden canvas. None of these checks asks for permission, so a tick next to the camera or Bluetooth means the API is present, not that a site has been allowed to use it. Developers use this to confirm a device before testing, to decide on fallbacks and to explain bugs. Honest limits: a present API can still be blocked by permissions, enterprise policy or the page's own security headers, codec answers of "maybe" aren't guarantees, and cross-origin isolation depends on how a page is served. The user agent checker shows your browser string, the screen resolution checker details your display and the keyboard tester checks input.
Frequently asked questions
Does my browser support WebGPU?
Open the tool: the Graphics section shows a tick next to WebGPU if navigator.gpu is available in this browser.
Why does a feature show as supported but not work?
The API may exist but be blocked by permissions, a policy, or the website's security headers.
Does this tool ask for camera or location access?
No. It only checks whether those APIs exist; it never requests permission.
Is my data saved?
No. Detection runs in your browser and nothing is stored or sent.