Browser Fingerprinting
What Is Browser Fingerprinting?
Learn what makes up a browser fingerprint, how it differs from identity, and how to interpret Canvas, WebGL, font and device signals.
By BrowserCheakFrom environment signals to a fingerprint
Websites read screen size, language and browser capabilities to display content correctly. Combining these characteristics with rendering results produces a fingerprint of the current environment. It is not an identity card issued by the browser and does not require a website to first write a cookie.
What BrowserCheak measures
The fingerprint tool reads a Canvas rendering hash, WebGL parameter hash, offline audio hash, font probe results, screen information, time zone and language. Canvas renders twice within one run to check stability. Standalone tools display results locally; the report workflow has a separate submission step.
What matching or different results mean
Similar devices and configurations may produce matching signals, while an update may change the hash on the same device. Evaluating uniqueness requires a defined population and statistical method. BrowserCheak has no representative population database and does not turn hash length into a uniqueness percentage.
Make a comparison you can explain
Record your browser version, window size and network state before testing. Change one setting at a time, such as private browsing or a site permission. Observe which fields change and whether websites still work. A changed hash alone does not establish that tracking is impossible.