Lite Tools

My Browser Info

Inspect your browser, screen and system details.

User-Agent-
Browser language-
System platform-
Screen resolution-
Viewport size-
Color depth-
Time zone-
CPU logical cores-
Device memory-
Cookies-
Network status-
Touch support-

This page only reads the standard environment values your browser already exposes and shows them locally. No IP address, geolocation or other sensitive data is included, nothing is stored or reported, and "Copy all" runs only when you click it.

How to use

  1. The page reads and lists your browser and device environment automatically: no input needed.
  2. After resizing the window or switching networks, click "Refresh" to update the viewport size and online status.
  3. For bug reports or compatibility issues, click "Copy all" to place every value on your clipboard in one go.
  4. Everything is generated and displayed locally; nothing remains after you close the page.

FAQ

Does this leak my privacy?
The page only reads the standard environment fields a browser hands to every website (UA, screen size, time zone…). It never touches your IP, precise location or browsing history, sets no cookies, and sends nothing to any server.
Why do "Device memory" or "System platform" show "Not available"?
deviceMemory and userAgentData.platform are currently supported mainly by Chromium-based browsers, and some browsers deliberately fuzz or omit these fields for privacy. The page then falls back to navigator.platform or marks the value as not available.
What do all the parts of the User-Agent mean?
A UA string typically lists the browser name and version, the rendering engine, and the operating system and version. To reduce fingerprinting, modern browsers are gradually freezing and simplifying it, so seeing fewer fields than before is normal.
What is the difference between screen resolution and viewport size?
Screen resolution is the pixel size of your display, while the viewport is the area a web page can actually use inside the browser window. It changes with window resizing and open developer tools, so it is usually smaller than the screen resolution.

How to use

  1. Read the automatic report

    The page lists twelve environment fields the moment it loads. They include user agent, language, platform, screen, viewport, time zone and CPU cores. No input needed.

  2. Refresh after changes

    Resize the window or switch networks, then press Refresh to update values that move, such as viewport size and online status.

  3. Copy all for bug reports

    Click Copy all to place every value on the clipboard in one go. The result is ready to paste into a bug report or a support ticket.

  4. Diagnose environment issues

    Use the report to confirm language and time zone expectations. Or send developers the exact UA and viewport behind a rendering problem.

About this tool

My Browser Info surfaces the standard environment values every website can already read. The list covers User-Agent, browser language, platform, screen resolution, viewport size and color depth. It also covers time zone, CPU logical cores, device memory, cookie support, network status and touch support. These fields are public by design, so the page adds nothing new. It never touches your IP address, precise location or browsing history. It sets no cookies and sends nothing to any server.

It is the fastest way to attach a complete environment snapshot to a bug report. It also explains why a feature works on one device but not another. And it verifies that a spoofed user agent and time zone actually took effect. Teachers and newcomers can use it to see what the navigator object exposes. Since the viewport changes as you resize the window, the page doubles as a quick responsive-layout probe.

How it works

The twelve fields come from different layers. User agent, language and platform come from navigator; screen size and color depth come from screen; viewport comes from the window dimensions. Time zone comes from the Intl API, and cores and memory come from hardwareConcurrency and deviceMemory. Reading in layers makes the credibility cross-checkable. A UA string is trivial to spoof, but Intl time zones and hardware values come from the operating system and are hard to fake in-browser. Disagreements between layers expose naive tampering.

The list is being deliberately thinned. To fight fingerprinting, browsers are freezing the UA string, rounding device memory into coarse tiers, and proposing to drop combinable details altogether. The same machine reports different fields across browser versions. Compatibility statistics must separate an interface that was removed from one the device never had. The Not available marker for missing fields is exactly that distinction, not a defect of this page.

When to use it

  1. Attach the environment once

    When a page misrenders or a feature fails, click Copy all and paste the twelve fields into the ticket. Support stops asking which browser you use and starts fixing the real bug.

  2. Verify a spoof took hold

    Change the system time zone or the browser user agent, then reopen this page. Whether the override applied is visible at a glance, with no console or test page required.

  3. Probe responsive breakpoints live

    Drag the window and watch the viewport numbers while the layout reflows. The exact width where a media query fires becomes obvious in seconds, no code reading needed.

Tips & tricks

  • Screen resolution is the display size; the viewport is what the page actually uses. Check the viewport when debugging layout.
  • Device memory and platform fields are Chromium-only and may read Not available elsewhere; that is expected privacy behavior.
  • Modern browsers are freezing the UA string to fight fingerprinting, so shorter, simpler values than before are normal.

Things to watch

  • Date-stamp any report

    Environment snapshots drift with every browser update. Note the browser version and date next to copied values, so the numbers still match at review time.

  • Zoom changes the viewport

    System or browser zoom away from 100% shrinks or grows the viewport readings. Reset zoom before comparing viewport numbers against design breakpoints, or the widths will not line up.

  • Connectivity is an estimate

    Online status and connection type are browser inferences that lag briefly after network switches or waking from sleep. Treat them as a reference, never as final evidence.

Related Tools