Click"Collect Fingerprint" to analyze your browser's unique characteristics.
This analysis runs entirely in your browser - no data is sent to external servers.
ℹ️ About Browser Fingerprint Viewer
Browser fingerprinting identifies or re-identifies a browser by combining observable browser, device, graphics, locale, and capability signals. Unlike a cookie, the identifier is inferred from many small characteristics, so clearing site storage does not necessarily change it. The W3C fingerprinting guidance describes this surface as the set of observable characteristics that can identify a user agent or correlate its activity.
Privacy and security use cases
- • Audit how distinctive your browser looks before logging in, testing a VPN, or changing privacy settings.
- • Compare regular, private, hardened, and Tor/Brave/Firefox profiles to see which signals are reduced or standardized.
- • Verify whether enterprise browser policies, extension sets, or managed devices expose unusual identifiers.
- • Support fraud-defense reviews by understanding which signals can help detect risky automation or account takeover attempts.
- • Teach privacy teams why silent recognition can continue even when third-party cookies are blocked.
Signals this viewer checks
- • Browser: user agent, platform, language list, cookies, Do Not Track, online status, CPU thread count.
- • Display: screen size, available size, viewport, orientation, color depth, pixel depth, device pixel ratio.
- • Graphics: canvas rendering hash, WebGL vendor, renderer, shader version, extensions, and texture limits.
- • System: timezone, locale, detected font set, plugins, storage APIs, audio context details.
- • Capabilities: selected permission states, network information, battery API availability, and WebRTC support.
Example findings
- • A common laptop resolution plus default language may be low risk until paired with rare fonts and a unique WebGL renderer.
- • A spoofed user agent can become more identifiable if the platform, touch support, fonts, and GPU still reveal the real device family.
- • Private browsing may clear local history, but it does not automatically hide screen, canvas, WebGL, timezone, or language signals.
- • A hardened profile often works by joining a larger anonymity set: many users report the same standardized values.
Limitations
- • The uniqueness score is an estimate, not a measurement against a live population of browsers.
- • Browser vendors may reduce, randomize, or permission-gate some APIs, so missing values can be a privacy feature.
- • Network identity, IP reputation, login state, cookies, and server-side behavioral signals are outside this local viewer.
- • Asynchronous APIs such as permissions or battery status may be unavailable, delayed, or intentionally restricted.
References and privacy model
MDN's fingerprinting glossary summarizes common browser, timezone, codec, font, setting, and display signals. W3C's Privacy Principles recommends visibility and data minimization for recognition mechanisms, and EFF's Cover Your Tracks explains why combined browser metrics can be harder to discard than cookies.
Ethical use matters: collect fingerprint data only for your own browser, a system you administer, or a test where users have clear notice and consent. A fingerprint can expose device details, location hints, accessibility settings, enterprise configuration, and security posture.
Privacy Notice: This page calculates the displayed fingerprint locally in your browser and does not submit the collected fingerprint to an analysis API. Treat exported JSON, screenshots, and copied values as sensitive: sharing them can reveal a stable combination of browser and device characteristics that may be usable for tracking.