What is browser fingerprinting?

Fingerprinting combines many small, individually-common browser attributes — fonts, screen size, canvas rendering quirks, timezone — into a signature that is often unique enough to track a device across sites without cookies. The more distinctive your combination, the easier you are to follow.

Is any of this data sent to a server?

No. Every signal is read with browser APIs and rendered locally on this page. Nothing is uploaded, logged, or stored, so you can inspect your own fingerprint safely.

What is a canvas hash?

The tool draws text and shapes to an off-screen canvas and hashes the resulting pixels. Tiny differences in GPU, drivers, anti-aliasing, and font rendering make this hash vary between devices, which is why it is a strong fingerprinting signal.

Why does my WebGL renderer reveal my GPU?

The WebGL debug info extension exposes the unmasked GPU vendor and renderer string (for example Apple M2 or NVIDIA GeForce). That string is highly identifying, which is why privacy browsers spoof or block it.

How do I reduce my fingerprint?

Use a browser with anti-fingerprinting protection (Tor Browser, Brave, or Firefox resistFingerprinting), keep it at default window sizes, disable unnecessary extensions, and avoid rare fonts and settings. The goal is to look like the crowd, not to hide everything.

Browser Fingerprint Preview

This preview shows the fingerprinting signals your current browser hands to any website you visit. It reads them with standard browser APIs and displays them right here — nothing is transmitted — so you can judge how identifiable you are.

How it works

Fingerprinting does not rely on a single magic value; it combines many small attributes into a composite signature. This tool collects the signals trackers most commonly use:

User-agent and platform — browser, version, and OS family.
Screen — width, height, available area, pixel ratio, and colour depth.
Timezone and language(s) — your locale, often surprisingly distinctive.
Hardware — hardwareConcurrency (CPU cores) and deviceMemory (RAM bucket).
Canvas hash — the page draws text and shapes off-screen and hashes the pixels; GPU, drivers, and font rendering make this vary per device.
WebGL renderer — the unmasked GPU vendor/renderer string via the debug extension.
Font availability — a quick count of how many of a probe list of fonts are present, measured by text-width differences.
Touch support, cookies enabled, and Do Not Track.

Each individually-common value narrows the field; together they often identify a single device.

Reading your result

The more “unusual” values you have — a rare GPU string, an oversized window, exotic fonts, a non-default language list — the more unique and trackable you are. A hardened browser deliberately reports generic, crowd-matching values and blocks the canvas and WebGL signals entirely, which is why the same page can look very different in Tor Browser or with privacy.resistFingerprinting enabled.

Notes

The canvas and font checks render briefly off-screen; this is normal and visible to no one but you.
Some browsers (Safari, Brave, Tor) intentionally spoof or randomise these values, so your real hardware may differ from what is shown — that is the protection working.
Everything here is read and displayed locally. No fingerprint is sent to Gera or anyone else.