Introduction
Browser fingerprinting is a technique used to identify and track web users without relying on cookies or other traditional storage mechanisms. Instead, it collects information about your browser, hardware, and software configuration to create a “fingerprint” that may distinguish your browser from others in a sample. Different users can share the same fingerprint, and fingerprints can change over time.
How Browser Fingerprinting Works
When you visit a website, your browser exposes an enormous amount of information through JavaScript APIs and HTTP headers. Individually, each piece of data is common — millions of people use Chrome on Windows. But when combined, these signals create a surprisingly unique identifier.
Canvas Fingerprinting
The HTML5 Canvas API allows websites to draw graphics programmatically. Due to differences in GPU, drivers, font rendering, and anti-aliasing implementations, the same drawing instructions produce subtly different pixel output on different machines. By rendering a specific image and hashing the result, trackers can generate a stable identifier.
WebGL Fingerprinting
WebGL exposes detailed information about your GPU, including the renderer string (e.g., “ANGLE (NVIDIA GeForce RTX 4090)”), supported extensions, and maximum capabilities like texture size. This data is unique enough to narrow down your hardware configuration significantly.
Audio Fingerprinting
The Web Audio API processes audio through an AudioContext. By creating an oscillator and analyzing the output waveform, fingerprinters can detect differences caused by audio hardware and driver implementations. This technique works even when no actual sound is played.
Font Detection
By measuring the rendered width of text in different fonts, websites can determine which fonts are installed on your system. Since font collections vary by OS, language packs, and installed applications, your font list is a powerful fingerprinting signal.
Other Signals
Additional signals include screen resolution, color depth, timezone, language settings, installed plugins, and even the order that CSS media queries report features like prefers-color-scheme or prefers-reduced-motion.
How Unique Is Your Fingerprint?
EFF's 2010 Panopticlick study found at least 18.1 bits of entropy in its sample — roughly one matching fingerprint per 286,777 browsers. This historical result is not a measurement of today's browser population. Results depend on the signals collected and the people represented in the sample.
How to Reduce Your Fingerprint
- Use Tor Browser: Reduces fingerprint differences by standardizing browser behavior, limiting exposed fonts, and applying features such as letterboxing. This does not guarantee anonymity.
- Browser Extensions: Tools like CanvasBlocker can inject noise into canvas and WebGL outputs.
- Brave Browser: Includes built-in fingerprint randomization that adds noise to common signals.
- Limit Installed Fonts: Remove unnecessary fonts to reduce your font fingerprint surface.
- Disable WebGL: In privacy-sensitive contexts, disabling WebGL removes a powerful signal at the cost of some web functionality.
Test Your Fingerprint
Use Zunavek's Fingerprint Lab to inspect your browser's signals and compare their frequencies with previous site observations. The blending score summarizes individual signal frequencies; it does not measure how uniquely your complete fingerprint identifies you online. Our Full Privacy Scan also includes fingerprint analysis as part of its comprehensive audit.