What is browser fingerprinting?
How websites identify you without cookies — the signals they read, why they correlate across sessions, and how consistent browser identities defeat tracking.
TL;DR
Browser fingerprinting identifies a device from the properties your browser exposes — canvas, WebGL, fonts, audio, screen, timezone and more. No cookies required. The defense is not randomness; it is consistency: every session of an identity must present the same believable device.
Browser fingerprinting is a technique websites use to recognize a device across visits without storing anything on it. Instead of a cookie, the site reads dozens of properties your browser reveals and combines them into a single, stable identifier.
Why fingerprinting works
Any one property — your timezone, say — is not unique. But combine timezone with your screen size, GPU, installed fonts, language, and the way your browser renders a hidden canvas, and the result is very often unique. Research has repeatedly shown that the combination of a handful of signals is enough to single out most browsers.
Because these signals come from your real hardware and OS, they are stable over time. That stability is exactly what trackers and anti-fraud systems rely on.
The signals that matter most
- Canvas — how your browser rasterizes text and shapes. See Canvas fingerprinting, explained.
- WebGL / GPU — your graphics vendor and renderer. See WebGL and GPU fingerprinting.
- Audio — subtle differences in how audio is processed. See Audio and font fingerprinting.
- Fonts — the exact set installed on your system.
- Network — your IP, plus WebRTC leaks that can expose your real address. See WebRTC leaks and proxy consistency.
- Environment — screen metrics, timezone, language, device memory, hardware concurrency, and client hints.
Randomizing is the wrong fix
The intuitive reaction is to randomize every signal on every visit. It backfires. A browser whose canvas hash changes on each request, or whose fonts do not match its platform, is itself an anomaly — a strong signal that something is being spoofed.
The goal is the opposite of randomness. A believable identity presents one coherent device, and presents it the same way every time. That is what real users look like.
How consistent identities defeat tracking
An antidetect browser gives each profile a fingerprint that is:
- Internally consistent — the user-agent, platform, fonts, GPU and screen all agree with one another.
- Stable across sessions — the same profile returns the same signals every launch.
- Network-aligned — timezone and locale match the proxy IP, and WebRTC does not leak the real address.
VeilBrowser controls these signals at the browser level rather than patching them with injected JavaScript, which is what keeps them consistent under scrutiny. Read the fingerprint concepts for how that works in practice.
FAQ
Try it
Create a profile with a consistent, browser-level fingerprint and see the difference. Start free or explore the documentation.