stealth browsers thatbypass bot detection

Cloud Browsers

Run automation on stealth Chromium instances hosted in the cloud. Each cloud browser is a separate machine with its own cookies, storage, IP address, and fingerprint; completely isolated from your other browsers. They come with residential proxies, automatic CAPTCHA solving, and anti-bot fingerprint evasion built in. No setup, no proxy configuration, no CAPTCHA API keys to manage.

Cloud browsers appear alongside your local Chrome in playwriter session new, so your existing workflows and scripts work without changes.

Ask AI about this page

Cloud browsers are a paid add-on. Your local Chrome extension stays free forever.

Pricing

	Monthly	Yearly
Per browser	$10 / month	$100 / year (2 months free)

Subscription quantity = max concurrent cloud browsers you can run at the same time. Each browser is an independent machine with its own state. Start with 1 and scale up as needed. Subscribe from your dashboard.

Billing runs on Stripe. Update payment method, download invoices, or cancel any time from the portal.

Why multiple browsers

Each cloud browser is a separate Chromium machine with its own IP address, fingerprint, cookies, localStorage, and auth state. They don't share anything; logging into a site in one browser has zero effect on the others. Adding more browsers lets you:

Run agent tasks in parallel. Spin up 5 browsers and let 5 agents work simultaneously instead of waiting for one to finish before starting the next.
Use different identities. Log into separate accounts on the same site at the same time. Useful for testing multi-user flows, managing multiple client accounts, or comparing search results across regions.
Open more tabs for resource-intensive tasks. Heavy pages (dashboards, SPAs, video players) consume memory and CPU. Spreading tabs across multiple browsers keeps each instance responsive instead of slowing everything down in a single browser.

Your subscription quantity controls how many browsers can run at the same time. If you need 3 concurrent machines (for example, 3 agents each logged into a different account), set quantity to 3.

Stealth and anti-detection

Cloud browsers are purpose-built to look like a real user, not a bot.

Stealth Chromium. The browser ships with patches that remove common automation signals. Headless detection checks, navigator.webdriver, CDP leak fingerprints, and other bot indicators are all handled. Sites that block Playwright, Puppeteer, or Selenium out of the box work normally in a cloud browser.

Residential proxies. Proxies are disabled by default to keep costs low. Enable them with --proxy <region> when you need anti-detection or geo-targeting. Pick from 195+ countries. Sites that block datacenter IPs or rate-limit by IP range see a normal residential connection.

Automatic CAPTCHA solving. When a CAPTCHA appears (Turnstile, reCAPTCHA v2/v3, hCaptcha), the cloud browser solves it automatically via token injection. No CAPTCHA API key needed, no manual intervention, no extra code in your scripts.

Custom proxies. If you have your own proxy infrastructure, pass it directly instead of using the built-in residential proxies:

1playwriter session new --browser cloud --custom-proxy user:pass@host:8080

CAPTCHA solving works for Cloudflare Turnstile, reCAPTCHA v2, reCAPTCHA v3, and hCaptcha. Other types are not yet supported.

Getting started

1. Authenticate

Option A: Interactive login (opens browser for OAuth)

1playwriter cloud login

This opens a device flow in your browser. Sign in at playwriter.dev and the CLI stores your token locally.

Option B: API key (for CI, VPS, headless environments)

Create an API key at playwriter.dev/dashboard, then set it as an environment variable:

1export PLAYWRITER_API_KEY=pw_xxxxx

API keys work everywhere cloud login works but don't require a browser or interactive terminal.

1playwriter cloud subscribe

Opens the subscription page where you pick monthly or yearly and set the number of concurrent browsers.

3. Start a cloud browser

1234567891011# New cloud browser (no proxy, cheapest)
playwriter session new --browser cloud

# Enable US residential proxy (for anti-detection / geo-targeting)
playwriter session new --browser cloud --proxy us

# German proxy
playwriter session new --browser cloud --proxy de

# Japanese proxy
playwriter session new --browser cloud --proxy jp

Cloud sessions appear in the session table with keys like cloud-1, cloud-2. Selecting an existing cloud session reattaches to the running VM instead of creating a new one.

4. Use it

Once connected, the cloud browser works exactly like a local one. All Playwright commands, snapshots, screenshots, and MCP tools work the same way:

12playwriter -s 1 -e "await page.goto('https://example.com')"
playwriter -s 1 -e "console.log(await snapshot({ page }))"

5. Check status

1playwriter cloud status

Lists all active cloud browser VMs with their index, region, and uptime.

Cloud sessions auto-stop after 10 minutes of inactivity so you don't burn resources when you're done.

MCP and agent usage

Cloud browsers work with the MCP server too. Set env vars in your MCP client config:

12345{
  "env": {
    "PLAYWRITER_CLOUD_TOKEN": "your-token"
  }
}

The MCP server discovers cloud browsers alongside local ones. Agents can request a cloud browser when they need stealth browsing, geo-targeted access, or CAPTCHA bypass without any extra prompting.

Manage your subscription from the dashboard. Pick monthly or yearly, adjust the number of concurrent machines, and switch or cancel any time through the Stripe billing portal.