← TOOLS.MAO.MS Home简体 · 繁體

Browser Fingerprint Experimental

No cookies, no storage: dozens of signals your device gives off are enough to recognise it. Both fingerprints below are computed locally in your browser — nothing is uploaded or stored.

Device Fingerprint Cross-browser
Computing…
Built only from hardware and OS signals that do not change between browsers (GPU, screen, fonts, time zone…). On this device it should stay identical in any browser and in private mode — and be completely different on another device.
Full Fingerprint Includes browser traits
Computing…
Adds the browser’s own rendering traits (Canvas, audio, UA…) on top of the device signals. More distinctive, but it changes when you switch browsers.
FingerprintJS Open source
Computing…
The ID from the open-source FingerprintJS v5 library (MIT) — the most widely used open-source fingerprinter. If you just want a quick comparison, checking whether these four values match is enough.
ThumbmarkJS Open source
Computing…
The ID from the open-source ThumbmarkJS library (MIT), which picks signals for stability and is reported to stay consistent even in Firefox private mode.

Comparison Fingerprint · 512-bit

Skip the four values and use this instead: 32 stable components collected by this site are encoded as a 32-segment code (16 bits per segment, 512 bits total), one segment per component. The code exists purely for comparison — generate the code on another device or in another browser, paste it back, and compare segment by segment: the more segments match, the more likely it is the same device, and you can see exactly which components differ. Unlike a single hash, one differing component no longer changes everything. (All components are collected by this site: in our testing the two open-source libraries’ components were not stable enough under Firefox, so they are shown in the four values above but are not part of this code.)

Computing…

What does each of the 32 segments represent?
SegComponentSource

Signal Details

SignalValueProperty

Signals marked “Cross-browser stable” feed the device fingerprint; “Browser-specific” ones feed only the full fingerprint. That separation is the key to cross-browser matching: anything browsers render differently (Canvas, audio waveforms) is kept out of the device identity.

Try It Yourself

1) Open this page in a private / incognito window — the device fingerprint should match exactly. 2) Open it in a different browser (say, Chrome vs Firefox) — the device fingerprint should still match, while the full fingerprint changes. 3) Open it on another device — both should be completely different.

Exceptions: Firefox’s strict fingerprinting resistance, Brave and Tor Browser deliberately randomise or unify some signals, so the device fingerprint will drift there too — that is the browser protecting you. If a signal is blocked or unsupported, the table says so honestly and the rest still computes.