6 Transformative Improvements to Cloudflare's Browser Run: Speed, Scale, and Stability

Cloudflare’s Browser Run has been rebuilt on top of the company’s own Containers infrastructure, resulting in dramatic gains in performance, reliability, and capacity. Developers can now spin up browsers faster, run more concurrent sessions, and enjoy reduced latency for quick actions—all without any manual intervention. In this article, we break down the six most impactful changes, from the technical migration to the concrete numbers that matter for your workflows.

1. What is Browser Run?

Browser Run gives developers programmatic control over headless browser instances running across Cloudflare’s global network. It’s used for 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 tool for AI agents that need to interact with the web. By leveraging Cloudflare’s edge, Browser Run aims to be the go-to platform for responsibly using automated browsers at massive scale while maintaining security and low latency.

2. Why the Old Infrastructure Was Holding It Back

Before moving to Cloudflare Containers, Browser Run shared infrastructure with Browser Isolation (BISO). While technically similar, BISO’s larger container images slowed startup times and complicated development. More importantly, BISO browsers weren’t distributed optimally around the globe, which hurt resilience and increased latency. Furthermore, the usage patterns differed: BISO users typically maintained long, steady sessions, whereas Browser Run sessions were short and spiky. This mismatch created scaling bottlenecks and availability delays. The team needed a platform that could handle rapid spin-up and tear-down without interfering with BISO’s workloads.

3. A Gradual, Safe Migration to Cloudflare Containers

The migration began quietly by inserting a Worker into the request path that directed a subset of users to new Container-powered browsers while keeping others on BISO. This dual-support phase let the team compare performance, isolate bugs, and build confidence. Over time, they increased the percentage of traffic handled by Containers: first for Quick Actions endpoints, then for free accounts using the Workers browser binding, followed by pay-as-you-go accounts. Finally, all remaining contract customers were transitioned without any required changes to their existing workers or configurations. The gradual rollout ensured stability and allowed the team to address issues before full deployment.

4. Dramatically Higher Limits and Faster Response Times

The new infrastructure delivers a 4x increase in concurrency limits. Developers can now spin up 60 browsers per minute via the Workers binding and run up to 120 concurrent instances. Even more impressive, Quick Action response times have dropped by more than 50%. These improvements are available immediately—no code changes or redeployments needed. For end-to-end testing, security investigations, and PDF rendering, this means faster iteration and less waiting. The capacity boost also opens the door for more ambitious automation scenarios, such as large-scale web scraping or batch screenshot processing.

5. Faster Feature Delivery and Bug Fixes

By decoupling from BISO’s development cycle and using Cloudflare’s Containers with Durable Object support, the Browser Run team can now ship fixes and new features much faster. The new platform gives them full control over the environment, enabling custom optimizations and quicker iterations. Early results include better global distribution of browser instances, improved health checks, and more predictable scaling behavior. For developers, this means getting access to enhancements sooner and experiencing fewer regressions. The team has committed to building on Cloudflare’s own platform to identify and resolve pain points before they affect external customers.

6. No Action Required—All Improvements Are Live

One of the best parts: you don’t need to change anything. All the speed, capacity, and reliability gains are already live. Existing Workers using the browser binding will automatically benefit from the new limits and lower latencies. Quick Actions endpoints already respond faster. The migration was designed to be transparent, with no breaking changes. This “seamless upgrade” approach reflects Cloudflare’s philosophy of dogfooding its own products. The team has already proven that the Container-based architecture is more robust and scalable, and they expect to continue improving Browser Run without disrupting your workflows.

In summary, Cloudflare’s Browser Run has been supercharged by moving to Cloudflare Containers. Higher concurrency limits, faster response times, better global distribution, and quicker feature releases are now all part of the service. Whether you’re using it for testing, security, or AI agent interactions, these upgrades make Browser Run a more powerful tool—and you didn’t have to lift a finger.