Breaking: Browser Run Now Up to 4x Faster and More Scalable
Cloudflare has dramatically upgraded Browser Run by rebuilding it on its own Container platform, achieving a 4x increase in concurrent browser limits and over 50% faster response times for quick actions, the company announced today.
Developers can now spin up 60 browsers per minute via the Workers binding and run up to 120 concurrently—a fourfold jump from the previous cap. The improvements go live immediately, requiring no code changes from users.
“This is a leap forward in performance and reliability for any application relying on automated browsers—from testing to AI agents,” said Jordan Michaels, Senior Product Manager at Cloudflare. “We’re shipping fixes and features faster than ever.”
Background: Why the Move Was Necessary
Browser Run lets developers programmatically control headless browsers on Cloudflare’s global network—used for end-to-end testing, investigating suspicious URLs, rendering PDFs, and capturing screenshots. It’s also become a critical tool for AI agents interacting with the web.
Previously, Browser Run shared infrastructure with Browser Isolation (BISO). That proved problematic: BISO’s larger container images slowed startup, and its long, steady sessions clashed with Browser Run’s short, spiky usage, creating scaling bottlenecks and latency issues. Additionally, browsers lacked optimal global distribution, hurting resiliency.
“We had outgrown the shared setup,” explained Michaels. “Building on Cloudflare Containers—our own platform—was the natural next step to remove those bottlenecks and give users a truly scalable solution.”
Migration to Cloudflare Containers
The team executed a gradual migration, inserting a Worker to route some requests to Container-powered browsers alongside the old BISO infrastructure. This allowed side-by-side performance testing and helped isolate bugs. They first enabled Container browsers for Quick Actions endpoints, then for Workers browser bindings on free accounts, followed by pay-as-you-go users, finally rolling out to all contract customers.
“The dual support during development was key,” said Michaels. “We could compare performance, catch issues early, and gain confidence—all with zero impact on existing users.”
What This Means for Developers
Immediate benefits include dramatically higher concurrency limits and faster response times. Quick Actions—like capturing screenshots or extracting content—now complete in less than half the time. The new infrastructure also enables faster shipping of features and fixes.
For AI agents that rely on Browser Run to browse the web, the performance boost means more responsive interactions and the ability to handle larger workloads simultaneously. End-to-end testing pipelines will see reduced wait times and fewer failures due to scale limits.
“We’re making Browser Run the go-to platform for responsible, secure, large-scale automated browsing,” added Michaels. “And we’re only getting started.”
Performance Data and Next Steps
Cloudflare provided internal metrics showing response times for Quick Actions dropped more than 50%. The concurrency limit of 120 browsers and spin-up rate of 60 per minute are now standard for all paying customers.
No changes to existing code or redeployments are required—the upgrade is transparent. Developers can check their Cloudflare dashboard to take advantage of the new limits immediately.
For more details, read the original announcement on Cloudflare’s blog.