Skip to main content
Zeus Desktop provides comprehensive browser fingerprint management, allowing each profile to present a unique and consistent browser identity. This prevents websites from linking multiple profiles through fingerprint correlation.

What is Browser Fingerprinting?

Browser fingerprinting is a technique websites use to identify and track users by collecting unique characteristics of their browser and device — even without cookies. These include:
  • User-Agent string
  • Screen resolution
  • Installed fonts
  • WebGL renderer information
  • Canvas rendering patterns
  • AudioContext output
  • Hardware specifications (CPU cores, memory)
  • Timezone and language
When two browser sessions share the same fingerprint, websites can determine they likely belong to the same user — defeating the purpose of separate profiles.

Fingerprint Configuration

Configurable Properties

CategoryPropertyDescriptionExample
BasicUser-AgentBrowser identification stringMozilla/5.0 ... Chrome/120.0.0.0
BasicPlatformOperating system identifierWin32, MacIntel, Linux x86_64
BasicLanguageBrowser language preferenceen-US,en;q=0.9
BasicTimezoneGeographic timezoneAmerica/New_York
ScreenResolutionScreen dimensions1920x1080, 2560x1440
ScreenColor DepthDisplay color depth24
ScreenPixel RatioDevice pixel ratio1 or 2 (Retina)
AdvancedWebGL VendorGPU vendor stringIntel Inc., NVIDIA Corporation
AdvancedWebGL RendererGPU renderer stringIntel Iris OpenGL Engine
AdvancedCanvas NoiseDeterministic canvas noise seedRandom integer
AdvancedAudio NoiseDeterministic audio noise seedRandom integer
HardwareCPU Coresnavigator.hardwareConcurrency4, 8, 12, 16
HardwareDevice Memorynavigator.deviceMemory (GB)4, 8, 16

Random Fingerprint Generation

Click the “Generate Random Fingerprint” button to instantly fill all fields with a realistic, internally consistent configuration. The generator ensures consistency:
  • A Windows User-Agent gets a Win32 platform and Windows fonts
  • A macOS User-Agent gets a MacIntel platform, devicePixelRatio: 2, and macOS fonts
  • WebGL vendor/renderer combinations match the selected OS
  • All values are drawn from pools of real-world common configurations

How It Works

Zeus applies fingerprint overrides at two levels:

Level 1: Chrome Launch Arguments

Applied before Chrome starts:
--user-agent="Mozilla/5.0 ... Chrome/120.0.0.0 Safari/537.36"
--lang=en-US

Level 2: CDP (Chrome DevTools Protocol) Injection

Applied immediately after Chrome launches, via WebSocket connection to the CDP debug port:

Anti-detection Script Details

The injected script runs on every new document (including iframes) before any page JavaScript executes. Here’s what each protection does:
Object.defineProperty(navigator, 'webdriver', { get: () => undefined });
delete Object.getPrototypeOf(navigator).webdriver;
Websites check navigator.webdriver to detect automation tools. This removes the flag completely.

Canvas Fingerprint Noise

Adds deterministic noise to Canvas API output. The noise is:
  • Deterministic — Same seed always produces the same noise (consistent across page reloads)
  • Imperceptible — Tiny pixel-level changes invisible to the eye
  • Unique — Different seed = different fingerprint
This prevents canvas fingerprinting by making each profile produce distinct but consistent canvas output.

WebGL Spoofing

Overrides WEBGL_debug_renderer_info to report custom GPU vendor and renderer strings. This is one of the strongest fingerprint signals, as GPU information is highly device-specific.

AudioContext Noise

Injects deterministic noise into AudioContext.createAnalyser() output. Audio fingerprinting uses subtle differences in audio processing to identify devices.

Font Detection Protection

Intercepts font measurement queries to add consistent variations, preventing websites from enumenting your installed fonts.

Consistency Guidelines

For maximum anti-detection effectiveness, ensure your profile settings are internally consistent:
If you set…Then also set…Why
Windows UAWin32 platformUA/platform mismatch is an instant red flag
macOS UAMacIntel platform, devicePixelRatio: 2Most Macs have Retina displays
en-US languageAmerica/New_York timezone (or similar US tz)Language-timezone mismatch looks suspicious
1920x1080 resolutiondevicePixelRatio: 11080p displays typically have 1x pixel ratio
Intel GPUIntel WebGL rendererMismatched GPU brands are detectable
The Random Generate button automatically handles all consistency rules for you. It’s recommended to start with a random generation and then fine-tune specific values if needed.

Canvas & Audio Protection Toggles

The UI provides two easy switches:
  • Canvas Protection — When enabled, injects deterministic noise into canvas operations. This makes your canvas fingerprint unique to this profile while remaining consistent across sessions.
  • Audio Protection — When enabled, injects deterministic noise into AudioContext operations. Similar to canvas protection but for audio-based fingerprinting.
Both are enabled by default when generating a random fingerprint.

Verifying Your Fingerprint

After launching a profile, you can verify its fingerprint using these websites:
ToolURLWhat it checks
BrowserLeaksbrowserleaks.comComprehensive fingerprint analysis
CreepJSabrahamjuliot.github.io/creepjsAdvanced anti-detection analysis
AmIUniqueamiunique.orgFingerprint uniqueness score
Pixelscanpixelscan.netBot detection and consistency checks

Troubleshooting

Fingerprint Not Applied

  1. Ensure the profile has fingerprint settings configured (check the config dialog)
  2. Verify Chrome launched with the correct debug port (check logs)
  3. CDP injection only works if Chrome started correctly — check for Chrome launch errors

Website Still Detects Automation

  1. Make sure navigator.webdriver is removed (check in DevTools console: navigator.webdriver should be undefined)
  2. Verify window.chrome exists (some sites check for its absence)
  3. Ensure all fingerprint values are consistent (see Consistency Guidelines above)
  4. Some advanced detection may check for timing anomalies — fingerprint spoofing helps but isn’t perfect against all detection methods

Canvas/WebGL Test Shows Same Fingerprint

  1. Ensure canvasNoiseSeed is different between profiles
  2. Verify canvas protection is enabled in the profile settings
  3. Close and relaunch the browser — fingerprint injection happens at launch time