Agent Sandboxesagentsandboxes.org
Head-to-head

Browserless vs Cloudflare Browser Run

Answer in brief

Choose Browserless for existing Puppeteer, Playwright or Selenium automations that want a managed or self-hosted browser pool; choose Cloudflare Browser Run for screenshots, scraping and short agent browsing from Workers without running a browser fleet. Browserless uses Not documented isolation and is open source; Cloudflare Browser Run uses Not documented isolation.

By the Agent Sandboxes editors · Updated

Key differences between Browserless and Cloudflare Browser Run

  • Open source: Browserless is open source (SSPL-1.0 OR Browserless Commercial License); Cloudflare Browser Run is not.
  • Self-hosting: Browserless documents a self-hosted option; Cloudflare Browser Run does not.
  • Session length: 2 min to 60 min by plan (Browserless) versus 60 s idle, 20 min keep_alive (Cloudflare Browser Run).
  • SDKs and interfaces: Only Browserless lists Python and CLI.

What they have in common

  • Both companies are based in the United States.
  • Both are hosted platforms.
  • Both list TypeScript, REST API and MCP server.

Browserless vs Cloudflare Browser Run at a glance

AttributeBrowserlessCloudflare Browser Run
What it isManaged headless Chrome, Firefox and WebKit over WebSocket for Puppeteer, Playwright and Selenium, with BrowserQL stealth, REST endpoints and a Docker image you can self-host.Headless Chrome on Cloudflare's network (formerly Browser Rendering), driven from a Workers binding, a REST API or a CDP endpoint, billed by browser hour on the Workers plan.
TypeHosted platformHosted platform
IsolationThe trust page states browser automation runs in isolated, containerised environments (the per-session boundary is not described); Enterprise offers network isolation and dedicated resources; the self-hosted image runs headless browsers inside DockerThe container or VM boundary is not documented; sessions draw from a global pool of warm Chrome instances, and the FAQ says a fresh browser gives process-level isolation while incognito contexts isolate cookies and storage
Open sourceYes (SSPL-1.0 OR Browserless Commercial License)No
Self-host / BYOCYes / Not documentedNo / No
SDKsJavaScript/TypeScript, Python, CLI, REST API, MCP serverJavaScript/TypeScript, REST API, MCP server
Cold start (vendor claim)Not documentedBlog states sessions come from a global pool of warm instances with no cold start waiting for a browser; no figure given
Max sessionMaximum session time per plan: 2 minutes (Free), 15 minutes (Prototyping), 30 minutes (Starter), 60 minutes (Scale); Enterprise not listedBrowser closes after 60 seconds of inactivity by default; keep_alive extends the inactivity timeout to at most 20 minutes
PersistencePersisted sessions and replays retained 1 to 90 days by plan; reconnects count as new connections; Authenticated Profiles save cookies, localStorage and IndexedDB for reuse across sessionsNone documented beyond reusing a live browser across requests (for example from a Durable Object); session recordings for debugging
Snapshots / pauseNot documented / Not documentedNot documented / Not documented
GPUGPU-enabled infrastructure listed for Enterprise onlyNot documented
NetworkingResidential proxies (6 units/MB) and datacenter proxies (2 units/MB); bring-your-own proxies from Prototyping; automatic captcha solving; stealth routesRuns on Cloudflare's edge near users; no proxy or stealth features documented
PricingUnits: 1 unit per 30 seconds of browser time per connection; captcha solve 10 units. Free $0: 1k units, 2 concurrent, 2-minute sessions. Prototyping $25/month (annual): 20k units, 10 concurrent, 15-minute sessions, $0.0020 per extra unit. Starter $140/month: 180k units, 40 concurrent, 30-minute sessions, $0.0017 overage. Scale $350/month: 500k units, 100 concurrent, 60-minute sessions, $0.0015 overage. Enterprise: custom, private deployment or self-hosting licenceWorkers Free: 10 minutes of browser time per day, 3 concurrent browsers. Workers Paid: 10 browser hours per month included then $0.09 per additional hour; 10 concurrent browsers (averaged monthly) included then $2.00 per additional browser; up to 200 concurrent per account
Free tierFree plan: 1,000 units, 2 concurrent browsers, 2-minute sessions; open-source Docker image free for non-commercial useWorkers Free: 10 minutes of browser time per day, 3 concurrent browsers, 1 new browser every 20 seconds
ComplianceSOC 2 Type II; GDPR; HIPAA-compatible deployments with BAA on EnterpriseNot documented
RegionsShared fleet: US West (SFO, default), Europe UK (LON), Europe Amsterdam (AMS); private fleet adds US East (NYC)Cloudflare global network; sessions open near the user
Company headquartersWashington, United StatesSan Francisco, California, United States
Good fit forExisting Puppeteer, Playwright or Selenium automations that want a managed or self-hosted browser poolScreenshots, scraping and short agent browsing from Workers without running a browser fleet

