Every website you open can read a short list of facts about your device without asking: screen size, pixel density, rough CPU and memory figures, your graphics chip, and on some browsers your network speed and battery level. Our browser test prints that list for your own browser. Some of those numbers are deliberately vague, and a few look wrong at first glance. Here's what each one means and why.
Run the browser test and you'll get the same values any page can read with a few lines of JavaScript. None of them needs a permission prompt:
| Readout on the test | Where it comes from | What gets rounded or hidden |
|---|---|---|
| Screen resolution, viewport | screen.width / height, window.innerWidth | Nothing hidden, but it's in CSS pixels, not physical ones |
| Pixel ratio (DPR) | window.devicePixelRatio | Changes with zoom and display scaling |
| CPU cores | navigator.hardwareConcurrency | Safari reports 4 or 8 whatever the real count |
| Device memory | navigator.deviceMemory | Rounded to a power of two and capped. Chrome and Edge only |
| WebGL renderer | WEBGL_debug_renderer_info extension | Privacy settings can block it, then the test shows "Not exposed" |
| Connection | navigator.connection.effectiveType | A speed bucket, not your real network type. Chrome and Edge only |
| Battery | navigator.getBattery() | Chrome and Edge only. A desktop with no battery reads 100%, charging |
Camera, microphone and precise location are different. Those need your OK first, which is why the webcam test pops up a prompt and this test doesn't. The browser test only checks that the camera API exists. It never turns anything on.
The user agent string is the other big one. It names your browser, version and operating system, and every site gets it. The test cuts it at 140 characters.
Because browsers measure in CSS pixels, not physical ones. A high-density phone screen packs two or three physical pixels into each CSS pixel, so pages don't render at a microscopic size. Multiply the resolution by the pixel ratio to get the real panel:
| Device | Test shows | Pixel ratio | Physical pixels |
|---|---|---|---|
| iPhone 13 to 15 | 390 × 844 | 3 | 1,170 × 2,532 |
| Pixel 7 | 412 × 915 | 2.625 | 1,082 × 2,402 (the panel is 1,080 × 2,400; the ratio is rounded) |
| Windows laptop at 125% scaling | 1,536 × 864 | 1.25 | 1,920 × 1,080 |
| MacBook Pro 15-inch (Retina) | 1,440 × 900 | 2 | 2,880 × 1,800 |
| 4K monitor at 150% scaling | 2,560 × 1,440 | 1.5 | 3,840 × 2,160 |
On a computer, the ratio follows your display scaling, and in most desktop browsers it also changes when you zoom the page. If the numbers look odd, press Ctrl+0 (Cmd+0 on a Mac) to reset the zoom and run the test again.
Device memory is rounded to a power of two and clamped to a range, on purpose, so it can't be used to tell similar machines apart. MDN's compatibility data says that from Chrome 147 the reported values are 2, 4, 8, 16 and 32 GB, and that older versions reported 0.25 up to 8. So on an older Chrome, a 32 GB workstation and an 8 GB laptop both show "~8 GB". Firefox and Safari don't support the property at all, and the test shows "Not reported".
CPU cores have a similar catch. MDN says the figure can be lower than the real count. Safari goes further: its compatibility note says the value is clamped to 4 or 8 cores "to prevent device fingerprinting". If a Mac with 12 cores shows 8 in Safari, the browser is behaving as designed.
It isn't your network type. The label comes from the Network Information API, which buckets the speed your browser has recently measured into one of four groups. The thresholds come from the WICG draft spec:
| Test shows | Round-trip time (at least) | Download speed (at most) |
|---|---|---|
| SLOW-2G | 2,000 ms | 50 kbps |
| 2G | 1,400 ms | 70 kbps |
| 3G | 270 ms | 700 kbps |
| 4G | Anything faster | Anything faster |
So a home Wi-Fi connection will usually read 4G, and so will gigabit fiber, because 4G is the top bucket. A weak signal in the countryside can read 3G even when your phone shows 5G bars. The draft also says browsers may update these thresholds later. Firefox and Safari don't support the API, so the test shows "Not reported" there.
The codec chips ask the browser, one format at a time, whether it can play it. The browser answers with one of three strings. MDN describes them as empty (it can't play it), "maybe" (not enough information until playback is tried) and "probably". The test shows a green tick for either maybe or probably.
A tick means the browser expects to decode that format. It doesn't say whether your graphics chip does the work or the processor does, and that matters for battery life on long videos. AV1 is the usual example: many browsers can play it in software on hardware that has no AV1 decoder.
HEVC (H.265) is the chip most likely to be red. When we ran the test in headless Chromium, the browser gave an empty answer for HEVC and "probably" for all five other formats. Support depends on the browser, the operating system and the hardware, so the same laptop can pass in one browser and fail in another.
That's what the Battery Status spec tells browsers to report when there's no battery: fully charged and plugged in. It isn't a bug in your PC. The battery card only appears in Chrome and Edge. Firefox dropped the API in version 52 and Safari never shipped it. Our battery health guide covers how to read real wear figures, and the battery test tracks drain over time.
It names the GPU and the driver layer the browser uses for WebGL. On Windows you'll often see "ANGLE (...)", which is the translation layer Chrome and Edge use to run WebGL on top of DirectX. "SwiftShader" or "llvmpipe" means software rendering with no GPU, and 3D sites will crawl.
MDN notes this extension may be restricted by privacy settings. In Firefox, turning on privacy.resistFingerprinting disables it, and the test then shows "Not exposed".
Not by itself, but combined with the user agent, fonts and other signals, these values help build a fingerprint. That's exactly why Safari clamps cores, Chrome rounds memory, and Firefox hides more under its privacy settings. The test sends nothing anywhere, but every site you visit can read the same list. If privacy is your concern, our guide on removing location from photos deals with a much bigger leak: the GPS position inside the pictures you share.
It lists what your browser reports to every website: screen and viewport size, pixel ratio, CPU cores, rounded memory, the WebGL graphics renderer, which video codecs it can play, a few feature checks, and on Chrome or Edge the connection speed bucket and battery level.
Device memory is rounded to a power of two and capped. From Chrome 147 the values are 2, 4, 8, 16 and 32 GB; older Chrome versions stopped at 8. Firefox and Safari don't report it at all.
The connection label is a speed bucket, not your network type. Roughly anything faster than 700 kbps with a round trip under 270 ms counts as 4G, so most Wi-Fi and fiber connections read 4G.
Browsers report CSS pixels. Multiply by the pixel ratio to get physical pixels. An iPhone showing 390 by 844 at a ratio of 3 has a 1,170 by 2,532 panel.
Yes. It reads values the browser already gives every website, runs entirely on your device, and uploads nothing. It doesn't turn on your camera, microphone or location.