Browser fingerprint exposure checker
See what information your browser exposes automatically — the same signals tracking scripts use to identify your device without cookies.
Results appear below automatically. All signals are read locally — nothing is sent anywhere.
Browser fingerprint signals
Detected signals
Risk rating reflects how uniquely identifying each signal is.
Scanning…
Exposure estimate
Estimated identifying information
…
Scanning…
High-risk signals
Scanning…
How the exposure score works
Each signal is assigned an approximate number of bits of identifying information based on how many distinct values it typically takes across real-world browsers. A signal with 2 possible values contributes roughly 1 bit; one with 1,024 possible values contributes roughly 10 bits. The total is a rough estimate of how unique your browser looks — not a precise measurement, since the real distribution of values varies by signal and device pool.
For reference, 33 bits of information is enough to uniquely identify one person among 8 billion. Most browsers with an active canvas and WebGL fingerprint exceed this threshold from those two signals alone.
About this tool
This tool collects the browser signals that tracking scripts and fingerprinting libraries commonly read to build a persistent identifier for your device. It checks your user agent, screen metrics, timezone, language settings, hardware concurrency, device memory, touch capability, canvas rendering signature, WebGL renderer, and a sample of installed fonts. All data collection runs locally in your browser — nothing is transmitted anywhere. The bits-of-information score is an estimate of how uniquely identifying each signal is; it is not a lookup against a real fingerprint database.
Frequently asked questions
What is browser fingerprinting?
Browser fingerprinting is a tracking technique that collects a combination of browser and device attributes — screen size, installed fonts, graphics renderer, timezone, and more — to build a unique identifier for a device without cookies. Unlike cookies, fingerprints persist across private browsing sessions, cookie clears, and browser restarts, making them harder to block and nearly impossible to detect when used by a third party.
Does this tool send my fingerprint anywhere?
No. All data collection runs in your browser using standard JavaScript APIs. Nothing is transmitted to a server. The tool reads the same signals that third-party trackers would read, then displays them locally so you can see exactly what is available.
What makes a canvas fingerprint unique?
When a browser draws text or shapes on an HTML5 canvas element, subtle differences in the graphics pipeline — GPU model, driver version, installed fonts, anti-aliasing settings, sub-pixel rendering — produce a slightly different pixel output on each device. Hashing the resulting image produces a value that is remarkably consistent for one device and remarkably different across devices, making it one of the most reliable fingerprinting signals.
Can I reduce my fingerprint exposure?
Firefox with resistFingerprinting enabled, the Tor Browser, and Brave's fingerprint randomisation mode all attempt to normalise or randomise these signals. Extensions like CanvasBlocker can spoof the canvas API specifically. No solution eliminates exposure entirely — the practical goal is to make your browser look like a larger pool of users rather than a unique individual.
Why do I see different scores in different browsers?
Each browser exposes different amounts of information. Safari restricts several APIs (device memory, hardware concurrency) and uses a simplified user agent. Brave randomises canvas and WebGL output. Firefox's resistFingerprinting mode lies about screen resolution and timezone. The score reflects how much your current browser reveals, not a fixed property of your device.