Browser fingerprint test

See what your browser reports about its settings, screen and graphics. Inspect locally and compare two snapshots.

Take a local fingerprint snapshot

Inspect the browser signals this page can read. Collection starts only when you choose Inspect browser; the report stays in this tab.

Basic browser signalsRequired

Values may be reduced, spoofed or randomized by your browser. This snapshot does not identify a person or measure uniqueness among other visitors.

Draw a fixed local image and inspect its digest.

Read available graphics vendor, renderer and limits.

Optional local drawing sample and graphics details. No images are uploaded, and no camera, microphone or location permission is requested.

Ready. No fingerprint report has been collected.

Inspect browser signals without a tracking score

  1. Choose collection scope

    Start with ordinary browser and display values.

  2. Read named APIs

    Keep every available, blocked and missing state.

  3. Optionally inspect graphics

    Collect the fixed Canvas sample and WebGL fields locally.

  4. Compare a controlled change

    Review actual changed fields instead of a uniqueness percentage.

The snapshot and previous-snapshot comparison stay in this tab. Graphics reads are an additional opt-in choice.
On this page

Learn more about Browser fingerprint test

Run a browser fingerprint test with a clear question

This browser fingerprint test shows selected JavaScript-readable values from this page’s context. Inspect browser creates a local snapshot of browser claims, display values and preferences. Opening the page does not create a report or require an account.

Read more

Start with optional graphics off. Ordinary fields are read while graphics entries remain Not requested. A returned value is a named API observation, not an independently verified hardware fact.

Inspect again compares with the immediately preceding completed snapshot in this tab. Value and availability changes count; collection timestamps do not. Keep other conditions stable when investigating one change.

Clear removes both snapshots and resets graphics consent. Hiding the tab, leaving the tool or page-cache navigation discards them. A late result cannot restore a cleared report.

Optional graphics in the browser fingerprint test

Canvas graphics and WebGL graphics are independent optional choices. Each is off until selected; no camera, photographs or pixel upload occurs.

Canvas pixels are hashed with SHA-256 when Web Crypto is available. The digest describes this specific sample, not a universal identifier or a uniqueness measurement. Other websites’ differently rendered samples are not directly comparable.

WebGL reads standard context properties and attempts the optional debug-renderer extension. Generic, software, reduced and unavailable values remain possible. Temporary contexts are released without attempts to bypass denied reads.

Read each browser inspection observation in context

Forty-six named entries are grouped into browser, display, preferences and graphics. Available, unavailable, blocked and not-requested counts describe collection coverage, not a privacy rating.

Read more

Reported includes legitimate false, zero and empty values. Unavailable means absent, unsupported or unreadable data. Read blocked denotes a permission-related error; Not requested denotes unselected graphics.

Read blocked means the browser inspection received a permission-related API error, such as a SecurityError. It does not mean the tool has identified the extension or setting responsible. Not requested applies to the optional graphics fields when the corresponding option was off. These states remain separate in copied reports, so missing data cannot be mistaken for a reassuring result.

API source reveals the property, media query or method behind each value. Changed entries also show their earlier value or state, so the comparison remains inspectable.

Browser claims and compatibility

User-agent and platform strings are browser claims that can be reduced or overridden. MDN explains their compatibility limits. Processor and memory values can also be reduced or approximate; they are not a hardware inventory.

Display, preferences and graphics

Display dimensions use CSS pixels, with device pixel ratio separate. Screen, available area and viewport differ. Window size, zoom, operating-system scale and monitors can change these observations.

Time zone and UTC-minus-local offset are configuration observations, not physical location. Media queries expose preferences such as reduced motion and color scheme, not proof of every input device’s capabilities.

What a browser fingerprint test cannot establish

Without a representative population database, the tool cannot calculate a defensible uniqueness percentile or anonymity-set size. Matching snapshots are not proof of one person; updates and protections can change the same browser’s values.

Read more

Only selected APIs in this origin are inspected. Other origins, installed software, account cookies and network protocols remain outside coverage. W3C fingerprinting guidance describes wider techniques and mitigation limits.

Local handling and deliberate sharing

Collected values stay in component memory without a fingerprint service submission, storage write, URL parameter or tool analytics payload. Ordinary page delivery and site analytics remain separate; analytics may independently receive browser metadata.

Copy deliberately exports browser, time-zone and optional graphics details. Review them before sharing. Clipboard history, synchronization and other software have separate access and retention; Clear does not erase their copies.

There is no camera, microphone, geolocation, font enumeration, audio fingerprint or extension scan. Optional Canvas and WebGL are the documented active surfaces. Missing values stay missing without circumvention.

Browser fingerprint test questions

Does a browser fingerprint test reveal my name or exact location?

No. This browser fingerprint test reports selected browser properties and local observations. It does not query an identity directory or request GPS. A time-zone setting and language list are not precise location measurements. Other websites may combine browser observations with accounts or other data, but this tool does not perform that correlation.

Why does the browser fingerprint test show a software renderer?

A browser fingerprint test can expose the renderer used by its current graphics context. Virtual machines, remote desktops, browser flags, driver failures and browser policy can influence that choice. A software-renderer string does not prove that the underlying computer lacks a GPU. Check the browser's own graphics diagnostics when investigating a rendering or acceleration issue.

Why can the Canvas value change between runs?

The browser fingerprint test hashes one fixed pixel sample. Rendering changes, browser updates, font behavior and privacy-related randomization can affect its bytes. This tool does not distinguish those causes from one changed digest. The Canvas pixel-reading API and Web Crypto digest method are named in the result so its computation remains explicit.

Canvas pixel-reading API

Web Crypto digest method

Are privacy flags proof that websites cannot track me?

No. The browser fingerprint test reports the Global Privacy Control and legacy Do Not Track properties when available. A reported preference does not audit whether every service honors it. Do Not Track is deprecated, and support for individual preference interfaces varies. Keep an unavailable property separate from a reported false value.

Do Not Track is deprecated

Can I compare different browsers with this browser fingerprint test?

You can copy a report deliberately from each browser and compare the documented fields yourself. The browser fingerprint test's automatic comparison works only between two completed runs retained in this tab. It does not upload or merge reports across devices, and hiding or leaving the page clears its temporary comparison state.

Why did my browser fingerprint test report disappear?

Clear, a changed graphics option, a hidden tab or leaving the tool invalidates the working snapshots. This is deliberate local-state handling. If you need a record for troubleshooting, copy the browser inspection report before making that transition. Stop and late-result handling keep an abandoned collection from unexpectedly repopulating the screen.

Where can I check the browser fingerprint test method?

Read the per-field API sources, the method identifier in the copied report, and our methodology and data sources. The browser inspection uses direct browser interfaces and a versioned Canvas sample, with no external fingerprinting library or visitor-comparison dataset. Source documentation was checked on September 28, 2026. The IP tools directory separates this local inspection from tools that contact a resolver, registry or remote probe.

methodology

data sources

IP tools directory

Must I enable Canvas and WebGL to inspect ordinary signals?

No. Optional graphics collection is separate from ordinary browser-readable fields. Start with it off when those details do not answer your question. Not requested records that choice rather than pretending that the browser lacks the capability.