10 Game-Changing Upgrades for Browser Run on Cloudflare Containers

Browser Run has undergone a major transformation. By rebuilding on Cloudflare's Containers, the platform now delivers dramatically faster performance, higher limits, and greater reliability. In this article, we break down the ten most important improvements and what they mean for developers, from speed gains to scalability leaps. Read on to discover how these changes can supercharge your headless browser workflows.

1. What Is Browser Run? A Quick Refresher

Browser Run lets developers programmatically control headless browser instances on Cloudflare's global network. It's ideal for end-to-end testing of web apps, investigating suspicious URLs securely, rendering PDFs, capturing screenshots, and extracting content. Recently, it has become a critical tool for AI agents that need to interact with websites in a human-like but automated way. Browser Run is designed to be the go-to platform for responsibly using automated browsers at massive scale, balancing performance with security.

2. From Shared Infrastructure to Dedicated Containers

Previously, Browser Run shared infrastructure with Browser Isolation (BISO). While technically similar, BISO's larger container images slowed startup times and development. More importantly, BISO browsers lacked optimal global distribution, which hurt resiliency and increased latency. BISO's long, steady sessions clashed with Browser Run's short, spiky usage, causing scaling bottlenecks and availability delays. Moving to Cloudflare Containers solved these tensions, giving Browser Run its own optimized environment.

3. 4x Higher Concurrent Browser Limits

One of the biggest wins is the drastic increase in 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 cap. This leap means you can handle more test scenarios, scrape more pages, or support more AI agent sessions without hitting rate limits. The upgrade is live now with no configuration changes needed on your end.

4. Quick Action Response Times Cut by More Than Half

Quick Actions — like taking a screenshot or extracting content — now respond more than 50% faster than before. This improvement comes directly from the container-based architecture, which reduces cold starts and optimizes request routing. For developers who rely on Browser Run for rapid, on-demand tasks, this speed boost translates to snappier user experiences and shorter wait times in automated pipelines.

5. No Changes Required — Instant Upgrade

Perhaps the most developer-friendly aspect: you don't need to modify any code. These improvements are live today. All existing Workers bindings and API calls continue to work exactly as before, but now benefit from the new performance and limits. Cloudflare seamlessly migrated traffic from the old infrastructure to the new containers, ensuring zero downtime and no required redeployments.

6. Faster Ship Cycles for New Features and Fixes

With the dedicated container platform, the team can now deploy updates more rapidly. Previously, shipping fixes or new features required coordination with the Browser Isolation release cycle, which slowed everything down. Now, Browser Run has its own pipeline, enabling quicker iterations. Users can expect more frequent improvements, bug fixes, and new capabilities without long waits.

7. A Gradual, Safe Migration Strategy

The migration to Containers was executed carefully to avoid disruptions. Cloudflare inserted a Worker into the request path to route a subset of users to the new container-powered browsers while others remained on the old BISO infrastructure. This dual-support phase allowed performance comparisons and bug isolation. They gradually rolled out to Quick Actions endpoints first, then free account Workers bindings, followed by pay-as-you-go, and finally all contract customers — each step validated stability before expanding.

8. Overcoming Performance and Scale Bottlenecks

Under the old shared setup, Browser Run's spiky usage patterns created scaling bottlenecks. Browsers took longer to become available because BISO's steady-state sessions consumed resources. The new container architecture eliminates these bottlenecks by provisioning browsers on demand, with faster startup times and better global distribution. The result is higher reliability and lower latency, especially during peak usage.

9. Enabled by Cloudflare's Own Platform (Dogfooding)

Cloudflare is committed to building on its own platform — a practice known as dogfooding. By migrating Browser Run to Durable Object-enabled Containers (announced in open beta last year), the team could test and refine the same infrastructure that external customers will use. This approach helps identify and fix pain points before they affect anyone else, ensuring a more robust product for all.

10. Future Outlook: Continuous Improvement

This container migration is just the beginning. With faster ship cycles and a scalable foundation, Browser Run is poised to extend its capabilities further. Expect more advanced features for AI agent interactions, better integration with Workers, and even tighter security controls. The performance gains and higher limits open doors for new use cases, from large-scale web scraping to complex multi-browser testing scenarios.

Browser Run's move to Cloudflare Containers marks a significant leap forward. Whether you're running end-to-end tests, powering AI agents, or capturing screenshots at scale, these ten improvements deliver tangible benefits: higher concurrency, faster responses, and a more reliable service — all without requiring any code changes. Stay tuned for what comes next as the platform continues to evolve.