9314JIUsi
Utilities · Browser-local detection

Your Browser, This Very Moment, Under the Hood

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.

Privacy note: every check is displayed on this page only - view and leave, zero reporting: no requests, nothing written to localStorage, gone when you close the tab. To keep a copy, hit Copy report and take it with you.
Detecting...
Browser and operating system
USER AGENT (full string)
Reading...

Browser and engine

Screen and display

Language and locale

Capabilities and hardware

Network (NetworkInformation, optional API)

InputNone needed: the page auto-detects on load; Re-run refreshes against the current window state (after resizing, say)
OutputGrouped cards (browser/screen/locale/capabilities/network) plus the full UA string; Copy report yields plain key-value text
Key parametersNo options; about 25 detection items; UA parsing uses built-in rules (offline)
ProcessingRead and displayed entirely on this page, zero reporting: no requests, nothing in localStorage, results vanish on tab close
LimitsNo quantity limit; a single run takes milliseconds
Known limitsUA 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)

Where each field earns its keep

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 traps of UA parsing

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.

The privacy boundary, in plain words

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.

Related tools

Is anything uploaded or saved from the detection?

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.

Why does my browser show up as Chrome?

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.

Why do screen resolution and CSS viewport differ?

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.

What does the WebGL renderer tell me?

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.