See the canvas fingerprint your browser produces
This test draws the same hidden text, color and geometry twice, hashes the pixels and checks whether the result stays stable. Nothing from the test is uploaded or stored.
Your canvas fingerprint result
Computed for this visitRunning the test locally in your browser…
How this signal works
Canvas fingerprinting uses the browser's drawing API. Fonts, emoji artwork, graphics libraries, the operating system and GPU can make tiny changes to the rendered pixels. A site does not need to keep the image; it can reduce those pixels to a short hash and compare that value on a later visit.
The hash is useful as one component of a broader browser fingerprint. It is not a serial number and it is not guaranteed to be unique. Many machines with the same software and hardware can produce the same result.
What this result cannot tell you
- Brave, Tor Browser and privacy extensions may block canvas readback or add noise so repeated draws differ.
- A graphics-driver, browser, font or operating-system update can change the hash.
- A stable canvas result should support a broader comparison, never identify a person by itself.
Use browser and network signals in your app
The verification API collects the broader fingerprint, binds it to the network request and returns the result to your backend.