Your Browser Info

Features

• Browser: user agent, claimed brands, mobile claim, whether it is script-driven
• Language & time zone: preference list, time zone, UTC offset, the locale `Intl` resolves, format samples
• Screen & viewport: resolution, available area, viewport, device pixel ratio, colour depth, orientation
• Hardware & network: logical CPU cores, device memory, touch points, connection type and bandwidth estimates, storage usage
• Feature detection: 72 Web APIs listed item by item under eight groups (storage, network, media, graphics, input, system, clipboard & sharing, security), each marked supported or not, with the experimental ones flagged (WebGPU, View Transitions, File System Access, …)
• The HTTP protocol of this page load (h2 / h3 / http/1.1) plus a breakdown of the protocols its resources used — when it cannot be read it says “unknown” rather than guessing
• Page-load timings: TTFB, DOMContentLoaded, load, plus transfer size and the encoded/decoded body sizes — with an explanation of why a warm cache makes this group tiny
• DRM / EME probe: whether Widevine, FairPlay and PlayReady are available (and that EME only works over https / localhost)
• Privacy notes: cookies, colour-scheme preference, reduced motion, Do Not Track, WebGL vendor and renderer
• A filter box at the top: narrow by name or value so a long report still points you at the row you need (filtering affects the display only; copying takes everything)
• Copy everything at once, or export JSON
• Read and displayed entirely on your device — nothing is sent

How to use

1. Open the page — the values appear immediately (nothing to paste)
2. Resize the window or change your system theme, then press “Read again”
3. When the report is long, use the filter box at the top (type h3 or WebGPU, say)
4. Use “Copy all” or “Download JSON” to take the result away

FAQ

Does this leak my privacy?

This page does not — it sends nothing at all. Open your developer tools’ network panel and press “Read again”: no requests appear. But any other website can read exactly the same things, with no cookie, no localStorage and no consent prompt. That is the point this page makes: reading these is the default consequence of loading a web page, not something one particular site does maliciously. There are ways to reduce recognisability (a common resolution, a plain browser setup, no extensions), but eliminating it entirely is hard — which is why browser vendors keep tightening these interfaces.

Why is the WebGL renderer singled out?

Because it is the highest-information item on this page. “Chromium 141 on Windows” lumps hundreds of millions of people together, while the graphics card and driver version narrows the field a great deal — two machines on the same browser version almost always report different renderer strings, which is why it is treated as a high-entropy value in fingerprinting. It is shown rather than hidden on purpose: if this page concealed the one item that genuinely distinguishes you, readers would assume they are less identifiable than they are. The font list is deliberately not read, though — that is also high-entropy and has nothing to do with describing an environment; it exists only to identify people. This page shows what is seen; it is not a fingerprinting tool.

Do these change if I disable cookies or use private mode?

Barely. These values come from the browser’s own properties, independent of cookies, localStorage and private mode — private mode only keeps your history and cookies off the local disk; it does not alter your UA, screen, time zone or GPU. The only line that moves is “storage used” (quotas are usually smaller in private mode), and `Cookies allowed` may read no under some settings. The rest stays the same.

Why does the protocol say “unknown” and the transfer size show 0?

Both can be normal, and both are easy to misread. An “unknown” protocol does not mean an old one — the value is an empty string on a cache hit, or across origins when the other side sends no `Timing-Allow-Origin`, so the tool says “unknown” rather than guessing http/1.1. A transfer size of 0 with tiny durations likewise means the page came from cache: no bytes crossed the network this time, so it is not “an unbelievably fast network”. For real numbers, read again after a first visit or a hard reload (Ctrl+F5).