System & Screen Info

What this page shows

This is a quick read-out of what your browser knows about the machine it is running on: screen resolution and pixel density, the refresh rate the browser is actually drawing at, HDR and wide-gamut support, the graphics adapter, CPU core count, memory, battery state, and the browser and operating system. It is the fastest way to answer questions like "is my 144 Hz monitor really running at 144 Hz?" or "which GPU is this laptop using right now?" without opening a settings app or installing anything.

Every value is read through standard web APIs on your device and shown only to you. Browsers intentionally blur some of them for privacy — memory is capped, GPU names can be generic, and some fields are missing in Safari or Firefox — so treat the page as a reliable summary rather than a full hardware inventory. For a deeper check of the display itself, the monitor test on this site measures refresh rate over a longer window and includes dead-pixel and gradient checks.

How this page works

Nothing here requires a download or a permission prompt. When the page loads, a small script asks the browser a series of standard questions and lays the answers out in cards. The screen card reads the screen object and the window size, so the resolution you see is in CSS pixels — the units web pages are laid out in — together with the device pixel ratio that tells you how many physical pixels sit behind each CSS pixel. Multiplying the two gives the estimated physical resolution. HDR and color gamut come from CSS media queries, the same ones websites use to decide whether to serve wide-color images, so they reflect what the browser will actually use rather than what the panel could theoretically do.

The refresh rate is not reported by any API; it has to be measured. The script requests animation frames for about a second and a half, collects the timestamp of each frame, and takes the median of the intervals between them. A median is used rather than an average because a single stalled frame — from a tab switch, a garbage-collection pause, or a busy background process — would otherwise drag the result down. The resulting figure is snapped to a common refresh rate when it is within 3 Hz, so a panel running at 143.9 Hz reads as 144 Hz.

The GPU card creates an invisible WebGL canvas and asks for the renderer and vendor strings through the debug extension, then immediately releases the context. If the browser also implements WebGPU, the page requests an adapter and shows its description when the browser is willing to share it, with a timeout so a slow or absent driver cannot hang the page. Core count, memory, battery, network type, and storage quota come straight from the navigator object; whichever of them the browser does not implement is shown as "not available" instead of breaking the page.

Some values are filled in a moment after the rest. The refresh rate takes about 1.5 seconds, and the high-entropy platform details, battery, storage estimate, and WebGPU adapter are asynchronous, so their rows update when the browser responds. The spinner at the top disappears once every request has either returned or timed out.

How to read the results

Start with the screen card. The screen resolution in CSS pixels is what websites see; on a laptop with display scaling the physical resolution row is the one that matches the panel's spec sheet. A device pixel ratio of 2 on a 1512 × 982 MacBook screen therefore gives the expected 3024 × 1964. A ratio of 1.25 or 1.5 on Windows means scaling is set to 125 % or 150 %, which is normal, but it also means the estimated physical resolution can be off by a pixel from rounding. Color depth is typically 24 bits (8 bits per channel) or 30 bits on a 10-bit pipeline; the browser reports what the OS gives it, not the panel's native bit depth.

The refresh rate row answers the most common question people bring to this page: is my high-refresh monitor actually running at its advertised rate? If the number matches the spec, the operating system, cable, and browser are all set up correctly. If you see 60 Hz on a 120, 144, or 165 Hz display, the panel is fine but something upstream is limiting it — usually the refresh-rate setting in the OS display options, a laptop power-saving mode, or an HDMI cable or port that does not support the full rate at your resolution. The HDR row only turns to "Yes" when the operating system has HDR enabled for that display, not merely when the monitor is HDR-capable.

In the GPU card, a renderer string that names a real card — a GeForce, Radeon, Iris Xe, Apple M-series, or Adreno — tells you which adapter the browser is using right now. On laptops with two GPUs this is useful: if you expected the discrete card and the row shows the integrated one, the browser is being run on the power-saving GPU. WebGL 2 and WebGPU are capability flags; a "No" for WebGPU is still common and only matters for the newest web applications. The maximum texture size is a rough tier indicator: 16384 is the usual value for modern desktop GPUs, while 4096 or 8192 suggests an older or mobile chip.

The remaining cards are mostly about the browser's own limits. Logical cores equal physical cores times threads per core, so a 6-core, 12-thread CPU reports 12. Memory is capped at 8 GB by design. Battery time estimates are the operating system's guess and can change within minutes. The network figures are coarse estimates meant for adaptive loading, not a speed test. Storage quota is the amount this site is allowed to use, which browsers derive from free disk space, so it is a hint about your drive, not a precise free-space reading.

When to use it

Checking a high-refresh setting is the everyday case. Many monitors ship at 60 Hz and have to be switched to 144 Hz or more in the OS, and the setting can reset after a driver update, a cable swap, or a change of input. Opening this page after each change confirms within two seconds that the new rate is actually in effect, which is quicker than trusting the on-screen display menu of the monitor. Gamers also use it after connecting a laptop to an external display to verify which refresh rate and resolution the external output negotiated.

Inspecting a used or refurbished machine is another good moment. Before paying for a laptop, open the page and compare the GPU name, core count, screen resolution, and battery state with the listing. A seller cannot fake the renderer string or the pixel ratio from inside the browser, and a battery that shows 100 % but reports an unusually short time remaining on a full charge is worth asking about. Pair it with the keyboard, monitor, webcam, and microphone tests on this site to cover the parts a spec sheet cannot show.

Support tickets and forum posts are easier to answer when they include exact numbers. Instead of guessing which browser version, OS, GPU, and resolution someone is on, ask them to press "Copy as text" and paste the result. The summary is short, has no personal data beyond language and time zone, and uses the same labels on every machine, so it is easy to compare across several reports. Game and software developers use the same summary to reproduce rendering issues on matching hardware.

Finally, it is a quick way to verify display features you paid for. If a monitor or laptop was sold as HDR or P3 wide gamut, the screen card shows whether the operating system has actually enabled those modes for the display the browser is on. A "No" here does not mean the panel lacks the feature — it usually means HDR is turned off in the display settings or the browser is on a different, non-HDR monitor — but it does tell you that content in the browser is not currently taking advantage of it.

Limits and what to check elsewhere

A browser is not a hardware inspector, and the gaps are intentional. Memory is rounded and capped, the GPU name can be generic, CPU model and clock speed are never exposed, and Safari and Firefox omit battery and network details entirely. These are privacy protections against fingerprinting, and no website can bypass them. If you need the exact CPU model, RAM amount, or GPU driver version, use the system information tools built into Windows, macOS, or Linux, or a dedicated hardware utility.

The refresh rate measurement depends on the browser being allowed to render at full speed. Background tabs, minimized windows, overlays, and some power-saving modes throttle animation frames, which lowers the result without any change to the monitor. Browsers on multi-monitor setups report the rate of whichever display the window is mostly on. If the number looks wrong, keep the tab in the foreground and still for a few seconds, or use the monitor test, which measures for a full five seconds and shows the raw value next to the snapped one.

Values are also read once at page load. If you plug in a charger, switch displays, or change the OS refresh-rate setting while the page is open, reload it to see the new state. The storage quota in particular is a per-site allowance derived from free disk space and the browser's own policy, so two browsers on the same machine will show different numbers, and none of them is a measurement of your disk.

Nothing on this page replaces a check of the physical hardware. A refresh rate that reads correctly does not rule out flicker or dead pixels, a GPU name does not say whether the card is throttling, and a battery percentage says nothing about its remaining capacity in watt-hours. Use this page to confirm the settings and capabilities the browser can see, and then move on to the specific test for whichever component you are worried about.