A browser fingerprint is a collection of technical signals that can make one browser look more or less distinctive among other browsers. It is different from a cookie: a cookie stores an identifier, while fingerprinting compares characteristics your browser exposes during normal web use.
What contributes to a fingerprint
Common signals include browser version, operating system, screen size, timezone, language, available APIs, graphics information and rendering behavior. No single field automatically identifies a person. The risk comes from combining many signals.
Why a test result is not a permanent identity
Your fingerprint can change after browser updates, operating-system changes, connected displays, privacy settings or extensions. Two different people can also share many of the same values. A browser test therefore describes current observability rather than proving real-world identity.
How privacy features affect results
Modern browsers may reduce precision, standardize certain values or block some APIs. Private browsing can change storage behavior, but it does not necessarily make every device signal identical. Aggressive anti-fingerprinting extensions can also create unusual combinations that are themselves distinctive.
What to do with the result
Use fingerprint tools to understand exposed signals, not to panic about a score. Keep your browser updated, limit unnecessary extensions, review site permissions and use privacy controls that match your threat model. For most users, basic browser hygiene is more practical than constantly changing configuration.
Worked example
Example interpretation
If your fingerprint changes after a browser update or a new monitor, that does not mean the previous result was false. It shows that fingerprinting observes a changing combination of browser and device signals.
Practical checklist
Before you finish
- Treat uniqueness scores as estimates, not identity proof.
- Browser updates can legitimately change the result.
- More extensions are not always better for privacy.
- Review camera, microphone, location and notification permissions separately.
Common mistakes
What to avoid
- Treating one uniqueness score as proof that a person can be identified.
- Installing many privacy extensions without understanding how they change the browser profile.
- Assuming private browsing makes every exposed signal identical.
- Comparing results from different browsers as if they were the same environment.