System Info
Everything your browser will tell you about this device — display, GPU, cores, capabilities, connection and battery — read locally and copyable in one block.
Everything on this page is read from JavaScript APIs on your own device and rendered here. Nothing is uploaded, and the page never asks for camera, microphone, screen or location access.
These come from the Network Information API. They are the browser's own coarse guess from recent traffic — rounded into buckets on purpose — not a measurement. For a real figure run the internet speed test.
These are operating-system and browser accessibility settings that change how every site renders. “The site looks wrong” is very often one of these being switched on.
How to use this page
- Nothing to start. The report fills in as the page loads. Only the refresh-rate line takes a moment — it has to time about a second of real animation frames.
- Read the four tiles first. Screen size in device pixels, pixel ratio, logical cores and measured refresh rate answer most “is this machine set up right?” questions on their own.
- Reset zoom before you screenshot it. Browser zoom is folded into the device pixel ratio, so press Ctrl+0 (⌘+0 on a Mac) first or the resolution rows will describe your zoom level instead of your monitor.
- Scan the Capabilities grid for grey dots. A missing WebGL or WebGPU almost always means hardware acceleration is switched off — not that the GPU is dead.
- Check Preferences when a site renders oddly. Forced colours, reduced motion and increased contrast all change page rendering, and people rarely remember turning them on.
- Press Copy everything as text and paste the block into your support thread. It contains no account details, but it does include your user agent, language and time zone — which is the part support actually needs.
CSS pixels, device pixels, and why your resolution looks wrong
Web pages are laid out in CSS pixels, which are a unit of apparent size, not of hardware. The bridge between them is devicePixelRatio: physical pixels ÷ CSS pixels. At 100% scaling on a normal monitor the ratio is 1 and the two match. Set Windows display scaling to 125% and a 2560×1440 panel reports 2048×1152 CSS pixels at a ratio of 1.25. A MacBook reports 1728×1117 at ratio 2 for a 3456×2234 panel.
Two consequences bite people constantly. First, browser zoom is indistinguishable from OS scaling — the browser folds both into the same number, so a page cannot tell you whether you are zoomed or scaled. Second, the “device px” figure on this page is arithmetic, not a panel reading: it is CSS pixels multiplied by the ratio. If your GPU is driving a 4K panel at 1080p, this page reports 1080p, because that is genuinely the desktop it is drawing into.
The screen rows also follow the display the window is currently on. Drag the browser to your second monitor and the numbers change — which makes this a quick way to confirm a multi-monitor setup is running each panel at the mode you think it is.
Why cores, memory and the user agent are coarse by design
Every one of these values doubles as a fingerprinting signal, so browsers have spent a decade blunting them. hardwareConcurrency is capped and rounded: Safari reports at most 8, Firefox caps it, and hardened privacy modes report 2 regardless of the silicon. That is why the label here says “logical cores the browser will admit to”.
deviceMemory exists only in Chromium and is bucketed to 0.5, 1, 2, 4 or 8 GB — a 64 GB workstation and a 16 GB laptop both report 8. It was designed so sites can downgrade themselves on weak devices, not so anyone could read your RAM.
The user agent string is the least trustworthy line on the page. Chrome froze most of it years ago, so the version and platform inside it are partly fiction; the modern equivalent is navigator.userAgentData, which deliberately includes one junk “GREASE” brand (something like Not)A;Brand) to stop sites from string-matching the list. On top of that, any extension or dev-tools override can rewrite the whole thing in a second. Use it as a hint, never as evidence.
When a missing capability is a real problem
- No WebGL, or a GPU name like SwiftShader / llvmpipe / Microsoft Basic Render Driver. That is software rendering: the CPU is drawing every pixel. Expect stutter in anything animated. Check chrome://gpu (Edge: edge://gpu, Firefox: about:support → Graphics) and re-enable hardware acceleration in browser settings. It is also normal inside VMs and remote-desktop sessions.
- localStorage says no. Storage is blocked or full — private windows, strict tracking protection and “block third-party cookies” all do this. It is the usual cause of “this site keeps logging me out” and of settings that never save.
- Refresh rate reads 60 on a 144 Hz monitor. Either Windows is running the panel at 60 Hz (Settings → System → Display → Advanced display), the window is sitting on a slower second monitor, or battery saver has capped the browser. Confirm with the dedicated refresh rate test.
- Forced colours: active. Windows High Contrast is on. It overrides site palettes by design, so a page looking monochrome or losing its buttons is expected, not a bug.
- Save-Data: on. Data Saver is enabled and well-behaved sites are deliberately serving you lower-quality images and video. Turn it off before judging image quality.
- Colour gamut reports sRGB on a P3 or HDR panel. The OS colour profile, not the browser, is what feeds that media query — HDR may be off in display settings, or the browser window is not on an HDR-capable output.
- Device memory 0.5–2 GB. Some sites automatically drop to a low-fidelity mode at these values, which can look like a broken page rather than a deliberate downgrade.
FAQ
Why does my screen resolution look wrong here?
Browsers report the screen in CSS pixels, not physical pixels. Multiply by the device pixel ratio to get the panel resolution: a 2560 by 1440 monitor at 125% Windows scaling reports 2048 by 1152 CSS pixels with a ratio of 1.25. Browser zoom folds into that same ratio, so press Ctrl+0 to reset zoom before reading it.
Why does it say 8 logical cores when my CPU has 16?
navigator.hardwareConcurrency is deliberately capped and rounded to make browser fingerprinting harder. Safari reports at most 8, Firefox caps the value, and privacy modes can push it down to 2. It is a hint for sizing worker pools, not a CPU spec sheet.
Why is my GPU shown as not exposed?
The real GPU name comes from the WEBGL_debug_renderer_info extension. Firefox and Safari withhold it, and Firefox resistFingerprinting removes it entirely. Chrome and Edge normally expose it. A missing name does not mean your GPU is broken — check the WebGL and WebGPU rows instead.
Is the refresh rate here my monitor's real refresh rate?
It is an estimate. The page times about a second of animation frames and takes the median gap, which is the rate the browser is compositing at — normally the display mode, but battery saver, a background tab, a browser frame cap or a struggling GPU can all hold it lower. No browser API can read the true display mode.
Can I use this as proof of what hardware I have?
No. Every value is what the browser chooses to report. User agent strings change with one setting, extensions and privacy modes blank or fake many fields, and browsers intentionally coarsen cores, memory and battery. Read it as what this browser reports, which is exactly what a support agent needs to debug your session.
Is any of this sent anywhere?
No. Everything is read from JavaScript APIs on your own device and rendered locally. Nothing is uploaded, no account is needed, and the page never requests camera, microphone, screen or location access. The copy button puts the report on your clipboard and nowhere else.