Blog / How the internet works /
Browser fingerprinting explained
You clear your cookies, open a private window, and still the same shoe advert follows you around. It feels like magic, or like cheating. Usually it is neither. It is browser fingerprinting, and it works because your browser is surprisingly easy to recognise.
Browser fingerprinting means identifying a visitor by the combination of small details their browser reveals, rather than by a cookie stored on their device. No single detail is unique. Together, they often are.
The analogy: a crowd at a wedding
Imagine describing a guest at a wedding. “Wearing a blue jacket” matches fifty people. Add “left-handed”, “size 43 shoes”, “carrying a green umbrella” and “speaks with a Yoruba accent” and suddenly you are describing one person. Nobody gave their name. You just kept adding ordinary facts until the crowd shrank to one.
A fingerprint script does the same with your browser.
What gets collected
Every website your browser talks to gets some information, because it needs it to display the page properly. A script can ask for more. Typical ingredients:
- User agent: browser name, version and operating system.
- Screen details: resolution, colour depth, pixel ratio, window size.
- Language and time zone: your language settings and your clock’s zone.
- Fonts installed: the list varies a lot between machines.
- Hardware hints: number of CPU cores, approximate memory, touch support.
- Canvas and WebGL rendering: the script asks your browser to draw a hidden image. Small differences in your graphics hardware, drivers and fonts produce slightly different pixels. Hash those pixels and you have a very stable number.
- Audio processing: a similar trick using the browser’s audio engine.
- Plugins, codecs and settings: which video formats you can play, whether Do Not Track is on, and so on.
Each item is shared by thousands of people. The combination is what narrows things down. Researchers have shown for years that a large share of browsers are unique or nearly so in this sense. The EFF’s Cover Your Tracks tool (formerly Panopticlick) lets you test your own browser and see how identifiable it is.
Why clearing cookies does not help
A cookie is a label stuck on you. You can peel it off. A fingerprint is more like your handwriting. You are not carrying anything extra; the identifying part is just how you write.
That is why it survives cookie clearing, and why private windows only help a little. Private mode stops the browser saving history and cookies afterwards. It does not change your screen, fonts or graphics hardware, so the fingerprint is mostly the same.
Why it exists
Not all of it is sinister.
- Fraud prevention. Banks and shops use device signals to spot a stolen account being used from an unusual machine. If the “same” login suddenly looks like a completely different device, that is a flag.
- Bot detection. Real browsers look different from scripts pretending to be browsers.
- Advertising and analytics. This is the part people dislike: following someone across sites after they declined cookies.
The technique is the same. The intent is what differs, and from the outside you often cannot tell which one you are looking at.
What it means for you as a visitor
You cannot make yourself invisible, but you can make yourself look less unusual.
- Pick a browser that fights it. Firefox and Brave both have protections that limit or randomise some of the signals. Safari has also reduced what scripts can read. Tor Browser goes furthest by making every user look the same, at a cost to convenience.
- Avoid exotic customisation. Odd fonts, a rare browser and lots of extensions make you easier to pick out. Ironically, a few privacy extensions can make you more distinctive.
- Keep the browser updated. Updates tend to include new protections.
- Do not expect perfection. The aim is fewer trackers, not none.
What it means if you run a website
If you run a site, you probably touch this without noticing. Ad networks, chat widgets, analytics tools and “fraud protection” scripts can all fingerprint your visitors on your behalf. You are still the one who put the script on the page.
Some practical habits:
- Know what is on your pages. Look through your tag manager and your theme’s script list. If you cannot say what a script does, ask why it is there. I covered this from a speed point of view in third-party scripts, chat widgets and pixels; the privacy angle is the same list.
- Read the privacy policy of every tool you add, or at least the section on data collected.
- Be honest in your own privacy policy. If a tool uses device signals, say so. Laws such as the GDPR and the ePrivacy rules in Europe treat fingerprinting much like cookies for consent purposes, which is why consent banners matter. See cookie banners and consent mode v2 in plain English.
- Collect less. The cleanest data policy is not storing what you do not need.
It is also worth knowing that the bigger shift is already in motion. Browsers have been closing the cookie route for years, and Chrome has said it is keeping third-party cookies, as I wrote in Chrome is keeping third-party cookies: what now. When cookies get harder, other methods, fingerprinting included, become more tempting for the people who track. That is a reason for browsers to keep tightening, and for site owners to stay honest.
Myths
“Incognito makes me anonymous.” It only stops local history. Websites, your network and your internet provider still see you.
“A VPN fixes fingerprinting.” A VPN hides your IP address. It does not touch your fonts, screen or canvas output. It solves a different problem.
“Only advertisers do this.” Banks, ticket sites and security companies do it too, often for good reasons.
“It is illegal.” It depends on where you are, what data is collected and whether people consent. It is regulated, not banned across the board.
Key takeaways
- A fingerprint is built from many small, ordinary browser details that become unique together.
- It survives clearing cookies and private browsing.
- The same technique protects banks from fraud and lets advertisers follow you. Intent is the difference.
- Visitors can reduce exposure with privacy-focused browsers and fewer odd extensions.
- Site owners are responsible for the scripts they add, and for being honest about them.
FAQ
Can I test my own fingerprint?
Yes. The EFF’s Cover Your Tracks site shows how unique your browser looks and whether your tracker blocking is working. Try it in your normal browser, then in a different one, and compare.
Does a mobile phone have a fingerprint too?
Yes, though many phones of the same model look alike, which makes individual phones harder to separate. Different apps and browsers behave differently, so there is no single answer.
Should I block JavaScript to stop it?
You would stop most fingerprinting, and also break most of the modern web. For most people, a privacy-minded browser is a more realistic step.
Related reading
Open your own site’s page source this week and list every third-party script on it. If you can explain what each one does, you are ahead of most site owners. If you cannot, that is your first job.