Skip to content
BenchDevice

What a browser can see about your computer

The facts a web page can read, the ones it only guesses, and the ones that need an installed tool.

A web page runs inside a browser, and the browser decides what the page may know about the computer it runs on. Some facts come through plainly. Some come rounded, capped or frozen on purpose, so that pages cannot tell one person from another. Some never come at all. The system tools on this site report the first kind, say when a figure is the second kind, and name the third kind at the foot of every page.

The facts a page can read

A page gets a handful of plain numbers. The number of logical cores is one: the count the system schedules work on. The screen is another: its size in CSS pixels, its pixel ratio and its colour depth, from which the size in device pixels follows.

The browser also says who it is. Chromium browsers hand over a list of brands with a version each, and the page takes the first that isn't Chromium itself or a decoy. Other browsers say it in the user agent string, where the order of the tokens matters: on iOS every browser is built on WebKit, so the page looks for the browser's own token before Safari's. The engine comes from the same string: Gecko, Blink or WebKit.

Two more facts are real but partial. The storage line is how much the browser will let this site keep on the drive, and how much it keeps already, in GB. It is not the drive's size. The graphics line is the name the browser's WebGL layer reports, with the driver's wrapping stripped off; it names the adapter the browser is drawing with, not necessarily the only one in the machine.

The facts a page guesses

Memory looks like a fact and is not quite one. Only Chromium browsers give it, and they round it to a power of two and stop at 8 GB. A machine with more reads as "8 GB or more", and the System info page says so under the figure.

The operating system is a guess from the user agent. Windows 10 and Windows 11 send the same version there, so a page that reads only that string cannot tell them apart; Chromium browsers offer a separate platform version that can, and the page uses it. The user agent string froze its macOS version years ago, so a browser that offers nothing else shows macOS with no version rather than a wrong one. On a Mac or a PC, Safari and Firefox give no system version.

The processor's architecture and bitness are given only by Chromium browsers, and never its model name or clock speed. A page can say the machine runs 64-bit code, not which chip.

Capabilities are a guess of a different sort. The Browser capabilities page checks each WebAssembly feature by handing the browser a tiny module and asking whether it is valid, never running it. A "No" there means this browser, as set up now, refuses the feature. It may be switched off by a flag or a policy rather than missing from the hardware, and the WebGL and WebGPU limits are the ones the browser allows a page, which can be lower than what the card can do.

The facts that need an installed tool

Some things live below the browser, and no web page reads them. The processor's temperature, clock speed and fans are among them. The CPU load test can show that the work done each second falls over a run, and say that a processor slowing down to stay cool or within its power limit is the usual cause, but it cannot read the temperature that caused it. The system's own monitor, or a utility from the machine's maker, can.

The drive is another. A browser reaches only its own private storage, through its own layers, and the system keeps recent files in memory. The storage test measures that path, which is the path every web app on this computer takes, and a native benchmark measures the drive. The guide on storage speed numbers goes into the difference.

The battery is a third. Chrome and Edge give a page the level, in whole percent, and whether the battery is charging; other browsers give nothing. No browser gives the battery's health, its wear or its real capacity, which is what you need when a battery seems worn out. The system's battery report or settings page has them.

The processor's model, the memory above 8 GB, the motherboard and the drivers all sit in the same place. A driver that crashes and resets a device happens below the browser too: the connection watch sees the device disappear and come back, with the time, but not why.

What to do with this

Treat what a page shows as the browser's answer, not the computer's. Another browser on the same machine may say less, round differently or hide a figure to protect your privacy, and none of that means the machine changed.

When a figure matters, cross-check it. Open the system's own information panel for the processor model, the real memory and the drive, and compare it with what the page shows. Where you need temperatures, fan speeds, drive health or battery wear, install a tool that runs on the system, because a browser was never built to see those.

All guidesBack to the system tools