Browser Fingerprint Checker
See the fingerprint every site can build from your browser — canvas, WebGL, audio, fonts and hardware — and how identifiable it makes you.
- Free
- No signup
- Runs in your browser
- Nothing uploaded
Your fingerprint
How to read your result
What the uniqueness number means
It is an estimate built from the eight scored signals, weighted by published research on how rare each value tends to be. It is not proof that you are globally unique, and it is not a measurement of our own visitors. Treat it as an order of magnitude, not a precise figure.
Why the full report is not scored
Expanding the report shows roughly 130 further readings, from codec support to permission states. They are real and sites can read all of them, but they overlap heavily with each other, so attaching bit values would double-count and inflate the total. They are shown as disclosure, not measurement.
Which signals are hard to change
User agent and language are trivially altered. Canvas, WebGL and your font set are not, because they come from real hardware and a real operating system. That is why antidetect browsers that only rewrite the user agent are detected immediately.
Why a perfect spoof backfires
Blocking every probe or returning implausible values makes you look unlike any real device, which is itself distinctive. The goal is to resemble a large population of ordinary users, not to be invisible. Being the only visitor with no canvas and forty CPU cores is worse than being ordinary.
How the fingerprint test works
Open the page
Every probe runs automatically in your browser. Nothing is uploaded and there is nothing to configure.
Read your hash and uniqueness
The combined fingerprint appears first, with a plain-language reading of how identifiable it makes you.
Find what gives you away
The entropy ranking orders your signals by how much each one narrows you down, so you can see which ones actually matter.
What this tool measures
The scored signals are below, with what each exposes and how much it narrows you down. Expanding the full report inside the tool adds around 130 further readings — media query preferences, WebGL driver limits, codec support, permission states, installed speech voices and WebRTC candidates among them.
| Field | What it means | Why it matters |
|---|---|---|
| Fingerprint hash | A digest of every signal combined. | This is the identifier a site would store instead of a cookie. |
| Uniqueness estimate | Roughly how many browsers share your combination. | Tells you whether you blend in or stand out. |
| Canvas | How your device rasterises a fixed drawing. | Varies by GPU, driver and font stack; very hard to change convincingly. |
| WebGL vendor and renderer | Your unmasked graphics hardware strings. | Often names your exact GPU, which is highly distinguishing. |
| Audio context | The result of rendering a tone through a compressor offline. | Differs by CPU architecture and audio stack, and is stable across reloads. |
| Installed fonts | Which fonts from a probe list your system can render. | The set reveals your OS, locale and installed software. |
| Screen and colour depth | Resolution, available area, depth and pixel ratio. | Unusual resolutions narrow you down quickly. |
| Device memory | Approximate RAM the browser reports. | Coarse but combines with other values to isolate you. |
| CPU cores | Logical processors reported by the browser. | Another coarse hardware signal that adds up. |
| Touch support | Maximum simultaneous touch points. | Separates phones and tablets from desktops — and catches bad spoofs. |
| Timezone | The zone your browser reports. | Compared against your IP; a mismatch is a classic proxy tell. |
| Languages | Your language preference list in order. | A locale that contradicts your IP country stands out. |
| Platform and user agent | What the browser claims to be. | Trivially spoofed, so sites weight it lightly and cross-check it. |
| Client hints | Structured Sec-CH-UA brand and platform values. | Disagreement with the user agent is a strong automation signal. |
| Do Not Track | Whether the DNT header is set. | Ironically identifying, because few people enable it. |
| Automation signals | Traces left by headless browsers and drivers. | What bot detection looks for before anything else. |
What browser fingerprinting is
Loading a page reveals more than an address. Your browser tells the site its screen size and colour depth, its timezone and language list, how much memory and how many CPU cores it has, and which fonts it can render. Ask it to draw a shape or process a tone and the result varies with your graphics driver and audio stack. None of that is stored on your device, so none of it can be cleared.
Individually these values are unremarkable. Combined, they are frequently unique, and — more importantly — stable. A site that records the combination can recognise you on your next visit without setting a cookie, which is precisely why fingerprinting became the standard fallback once cookie blocking became mainstream.
Every probe on this page runs locally. The values are computed in your browser, the hash is derived there too, and nothing about your fingerprint is transmitted to us. You can confirm it in your network tab.
Which signals actually matter
There is a large difference between signals that are declared and signals that are measured. The user agent, platform and language strings are declarations: your browser simply states them, and any extension can rewrite them in a line of code. Sites know this and weight them accordingly.
Canvas, WebGL and audio are measurements. Rendering a fixed drawing exercises your GPU, drivers, font rasteriser and anti-aliasing settings, and the resulting pixels differ subtly between machines while staying identical on the same one. WebGL often names your exact graphics card. The audio probe runs a tone through a compressor offline and reads the output, which varies by CPU and audio stack. These are the signals that survive spoofing attempts, and they are the reason changing your user agent accomplishes almost nothing.
The entropy ranking on this page orders your signals by how much each narrows the field. If you are trying to blend in, start at the top of that list; the values further down are rarely what is giving you away.
What to do if you look unique
The instinct is to block everything, and it is the wrong one. A browser that refuses canvas, reports no fonts and claims implausible hardware does not look like a private user. It looks like nothing else on the internet, which is a worse position than the one you started in. The objective is to resemble a large crowd, not to vanish.
Two approaches actually work. Tor Browser makes every user report near-identical values, at a real cost in speed and convenience. Antidetect browsers such as Evomium give each profile a coherent, plausible fingerprint and keep it consistent across sessions, which matters more than any individual value being unusual.
Whichever you choose, consistency is the whole game. A fingerprint claiming Windows while reporting macOS font metrics, or a browser timezone that contradicts the IP it arrived from, fails checks that neither value would have failed alone. Run What Is My IP alongside this page to see whether your address and your browser tell the same story.
FAQ
Fingerprinting questions
What is a browser fingerprint?
It is the combination of details your browser reveals just by loading a page: screen size, timezone, language, fonts, graphics hardware, and how your device draws and processes media. No single value identifies you, but together they form a pattern that is often unique and stays stable across visits, which lets a site recognise you without storing anything on your device.
Is my fingerprint sent to your servers?
No. Every probe on this page runs in your browser and the values are never transmitted to us. The hash is computed locally too. If the page also shows IP information, that single lookup is the only request that reaches our API, and it contains your address rather than your fingerprint.
Does incognito mode change my fingerprint?
Barely. Private windows clear cookies and history, but your screen, fonts, graphics hardware and timezone are identical, so the fingerprint is essentially the same. This is exactly why fingerprinting is used for tracking: it survives the thing most people do to stop tracking.
Does a VPN change my fingerprint?
No. A VPN changes the IP address sites see and nothing else. Your canvas, WebGL, fonts and hardware values are unchanged, so a site using fingerprinting can still recognise you across VPN servers. A timezone that does not match your new IP can even make you more conspicuous.
Why is my fingerprint unique?
Usually because of an uncommon combination rather than one exotic value. A particular GPU, a non-default screen size, an unusual font installed by some software, and a less common language setting can each be unremarkable while the combination is shared by almost nobody.
Can I change my browser fingerprint?
Partially. Antidetect browsers and hardened builds can spoof or block individual signals, and Tor Browser deliberately makes users resemble one another. The difficulty is consistency: values that contradict each other are more detectable than the original fingerprint was.
What is canvas fingerprinting?
A site draws text and shapes to an invisible canvas and reads back the pixels. Because rasterisation depends on your GPU, drivers, fonts and anti-aliasing, the output differs subtly between devices while staying identical on the same one. It is one of the most durable signals there is.
Do browser extensions make me more identifiable?
They can. Extensions that alter pages, inject elements or block requests are detectable, and an unusual set is distinguishing. Privacy extensions cut both ways: blocking a probe removes information but the act of blocking is itself a signal.
Does clearing cookies reset my fingerprint?
No. A fingerprint is derived from your device and browser configuration, not from stored data, so there is nothing to clear. Clearing cookies removes stored identifiers while leaving the fingerprint completely intact.
Is browser fingerprinting legal?
It depends on jurisdiction and purpose. Under GDPR and the ePrivacy rules, fingerprinting for tracking generally requires consent in the same way cookies do, because it accesses information on your device. Using it for fraud prevention and security is treated more permissively. Rules differ elsewhere.