Check your user agent and browser details for a bug report

Support teams ask for your browser and screen details. Get them all in one view — nothing is sent anywhere.

Tools used in this guide

The job

Filing a bug report, debugging a responsive layout, or checking whether a device reports what you expect. The user agent string alone is a paragraph of cryptic text; this page lays the pieces out with labels.

What it shows

User agent, interface languages, time zone, live viewport and screen sizes, device pixel ratio, color depth, platform, cookie/online state, CPU thread count, and device memory where the browser reports it.

  • The viewport value updates as you resize the window — useful for testing responsive breakpoints.
  • Copy button puts the full user-agent string on the clipboard for pasting into a report.

Reading the values honestly

The page reports only what the browser exposes via standard APIs. Privacy modes and some browsers mask or omit fields — deviceMemory and hardwareConcurrency show "not reported" where the browser declines to say. A user-agent string can be spoofed; treat it as a hint, not proof of the real browser.