Browser Run, the serverless headless browser service on Cloudflare’s global network, has undergone a major transformation. By migrating to Cloudflare Containers, the team unlocked dramatic improvements in speed, scalability, and reliability—all without requiring any changes from existing users. Here are the five critical enhancements you need to know about, from higher concurrency limits to a more responsive architecture.
1. What Is Browser Run and Why Does It Matter?
Browser Run lets developers programmatically control and interact with headless browser instances running on Cloudflare’s edge. It’s used for end-to-end testing, safe investigation of suspicious URLs, PDF rendering, screenshots, and content extraction. More recently, it has become a backbone for AI agents that need to browse the web autonomously. With this container‑based upgrade, Browser Run is positioned as the go‑to platform for responsible, large‑scale automated browsing.
2. What Changed Under the Hood: From Shared Infrastructure to Dedicated Containers
Previously, Browser Run shared infrastructure with Browser Isolation (BISO). That created several pain points: BISO’s larger container images slowed startup times; its browsers weren’t globally distributed enough, hurting latency and resiliency; and the long, steady sessions typical of BISO clashed with Browser Run’s short, spiky usage, causing scaling bottlenecks. By moving to Cloudflare Containers—powered by Durable Object (DO) containers—the team isolated Browser Run’s workload, eliminating these conflicts and enabling faster iteration.
3. How the Migration Happened (Without Downtime)
The migration was gradual and risk‑free. A Worker was inserted into the request path to serve Container‑based browsers to a small set of users alongside the old BISO ones. This dual‑support phase allowed the team to compare performance, isolate bugs, and build confidence. They first enabled Container browsers for Quick Actions endpoints, then for Workers binding on free accounts, followed by pay‑as‑you‑go users, and finally all contract customers—all without any redeployment or changes on the customer side.
4. Performance and Scalability Gains: The Numbers
The results speak for themselves. You can now spin up 60 browsers per minute via the Workers binding and run up to 120 concurrently—a 4‑fold increase over the previous limit. Quick Action response times dropped by more than 50%. These improvements are live today, with no action needed from developers. Additionally, the new architecture enables faster shipping of fixes and features, because the team no longer has to coordinate with the BISO release cycle.
5. What This Means for Your Workflows and the Future
For developers, these upgrades translate to faster E2E test suites, more responsive AI agent interactions, and the ability to run large‑scale web scraping or security investigations without hitting artificial ceilings. The team is now able to iterate more quickly, so users can expect even more improvements in the near future. By building on Cloudflare’s own platform, Browser Run also helps Cloudflare iron out any rough edges before exposing them to external customers.
Browser Run’s container‑powered evolution is a win for developers who need reliable, scalable headless browsers. Whether you’re running a hundred parallel tests or orchestrating AI web agents, these changes deliver concrete speed and concurrency enhancements—all without breaking your existing code. Check the official docs to start leveraging the new limits today.