Why does my canvas or audio rendering reveal anything?

Graphics and audio rendering depend on your specific combination of operating system, GPU, drivers, and browser engine. Two devices running the same browser can still produce subtly different pixel or waveform output. That tiny variation is enough to act as a fingerprint, even though nothing was technically 'stored'.

Can fingerprinting track me even in private/incognito mode?

Yes. Unlike cookies, fingerprinting doesn't rely on stored data, so clearing cookies, using incognito mode, or switching VPNs typically doesn't change your fingerprint. The same hardware and browser configuration tends to produce a consistent signature across sessions.

How can I reduce my fingerprint uniqueness?

Use a browser with built-in anti-fingerprinting protections (e.g. Firefox's resist fingerprinting mode, Brave, or Tor Browser), keep your configuration close to common defaults rather than heavily customized, disable unnecessary browser extensions, and consider blocking canvas/WebGL/audio API access with a privacy extension.

← Home

Browser Fingerprint Test

See the unique signals your browser exposes - canvas, WebGL, and audio rendering quirks, installed fonts, and device details - that sites can combine into a fingerprint to track you without cookies.

What Is Browser Fingerprinting?

Browser fingerprinting collects small, often overlooked technical details about your browser and device - how it renders canvas graphics, which GPU it reports, how it processes audio, which fonts are installed, screen size, timezone, and more. Combined, these details can be unique enough to identify and re-identify your device across websites without using cookies.

Unlike cookies, fingerprinting doesn't store anything in your browser. Clearing cookies or using incognito mode typically doesn't change your fingerprint - the same hardware and browser configuration produces a consistent signature across sessions.

Signals Collected

Canvas fingerprint - unique pixel-level rendering output driven by your GPU and browser
WebGL fingerprint - GPU vendor, renderer string, and WebGL rendering hash
Audio fingerprint - how your system processes and renders audio waveforms
Installed fonts - font availability varies by OS and installed software
Screen & hardware - resolution, color depth, CPU core count, device memory
Locale & browser - timezone, language, browser type, operating system, Do Not Track status

Frequently Asked Questions

What is browser fingerprinting?: Browser fingerprinting collects small, often overlooked technical details about your browser and device - how it renders canvas graphics, which GPU it reports, how it processes audio, which fonts are installed, screen size, timezone, and more. Combined, these details can be unique enough to identify and re-identify your device across websites without using cookies.
Why does my canvas or audio rendering reveal anything?: Graphics and audio rendering depend on your specific combination of operating system, GPU, drivers, and browser engine. Two devices running the same browser can still produce subtly different pixel or waveform output. That tiny variation is enough to act as a fingerprint, even though nothing was technically stored.
Can fingerprinting track me even in private/incognito mode?: Yes. Unlike cookies, fingerprinting doesn't rely on stored data, so clearing cookies, using incognito mode, or switching VPNs typically doesn't change your fingerprint. The same hardware and browser configuration tends to produce a consistent signature across sessions.
How can I reduce my fingerprint uniqueness?: Use a browser with built-in anti-fingerprinting protections (Firefox's resist fingerprinting mode, Brave, or Tor Browser), keep your configuration close to common defaults, disable unnecessary extensions, and consider blocking canvas/WebGL/audio API access with a privacy extension.

Related Tools