Skip to main content
A Browser Use cloud browser is a real Chromium instance running on our infrastructure that your code controls remotely over the Chrome DevTools Protocol (CDP). Create one with an API call, get back a cdpUrl, and drive it with Playwright, Puppeteer, or any CDP client, the same way you’d drive a local browser. The difference from local Chromium is what’s built in. Every session runs our hardened Chromium fork with anti-fingerprinting patches, automatic CAPTCHA solving, and a residential proxy in your choice of 195+ countries. None of it needs configuration.

​
When to use a cloud browser

  • Your Playwright/Puppeteer scripts get blocked. Same code, but running on infrastructure that sites treat as a normal user.
  • You don’t want to run browsers. No Chrome processes, no headless servers, no scaling browser pools.
  • You’re building your own agent. Full CDP access means any framework or custom tooling works. You can also run the open-source Browser Use agent on a cloud browser.
  • You need a watchable, recordable session. Every session has a live view you can open or embed, and optional recording.
If you’d rather describe the task and let AI do the driving, use the Agent instead. The two combine: agents run inside browser sessions, and you can connect your own code to the browser behind an agent run.

​
How it fits together

  1. Create a browser session — SDK, REST, or a single WebSocket URL
  2. Connect your framework — Playwright, Puppeteer, or Selenium
  3. Automate as usual — the session behaves like local Chromium with better manners from websites
  4. Manage the session — timeouts, stopping, what you’re billed for

​
Logging into websites

Sessions start clean by default. To carry login state across sessions, use profiles / cookie sync, authentication, and 2FA support.

​
Further reading