Verified November 14, 2026 from each provider’s documentation. Cold-start figures are vendor claims, not our measurements.

Which should you choose?

Reasons to choose Browserless

  • You want to keep existing Puppeteer, Playwright or Selenium code unchanged
  • You need Firefox and WebKit as well as Chrome
  • You want a Docker image you can run on your own infrastructure
  • You need European endpoints and SOC 2 Type II

Reasons to choose Cloudflare Browser Run

  • You already run on Cloudflare Workers and want a browser binding
  • You need one-shot screenshot, PDF or scrape endpoints without infrastructure
  • You want edge-local sessions near end users
  • You want a free daily allowance for light use

Trade-offs to check first

  • Browserless: The trust page describes containerised browser environments but not the per-session boundary
  • Browserless: Sessions are capped at 2 minutes on Free and 60 minutes at most on self-serve plans
  • Cloudflare Browser Run: The container or VM boundary around a browser is not documented
  • Cloudflare Browser Run: Browsers close after 60 seconds of inactivity by default, extendable to 20 minutes with keep_alive

Both are worth piloting with your own image and region. See the full Browserless profile and Cloudflare Browser Run profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Browserless or Cloudflare Browser Run better for AI agents?
Neither is better for every workload. Browserless suits existing Puppeteer, Playwright or Selenium automations that want a managed or self-hosted browser pool. Cloudflare Browser Run suits screenshots, scraping and short agent browsing from Workers without running a browser fleet.
What is the difference between Browserless and Cloudflare Browser Run?
Browserless is open source (SSPL-1.0 OR Browserless Commercial License); Cloudflare Browser Run is not. Browserless documents a self-hosted option; Cloudflare Browser Run does not. Session length: 2 min to 60 min by plan (Browserless) versus 60 s idle, 20 min keep_alive (Cloudflare Browser Run). Only Browserless lists Python and CLI.
Which is open source, Browserless or Cloudflare Browser Run?
Browserless is open source (SSPL-1.0 OR Browserless Commercial License); Cloudflare Browser Run is not open source.
How do Browserless and Cloudflare Browser Run isolate code?
Browserless: The trust page states browser automation runs in isolated, containerised environments (the per-session boundary is not described); Enterprise offers network isolation and dedicated resources; the self-hosted image runs headless browsers inside Docker. Cloudflare Browser Run: The container or VM boundary is not documented; sessions draw from a global pool of warm Chrome instances, and the FAQ says a fresh browser gives process-level isolation while incognito contexts isolate cookies and storage.
How does Browserless pricing compare with Cloudflare Browser Run?
Browserless: Units: 1 unit per 30 seconds of browser time per connection; captcha solve 10 units. Free $0: 1k units, 2 concurrent, 2-minute sessions. Prototyping $25/month (annual): 20k units, 10 concurrent, 15-minute sessions, $0.0020 per extra unit. Starter $140/month: 180k units, 40 concurrent, 30-minute sessions, $0.0017 overage. Scale $350/month: 500k units, 100 concurrent, 60-minute sessions, $0.0015 overage. Enterprise: custom, private deployment or self-hosting licence. Cloudflare Browser Run: Workers Free: 10 minutes of browser time per day, 3 concurrent browsers. Workers Paid: 10 browser hours per month included then $0.09 per additional hour; 10 concurrent browsers (averaged monthly) included then $2.00 per additional browser; up to 200 concurrent per account. Rates change, so check the Browserless and Cloudflare Browser Run pricing pages before deciding.
Do Browserless and Cloudflare Browser Run support GPUs?
Browserless: GPU-enabled infrastructure listed for Enterprise only. Cloudflare Browser Run: Not documented.
Can you self-host Browserless or Cloudflare Browser Run?
Browserless can be self-hosted; Cloudflare Browser Run does not document a self-hosted option.
How long can sessions run on Browserless and Cloudflare Browser Run?
Browserless: Maximum session time per plan: 2 minutes (Free), 15 minutes (Prototyping), 30 minutes (Starter), 60 minutes (Scale); Enterprise not listed. Cloudflare Browser Run: Browser closes after 60 seconds of inactivity by default; keep_alive extends the inactivity timeout to at most 20 minutes.

Sources

  1. browserless.io
  2. browserless.io/pricing
  3. browserless.io/about
  4. browserless.io/trust
  5. developers.cloudflare.com/browser-run/
  6. developers.cloudflare.com/browser-run/limits/
  7. developers.cloudflare.com/browser-run/pricing/
  8. developers.cloudflare.com/browser-run/get-started/

Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 14, 2026. Confirm anything that matters in the provider’s own documentation.

Cite this page

Agent Sandboxes. (2026). Browserless vs Cloudflare Browser Run. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/browserless-vs-cloudflare-browser-rendering/