anti-detect-browser
v1.2.4
Published
Windows-only anti-detect browser client SDK powered by the Engine runtime and Playwright CDP
Maintainers
Readme
anti-detect-browser
Engine-level anti-detect browser for Node.js — real device fingerprints, the standard Playwright API, zero learning curve.
Drive an undetectable Chromium with the Playwright API you already know. Fingerprints are applied at the engine level (not fragile JS patches), so canvas, WebGL, audio, fonts, WebRTC, timezone and locale are spoofed deep enough to satisfy the strictest detectors — while you keep writing plain page.goto(...).
import { AntiDetectBrowser } from 'anti-detect-browser'
const ab = new AntiDetectBrowser({ key: 'your-api-key' })
const { page } = await ab.launch({ profile: 'amazon-us', proxyId: 'your-proxy' })
await page.goto('https://example.com') // standard Playwright from hereWhy anti-detect-browser
- 🛡️ Engine-level spoofing — fingerprints are generated from real devices and applied inside the browser engine, not injected via JavaScript that detectors can unmask.
- 🎭 Consistent identity — UA, platform, canvas, WebGL, audio, fonts, WebRTC, timezone and language all line up. No tells, no contradictions.
- 🌍 Geo-aware — point a profile at a proxy and the browser's timezone, locale and WebRTC automatically follow the proxy's location.
- 💾 Persistent profiles — each profile keeps its own cookies, storage and login state across runs, and syncs to the cloud.
- 🔌 Standard Playwright —
launch()returns a real PlaywrightPage/BrowserContext. Everything you know still works. - 🏷️ Account labels — floating tag, window title and theme color per profile, so you never act in the wrong account.
- 📺 Live View — stream any session to your dashboard and share a watch link.
- 🤖 MCP server — expose the browser to AI agents via the Model Context Protocol out of the box.
Detection benchmarks
Verified by launching a real profile through a US residential proxy (New York) with an engine-generated fingerprint, then opening the public detectors:
| Detector | Result |
|----------|--------|
| Whoer.net | 100% disguise — proxy not detected, no DNS leak, OS / browser / geo all consistent |
| CreepJS | 0% headless, 0% stealth, confidence high, navigator.webdriver = false |
| WebRTC | Exposes the proxy IP only — the real IP never leaks |
| Timezone / Locale | Auto-aligned to the proxy: a US proxy IP yields a US timezone (e.g. America/New_York, America/Los_Angeles) + en-US "American English" |
| Device coherence | UA Chrome 137, userAgentData (137.0.7151.69), platform, cores and memory all agree |
Results reflect one verification run; exact scores depend on the proxy and fingerprint. The point is consistency — every layer tells the same story.
Install
npm install anti-detect-browser playwright-coreWindows-only. The engine runtime and its fingerprint generation are Windows-native.
Quick start
import { AntiDetectBrowser } from 'anti-detect-browser'
const ab = new AntiDetectBrowser({ key: 'your-api-key' })
const { page } = await ab.launch({
profile: 'amazon-us', // persistent profile (cookies, storage, login)
proxy: 'http://user:pass@host:port', // or proxyId for a managed proxy
})
await page.goto('https://example.com')The engine applies the fingerprint at launch, so once launch() returns you have regular Playwright Page / BrowserContext objects with no extra setup.
Full options
const { browser, context, page } = await ab.launch({
profile: 'my-account', // persistent profile
proxy: 'http://user:pass@host:port',
proxyId: 'managed-proxy-id', // managed proxy; takes precedence over `proxy`
label: '[email protected]',
color: '#3366ff',
headless: false,
liveView: true, // stream this session to your dashboard
})
await page.goto('https://example.com')
await browser.close()MCP server
Run as an MCP server for AI agent integration:
{
"mcpServers": {
"anti-detect-browser": {
"command": "npx",
"args": ["anti-detect-browser", "--mcp"],
"env": {
"ANTI_DETECT_BROWSER_KEY": "your-api-key"
}
}
}
}Exposes tools such as launch_browser, close_browser, navigate and screenshot.
How it works
- Your API key authenticates an engine session with the server.
- The engine runtime is provisioned locally (cached after first use) and launched with a real-device fingerprint.
- The SDK connects over CDP and hands you a standard Playwright
BrowserContext. - Profiles persist locally and sync to the cloud; proxies set geolocation, timezone and language automatically.
Requirements
- Windows
- Node.js >= 18
- An API key from antibrow.com
Documentation
Visit antibrow.com for full documentation.
