BotBrowser
Advanced Privacy Browser Core with Unified Fingerprint Defense: Cloudflare, Akamai, Kasada, Shape, DataDome, PerimeterX, hCaptcha, FunCaptcha, Imperva, reCAPTCHA, ThreatMetrix, Adscore
Install / Use
npx skills add botswin/BotBrowserInstalls into whichever agent you are using.
README
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
<table cellspacing="0" cellpadding="8"> <tr> <td width="50%"><strong>High-Fidelity, Always-Current Profiles</strong> including <a href="docs/guides/platform/ANDROID_WEBVIEW.md">Android WebView</a> and <a href="WEBKIT_PROFILE_CONSISTENCY.md">WebKit-family profile consistency</a>, built on the latest stable Chromium so fingerprints stay aligned with current browser behavior and reduce stale-engine correlation risk</td> <td width="50%"><strong>Network Stack Parity</strong> with <a href="ADVANCED_FEATURES.md#network-fingerprint-control">Full-Proxy QUIC/STUN</a> (UDP over SOCKS5) delivers Chromium-level tunneling so geo metadata does not leak and privacy labs maintain clean transport parity</td> </tr> <tr> <td width="50%"><strong>Advanced Programmatic Control</strong> offers <a href="examples/">Playwright/Puppeteer integration</a> with CDP leak blocking so privacy tooling leaves no telemetry residue</td> <td width="50%"><strong>Distributed Privacy Consistency</strong> lets you verify privacy protection across multiple browser instances simultaneously <a href="tools/mirror/">with Mirror</a>, synchronizing input and validating privacy posture in parallel</td> </tr> <tr> <td width="50%"><strong>Per-Context Fingerprint</strong> enables <a href="PER_CONTEXT_FINGERPRINT.md">independent fingerprint bundles per BrowserContext</a> without spawning new processes, with millisecond-level switching and reduced memory overhead</td> <td width="50%"><strong>Zero-Overhead Performance</strong> adds <a href="BENCHMARK.md">no measurable latency</a>: Speedometer 3.0 within <1% of stock Chrome, zero fingerprint API overhead across macOS/Linux/Windows, 29% memory savings at scale with Per-Context Fingerprint, and a <a href="BENCHMARK.md#trimmed-build">Trimmed Build</a> (ENT Tier3) delivering 62% lower wall time and 85% faster per-context spin-up on Linux x64</td> </tr> </table>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
- A matching profile package. BotBrowser 150 and newer profiles are available through subscription or support at support@botbrowser.io or @botbrowser_support; legacy demo profiles remain available for earlier evaluation lines.
Step 2: Launch
- GUI: Use BotBrowserLauncher for one-click profile selection and multi-instance management
- CLI (use absolute paths):
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.
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-dirwith a unique temporary folder to avoid conflicts with running Chromium instances - Prefer
--proxy-serveror 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 Flag Directory
- Setup guides: docs/guides
<a id="builds"></a>
Builds
BotBrowser ships in two builds. Both share the same fingerprint protection model, profile format, and documented CLI/CDP interfaces. Capability availability still depends on the active profile package and subscription tier.
| | Standard Build | Trimmed Build (ENT Tier3) | |---|---|---| | Distribution | Public releases | Enterprise channel only | | Built for | Long-running and interactive sessions | Short-session, high-concurrency automation | | Browser feature surface | Full | Tuned for short-session workloads | | Fingerprint protection | Same | Same | | Per-Context Fingerprint | Same | Same | | Profile compatibility | Same | Same |
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
<details> <sumConfiguration priority: CLI flags (highest) > Profile configs > defaults. Timezone, locale, and language auto-derive from your proxy IP.
Related Skills
gh-issues
385.5kFetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.
node-connect
385.5kDiagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.
browser-automation
385.5kUse when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts.
imsg
385.5kUse the imsg CLI from OpenClaw agents for iMessage/SMS DMs, groups, replies, reactions, polls, watching, and private-API actions.
