Testing Tools

Device Info

Everything the browser knows about your device — OS, CPU, memory, graphics and screen.

Rate this tool
Full user agent

How to use the Device Info

  1. Open the page — every detail is read automatically.
  2. Read your device type, CPU threads, memory, graphics chip and screen.
  3. Use Copy all details to paste them into a support ticket.

About the Device Info

Everything your browser knows about the machine you are on, in one list: a best guess at the device type, operating system, browser engine, CPU thread count, device memory, graphics chip, screen and viewport size, pixel ratio, colour depth, touch points, network type, language, time zone and more. There is a copy button to grab the lot as text, which is the fastest way to answer a support request that starts with "what are your specs?"

The device guess is made from capabilities, not the user-agent string, which lies routinely — an iPad claims to be a Mac, and browsers freeze or fake the UA on purpose. Instead it looks at maxTouchPoints, whether the primary pointer is coarse, and the screen size, which are hard to fake because they describe what the hardware can actually do.

Where a value is unreliable the list says so. Device memory is Chrome-only, approximate and capped by design, so it is labelled as a rough figure. The graphics chip name comes from a WebGL debug extension that some browsers hide for privacy, and you will see that stated instead of a made-up name. Everything is read locally in your browser and nothing is uploaded. For network details see what is my IP, or the screen resolution checker for the display alone.

Frequently asked questions

How does it know what device I am on?

From capabilities rather than the user-agent string. It combines the number of touch points the hardware reports, whether the main pointer is coarse like a finger or fine like a mouse, and the screen size. That is deliberate: user-agent strings are routinely spoofed, frozen or plain wrong, while touch capability is much harder to fake.

Why does my device memory look wrong or missing?

The deviceMemory value only exists in Chromium browsers, and even there it is intentionally approximate and capped, rounded to a coarse figure so it cannot be used to fingerprint you precisely. It is labelled as approximate for that reason, and shows as not reported where the browser omits it.

Why is my graphics card hidden?

The GPU name comes from the WEBGL_debug_renderer_info extension, and some browsers block it because a specific chip name narrows down who you are. When it is blocked the tool says the browser hid it rather than guessing.

Is any of this data sent to a server?

No. Every value is read from your own browser and rendered on the page. The copy button puts the text on your clipboard so you can paste it wherever you like. Nothing leaves the device.

Why does the browser report the wrong operating system?

Operating system and engine come partly from what the browser is willing to tell a page, and that information can be frozen at an old value or deliberately reduced for privacy. Modern iPads in particular present themselves as desktop machines, which is exactly why the device guess ignores the user agent.