Answer: Run the checks above — it instantly reports your browser, engine, OS, screen, and feature support (WebGL, WebRTC, codecs) client-side.
What your browser can do — a full capability report in one click
🔒 Everything is read locally from your browser. Nothing is uploaded or stored.
A browser test detects which features your current browser supports — WebGL, WebAssembly, WebRTC camera and microphone access, clipboard, notifications, service workers, localStorage, and more. It runs entirely on your device using feature-detection APIs, so nothing is uploaded to a server.
Unsupported usually means the browser is outdated, the feature is behind a flag, or the page is not served over HTTPS. Many sensitive APIs like camera, microphone, and geolocation only work on secure (https://) origins. Update the browser and reload the page on HTTPS before concluding the feature is missing.
Yes. WebRTC camera and microphone tests only work after you grant permission when the browser prompts you. If you accidentally blocked access, click the lock or tune icon in the address bar, reset the permission, and reload the page.
Yes — modern mobile Chrome and Safari support nearly all tested features, including WebGL and WebAssembly. Some desktop-only features like full keyboard detection behave differently on touch devices, and iOS Safari places extra restrictions on background audio and storage.
This page reads the capability APIs your browser exposes — screen geometry, hardware hints, the WebGL renderer string, media codec support and connectivity info — and turns them into a plain-English report. It's the fastest way to answer questions like "does my browser play AV1?", "how much RAM does this device report?" or "which GPU is rendering WebGL?" when troubleshooting a slow site or picking video quality.
Note that browsers deliberately round or hide some values for privacy: deviceMemory is capped and bucketed, hardwareConcurrency may report efficiency cores only on some laptops, and Firefox masks the WebGL renderer unless permitted. A missing battery card simply means the Battery API isn't available (Safari and Firefox have removed it).
The codec chips tell you which video formats a site can serve without transcoding — AV1 support means modern hardware decoding, while H.264-only devices will use more bandwidth for the same quality. A DPR above 1 means a high-density display, so UI is rendered at multiple physical pixels per CSS pixel. If WebRTC shows as unsupported, video-call sites and this suite's webcam test cannot work in that browser; enabling it is usually a flag or a more current browser version away.