Canvas rendering
Draws a fixed image and hashes the resulting data URL. Graphics hardware, fonts, rendering engines and privacy defenses can affect the output.
Local fingerprint surface
Browser Fingerprint Check: Inspect Exposed Signals
A browser fingerprint combines multiple values that websites can read without relying only on cookies. This browser fingerprint check demonstrates selected surfaces by computing hashes for Canvas rendering, WebGL, offline audio and client rectangles, alongside screen, language and browser identity values.
The hashes are useful for showing that outputs can be read and can remain stable within a session. They do not reveal how many other people share the same value. BrowserCheck does not collect a population dataset, so it does not publish an invented ‘1 in 250,000’ uniqueness estimate.
Your fingerprint signal sample
Hashes are computed in this page. The session ID is a short display hash, not a personal identity.
- Session signal ID
- Loading...
- Canvas
- Loading...
- WebGL
- Loading...
- Offline audio
- Computing...
- Client Rects
- Computing...
- Font sample
- 0 / 19
Copied and printed output omits IP addresses, the full User Agent, exact versions, fingerprint hashes, and precise location.
Fingerprint surfaces in this check
WebGL
Reads renderer/vendor data when the browser exposes it and hashes a small set of WebGL capabilities. Values may be masked or generalized.
Offline audio
Renders a deterministic audio graph in OfflineAudioContext and hashes a slice of the output without playing audible sound.
Font and layout samples
Checks a fixed list of common font names and hashes a client-rectangle layout. The font count is only the candidate sample, not every installed font.
What fingerprint hashes tell you
Readable
A hash value means the page could read and process that surface. It does not mean the exact value is globally unique.
Masked or unavailable
A protected browser may generalize, randomize, prompt for or block a surface. Unsupported APIs and execution errors can produce the same visible outcome.
Stable within one session
Repeated values on reload can demonstrate local stability, but cross-site or long-term tracking behavior depends on browser partitioning and defenses not measured here.
Fingerprint claims this test does not make
- No representative browser population is sampled, so rarity and uniqueness are not calculated.
- The font check covers a documented candidate list rather than every system font.
- A changed hash does not by itself prove anti-fingerprinting protection; software, window and hardware changes can also alter outputs.
- A stable hash does not prove that unrelated websites can link it across storage partitions or browser profiles.
Use a fingerprint check responsibly
- 1Review which surfaces return concrete values and which are masked or unavailable.
- 2Reload once if you need to observe local stability, then avoid treating that small experiment as a population study.
- 3Prefer standardized browser privacy modes over many unusual per-setting modifications.
- 4Use Tor Browser defaults when strong fingerprint uniformity is a requirement, and follow Tor Project guidance.
Browser fingerprint FAQ
Is a Canvas hash my identity?
No. It is a hash of one rendering output. Other devices can share it, it can change, and a person can use multiple environments.
Why is the font count lower than my installed fonts?
BrowserCheck tests only a fixed list of common candidate names. Browser APIs and font fallback can further limit what a webpage can infer.
Does clearing cookies change my fingerprint?
Usually not all browser-exposed attributes. Cookie deletion removes that storage, while screen, renderer and other values may remain the same.
Put fingerprint signals in context
Use the privacy test for preference signals and the leak test for network-address comparison.