What changed? Cloudflare announced on that the default limits for Browser Run – its headless‑browser automation platform on the Workers network – have been increased for customers on the Workers Paid plan.
New default limits (vendor claim)
- Concurrent browsers: 200 (up from 120)
- New browser instances per second: 3 (up from 1)
- Quick Actions requests per second: 30 (up from 10)
These numbers are the new defaults; they are not hard caps. Customers with higher‑volume workloads can request custom limits through Cloudflare support.
Why it matters
Browser Run enables developers to run full browser sessions for interactive workflows or use lightweight Quick Actions for single‑request tasks such as screenshots, PDF generation, and page‑content extraction. Raising the concurrency and request rates means:
- More parallel browser sessions, useful for large‑scale testing, data‑scraping, or rendering workloads.
- Faster spin‑up of new browsers, reducing latency for on‑demand tasks.
- Three‑fold increase in Quick Actions throughput, which can lower overall processing time for batch jobs.
How to adjust limits
If the default limits are still insufficient, Cloudflare states that users can request higher limits via their support portal.
Bottom line
For teams already using Cloudflare Workers and Browser Run, the updated limits provide immediate capacity gains without additional cost, as long as they remain on the Paid plan. Organizations with heavy headless‑browser workloads should evaluate whether the new defaults meet their needs or if a custom limit request is warranted.