About Browser Fingerprint Test
This tool shows what your browser shares with every website without asking. You use it to see headers, client hints, canvas and WebGL outputs, audio hashes, and more. The test runs entirely in your browser and does not upload any data. It lists user agent, client hints, languages, screen size, CPU threads, memory, time zone, WebGL graphics card, canvas and audio hashes, and 30 tested fonts. The page also produces a single fingerprint ID by hashing the collected values locally. Unlike services that give a uniqueness score, this tool does not compare you to other visitors because that requires a server database. If you want deeper research references, see EFF Cover Your Tracks, FingerprintJS, and the W3C fingerprinting guidance for methods and standards.
How to use it
- 1Click Run test to start the local collectors
- 2Wait while the page reads headers, canvas, WebGL, audio and fonts
- 3Review each exposed value and what it can reveal
- 4Copy the local fingerprint ID if you want to save it
Worked example
Input: Chrome on Windows, languages en-US, screen 1920x1080, 8 CPU threads, 16384 MB RAM, timezone America/New_York. Output: lists include canvas hash 4f3a2b..., audio hash 1b2c3d..., 23 of 30 fonts found, Fingerprint ID (SHA-256 style) 2b7e1f...
How it works
Shows what your browser tells every website without asking (user agent, client hints, languages, screen, CPU threads, memory, time zone, WebGL graphics card, canvas and audio hashes, 30 tested fonts) with what each one reveals, and a fingerprint ID made from themRead and hashed in the page; nothing is sentNo uniqueness score, because that needs a database of other visitorsWorks in the browser with nothing to installSource: EFF Cover Your Tracks (method and background)FingerprintJS (open source fingerprint method)W3C guidance on mitigating browser fingerprinting. Last checked 12 November 2026.
What it is good for
- Shows exactly which values your browser exposes to sites
- Runs locally in your browser; nothing is uploaded or stored externally
- Produces a single hashed fingerprint ID you can copy for testing
- No uniqueness or tracking score, because that requires comparing many visitors
- Client-side values can change with browser updates or settings, so results vary over time
Questions people ask
Does this tool send my data to a server?
No. The page reads and hashes the values locally in your browser. Nothing is uploaded or shared by default.
Will this tell me how unique my browser is?
No. This tool does not compute a uniqueness score because that needs a database of other visitors. Use services like EFF or AmIUnique for population comparisons.
Can a VPN stop this fingerprinting?
A VPN hides or changes your network IP and related network context. It does not change client-side signals like canvas, fonts, or WebGL.
Which browser gives the best protection?
Tor Browser is designed to make users look similar and offers the strongest protection. Privacy-focused builds like Brave or hardened Firefox reduce some signals but results vary.
How can I reduce my fingerprint surface?
You can use a privacy browser profile, disable unnecessary plugins, block font enumeration, or use extensions that reduce client hints. Test after each change to verify the effect.
Is fingerprinting legal?
Laws vary. In the EU and UK fingerprinting for tracking often needs a legal basis such as consent. Check guidance from your local regulator like the ICO for details.
Help keep every tool free
FreeToolr stays free because people help it grow. Share a tool you like, tell us what to build next, or support us on Ko-fi.