10 Game-Changing Improvements in Browser Run with Cloudflare Containers
Browser Run has undergone a major transformation. By rebuilding on Cloudflare’s Containers, the service now delivers higher limits, faster responses, and rock-solid reliability—all without any changes on your end. Here are ten things you need to know about this upgrade.
1. 4× Higher Concurrent Browser Limits
You can now spin up 60 browsers per minute via the Workers binding and run up to 120 concurrently—that’s four times the previous limit. Whether you’re running end-to-end tests or handling bursts from AI agents, the platform scales effortlessly. And the best part? No code changes needed. These improvements are live right now.
2. 50% Faster Quick Action Responses
Quick Actions like screenshots, content extraction, and PDF rendering now complete in half the time. The shift to Cloudflare Containers optimized request routing and reduced latency. For developers, this means faster feedback loops in testing and more responsive automated workflows.
3. Better Reliability Through Global Distribution
Previously, Browser Run shared infrastructure with Browser Isolation, which wasn’t optimized for global reach. Now, browsers run closer to your users on Cloudflare’s network, improving resiliency. The container-based architecture ensures that if one region has issues, traffic automatically fails over to another.
4. What Exactly Is Browser Run?
For those new to the feature: Browser Run lets you programmatically control headless browsers on Cloudflare’s edge. Use it for end-to-end testing, investigating suspicious URLs, rendering PDFs, or powering AI agents that need to interact with web pages. It’s designed to be secure, scalable, and easy to integrate via Workers.
5. The Infrastructure Shift: Why Containers?
The original setup shared resources with Browser Isolation (BISO). While technically similar, BISO’s larger container images slowed startup times. More critically, BISO’s long, steady sessions clashed with Browser Run’s short, spiky usage, causing scaling bottlenecks. Moving to Cloudflare Containers solved these conflicts.
6. Solving the Spiky vs. Steady Usage Clash
BISO users typically keep sessions open for extended periods; Browser Run launches browsers for quick tasks. This mismatch made it hard to allocate resources efficiently. The new container-based platform can handle bursty, short-lived workloads without impacting other services, ensuring availability even during peak demand.
7. Built on Durable Object–Enabled Containers
The migration was possible thanks to Cloudflare’s internal release of Durable Object (DO)–enabled Containers in open beta last year. This allowed Browser Run’s team to adopt the technology early and refine it. The result: a more robust platform that benefits both internal products and external customers.
8. A Phased, Careful Migration
Rather than a big bang, the team inserted a Worker in the request path to route some traffic to container-powered browsers alongside the old BISO ones. This dual-support phase let them compare performance, isolate bugs, and gain confidence. Rollouts started with Quick Actions, then free accounts, then pay-as-you-go, and finally contract customers.
9. Real Performance Data: the Proof
During migration, the team collected metrics side by side. The container-based browsers consistently showed lower latency and faster startup times. Quick Actions, in particular, saw the 50% improvement mentioned earlier. The data confirmed that the infrastructure change was worth the effort.
10. Zero Effort for Customers
Perhaps the best part: you don’t have to do anything. All existing Workers bindings continue to work without any changes or redeployments. The transition was designed to be transparent. Your browser scripts now run faster and more reliably—automatically.
These upgrades make Browser Run a stronger platform for developers. Whether you’re testing, scraping, or building AI agents, you’ll benefit from the increased limits, lower latency, and improved scalability—all powered by Cloudflare Containers.