Responsive breakpoints need the viewport and DPR, timezone bugs need Intl checked, canvas jank needs the GPU identified - and that information is scattered across half a dozen console commands. This page detects on load: UA parsing, screen, language, timezone, cookies, touch, WebGL GPU, all read live and shown live.
| Input | None needed: the page auto-detects on load; Re-run refreshes against the current window state (after resizing, say) |
|---|---|
| Output | Grouped cards (browser/screen/locale/capabilities/network) plus the full UA string; Copy report yields plain key-value text |
| Key parameters | No options; about 25 detection items; UA parsing uses built-in rules (offline) |
| Processing | Read and displayed entirely on this page, zero reporting: no requests, nothing in localStorage, results vanish on tab close |
| Limits | No quantity limit; a single run takes milliseconds |
| Known limits | UA parsing is signature matching, so Chromium shells (Brave, Vivaldi, regional builds) display as Chrome; anti-fingerprinting may genericize the WebGL renderer and precise timezone; NetworkInformation is unavailable in Safari/Firefox (showing unsupported is normal) |
None of these fields exist to pad a specs list - each maps to a real troubleshooting moment: viewport and DPR decide how responsive breakpoints land on real devices; a mismatched timezone or Intl can shift order times by eight hours; the WebGL renderer is the first piece of evidence in canvas performance cases; cookie state steers login debugging.
The userAgent string is thirty years of accumulated baggage: Chrome UAs contain Safari, Edge UAs contain Chrome, and some regional builds copy Chrome wholesale. This page picks the last browser token in the string (Chrome found after Edg/ means Edge), which distinguishes the five majors - for anything else, read the full UA string yourself. For precise identification, UA-CH (User-Agent Client Hints) is the proper road.
Everything this page can read, every site you visit can read too - UA, screen, timezone are headers and JS interfaces your browser volunteers to everyone. The difference here: it is read for your eyes only and sent nowhere. The page source contains no fetch/XHR/beacon; detection data never touches localStorage; the shared site analytics log the page view only, never your device details.
No. Everything is read inside this device's browser and shown directly on the page - there is no reporting endpoint, nothing is written to localStorage, and closing the tab wipes it all. To keep a copy, use the copy-report button and take it with you.
Most Chromium-based browsers (Edge, Opera, Brave, Vivaldi and many regional builds) carry a Chrome/version token in the UA. This page matches known browser tokens in priority order (Edg before Chrome, Chrome before Safari), so Chromium-family browsers display as Chrome; check the full UA string below to confirm the actual brand.
screen.width is physical pixels while CSS layout uses logical pixels (CSS px); the two differ by the device pixel ratio DPR. A MacBook driving a 4K display at 200% scaling: physical 3840x2160, viewport about 1920x1080, DPR=2. Responsive breakpoints follow the CSS viewport, not physical resolution.
The WEBGL_debug_renderer_info extension exposes the GPU model (Apple M3, NVIDIA RTX 3060 and so on) - often the first evidence when triaging canvas performance or WebGL compatibility. Some browsers return generic values or block the extension under anti-fingerprinting; showing unavailable is normal.