sums every identifying signal a browser leaks across timing · sensors · rendering · network · hardware · runs locally
what is browser entropy
browser fingerprinting works by accumulating small pieces of identifying information. each signal contributes a number of “bits of entropy” — how many times it cuts the remaining population in half. a browser that reveals its exact gpu model, canvas rendering path, audio pipeline, installed fonts, screen resolution, and network topology is uniquely identifiable even with no cookies. this tool gathers those signals and shows you the total.
gather signals
why this matters
- cookies are not required. 33+ bits of browser fingerprint identify you uniquely among 8 billion people, and none of it requires storing anything on your device.
- mitigations are partial. privacy mode changes the cookie jar but not the gpu, screen resolution, or audio pipeline. only browser isolation (e.g. torBrowser’s normalisation) truly reduces fingerprinting surface.
- iphoneandroid are different worlds. ios safari on retina hardware has a very different fingerprint than android chrome on a mid-range screen — carrier hardware fragmentation creates entropy even within a device category.
- the sum understates the real value. commercial fingerprinters use machine learning on thousands of signals, including timing jitter across 30+ api calls, which dramatically increases accuracy.