Browser Fingerprint Checker
See exactly what websites can read from your browser — canvas hash, WebGL renderer, AudioContext signature, installed fonts, hardware, and automation markers.
What Each Test Means
All probes use standard public browser APIs. Anti-bot vendors like Cloudflare, DataDome, and PerimeterX repurpose these same APIs to identify automated traffic.
Canvas fingerprint
Draw text + emoji on hidden canvas, hash pixel output. GPU/driver/OS differences make hashes ~5.7 bits entropic alone (Mowery 2012), much higher combined.
Full fingerprinting guideWebGL renderer
gl.getParameter() exposes vendor + renderer strings. WEBGL_debug_renderer_info reveals exact GPU model. High entropy.
How browsers leak GPUAudioContext
OfflineAudioContext runs deterministic oscillator → compressor signal. Tiny float differences in audio stack produce stable per-device hash.
Audio fingerprinting explainedFont enumeration
Render text with fallback font stacks, measure width with canvas.measureText(). Differences from baseline = font installed. Reveals OS, locale, installed software.
Full detection layersAutomation markers
navigator.webdriver=true is the smoking gun. HeadlessChrome in UA, PhantomJS/Selenium globals, missing chrome.runtime, all indicate bots.
Stealth automation guideTZ + lang consistency
Anti-bots cross-check IP geolocation vs browser timezone vs language. A French IP with America/New_York timezone gets flagged. Antidetect browsers spoof all three together.
Profile isolation guideFrequently Asked Questions
How fingerprinting works, what it leaks, how antidetect browsers handle it
What does this tool actually test?
+
It exposes everything your browser leaks to any website that asks: canvas fingerprint hash, WebGL vendor + renderer + unmasked GPU info, AudioContext fingerprint, installed font list, screen + window dimensions, devicePixelRatio, hardware concurrency, deviceMemory, timezone, languages, platform, User-Agent, connection type, automation/headless markers (navigator.webdriver, PhantomJS/Selenium globals, HeadlessChrome UA), and feature support (cookies, storage, PDF viewer, Do Not Track).
Is anything sent to a server?
+
No. Everything runs locally in your browser via standard W3C APIs (Canvas 2D, WebGL, OfflineAudioContext, Intl.DateTimeFormat, navigator). The page makes zero network requests for fingerprint data. View source to verify.
What is a canvas fingerprint?
+
Your browser draws text and shapes on an invisible <canvas> element, then hashes the resulting pixel data. Identical canvas inputs produce different output hashes across devices because of subtle differences in GPU, graphics driver version, OS text rendering, anti-aliasing, and font availability. Original technique from Mowery & Shacham 2012; later refined by Princeton/KU Leuven 2014 large-scale studies.
What is WebGL fingerprinting?
+
WebGL exposes GPU vendor and renderer strings via gl.getParameter() and the WEBGL_debug_renderer_info extension. This reveals your exact GPU model (e.g., 'ANGLE (NVIDIA, NVIDIA GeForce RTX 4070 ...)'). Combined with WebGL parameter values and shader behavior, it produces a highly entropic identifier.
What is AudioContext fingerprinting?
+
OfflineAudioContext runs deterministic audio signals (oscillator → DynamicsCompressor) through the Web Audio API processing graph and measures the output sample data. Tiny floating-point differences in the browser's audio stack produce a stable hash unique to your device's audio implementation.
Why does my browser show all this to websites?
+
These APIs exist for legitimate web features: WebGL for 3D rendering, AudioContext for music apps, canvas for charts, Intl for localization. Anti-bot vendors (DataDome, Cloudflare bot management, PerimeterX) repurpose them to identify automated traffic. Privacy browsers (Brave, Tor) randomize or block these APIs to defeat fingerprinting.
How do antidetect browsers spoof this?
+
Antidetect browsers (Multilogin, GoLogin, Dolphin Anty, AdsPower) override each API in the Chromium source to return spoofed values per browser profile — fake canvas hash, fake WebGL renderer, spoofed font list. Combined with a separate proxy per profile, this creates the illusion of fully independent devices. Mobile proxies are usually paired with antidetect browsers for multi-account operations.
Why does proxy choice matter if my browser fingerprint is fixed?
+
Detection runs both layers in parallel. Even with a perfect browser fingerprint, a datacenter IP gets you flagged by ASN before any JavaScript runs. Even with a mobile carrier IP, a headless fingerprint gets you flagged by behavioral analysis. You need both: mobile carrier IP at the network layer + isolated browser fingerprint at the application layer.
Complete Your Detection Stack
Fingerprint is just one layer. Pair with the right network layer.
Network Layer Matters Too
A clean browser fingerprint with a datacenter IP still gets flagged at the ASN layer. Mobile carrier IPs complete the picture. Test for $5.