/browser/ — Browserless Browser as a Service
Connect Playwright or Puppeteer to hosted browsers with optional built-in or third-party proxies.
Hosted browser. Official documentation · Checked · Review due .
documented capabilities
CDP / WebSocket- Time metering
- Each started 30-second browser interval costs one unit, including idle time.[1]
- Built-in proxy costs
- Residential traffic costs 6 units per MB and datacenter traffic 2 units per MB, in addition to browser time.[1]
- Custom proxy costs
- Third-party proxies configured through --proxy-server do not consume Browserless proxy units; their own provider may bill separately.[1]
- Failures
- Pre-start validation or queue rejections consume no browser units; failures after startup consume elapsed time and transferred proxy traffic.[1]
- Session timeout
- The documented default timeout is 30 seconds; a custom timeout can be set on the connection.[1]
Billing: Units for browser time, built-in proxy bandwidth and successful CAPTCHA solves.
Outputs: browser-session
Documented for: Playwright, Puppeteer
getting started
documentation reviewed- Obtain a Browserless Cloud API token and choose the regional connection endpoint.
- Connect Playwright or Puppeteer with token and timeout parameters.
- Select a built-in proxy or supply a third-party proxy through launch arguments, and close the session when finished.
Requirements & limitations
- Session duration and concurrency limits depend on the plan.
- A failed automation run can still consume units.
- Third-party proxy charges are separate from Browserless browser-time charges.
We reviewed the linked documentation. No live service connection, checkout or performance test is claimed for this listing.
primary sources
2 references- Unit consumption and billing examplesChecked 2026-09-27
- Browser session connection examplesChecked 2026-09-27