Browser UseTalk to sales

Anti-detect browser for automation. Measured on real sites.

An anti-detect browser changes the fingerprint a site sees and keeps each profile apart. Ours is built for code and agents: our own Chromium fork in the cloud, a new fingerprint every session, residential IPs in 195+ countries, $0.02 per browser-hour.

Create a stealth browserHow we measured
fernway.com/flightsSFO to JFK6:05 – 14:32$18918:40 – 17:05$21411:15 – 19:48$236Selectfernway.com/flightsSFO to JFK6:05 – 14:32$18918:40 – 17:05$21411:15 – 19:48$236Select

Browser Use Cloud: 90.5% got through. 8.5 points ahead of Anchor, the next best.

  • Browser Use Cloud90.5%
  • Anchor82%
  • Kernel80.5%
  • Browserbase78.5%
  • Browserless77.5%
  • Steel74.5%
  • Hyperbrowser73.5%

Got through · longer is better · scale 0–100%

Stealth Bench V2 · updated 2026-09-25 · all benchmarks

Cloud browser providers only; desktop anti-detect browsers were not tested. The 100 sites were picked because Browser Use Cloud historically got through where stock Chrome with a US proxy did not. They are hard on purpose and not a balanced sample of the web or of anti-bot vendors.

of visits got through, 100 bot-protected sites
90.5%
Anchor, the next best cloud browser provider
82%
plain headless Chrome, the baseline
3%

What an anti-detect browser is. And which kind you need.

An anti-detect browser makes each browser profile look like a different person's computer: it changes fingerprint signals such as canvas, WebGL, fonts and the user agent, and keeps every profile's cookies separate. Separate IP addresses need a separate proxy per profile. There are two kinds. Managing many accounts by hand, each in its own profile? Use a desktop anti-detect browser; that is what they are built for, and Browser Use is not a desktop app. Writing code or running agents that open browsers on servers, many at a time? Use a cloud anti-detect browser, also called a stealth browser. Browser Use is one; some multi-account vendors, such as GoLogin, also run browsers in their cloud. Either way, use it on sites you are allowed to automate, not to get around a ban; see our Terms of Service.
Built for
DesktopPeople running many accounts by hand, each in its own saved profile
Cloud (Browser Use)Code and AI agents that open browsers, many at a time
Where it runs
DesktopAn app on your computer. Some also launch profiles in their cloud
Cloud (Browser Use)On our servers. Nothing to install
Identity
DesktopEach profile keeps its own fingerprint, cookies and proxy
Cloud (Browser Use)A new fingerprint every session. Profiles keep cookies and logins
Automation
DesktopA local API starts a profile; your script attaches to its debug port
Cloud (Browser Use)One API call returns a CDP URL; your script connects to it
Price
DesktopPer month, by number of profiles
Cloud (Browser Use)Per browser-hour, $0.02, plus proxy traffic

Five anti-detect browsers built for multi-accounting, and Browser Use

Where each one runs, how code drives it and what it costs, from each vendor's own pages.

  • Browser Use

    Where it runs
    Cloud only. Browsers run on our servers, created by API · source
    How code drives it
    One API call returns a CDP URL. Playwright, Puppeteer, any CDP client · source
    API on
    Every account, including free · source
    Starting price
    $0.02/browser-hourplus $5/GB residential proxy, no subscription · pricing
    Free
    One-time $1 credit for eligible signups, 10 browsers at once per project, shared by its API keys (up to 1,000 with spend, more on Enterprise) · source

  • Multilogin

    Where it runs
    Desktop app; profiles saved locally or in Multilogin's cloud storage. Scripts need the app running · sources 1, 2
    How code drives it
    A local launcher starts a profile and returns a port. Playwright, Puppeteer, Selenium · source
    API on
    Pricing table lists API rate limits on paid plans · source
    Starting price
    $11/moPro, 10 profiles · source
    Free
    5 profiles, cloud storage only · source

  • GoLogin

    Where it runs
    Desktop app, web app and a cloud browser (1 to 4 cloud launches at a time, by plan) · source
    How code drives it
    REST API and SDK; Puppeteer, Playwright, Selenium; a CDP endpoint for cloud sessions · sources 1, 2
    API on
    Paid plans list 300 to 1,200 API requests a minute · source
    Starting price
    $9/moProfessional, 10 profiles · source
    Free
    3 profiles · source

  • AdsPower

    Where it runs
    Desktop app with Chrome and Firefox based browsers · source
    How code drives it
    Local API on localhost:50325 opens a profile and returns its debug address. Selenium, Puppeteer, Playwright · source
    API on
    Paid plans · source
    Starting price
    $9/moProfessional, 10 profiles · source
    Free
    2 profiles · source

  • Octo Browser

    Where it runs
    Desktop app; can run headless in Docker · source
    How code drives it
    Local API on localhost:58888 starts a profile and returns a CDP endpoint. Selenium, Playwright, Puppeteer · source
    API on
    Base plan and up, from €79/mo · source
    Starting price
    €10/moLite, 3 profiles · source
    Free
    No free desktop plan listed; a 2-day Starter trial with a promo code · source

  • Dolphin Anty

    Where it runs
    Desktop app for Windows, macOS and Linux · source
    How code drives it
    Local API on localhost:3001 starts a profile and returns a port. Puppeteer, Playwright, Selenium · source
    API on
    Not on the Free plan · source
    Starting price
    $10/moStarter, 20 profiles · source
    Free
    3 profiles · source

