DeviceBenchFree device specs readout
Device info, with the rounded numbers marked
This page collects the hardware facts a web page is allowed to see — logical processors, the memory figure the browser publishes, the GPU renderer string, screen geometry, pixel ratio and touch contacts — into one sheet you can copy. Two of those are not measurements: memory arrives as a bucket that stops at 8 GiB and the processor count is capped by several browsers, so both carry a marker instead of being printed as fact. Serial numbers, drive models and installed RAM appear nowhere here because no web API returns them to any site.
- 100% free
- No signup
- CPU, RAM, GPU
- Rounded values flagged
- Copy the sheet
How to read your machine's specs from a browser
Four cards, four panels, and one marker that tells you which figures to distrust.
Start with the four cards, and note which two carry a marker
Processors, memory, pixel ratio and touch points sit across the top. The first two are marked rounded, and that marker is the point of the page: a browser publishes a thread count several vendors cap and a memory figure that is snapped to a bucket, so those two are what the platform decided to say rather than what is installed. Pixel ratio and touch points are exact.
Look up the GPU name and see whether you got a real one
The graphics panel prints the renderer string a driver reports through WEBGL_debug_renderer_info — something like ANGLE (NVIDIA GeForce RTX 4070 Direct3D11 vs_5_0 ps_5_0) on Chromium. If it instead shows a generic name, that is Safari or a hardened Firefox refusing the extension, and no browser setting on your side changes it back.
Copy the sheet before you close the tab
Copy the spec sheet writes every panel out as plain text with the capped figures still labeled capped, which matters when you paste it under a listing or into a support ticket: a buyer who reads 8 GiB without that label will argue about it. Reloading the page is enough to lose the sheet, since nothing here is stored between visits.
Technical specifications
| Logical processors | navigator.hardwareConcurrency — threads as published, counting hyper-threads and efficiency cores; Firefox under resistFingerprinting answers 2 regardless of the chip |
|---|---|
| Memory | navigator.deviceMemory, snapped to 0.25, 0.5, 1, 2, 4 or 8 GiB with 8 as a hard ceiling; Firefox and Safari do not implement it at all |
| GPU name | UNMASKED_RENDERER_WEBGL and UNMASKED_VENDOR_WEBGL from WEBGL_debug_renderer_info, released immediately afterwards so the tab does not hold a context open |
| GPU fallback | gl.RENDERER, which returns the wrapper's name rather than the chip's — WebKit WebGL on Chromium, Apple GPU on Safari |
| Screen figures | screen.width × screen.height in CSS pixels and the same pair multiplied by devicePixelRatio; both re-read on resize, on rotation and when the page is dragged to a differently scaled monitor |
| Touch contacts | navigator.maxTouchPoints — 0 on a mouse-only desktop, 5 on iPhone and iPad, 10 on most Windows touchscreens |
| Battery | Presence only: whether navigator.getBattery exists and answers. Design capacity, current capacity, wear and cycle count are exposed by no web API |
| Where the sheet lives | In this tab's memory until you press Copy or reload; nothing is written to storage and no request is made after the page loads |
Frequently asked questions
Why does this say 8 GB when my machine has 32?
Because navigator.deviceMemory is capped at 8 by the specification itself. The value is snapped to one of 0.25, 0.5, 1, 2, 4 or 8 GiB and never goes above the top bucket, so every machine with more than 8 GiB looks identical from a web page — which is exactly the intent, since precise RAM would be a strong identifier for very few people. There is no flag, permission or API that returns the true figure to a website.
Why are there fewer processors here than in Task Manager?
Three different reasons, and the card cannot tell them apart. hardwareConcurrency counts logical processors, so a chip with hyper-threading reports double its physical cores and a modern hybrid chip counts its efficiency cores too. Several browsers then cap the number, and Firefox with resistFingerprinting enabled — the mode Tor Browser ships — simply answers 2 for everyone. Treat a low number as the browser's answer, not the chip's.
Why is my graphics card called WebKit WebGL or Apple GPU?
That is the masked renderer, the placeholder a browser returns when it will not give you the real one. The true name comes from an extension called WEBGL_debug_renderer_info, added so sites could dodge specific driver bugs and now recognized as the single most identifying string a page can read: Safari answers with a generic family name, Firefox withholds it under resistFingerprinting, and Chromium still answers in full. A masked name means the browser declined, not that the driver is missing.
Can a web page read my serial number, my drive or my exact RAM?
No, and no permission prompt exists that would let it. Serial numbers, motherboard identifiers, disk models, installed RAM sticks, CPU model names and firmware versions are all outside what any web API returns — the platform deliberately exposes coarse capability figures instead, so that sites can size their workload without identifying the machine. Anything on the web claiming to read your CPU model is reading the GPU string and guessing.
The screen numbers do not match the box my monitor came in.
They match once you multiply by the pixel ratio, which is what the display panel here shows on its own line. A 4K monitor running at 150% scaling reports 2560 × 1440 CSS pixels and 3840 × 2160 device pixels, and the first pair is what a web page means by resolution. The full explanation, including what browser zoom does to both numbers, is on the screen resolution page.
Does this tell me whether I am on a laptop, a tablet or a desktop?
It reports a form factor, and it is an inference rather than a reading. The guess combines the platform token, whether a battery is exposed and whether the display reports touch contacts, which is right most of the time and wrong in the interesting cases: an iPad sends a desktop Safari user agent and gives itself away only through its five touch points, and a touchscreen all-in-one looks like a tablet on every signal that matters.
Is this sheet enough to sell a machine on?
It is a starting point, not a listing. What it gives you is the GPU name, the screen geometry and a lower bound on cores and memory, all readable without installing anything on a machine you may be about to hand over. What it cannot give you is the model number, the serial, the storage size or the battery's condition, and a buyer will ask for all four — take those from the operating system's own system information panel.
About the specs a browser publishes, and the ones it rounds
Every hardware figure on this page exists for the same reason: a site needs to size its own work. hardwareConcurrency was added so that a page could decide how many Web Workers to start, and deviceMemory so that it could serve a lighter bundle to a cheap phone. Neither was ever meant as an inventory, and it shows in how they are specified — memory is defined as a value snapped to a power of two, clamped to a maximum the specification fixes at 8 GiB, precisely so that the figure answers “is this a low-memory device?” without answering “which device is this?”. A 16 GiB laptop and a 128 GiB workstation are the same reading here, and that is the feature working.
The GPU string is the exception that proves the pattern. It came in through WEBGL_debug_renderer_info, an extension whose stated purpose was letting sites work around driver bugs, and it turned out to carry more identifying information than everything else on this page combined — a full renderer name pins a visitor to a narrow slice of hardware in one string. So it has been retreating ever since: WebKit replaced it with a generic family name, Firefox hides it whenever resistFingerprinting is on, and Chromium keeps it while routing through ANGLE, which is why a Windows machine reports its card wrapped in Direct3D version numbers. When the panel shows a masked name, nothing on your side is broken and nothing you can toggle will change it. Whether the browser is even capable of WebGL in the first place is a browser question rather than a hardware one, and is answered on the browser info page.
Where this page ends is worth stating plainly, because the queries that arrive here often want more than a browser can give. There is no route to a serial number, a motherboard identifier, a disk model, a CPU part number, an installed-RAM total or firmware versions — those live behind the operating system, and the web platform has no door to them by design. Battery condition is the sharpest example: the Battery Status API reports charge and charging state and nothing about health, so the battery health check spends most of its length explaining where wear figures actually come from. The display numbers here are a summary rather than the full treatment; the screen resolution page takes scaling, zoom and multi-monitor setups apart properly, and if the touch count on the card looks wrong, the touch screen test makes you prove it with your fingers.
What the sheet does with your machine's numbers
Every number on this page is worked out by JavaScript running in the tab you are reading it in. Nothing you type, paste or open is uploaded, logged or kept, which is also why the tools carry on working after you disconnect from the network.
Nothing on this sheet is measured by touching your hardware: each figure is a value the platform hands out on request, and the one active step this page takes is opening a throwaway WebGL context to read the renderer name and closing it again in the same function. The sheet lives in this tab and goes when you reload it.