How browser fingerprinting actually identifies you (and how to check yours)

Cookies are easy to block. Fingerprinting is the technique that quietly replaces them — and most people have never tested how exposed they are.

What a fingerprint actually is

A browser fingerprint is a combination of attributes your browser exposes to every site: user-agent, screen resolution, timezone, installed fonts, language, and — crucially — the way your specific GPU and graphics stack render a hidden <canvas> or WebGL scene. Individually these are low-entropy. Combined, they're often unique enough to single you out of millions, with no cookie and no login.

The key idea is entropy: each attribute carries some bits of identifying information. Timezone alone is weak. Timezone + a canvas hash + your exact font list + audio-stack quirks can be more than enough to re-identify you across sessions and even across sites.

The main vectors in 2026

• Canvas / WebGL rendering — the same drawing instructions produce subtly different pixels depending on your GPU, drivers and OS. A hash of that output is one of the most stable signals.
• AudioContext — generating a waveform and reading it back leaks tiny differences in your audio stack.
• Font enumeration — the set of fonts you have installed is surprisingly personal.
• Hardware hints — navigator.hardwareConcurrency, deviceMemory, pointer/touch capabilities.

How to reduce your fingerprint

There's no perfect answer, but there are real trade-offs:

• Tor Browser makes everyone look identical by design — the strongest option, at the cost of speed and convenience.
• Firefox with privacy.resistFingerprinting (or the simpler "strict" tracking protection) normalizes many of these signals.
• Brave randomizes canvas/audio readings per session so the hash isn't stable.
• Counter-intuitively, rare extensions or an exotic setup can make you more identifiable, not less — uniqueness is the enemy.

Test yours

Before changing anything, measure it. Cover Your Tracks (EFF) and AmIUnique both show your uniqueness score and which attributes leak the most bits.

For a full 2026 technical breakdown — every vector, how detection works under the hood, and what each browser actually mitigates — I keep a deeper reference here: Browser fingerprinting: state of the art 2026.

The honest takeaway: you can't get to zero in a normal browser, but you can move from "trivially unique" to "blends into a large crowd" — and that's most of the battle.