Browser / UA info
Show your browser, OS and User-Agent details.
| Browser | - |
|---|---|
| OS | - |
| Device type | - |
| Screen resolution | - |
| Viewport | - |
| Language | - |
| Time zone | - |
| Cookies | - |
Someone reports that a page looks broken and the only useful question is: broken where? Browser, version, screen size and whether cookies are on usually explain it. This page reads those values straight from your own browser and lays them out so you can copy the lot into a bug report.
How it works
What each line is reading
| Row | Where it comes from |
|---|---|
| Browser | The browser name and version parsed from the User-Agent string |
| OS | The operating system reported by the same string |
| Device type | Inferred as desktop, tablet or mobile from that string |
| Screen resolution | The full size of your display in CSS pixels |
| Viewport | The size of the visible page area inside the window |
| Language | Your browser's preferred language setting |
| Time zone | The zone your system is set to, as an IANA name such as Asia/Seoul |
| Cookies | Whether the browser currently accepts cookies |
Copy puts the whole set on your clipboard in one go.
Screen and viewport are not the same number
Screen is the whole display; viewport is the part of the page you can actually see, minus browser chrome and any open sidebar. Resize the window and the viewport changes while the screen stays put. When a layout bug depends on width, the viewport is the number worth quoting.
Why the User-Agent may not describe reality
The string is a historical mess. Nearly every browser still claims to be Mozilla, most Chromium-based browsers — Edge, Brave, Opera, Arc — identify largely as Chrome, and iPad Safari can present itself as a desktop browser. Browsers have also been trimming the detail they report to reduce fingerprinting, so minor versions and exact OS builds are increasingly rounded off. Read the result as a strong hint rather than a certificate.
When it is actually useful
Filing a bug, checking whether a site is serving you the mobile layout, confirming a time-zone or language setting before debugging a date that renders wrong, or verifying that cookies are enabled before chasing a login problem.
Terms explained
- User-Agent
- A text string your browser sends with every request, describing itself, its engine and the operating system.
- Device type
- Desktop, tablet or mobile, guessed from the User-Agent rather than measured directly.
- Screen resolution
- The dimensions of your whole display in CSS pixels, which on a high-density screen is fewer than the physical pixels.
- Viewport
- The width and height of the visible page area — the number CSS media queries respond to.
- Time zone
- Reported as an IANA identifier like Asia/Seoul or Europe/London, taken from your operating system.
- Cookies enabled
- Whether the browser is currently willing to store cookies, which many logins depend on.
Frequently asked questions
Is any of this information stored or sent somewhere?
The values are read by JavaScript running in your own browser and drawn straight onto the page — nothing here is a form you submit. For how the site as a whole handles data, see the privacy page.
Why does it say Chrome when I am using Edge or Brave?
Those browsers are built on Chromium and their User-Agent string is deliberately Chrome-like, so that sites written for Chrome do not treat them as unknown. A brand hint is sometimes included further along the string, but many detectors simply report Chrome.
The screen resolution is smaller than my monitor's specification. Is that a bug?
No. The figure is in CSS pixels, and a high-density or scaled display packs several physical pixels into each CSS pixel. A 3840-pixel-wide monitor running at 200% scaling correctly reports 1920.
Why is the time zone wrong?
It comes from your operating system's clock settings, so a VPN, a recent trip, or a machine that was set up in another region will show that zone. Changing it in system settings and reloading updates the reading.
What should I paste into a bug report?
Use the Copy button and include everything, plus what you were doing and what you expected. Browser version, viewport width and cookie status resolve a large share of "works for me" reports on their own.
Tell us what went wrong and we'll fix it fast. (Leave an email if you'd like a reply.)