See what your browser reveals about you — user agent, screen size, timezone, canvas and WebGL fingerprint, estimated fonts, and an overall uniqueness score. Useful for understanding browser tracking and testing privacy settings.
Websites can identify and track visitors without cookies by combining small pieces of information your browser exposes — screen size, timezone, installed fonts, and subtle rendering differences in canvas and WebGL. Together, these form a "fingerprint" that can be surprisingly unique to your device.
This tool shows you exactly what a website could learn from your browser in a single visit, and gives you a rough uniqueness score based on how distinctive that combination of signals is.
Step 1 — Load the page. The test runs automatically as soon as the page opens, reading your browser's available signals.
Step 2 — Review each signal. Look through the list — user agent, screen resolution, timezone, canvas hash, WebGL renderer, and detected fonts — to see what's being exposed.
Step 3 — Compare across browsers or privacy tools. Try running the test in a different browser, in incognito mode, or with a privacy extension enabled to see how the fingerprint changes.
Assuming incognito mode hides your fingerprint. Private browsing blocks cookies and history, but most of the signals shown here (screen size, fonts, canvas/WebGL) remain identical in incognito mode.
Treating the uniqueness score as exact. It's a simplified estimate for illustration — real-world fingerprinting services use much larger signal sets and historical comparison data.
Ignoring browser extensions as a factor. Installed extensions can add or remove signals (like ad blockers changing rendering behaviour), which also affects how unique your browser appears.
No. Cookies are stored data a site can read back later; fingerprinting instead reads passive signals your browser already exposes, without storing anything on your device.
You can reduce it — using privacy-focused browsers, disabling JavaScript canvas access, or using anti-fingerprinting extensions — but completely eliminating it is very difficult since some signals are needed for websites to function.
No. Everything is read and calculated locally in your browser — nothing is transmitted, logged, or stored on any server.
Small variations can occur if fonts load differently or WebGL initializes slightly differently between runs, but the core signals (screen size, timezone, user agent) should remain stable.
Understanding what your browser exposes helps you make informed choices about privacy tools, and helps developers understand how analytics and anti-fraud systems can identify unique visitors without cookies.