Browser Run Powered by Cloudflare Containers: Faster, More Scalable, No Changes Needed
Browser Run, Cloudflare's platform for programmatic headless browser automation, has undergone a major upgrade. By migrating to Cloudflare Containers, it now offers 4x higher concurrency limits, 50% faster Quick Actions, and improved reliability—all without any action required from users. This Q&A covers what Browser Run is, why the migration happened, how it was executed, and what the improvements mean for developers.
- What exactly is Browser Run?
- What recent improvements have been made to Browser Run?
- Why was the move to Cloudflare Containers necessary?
- How was the migration carried out without disrupting users?
- What are the key benefits of using Cloudflare Containers for Browser Run?
- Are these improvements live now? Do users need to change anything?
What exactly is Browser Run?
Browser Run is a Cloudflare product that lets developers programmatically control and interact with headless browser instances running on Cloudflare's global network. It enables tasks like end-to-end testing of web applications, securely investigating suspicious URLs, rendering PDF documents, capturing screenshots, and extracting content. More recently, it has become a critical enabler for AI agents that need to interact with the web. Browser Run provides a Workers binding, allowing developers to launch browsers from Cloudflare Workers with minimal overhead. It's designed to handle short, spiky usage patterns efficiently, making it ideal for automation tasks at scale.
What recent improvements have been made to Browser Run?
Browser Run has been rebuilt on top of Cloudflare Containers, unlocking significant performance and scalability upgrades. Users can now spin up 60 browsers per minute via the Workers binding and run up to 120 concurrent browsers—a 4x increase over the previous limit. Additionally, Quick Action response times dropped more than 50%, meaning operations like screenshot capture or URL analysis are much faster. These improvements are live now with no configuration changes required from existing users. The migration also enables faster feature delivery and bug fixes.
Why was the move to Cloudflare Containers necessary?
Previously, Browser Run shared infrastructure with Browser Isolation (BISO), a product with different usage characteristics. BISO's larger container images led to slower startup times and hindered development speed. More critically, BISO browsers lacked optimal global distribution, which compromised both resiliency and latency for Browser Run. The two products also had conflicting traffic patterns: BISO users had long, steady sessions while Browser Run experienced short, spiky bursts. This created scaling bottlenecks and availability delays. By migrating to Durable Object (DO)-enabled Containers, Browser Run could decouple from BISO and achieve dedicated, optimized infrastructure that better matches its workload.
How was the migration carried out without disrupting users?
The migration was gradual and carefully staged. Cloudflare inserted a Worker in the incoming request path to route a subset of users to container-powered browsers alongside the existing BISO ones. This dual-support phase allowed the team to compare performance and isolate bugs. The rollout proceeded step by step: first, all Quick Actions endpoints were switched to Containers; next, the Workers browser binding for free accounts; then pay-as-you-go accounts; and finally, all contract customers. Each stage validated stability before expanding. Crucially, no existing Workers or customer configurations needed to be redeployed—the transition was completely transparent.
What are the key benefits of using Cloudflare Containers for Browser Run?
The shift to Cloudflare Containers brings several advantages. First, scalability is dramatically improved: the new infrastructure supports up to 120 concurrent browsers and 60 browser startups per minute, a 4x increase over the old limit. Second, performance receives a boost, with Quick Action response times more than halved. Third, reliability is enhanced because container browsers can be optimally distributed across Cloudflare's global network, reducing latency and improving fault tolerance. Finally, the decoupling from BISO means each product can be fine-tuned for its specific usage patterns—short, spiky for Browser Run versus long sessions for BISO—eliminating previous scaling conflicts. This also enables faster feature development and bug fixes.
Are these improvements live now? Do users need to change anything?
Yes, all the improvements are live and active as of this announcement. No action, code changes, or Worker redeployments are required from current Browser Run users. The migration was designed to be fully transparent—existing bindings, endpoints, and scripts continue to work as before, but now benefit from higher limits and faster performance automatically. Users who previously experienced rate limits of 30 concurrent browsers now automatically enjoy up to 120. Quick actions that took a second now respond in under half that time. For new users, the same advantages apply from day one. Cloudflare recommends checking the updated documentation for any optional configuration tweaks, but the core improvements are immediately available.