Remote Browser
A remote browser runs in the cloud or on a remote server rather than your local machine, controlled over the network. It is used for scalable automation, scraping, and isolation.
Definition
A remote browser is a web browser that runs on a remote server or cloud infrastructure instead of your local device, controlled programmatically over the network through protocols like the Chrome DevTools Protocol or WebDriver. Your automation code connects to it via a WebSocket or HTTP endpoint.
How it works
Tools such as Playwright and Puppeteer connect to a remote endpoint using methods like connect() or connectOverCDP(). The browser itself, often a headless browser, executes in a container or managed service, while your script issues commands from anywhere.
Why it matters for scraping and proxies
- Scalability: Spin up many cloud browser instances in parallel without straining local hardware.
- Built-in proxies: Managed remote browser services often bundle rotating residential proxies and anti-detect fingerprinting.
- Isolation and security: Untrusted pages run away from your local environment.
Remote browsers are central to scalable web scraping, where managed services handle proxy rotation, CAPTCHA solving, and fingerprint management so you can focus on extracting data.
Examples
Connecting Playwright to a cloud browser via chromium.connect(wsEndpoint)
Using a managed remote browser service with built-in proxy rotation
Running hundreds of parallel headless sessions in the cloud
Common Use Cases
Frequently Asked Questions
Keep Learning
All termsWeb Scraping
Web scraping is the automated extraction of data from websites — fetching pages programmatically and parsing their content into structured data.
Read definitionRotating Proxy
A rotating proxy automatically assigns a different IP address from a pool for each request or on a set interval, spreading traffic across many IPs to avoid blocks.
Read definitionAnti-Detect Browser
An anti-detect browser lets you run many isolated browser profiles, each with its own fingerprint, cookies and proxy, so sites see them as separate, genuine users.
Read definitionHeadless Browser
A headless browser is a real browser that runs without a visible interface, controlled by code — the workhorse for scraping JavaScript-heavy sites and automation.
Read definition