What browser fingerprinting is
Every browser leaks small details as it loads a page: your screen resolution, timezone, installed fonts, graphics card (via canvas and WebGL rendering), CPU cores, and more. Individually these are common. Combined, they can form a near-unique signature — one that follows you across sites without any cookie, and survives clearing your history.
This test collects those signals in your browser, hashes them into an id, and estimates the entropy — a measure, in bits, of how much identifying information the combination carries. Everything happens locally; none of these signals leave your browser.
An honest limit
We can measure your signals, but we can't tell you how many other people share them without a population dataset. So we report entropy in bits rather than claiming "you are unique." More bits means more distinguishing; it is an estimate of exposure, not a verdict on your identity.
How to reduce your fingerprint
- Use a browser that resists fingerprinting — some normalize canvas, fonts, and screen values so users look alike.
- An antidetect / privacy browser goes further, presenting a deliberately generic or rotating signature.
- Avoid rare extensions and custom fonts that make your setup stand out.
Common questions
Does this prove I'm trackable?
It shows how much distinguishing information your browser exposes. High entropy makes fingerprint-based tracking easier, but actual uniqueness depends on the wider population, which no single test can measure. We report the signals, not a false certainty.
Will incognito mode hide my fingerprint?
Mostly no. Private windows stop history and cookies from persisting, but the hardware and browser signals used for fingerprinting are largely the same. That's why fingerprinting is a separate concern from cookies.
Do you send my fingerprint anywhere?
No. The signals are collected and hashed entirely in your browser and never leave it.
Related checks
Fingerprinting is cookieless tracking. These cover your network layer: