What Is a Browser Fingerprint and How to Check Yours

How websites recognise a browser without cookies, what a fingerprint is made of, why incognito mode and clearing cookies do not help, and how to check what your browser gives away.

Published 4 min read
Browser fingerprint — what every website can read

You open a site in incognito mode, with no cookies and a clean history, and the site still recognises you. No account is involved: your browser describes itself in so much detail that the description is enough to tell it apart from millions of others. That set of traits is called a browser fingerprint.

What a browser fingerprint is

A fingerprint is everything a site can read from your browser and your network connection without asking. Each trait on its own is harmless: screen size, time zone, a list of fonts. Together they form a combination that is almost always unique to your device.

The key difference from cookies: a fingerprint stores nothing on your side. There is nothing to delete, because it is computed again on every visit from the way your browser, system and hardware behave.

What it is made of

Most traits fall into a few groups.

What the browser says about itself

  • User-Agent and Client Hints — browser version, operating system, device type.
  • Language and time zone — the interface languages and the time offset.
  • Screen — resolution, colour depth, pixel density, the available window area.
  • Hardware — the number of logical CPU cores and a rounded amount of memory.

How the browser draws and computes

  • Canvas — the site draws an invisible picture with text and shapes. The result differs slightly with the graphics card, driver, anti-aliasing and fonts.
  • WebGL and WebGPU — the GPU model, supported extensions and small differences in 3D rendering.
  • Audio — processing a signal through AudioContext gives tiny but stable differences.
  • Fonts — the installed fonts depend on the system, language packs and installed software such as an office suite.

What the network shows

Part of the fingerprint does not depend on JavaScript at all. The server sees how the connection is made: TCP parameters (which hint at the operating system), the TLS ciphers and extensions, the order of HTTP/2 settings. These fingerprints (TCP/IP, JA4, HTTP/2) cannot be changed in browser settings: they come from the system's network stack and the TLS library.

Why incognito mode and clearing cookies do not help

Incognito mode stops history and cookies from being kept, but it does not change your graphics card, fonts or network stack. The fingerprint in a normal window and in incognito is nearly the same. A VPN changes your IP address but not the browser fingerprint, and, as we explain in the article on the WebRTC IP leak, sometimes it does not even hide the address.

Uniqueness and consistency

Sites that fight bots and fraud look at a fingerprint from two angles.

  1. Uniqueness. How rare your combination of traits is. The rarer it is, the easier it is to recognise you next time.
  2. Consistency. Whether the traits agree with each other. A browser that calls itself Safari on a Mac but renders canvas like Windows and has Windows fonts looks suspicious: that is how spoofing usually gives itself away.

The second point matters more than it seems. Trying to hide by changing one or two values often makes a fingerprint more visible, not less: it creates contradictions that real browsers never have.

How to check your browser

  1. Open the fingerprint test. It collects browser, graphics, font and network traits and shows what a site sees.
  2. Look at the overall score and at the checks that failed: they show which traits contradict each other.
  3. Check the network separately, the IP leak test and the DNS leak test, if you use a VPN or a proxy.
  4. Save a snapshot with the Compare button and run the test again later, in another mode or profile, to see which traits change and which stay.

Can you protect yourself

You cannot remove a fingerprint entirely, but two approaches work.

  • Look like everyone else. Tor Browser tries to make all its users identical: the same window size, the same fonts, disabled APIs. The more people share a fingerprint, the less it says about each of them.
  • Add the right noise. Some browsers, Brave for example, add a little random noise to canvas and audio so the fingerprint changes from site to site. The noise has to be plausible and must not create contradictions.

What not to do is spoof single values with extensions. It almost always breaks consistency and makes the browser easier to spot.

A fingerprint is not a verdict, it is a description of your setup. Knowing what it shows makes it easier to decide what to change, and why.

Check what your browser gives away

Run the free fingerprint test: canvas, WebGL, fonts, WebRTC, TCP/IP and TLS, checked for consistency on our server.

Run the test