BotBrowser

Advanced Privacy Browser Core with Unified Fingerprint Defense 🚀

Identical privacy posture on any OS • Cross-platform & WebView simulation • Fingerprint protection validated across 31+ tracking scenarios

What Is BotBrowser?

BotBrowser is a privacy-first browser core designed to protect users from browser fingerprinting, a technique recognized as a privacy threat by W3C, major browser vendors, privacy regulators, and academic research (see references). It keeps fingerprint signals uniform across every platform, preventing tracking systems from collecting and correlating data to identify users. Run the same profile on Windows, macOS, or Linux and the fingerprint posture stays identical each time.

All engineering focuses on privacy research, cross-platform tracking-resistance validation, and maintaining protected environments for authorized defensive benchmarking. Review the project Legal Disclaimer and Responsible Use Guidelines before using the software.

Why BotBrowser

What makes BotBrowser different: Cross-platform privacy browser core with unified fingerprint technology that prevents tracking data collection and device linkage.

Cross-Platform Fingerprint Protection

• Single profile, every host OS: identical UA, screen metrics, touch surfaces, fonts, and device APIs on Windows, macOS, Linux (ENT Tier1), Android (PRO), WebView (ENT Tier3), and WebKit-family profile bundles (ENT Tier4) for consistent browser identity across environments.
• Built-in configuration handles touch simulation, device metrics, and locale/timezone detection from the proxy IP while still allowing CLI overrides when privacy experiments require them.
• Quick demos: ▶️ CreepJS Android • ▶️ Iphey • ▶️ Pixelscan

Getting Started

Quick Start

Step 1: Download - Latest release for your OS - Demo profile (any .enc file)

Step 2: Launch - GUI: Use BotBrowserLauncher for one-click profile selection and multi-instance management - CLI (use absolute paths): cmd chrome.exe --bot-profile="C:\absolute\path\to\profile.enc" --user-data-dir="%TEMP%\botprofile_%RANDOM%" - macOS/Linux commands follow the same pattern; see INSTALLATION.md for full instructions.

Step 3: Verify - Visit CreepJS or your preferred tracking observatory to confirm identical privacy posture. - Timezone/locale/language auto-derive from your proxy/IP; override via CLI only when needed.

Complete Installation Guide →

Minimal Playwright Example

const browser = await chromium.launch({
  headless: true,
  executablePath: BOTBROWSER_EXEC_PATH,
  args: [`--bot-profile=${BOT_PROFILE_PATH}`,
  '--proxy-server=socks5://usr:pwd@127.0.0.1:8989']  // or: http://usr:pwd@127.0.0.1:8989
});
const page = await browser.newPage();
await page.addInitScript(() => { delete window.__playwright__binding__; delete window.__pwInitScripts; });
await page.goto('https://abrahamjuliot.github.io/creepjs/');

Notes: - Use --user-data-dir with a unique temporary folder to avoid conflicts with running Chromium instances - Prefer --proxy-server or per-context proxies (ENT Tier1); auto timezone/locale detection applies in both cases - Avoid framework-specific proxy/auth options (e.g., page.authenticate()), which disable BotBrowser's geo-detection and may leak location information

Examples: Playwright • Puppeteer

More options: - Framework-less approach: --bot-script + CDP (privileged context, earlier hook, fewer artifacts) - Docker: docker/README.md - Full flags: CLI_FLAGS.md

Builds

BotBrowser ships in two builds. Both share the same fingerprint protection model, the same profile format, the same CLI flag surface, and the same CDP commands.

Linux x64 benchmark (400 official samples, 1..20 contexts × 10 repeats × 2 builds): Trimmed Build cuts wall time by 62%, per-context creation by 85%, first navigation by 38%, CPU peak by 68%, PSS peak by 31% versus Standard, with 100% success rate and 0 residual processes for both builds.

Trimmed Build is the right choice when context spin-up dominates total wall time, when CPU peak per context limits density, or when shared memory is the binding constraint. Standard Build remains the right choice for interactive workflows and scenarios that exercise the full browser feature surface.

Product overview, engineering design, FAQ: TRIMMED_BUILD.md. Full performance table: BENCHMARK.md#trimmed-build. Access: Enterprise or Pricing.

Feature Reference

Configuration priority: CLI flags (highest) > Profile configs > defaults. Timezone, locale, and language auto-derive from your proxy IP.

Network & Proxy

Fingerprint & Rendering

Identity & Platform