Device Fingerprint
Your device fingerprint uniqueness
Estimating…
Computed locally in your browser. Uniqueness is a heuristic estimate — not from a global database.
How to use
- Open the page on the device you want to test — ID appears automatically.
- Resize the window or rotate mobile, then Refresh to see viewport changes.
- Copy the ID for privacy audits or QA notes.
FAQ
What is a device fingerprint?
Device fingerprinting combines display geometry (screen, viewport, DPR), touch capability, and hardware hints (CPU cores, device memory) to distinguish devices even when cookies are cleared.
Does this include canvas or WebGL?
No — this page hashes **hardware/display signals only**. Use [canvas fingerprint](/tools/canvas-fingerprint) and [WebGL fingerprint](/tools/webgl-fingerprint) for rendering layers.
Why did my ID change after resize?
Viewport dimensions are part of the hash. Fullscreen and window size affect the fingerprint — trackers often read innerWidth/innerHeight too.
Is device memory accurate?
navigator.deviceMemory is rounded and may be undefined in Firefox/Safari. When unknown, the table shows unknown — still a signal.
Same as What Device Am I Using?
[What device am I using](/tools/what-device-am-i-using) labels vendor/model from UA. This tool hashes **screen and hardware hints** for fingerprint education.
Uploaded to your servers?
No. All values are read from standard Web APIs in your browser locally.
Introduction
Device Fingerprint hashes display and hardware-hint signals — screen resolution, available area, orientation, viewport size, device pixel ratio, touch points, coarse pointer media query, hardware concurrency, and device memory when exposed. Trackers merge this layer with canvas, WebGL, and browser UA data to re-identify visitors.
Rotating a phone or resizing a desktop window can change viewport fields and therefore the ID — mirroring real-world tracker behavior.
Signals in this hash
| Signal | Source |
|---|---|
| Screen & avail area | window.screen |
| Orientation | Screen orientation type |
| Viewport | innerWidth × innerHeight |
| DPR | devicePixelRatio |
| Touch | maxTouchPoints, (pointer: coarse) |
| Hardware hints | hardwareConcurrency, deviceMemory |
| Device class | UA device type token |
Common use cases
- Mobile vs desktop compare — same account, two form factors, two IDs.
- Zoom / scaling audit — OS display scaling changes DPR and sometimes viewport reporting.
- Privacy mode — see which hardware hints remain in private browsing.
- Stacked review — combine with browser fingerprint for full picture.
Best practices
- Refresh after rotation on phones/tablets if testing responsive fingerprint stability.
- Pair with what is my screen resolution for live resolution detail without hashing.
- For coarse combined hash including canvas/WebGL, use what is my fingerprint.
- Device fingerprint alone is rarely unique — risk rises when sites combine layers.