
Browser Fingerprinting: How You're Tracked Without Cookies
Cookie blocking is the privacy advice everyone’s heard. It also solves yesterday’s tracking problem — a large and growing share of cross-site tracking today doesn’t rely on cookies at all.
The idea behind fingerprinting
Every browser, running on every specific device, exposes a combination of characteristics to any website it visits: screen resolution, installed fonts, GPU rendering quirks, timezone, language settings, browser and OS version, and dozens of smaller signals. Individually, most of these are shared by thousands of other users. Combined, the specific set of values is often close to unique — the EFF’s long-running Panopticlick/Cover Your Tracks project has repeatedly found that the majority of tested browsers had a fingerprint unique among all others tested.
Why it’s more durable than cookies
A cookie is a small file the site itself gave you — clear it or block it, and the link to your prior visit is gone. A fingerprint isn’t stored anywhere on your machine; it’s re-derived from your browser’s actual characteristics on every visit. Clearing cookies, using private/incognito mode, or even switching networks doesn’t change your device’s rendering behavior, so none of it breaks the fingerprint the way it breaks cookie-based tracking.
Canvas and WebGL fingerprinting
One especially effective technique asks your browser to render an invisible image or 3D graphic and reads back the resulting pixels. Tiny differences in GPU, drivers, and rendering pipeline produce measurably different output even for identical instructions — a signal that has nothing to do with cookies, local storage, or any conventional tracking mechanism, and one most users have no idea is even possible.
What actually helps
- Tor Browser is specifically engineered against this — its defining design goal is making every user’s browser look as close to identical as possible (identical window size via letterboxing, disabled or heavily restricted APIs that leak entropy, no canvas data returned without an explicit prompt), so fingerprinting has as little unique material to work with as possible.
- Uniformity beats customization. A heavily customized “privacy” browser with unique extensions and settings can paradoxically be easier to fingerprint than a completely default, unmodified one — because the customization itself becomes part of the unique signature. This is genuinely counterintuitive and worth sitting with.
- Disabling JavaScript removes most of the richest fingerprinting surface (canvas, WebGL, and font enumeration all typically require it), at the cost of breaking a lot of ordinary site functionality — the classic security/convenience tradeoff.
The core lesson
Fingerprinting resistance is fundamentally about blending into a large, identical-looking crowd, not about individually hardening your own unique setup — which is exactly backwards from most security intuition, where a distinctive, hardened configuration is usually the goal.