Agent Sandboxesagentsandboxes.org
Head-to-head

Cloudflare Browser Run vs Lightpanda

Answer in brief

Choose Cloudflare Browser Run for screenshots, scraping and short agent browsing from Workers without running a browser fleet; choose Lightpanda for high-volume page fetching and crawling where memory and speed matter more than pixel-accurate rendering. Cloudflare Browser Run uses Not documented isolation; Lightpanda uses Not documented isolation and is open source.

By the Agent Sandboxes editors · Updated

Key differences between Cloudflare Browser Run and Lightpanda

  • Open source: Lightpanda is open source (AGPL-3.0); Cloudflare Browser Run is not.
  • Self-hosting: Lightpanda documents a self-hosted option; Cloudflare Browser Run does not.
  • Company headquarters: Cloudflare is based in San Francisco, United States; Lightpanda is based in Paris, France.
  • Session length: 60 s idle, 20 min keep_alive (Cloudflare Browser Run) versus 15 min per connection (Lightpanda).
  • SDKs and interfaces: Only Cloudflare Browser Run lists JavaScript/TypeScript. Only Lightpanda lists CLI.

What they have in common

  • Both are hosted platforms.
  • Both list REST API and MCP server.

Cloudflare Browser Run vs Lightpanda at a glance

AttributeCloudflare Browser RunLightpanda
What it isHeadless 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.A headless browser written from scratch in Zig (AGPL-3.0) with no graphical rendering, offered as a CDP endpoint on Lightpanda Cloud with a free 10-hour tier.
TypeHosted platformHosted platform
IsolationThe 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 storageNot documented for Lightpanda Cloud; locally Lightpanda runs as a single headless browser process or Docker container
Open sourceNoYes (AGPL-3.0)
Self-host / BYOCNo / NoYes / Not documented
SDKsJavaScript/TypeScript, REST API, MCP serverCLI, REST API, MCP server
Cold start (vendor claim)Blog states sessions come from a global pool of warm instances with no cold start waiting for a browser; no figure givenNot documented
Max sessionBrowser closes after 60 seconds of inactivity by default; keep_alive extends the inactivity timeout to at most 20 minutesA CDP connection to the cloud closes after 15 minutes on every plan; MCP sessions close after 5 minutes without a request
PersistenceNone documented beyond reusing a live browser across requests (for example from a Durable Object); session recordings for debuggingNone documented; the cloud console lists recent sessions and logs
Snapshots / pauseNot documented / Not documentedNot documented / Not documented
GPUNot documentedNo — the engine has no graphical rendering
NetworkingRuns on Cloudflare's edge near users; no proxy or stealth features documentedManaged proxy pool with country selection on the cloud, or bring your own proxy; local builds can block private networks and CIDRs
PricingWorkers 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 accountExplorer $0: 10 browser hours per month, 5 concurrent sessions. Builder $19/month: 300 hours then $0.08 per hour, 30 concurrent sessions. Enterprise: custom volume pricing, on-premise or private cloud. Usage counted by the second
Free tierWorkers Free: 10 minutes of browser time per day, 3 concurrent browsers, 1 new browser every 20 secondsExplorer plan: 10 browser hours per month, 5 concurrent sessions; the browser is free to self-host
ComplianceNot documentedNot documented
RegionsCloudflare global network; sessions open near the usereuwest (west Europe) and uswest (west US) cloud endpoints
Company headquartersSan Francisco, California, United StatesParis, France
Good fit forScreenshots, scraping and short agent browsing from Workers without running a browser fleetHigh-volume page fetching and crawling where memory and speed matter more than pixel-accurate rendering

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 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

Reasons to choose Lightpanda

  • You want a lightweight engine for crawling and scraping at volume
  • You need a free tier with real browser hours
  • You want to self-host an open-source browser without Chromium
  • You are running CDP scripts and only need a WebSocket endpoint

Trade-offs to check first

  • 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
  • Lightpanda: No graphical rendering, so screenshots return a placeholder image rather than a real render
  • Lightpanda: Passes about 80% of Chrome's Web Platform Tests subtest count (1.0 release post)

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

More comparisons

Frequently asked questions

Is Cloudflare Browser Run or Lightpanda better for AI agents?
Neither is better for every workload. Cloudflare Browser Run suits screenshots, scraping and short agent browsing from Workers without running a browser fleet. Lightpanda suits high-volume page fetching and crawling where memory and speed matter more than pixel-accurate rendering.
What is the difference between Cloudflare Browser Run and Lightpanda?
Lightpanda is open source (AGPL-3.0); Cloudflare Browser Run is not. Lightpanda documents a self-hosted option; Cloudflare Browser Run does not. Cloudflare is based in San Francisco, United States; Lightpanda is based in Paris, France. Session length: 60 s idle, 20 min keep_alive (Cloudflare Browser Run) versus 15 min per connection (Lightpanda). Only Cloudflare Browser Run lists JavaScript/TypeScript. Only Lightpanda lists CLI.
Which is open source, Cloudflare Browser Run or Lightpanda?
Cloudflare Browser Run is not open source; Lightpanda is open source (AGPL-3.0).
How do Cloudflare Browser Run and Lightpanda isolate code?
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. Lightpanda: Not documented for Lightpanda Cloud; locally Lightpanda runs as a single headless browser process or Docker container.
How does Cloudflare Browser Run pricing compare with Lightpanda?
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. Lightpanda: Explorer $0: 10 browser hours per month, 5 concurrent sessions. Builder $19/month: 300 hours then $0.08 per hour, 30 concurrent sessions. Enterprise: custom volume pricing, on-premise or private cloud. Usage counted by the second. Rates change, so check the Cloudflare Browser Run and Lightpanda pricing pages before deciding.
Do Cloudflare Browser Run and Lightpanda support GPUs?
Cloudflare Browser Run: Not documented. Lightpanda: No — the engine has no graphical rendering.
Can you self-host Cloudflare Browser Run or Lightpanda?
Lightpanda can be self-hosted; Cloudflare Browser Run does not document a self-hosted option.
How long can sessions run on Cloudflare Browser Run and Lightpanda?
Cloudflare Browser Run: Browser closes after 60 seconds of inactivity by default; keep_alive extends the inactivity timeout to at most 20 minutes. Lightpanda: A CDP connection to the cloud closes after 15 minutes on every plan; MCP sessions close after 5 minutes without a request.

Sources

  1. developers.cloudflare.com/browser-run/
  2. developers.cloudflare.com/browser-run/limits/
  3. developers.cloudflare.com/browser-run/pricing/
  4. developers.cloudflare.com/browser-run/get-started/
  5. lightpanda.io
  6. lightpanda.io/pricing
  7. github.com/lightpanda-io/browser
  8. lightpanda.io/docs/run-on-lightpanda-cloud/getting-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). Cloudflare Browser Run vs Lightpanda. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/cloudflare-browser-rendering-vs-lightpanda/