Anti-Detect Browser Skills (AntiBrow)

---
name: anti-detect-browser
description: Drive Chromium from standard Playwright APIs with a real-device fingerprint applied in the kernel, one persistent isolated profile per identity, and a per-profile proxy whose exit IP sets timezone and WebRTC - JavaScript (npm 'anti-detect-browser') or Python (PyPI 'antibrow'). Use when sessions must stay logged in across runs and stay separate, when a scraper or agent is blocked by an incoherent headless fingerprint, when checking ads or pricing from another region, when a page must be reached as a phone rather than a desktop, when automation mints a profile per task, when running several of your own accounts from one machine, or when testing how your own bot detection scores a real device. Also for 'antibrow', 'fingerprint browser', 'multi-account browser', '防关联', '多账号', '安卓模拟', 'Android profile', 'mobile fingerprint', 'temporary profile', 'CreepJS', 'residential proxy', 'browser-use', 'crawl4ai'. MCP control is browser-mcp-agent; isolation is multi-account-isolation.
license: MIT
---

# Anti-Detect Browser SDK

Launch Chromium instances with real-device fingerprints via standard Playwright APIs. Every profile carries one coherent, real-device identity that is frozen at creation and replayed byte-for-byte on every later launch.

- npm package: `anti-detect-browser` (Node >= 18)
- PyPI package: `antibrow` (Python 3.9 - 3.13)
- Dashboard: `https://antibrow.com`
- REST API base: `https://antibrow.com/api/v1/`
- Documentation: `https://antibrow.com/docs`

> **Authorized use only.** This is for automating systems you own or are permitted to use: your own accounts, your own site's bot detection and anti-fraud stack, publicly available data, and region-specific views of your own ads and pricing. Do not use it to access systems without authorization, to log into accounts that are not yours, to create fake accounts or engagement, or to work around a platform's enforcement decision. Respect each site's terms, `robots.txt` and rate limits, and applicable law - see [Acceptable use](#acceptable-use).

**What this does not claim.** A coherent real-device fingerprint removes the *contradictions* a synthetic browser leaves behind. It is not a guaranteed pass against enterprise bot managers, which also score network reputation, request patterns, behaviour and account history - none of which a fingerprint touches. Measure with the suites listed under [What detection actually tests](#what-detection-actually-tests) rather than assuming.

Every code sample below reads credentials from the environment; none contain literal keys or proxy passwords.

## Why antibrow

- **Spoofing lives in the engine, not in a script.** A custom Chromium kernel answers Canvas, WebGL, WebGPU, audio, fonts, `navigator`, screen, DOMRect and timezone inside C++/Blink. There is no injected script to find, no property descriptor out of place, and worker contexts return exactly what the main thread does.
- **Real TLS and HTTP layer.** It *is* Chromium, so the ClientHello, cipher order and HTTP/2-3 behaviour are a genuine Chrome build's - the network half that a patched headless browser can never fake coherently.
- **One coherent persona per profile.** 30+ categories and 500+ parameters sampled from the same real machine. Independently randomized values contradict each other (an AMD renderer next to an Intel vendor string, a 1.0 DPR on a 1536x864 screen); these do not.
- **Timezone and geo follow the proxy.** The exit IP is resolved *through* the proxy before launch, then written into the fingerprint along with the WebRTC identity.
- **Proxy auth handled in the network stack.** HTTP/HTTPS 407 and SOCKS5 RFC 1929 are answered by the kernel, so nothing appears in `chrome://extensions` - a classic anti-detect tell avoided.
- **Unlimited local profiles, free.** A profile is a directory; name one and it exists. Plans cap *concurrent* browsers, not identities.
- **Desktop or phone.** `deviceType: 'android'` gives a profile a real phone's identity - mobile client hints, touch, portrait screen, mobile GPU - on the machine you already have.
- **Drop-in Playwright API** in both JS and Python - existing scripts change only their launch line.
- **Runs as an MCP server** so AI agents drive it directly via tool calls.

## Platform support

| Platform | Status | Notes |
|---|---|---|
| Windows 10/11 x64 | Supported | Headful, or headless via off-screen window |
| macOS 12+ Apple Silicon + Intel | Supported | Universal build (arm64 + x64 in one bundle) |
| Linux x64 (glibc) | Supported | Headless needs Xvfb; container flags applied automatically |
| Linux arm64 (glibc) | Supported | Separate arm64 kernel, picked automatically from the CPU |
| Docker `linux/amd64` + `linux/arm64` | Supported | Run headful under Xvfb |
| Linux musl (Alpine) | Not yet | No kernel build |