What Is My Fingerprint
Browser fingerprint (this tab)
Detecting…
Coarse environment fingerprint for this tab only. Computed locally — not stored or sent to our servers.
How to use
- Open the page — a short fingerprint ID appears at the top after local signals are hashed.
- Scroll the components table to see which browser traits contributed to the ID.
- Click Copy to save the fingerprint ID for a privacy audit or test notes.
FAQ
What is my browser fingerprint?
A browser fingerprint is a combination of traits your browser exposes — screen size, timezone, language, canvas rendering, WebGL renderer, and more — that can distinguish your browser from others. This page hashes those signals into a short ID for this tab.
Is this the same as FingerprintJS?
No. Commercial fingerprint libraries use more probes and server-side matching. This tool is educational: it shows common signals and a local SHA-256 hash — not a global tracking ID.
Will my fingerprint ID change?
Yes. Browser updates, zoom, extensions, privacy settings, and different devices all change signals. Treat the ID as a snapshot, not a permanent identity.
Do you store or upload my fingerprint?
No. Everything is computed in your browser when you open or refresh the page. We do not receive or log the ID.
Why is WebGL renderer hidden?
Firefox and some Chromium modes block WEBGL_debug_renderer_info to reduce fingerprinting. The table will show hidden (no debug extension) when that happens.
How can I reduce fingerprinting?
Use built-in privacy modes (Firefox strict, Brave shields, Safari IP hiding), limit extensions, and avoid unique font/plugin combinations. No setting makes you identical to everyone else, but it raises entropy cost for trackers.
Introduction
What Is My Fingerprint shows a short fingerprint ID derived from browser signals your tab already exposes — user agent, screen, timezone, canvas probe, WebGL renderer when available, and more — with every component listed so you understand what went into the hash.
Fingerprinting is used for fraud detection and, unfortunately, cross-site tracking. Seeing your own signals helps you judge privacy extensions, compare browsers, and debug why a site treats this session as "unique."
What goes into the ID
| Signal | Why it matters |
|---|---|
| User agent & platform | OS and browser family |
| Screen & color depth | Display geometry |
| Timezone & languages | Locale fingerprint |
| Hardware hints | cores, device memory, touch |
| Canvas / WebGL | GPU and rendering differences |
The headline ID is the first 16 hex characters of a SHA-256 hash of those values combined.
Common use cases
- Privacy education — see how identifiable a bare browser is without cookies.
- Compare browsers — open the page in Firefox vs Chrome vs Safari on the same machine.
- QA notes — attach a fingerprint ID when a site behaves differently per environment.
- Before/after extensions — refresh after installing a privacy add-on to see what changed.
Best practices
- Compare results in the same browser profile you use daily.
- Do not treat the ID as secret — it is a coarse local hash, not authentication.
- For permissions on this site, see what permissions have I granted.
- For full environment data, open device info.