Vendor facts are what each vendor states on its own pricing page or docs, checked October 24, 2026. Starting price is the cheapest paid plan at monthly billing, before VAT; Browser Use has no subscription and bills per browser-hour. We did not test these products, so there are no pass rates for them on this page; the Stealth Bench V2 chart above compares cloud browser providers only.

Why sites let it in.

The fingerprint layer makes the browser look like a person's machine: canvas, WebGL, fonts and navigator randomized per session, headless signals gone, patches kept current. The network layer gives it a residential address in the country the site expects. And if a reCAPTCHA or hCaptcha still renders, the browser tries to solve it in place with automatic CAPTCHA solving; hCaptcha support is newer and not guaranteed, and solving is off in the EU region. Most sessions never reach that third step.
Residential exits in 195+ countries · pick one per session

The only setting is the proxy country.

Every browser you create runs the hardened build. The one thing worth choosing is proxyCountryCode, because most protected sites score the IP and the locale together. Or route through your own proxy.
from browser_use_sdk.v4 import BrowserUse # Stealth is on. The one decision is the proxy country.with BrowserUse() as client:    browser = client.browsers.create(proxy_country_code="de")    try:        ...  # connect Playwright or Puppeteer to browser.cdp_url    finally:        client.browsers.stop(browser.id)
stealth.pyStealth on by default · CDP endpoint

How automation attaches. A local app, or one API call.

A desktop anti-detect browser automates through its app: a local API on your machine starts a saved profile and returns a debug port, and Playwright, Puppeteer or Selenium attach to it. The app has to be running and signed in. Browser Use has no app: POST /api/v4/browsers returns a cdpUrl, and connectOverCDP or puppeteer.connect attaches to a browser on our servers. To start it logged in, pass a profileId; profiles keep cookies and logins. Same code from Playwright or Puppeteer.
import { chromium } from "playwright"; const API = "https://api.browser-use.com/api/v4/browsers";const headers = {  "X-Browser-Use-API-Key": process.env.BROWSER_USE_API_KEY,  "Content-Type": "application/json",}; // One API call. Nothing to install or run on your machine.const res = await fetch(API, {  method: "POST",  headers,  body: JSON.stringify({ proxyCountryCode: "us" }),});const { id, cdpUrl } = await res.json(); try {  const browser = await chromium.connectOverCDP(cdpUrl);  const page = browser.contexts()[0].pages()[0];  await page.goto("https://example.com");} finally {  // Closing CDP does not stop the meter. This does.  await fetch(`${API}/${id}`, {    method: "PATCH",    headers,    body: JSON.stringify({ action: "stop" }),  });}
main.mjsPOST /api/v4/browsers · CDP endpoint

Questions people ask

Is Browser Use an anti-detect browser?

Yes, the cloud kind, built for automation. It changes the fingerprint a site sees and routes through residential proxies, like a desktop anti-detect browser. It is not a multi-account profile manager: browsers are created by API on our servers and driven by code or AI agents. If you manage many accounts by hand in a desktop app, a desktop anti-detect browser such as Multilogin, GoLogin, AdsPower, Octo Browser and Dolphin Anty is built for that.

Can I keep the same identity across sessions?

Logins, yes. A profile keeps cookies, local storage and login state, and a browser created with its profileId starts logged in. The fingerprint is randomized per session, and the API has no option to pin one fingerprint to a profile. If a site needs the exact same device fingerprint for months, a desktop anti-detect browser is built for that.

Do anti-detect browsers work with Playwright and Puppeteer?

The multi-account ones do: their API or SDK starts a saved profile and hands Playwright, Puppeteer or Selenium a debug port or WebSocket URL to attach to. Multilogin, GoLogin, AdsPower, Octo Browser and Dolphin Anty all document this. Browser Use returns a CDP URL from one API call, so connectOverCDP or puppeteer.connect works with no local app.

What makes it hard to detect?

It is our own Chromium build, maintained and patched non-stop. Canvas, WebGL, fonts, navigator and the other fingerprint surfaces are randomized per session, and headless signals are removed.

How is the number measured?

Stealth Bench V2: 100 real sites that block bots, two visits per provider, 60 seconds each. A judge model that does not see the provider name checks whether the real site loaded. The chart on this page is the result, for cloud browser providers. Each ran the stealth setting its standard plans offer (Steel's have none); Browserbase Verified and Hyperbrowser Ultra Stealth need Enterprise plans and were not tested. Plain headless Chrome gets through 3% of the time. The sites were picked because Browser Use Cloud historically got through where stock Chrome with a US proxy did not, so they are not a balanced sample. Code and raw results are public.

Does it get through Cloudflare?

On our earlier 71-site benchmark it got through 93% of Cloudflare-protected sites, 85% of Akamai and 81% of PerimeterX. Nobody gets 100%, and detectors change, so the benchmark is re-run as they do.

Are proxies included?

Residential proxies in 195+ countries are on every browser at $5/GB, chosen per session by country code. Bring your own proxy and egress is $0.20/GB.

Does my Playwright or Puppeteer code need changes?

Your page logic stays the same. Two things change: replace the local launch with connectOverCDP (or puppeteer.connect) to the cdpUrl, and stop the browser through the API when you are done, because closing the CDP connection does not stop it.