Canvas fingerprint
measuring…
Trackers render hidden text + shapes to a canvas, read the pixels back, and hash them. Tiny GPU/font rendering differences make every browser unique.
Deep-dive: canvas fingerprint test →Browser fingerprint test
See your browser fingerprint, then scramble it.
A free, fully client-side browser fingerprint test. Six probes run in your browser to compute your unique fingerprint hash — canvas, WebGL, audio, WebRTC, Sec-CH-UA, and User-Agent. Nothing is sent to a server. Install our free Chrome extension and re-run the test to see your fingerprint change.
Live browser fingerprint test
Each card below is a separate fingerprint surface. The composite hash at the top is what a tracker would store to re-identify you on every site you visit. Higher entropy = more unique = easier to track.
WebGL / GPU fingerprint
measuring…
WEBGL_debug_renderer_info exposes your exact GPU vendor + renderer string. ANGLE backends, Apple M-series, NVIDIA generations are all distinguishable.
Deep-dive: webgl / gpu fingerprint test →Audio fingerprint
measuring…
OfflineAudioContext + DynamicsCompressor produces a tiny floating-point sum that varies by ~12 bits across hardware. No mic permission required.
Deep-dive: audio fingerprint test →WebRTC IP leak
measuring…
STUN candidate gathering reveals your local LAN address (and sometimes public IP) regardless of VPN — to JavaScript on any page.
Deep-dive: webrtc ip leak test →Client Hints (Sec-CH-UA)
measuring…
Modern Chrome sends Sec-CH-UA, Sec-CH-UA-Platform, Sec-CH-UA-Arch on every request. The JS API exposes high-entropy versions on demand.
Deep-dive: client hints (sec-ch-ua) test →User-Agent + cross-checks
measuring…
navigator.userAgent + navigator.platform + hardwareConcurrency + deviceMemory together encode 14–18 bits even before touching graphics or audio.
Deep-dive: user-agent + cross-checks test →What is browser fingerprinting
Cookies are dead. Browser fingerprinting replaced them.
A browser fingerprint is a stable identifier built from dozens of tiny technical signals every browser exposes to JavaScript: how your GPU renders a canvas, what your audio stack produces under specific filters, the exact list of installed fonts, your screen geometry, your time zone, your CPU core count, your language preferences, and the new Client Hints HTTP headers. Combined, these surfaces typically encode 25–35 bits of entropy — more than enough to uniquely identify one browser among millions.
Unlike cookies, you can't clear a fingerprint. Incognito mode doesn't change it. A VPN doesn't hide it. The only defense is to spoof the surfaces themselves — return fake values consistently enough that the fingerprint is either non-unique or unstable from pageload to pageload.
Six surfaces this fingerprint test inspects
- Canvas fingerprint — pixel hash of rendered text
- WebGL fingerprint — unmasked GPU vendor + renderer
- Audio fingerprint — OfflineAudioContext sum
- WebRTC IP leak — local LAN address via STUN
- Client Hints inspector — Sec-CH-UA-* headers
- User-Agent inspector — UA + userAgentData mismatch
FAQ
Browser fingerprint questions
What is a browser fingerprint?
A unique identifier built from dozens of browser signals — canvas rendering, GPU, audio stack, fonts, screen size, time zone, language, User-Agent, and Client Hints. Trackers combine these into a hash that re-identifies you across websites without needing a cookie.
Is incognito mode enough to hide my browser fingerprint?
No. Incognito clears cookies and history but does not change your canvas hash, GPU string, audio fingerprint, or User-Agent. Trackers re-identify an incognito session by browser fingerprint alone within seconds.
Can a VPN hide my browser fingerprint?
A VPN hides your IP address but does not change any of the JavaScript-side fingerprint surfaces. Your canvas, WebGL, audio, and Client Hints fingerprints are identical with or without a VPN.
How do I block browser fingerprinting?
Install Browser Leaks Fingerprint Shield, a free Chrome extension that spoofs canvas, WebGL, plugins, and WebRTC by default. Free tier requires no sign-up. Re-run this browser fingerprint test before and after to verify the hash has changed.
Does this test send my fingerprint to a server?
No. All six probes run in your browser. The hash you see is computed locally and never leaves your machine. Open DevTools → Network to verify there are no fingerprint-related requests.
Block your browser fingerprint with one click.
Browser Leaks Fingerprint Shield is free, open about every spoof it applies, and works in any Chromium browser. No sign-up needed for the free tier.
Add Fingerprint Shield to Chrome — Free