Browserless

What is Browserless?

A managed headless browser platform for developers running Puppeteer, Playwright, and headless Chrome. No servers, containers, or Chrome updates to manage. Connect with one line of code.

How does Browserless work?

Replace launch() with connect() in your existing scripts and point to a Browserless endpoint. Your code stays the same. We manage the browsers, concurrency, memory, and Chrome versions on our side.

What's included in the free plan?

1,000 units per month, 2 concurrent browsers, automatic CAPTCHA solving, residential proxies, and access to Chrome, Firefox, and WebKit. No credit card required.

Do I need to rewrite my code?

No. Browserless is compatible with standard Puppeteer and Playwright APIs. If your scripts run locally, they run on Browserless.

Can I self-host Browserless?

Yes. Browserless offers cloud, managed cloud, and self-hosted deployment options. Same API everywhere. Enterprise customers can specify cloud providers, regions, GPU configs, and run on their own infrastructure.

How does pricing work? What's a 'unit'?

Browserless uses unit-based pricing. A Unit is any time a browser is started with our API and runs for up to 30 seconds, and a new Unit is charged every 30 seconds the session continues. Paid plans include a monthly unit allowance; overages are billed at a per-unit rate. Residential proxies use 6 units per MB. Free plan: 1,000 units per month, no credit card required.

How is Browserless different from Bright Data, Browserbase, or ScrapingBee?

Browserless runs standard Puppeteer and Playwright, not a proprietary wrapper, so your existing scripts work unchanged. It's battle-tested at scale: 173M+ Docker pulls, 8 years in production, SOC 2 Type II certified. Unlike Browserbase or Bright Data, Browserless is also available self-hosted on your own infrastructure. Unlike ScrapingBee's API-only model, you get full browser access for complex automations. Bright Data focuses on proxies; Browserless focuses on browsers, with proxies built in.