My System Info
Everything your browser will tell a web page about this device — screen, resolution, browser, operating system, processor, graphics, touch, language and time zone — on one page, with a button that copies the lot as plain text. Nothing is uploaded, and anything your browser withholds is marked as unavailable rather than guessed at.
Paste it straight into a support ticket, a forum post or a bug report.
Reading what this browser reports…
Measure the refresh rate
The one figure on this page that has to be measured rather than read. It takes five seconds of animation frames, and the result is added to the table above and to the copied text.
What this page cannot tell you
This page reports only what the browser exposes locally. It makes no network requests of any kind, so there are things people often come looking for that it genuinely cannot report, and it will not pretend otherwise:
Your IP address, internet provider and location. A web page cannot read its own visitor's IP address from JavaScript — the address is known to the server at the other end of a connection, which is why every site that shows you an IP is telling you what its server saw. Getting one here would mean calling somebody else's API and sending your request to them, and this site does not make outbound calls. Location works the same way: an approximate city comes from an IP lookup on a server, and a precise one comes from the Geolocation API, which asks your permission first and is a different thing from a system readout.
Your exact RAM, storage, model or serial number. Browsers do not expose them. deviceMemory is a deliberately coarse figure capped at 8 GB, and there is no equivalent for disks, motherboards or model names.
Whether the numbers describe a virtual machine, a VPN or a spoofed browser. Everything here is what the browser says, and any of it can be changed by an extension, a privacy setting or a developer tools override.
Why fields say “not available in this browser”
Because that is frequently the true answer, and a made-up value would be worse than none. Three of the readings above are missing for a large share of visitors, entirely by design:
Device memory exists only in Chromium-based browsers — Chrome, Edge, Opera, Brave, Samsung Internet. Safari and Firefox never implemented it. Even where it works, the figure is snapped to 0.25, 0.5, 1, 2, 4 or 8 GB and capped at 8, so a 64 GB workstation reports “8 GB or more”. That coarseness is the point: a precise memory size is one more bit of a fingerprint.
The graphics card comes from a WebGL extension named WEBGL_debug_renderer_info, which browsers increasingly restrict. Firefox masks it by default, and other browsers withhold it in private windows, in cross-origin frames, and when a page is not permitted to use it. When it is masked, the browser returns a generic string like “WebKit WebGL” — this page treats that as no answer at all rather than printing it as your graphics card.
The browser and OS version are the fields under most active change. Chrome has frozen the version in the old user agent string (which is why Chrome-based browsers report a version like 138.0.0.0, with the detail zeroed out), macOS has reported “10_15_7” in every release since Big Sur, and Windows 11 identifies itself as Windows NT 10.0 exactly as Windows 10 does. Where a browser supports User-Agent Client Hints — currently the Chromium family — this page asks for the real values through that API instead, which is how it can separate Windows 10 from Windows 11 and report a current macOS version. Where it does not, the page reports the ambiguity rather than resolving it with a guess.
How to use the copy button
Press Copy everything as text and the whole readout goes to your clipboard as plain text, grouped under headings, one field per line. It is meant to be pasted directly into a support ticket, a bug report, a forum post asking why a game stutters, or a message to whoever is helping you — the sort of place where “it doesn't work on my computer” is the opening line and the first four replies are all requests for exactly this information. Fields your browser withheld are included as “not available in this browser”, because knowing that a value could not be read is itself useful to whoever is helping. If your browser blocks clipboard access, the text appears in a box on the page instead so you can select it manually.
What the display numbers mean
Screen resolution is reported in CSS pixels, which is the figure your operating system's display settings usually show. Device pixel ratio is how many physical pixels the panel uses to draw one CSS pixel: 1 on a standard display, 2 on most Retina and HiDPI screens, and fractional values such as 1.25, 1.5 or 2.625 on scaled Windows displays and many phones. Multiply the two and you get the physical pixel count — a 1512 × 982 screen at a ratio of 2 is a 3024 × 1964 panel. On a display running at a non-native scaled resolution the multiplication is an approximation, which is why it is labelled as calculated.
Available screen area is the screen minus whatever the system reserves — a Windows taskbar, a macOS menu bar and dock — and the viewport is the part of the window this page can actually draw in, which changes as you resize the window and updates live above. If you are checking a monitor rather than a browser, the refresh rate test, dead pixel test and colour and gradient test each go deeper than a readout can.
Looking for one number in particular?
Three of the questions people arrive with have their own page, each leading with the answer in large type: what is my screen resolution, what browser am I using, and what is my user agent.
Nothing on this page is recorded, stored or transmitted. Every value is read from your own browser and rendered on your own device; the only thing that leaves it is whatever you choose to paste somewhere yourself.
