Browser fingerprint test: how unique is your browser?

What a browser fingerprint is made of

Any website can read dozens of properties from your browser without asking permission. Individually they are common; combined, they are almost always unique. The live analyzer collects and hashes the following families of signals:

• Canvas fingerprint — the exact pixels produced when text and shapes are drawn differ by GPU, driver and font rasteriser.
• WebGL / GPU — unmasked vendor and renderer strings, shader precision limits, maximum texture size.
• AudioContext — floating-point output of an offline oscillator, which varies with the audio stack.
• Fonts — which typefaces are installed, measured by rendering width comparisons.
• Display — resolution, available area, colour depth, device pixel ratio, refresh-adjacent metrics.
• Client hints — platform, architecture, bitness, full browser version list.
• Locale & hardware — time zone, language list, CPU cores, device memory, touch points.

How uniqueness (entropy) is measured

Uniqueness is expressed in bits of entropy. Each bit halves the population you could be confused with: roughly 33 bits is enough to single out one person among eight billion. A stock mobile browser might sit near 15–18 bits, while a desktop with an unusual GPU, a custom window size and extra fonts can exceed 25 bits — enough to be re-identified across sites and sessions.

Why cookies, incognito and VPNs do not help

Fingerprinting reads characteristics, not storage. Clearing cookies, using a private window or switching IP with a VPN leaves canvas, WebGL, audio and font signals unchanged, which is exactly why anti-fraud systems weight them so heavily. Changing browsers helps more, but shared hardware signals (GPU string, screen, fonts, time zone) still correlate the two profiles.

How to reduce your fingerprint

• Use Tor Browser or Firefox with privacy.resistFingerprinting, which standardises canvas, screen and time-zone values.
• Keep the default window size — resized windows create rare inner-dimension values.
• Avoid installing exotic font packs and rarely used extensions that inject detectable DOM changes.
• Prefer stock browser builds; heavily customised or spoofed user agents often make you more unique because they contradict other signals.

Frequently asked questions

How do I test my browser fingerprint?

Open the live analyzer, which reads every signal a website can read — canvas, WebGL, AudioContext, fonts, screen, client hints and network — then hashes them into a stable ID with an entropy estimate.

Does clearing cookies change my fingerprint?

No. A fingerprint is derived from hardware and software characteristics, not stored data, so clearing cookies or using a fresh profile usually produces the same or a very similar hash.

Does incognito or private mode hide my fingerprint?

Private windows block storage persistence, not fingerprinting. Canvas, WebGL, audio and font signals are identical in a private window.

How can I reduce my browser fingerprint?

Use a browser with built-in randomisation or standardised values (Tor Browser, Brave shields, Firefox resistFingerprinting), keep default window sizes, avoid rare font packs, and prefer stock browser builds without unusual extensions.