What signals are anti-detect browsers unable to spoof?

Anti-detect browsers cannot spoof device-level signals beyond the browser: hardware sensor data from accelerometers and gyroscopes, app-store install context, OS-level identifiers like advertising IDs, cellular network routing characteristics, and real touch pressure curves from physical touchscreens. These gaps are invisible in browser-only workflows but become the primary detection surface for mobile-first platforms like TikTok.

How consistent does a spoofed fingerprint need to be?

The fingerprint must be internally consistent across every spoofed value. A profile set to Windows 11 with an Intel GPU must report matching user agent, screen resolution, font list, canvas hash, WebGL renderer, and audio context for that specific configuration. Random or mismatched values are themselves detection signals. Consistency is harder than it sounds, because changing one value can break the consistency of a dozen others.

What Browser Fingerprint Types Do Anti-Detect Tools Actually Spoof?

Q: What browser fingerprint signals do anti-detect tools spoof?

Anti-detect tools spoof canvas fingerprint, WebGL renderer and vendor, audio context hash, user agent string, screen resolution, timezone, language, installed font list, platform type, hardware concurrency, device memory, and touch support. Modern tools manage 30 or more attributes per profile, ensuring each one is internally consistent so that a Windows profile with an NVIDIA GPU reports matching values across every signal.

Anti-detect tools spoof approximately 30 or more browser fingerprint attributes per profile, covering canvas rendering, WebGL signature, audio context, font enumeration, user agent, screen resolution, timezone, language, and hardware concurrency. Each spoofed value is configured to be internally consistent so that the manufactured fingerprint reads as a plausible real device. But the spoofing surface is limited to what the browser exposes, and platforms that inspect device-level signals beyond the browser operate on an inspection surface the anti-detect tool cannot reach.

What Is A Browser Fingerprint?

A browser fingerprint is a composite identifier built from the specific combination of technical attributes a browser exposes to websites. The EFF Cover Your Tracks project found that 84% of browsers tested had unique fingerprints, with the average fingerprint containing at least 18.1 bits of entropy. The fingerprint is derived from data the browser must reveal to function — it cannot be blocked without breaking the browser.

The attributes that make up a fingerprint fall into categories: rendering-based (canvas, WebGL, audio), software-based (user agent, fonts, plugins, language, timezone), hardware-based (screen resolution, CPU cores, memory, touch support), and network-based (IP address, proxy type). Anti-detect browsers target the rendering and software categories directly, and the hardware category indirectly through spoofed values.

Which Fingerprint Types Do Anti-Detect Tools Cover?

Canvas fingerprint. The HTML5 Canvas API renders a hidden image. The exact pixel output varies by GPU, graphics driver, OS font rendering engine, and browser version. Anti-detect browsers spoof the canvas hash by injecting a manufactured rendering result.

WebGL fingerprint. The WebGL API reports the GPU vendor and renderer string (e.g., "NVIDIA GeForce RTX 4090") and renders a 3D scene whose output varies by hardware. Anti-detect tools spoof both the vendor string and the rendering hash.

Audio fingerprint. The AudioContext API processes an audio signal, and the output varies by hardware and software stack. Anti-detect browsers generate a manufactured audio hash that matches the configured hardware profile.

Font enumeration. Websites can detect installed fonts by measuring text rendering dimensions. Anti-detect browsers report a curated font list that matches the target operating system configuration — a Windows 11 profile gets Windows 11 fonts, not a random set.

User agent and navigator properties. The user agent string, platform, language, timezone, hardware concurrency, device memory, and touch support are all configurable in modern anti-detect tools.

Screen properties. Resolution, color depth, device pixel ratio are spoofed to match the target device profile.

What Is Not Covered?

The signal gap exists wherever the platform inspects beyond the browser. Mobile-first platforms check hardware sensors (accelerometer, gyroscope, magnetometer), which browsers do not expose and cannot spoof. They check app-store install context (was the app installed from the Play Store or sideloaded), which does not exist in a browser session. They check OS-level identifiers (advertising ID, device serial, OS build) that are not browser properties.

GeeTest device fingerprinting research confirms that modern fingerprinting scans hundreds of data points across hardware, software, network, and behavioral layers. An anti-detect browser covers the software layer within the browser. Everything else is gap territory.

Why Do The Gaps Matter At Scale?

A single profile with gaps may pass because the platform cannot prove it is spoofed. Thirty profiles running from the same machine share gaps that become statistically detectable. The platform does not need to prove each profile is fake. It flags the cluster when the cumulative anomaly across the portfolio crosses the detection threshold. For mobile-first distribution at scale, the gap between what anti-detection tools spoof and what platforms inspect is the gap between distribution that works and distribution that gets wiped.

How Conbersa Closes The Gap

We built Conbersa on real physical devices, so there are no signal gaps to close because every signal — hardware sensors, OS identifiers, app-store context, cellular connectivity, and browser fingerprints — is genuine. There is nothing to spoof and nothing that spoofing can get wrong. Distribution across TikTok, Instagram Reels, YouTube Shorts, Facebook Reels, and Reddit runs on hardware that passes every layer of inspection by being real.