Browser & System Info
A labelled snapshot of what this browser exposes — screen, viewport, pixel ratio, and user-agent estimates.
Read-only informational snapshot
How to Test
- •Review the values with their sources: screen dimensions, viewport dimensions and device pixel ratio are three separate readings, and each row states what it is.
- •Read engine, OS and architecture as estimates parsed from the user-agent string — a spoofing extension can rewrite every one of them.
- •Press Re-read after resizing the window or changing display scaling to see the viewport and pixel ratio update.
Browser Limitations
- •This is an informational snapshot, not a diagnostic: it reports values and cannot pass or fail any hardware.
- •Browsers expose only partial device information. The panel's true physical resolution is not knowable from a web page, and memory and core counts are capped or bucketed.
Troubleshooting Tips
- •Values vary by browser privacy settings and OS scaling — that is expected, not an error.
About the Browser & System Info
The Browser & System Info takes a labelled snapshot of what this browser chooses to expose. Screen area, usable screen area, viewport size and device pixel ratio are reported as four separate readings because they are four separate facts: the viewport changes when you resize the window, and the pixel ratio describes the scaling between the two. The panel’s true physical resolution is not knowable from a web page, and this page never claims to know it.
Engine, operating system and architecture are parsed from the user-agent string, so every such row is labelled as an estimate. That string can be rewritten by a spoofing extension, and it carries genuine ambiguities this page refuses to paper over: Windows 10 and 11 send the identical token, browsers other than Safari on iOS deliberately report a desktop Safari string, and an iPad in desktop mode reports macOS — so each of those is reported as ambiguous or unidentified rather than guessed.
Tips for reading the snapshot
- Compare the raw user-agent string with the parsed rows: a disagreement is a strong hint that an extension is rewriting it.
- Treat CPU cores and device memory as coarse — browsers cap and bucket both, so a lower-than-actual number is normal.
- Press Re-read after resizing the window or changing display scaling to watch the viewport and pixel-ratio rows change.
- A genuine zero (such as 0 max touch points) is shown as a value, while an absent property reads ‘Not exposed’ — the two are never conflated.
Common questions
CPU cores or memory read ‘Not exposed’
Those APIs are absent in some browsers and partially implemented in others. Nothing is wrong — the information is simply not available to any web page in that browser.
The operating system row looks wrong
Check the caveat line beneath it. Where the user agent is genuinely ambiguous — iPadOS in desktop mode, a non-Safari iOS browser, Windows 10 versus 11 — this page says so rather than picking a confident answer.
The screen resolution looks smaller than the panel
The browser reports CSS pixels after operating-system scaling, not raw panel pixels. A 4K panel at 200% scaling legitimately reports half its dimensions, and that is the value web content actually uses.
Architecture says ARM but the machine is 64-bit (or the reverse)
An ARM token identifies the CPU family, not the instruction set, and 32-bit ARM builds exist. This page never infers AArch64 from the word ARM.
FAQ
Is this the same information websites use to track me?
Yes, these are among the surfaces used for fingerprinting — which is why browsers keep shrinking them. This page is a representative sample, not a complete one: a site can also read canvas and font metrics, storage and other APIs that this page deliberately never touches.
Does this show my device’s real specifications?
No, and it is not trying to. Core counts are capped, memory is bucketed, the user agent can be reduced or spoofed, and the physical panel resolution is not exposed at all. It is a snapshot of what the browser reveals.
Does this page test anything?
No. It reports values and deliberately produces no pass or fail verdict — an informational snapshot cannot certify hardware. Use the dedicated testers for anything you need judged.
Why does the platform string say something odd?
The legacy platform string is frozen and browser-specific: modern Chrome on Windows reports ‘Win32’ even on 64-bit systems. The estimated engine and OS rows are the more useful summary, and they are labelled as estimates.
Is any of this information sent anywhere?
No. Everything shown is read from your own browser and rendered locally; this page sends nothing.