10 Essential Insights into Browser Run’s Faster, More Scalable Container Era

Browser Run has undergone a major transformation by moving to Cloudflare Containers, resulting in dramatic performance gains, higher limits, and smoother operation. Whether you're already using it or just exploring, here are the ten key facts you need to know about this upgrade—no action required on your part.

1. What Is Browser Run?

Browser Run lets developers programmatically control headless browser instances running on Cloudflare’s global network. It’s ideal for end-to-end web app testing, safe investigation of suspicious URLs, PDF rendering, screenshot capture, and content extraction. Recently, it has become a critical tool for AI agents that need to interact with web pages. By moving to Cloudflare Containers, Browser Run now offers faster startup, higher concurrency, and better reliability—all without any changes to your existing code or workflows.

10 Essential Insights into Browser Run’s Faster, More Scalable Container Era — Source: blog.cloudflare.com

2. Massive Performance Leap: 4x Concurrent Browsers, 50% Faster Quick Actions

The new container-based architecture boosts the maximum concurrent browser count from 30 to 120—a fourfold increase. You can also spin up browsers at a rate of 60 per minute via the Workers binding. Quick Action response times have dropped by more than half, making tasks like screenshots or content extraction feel instantaneous. These improvements are live right now and require no configuration updates from your side.

3. Why We Moved Away from Browser Isolation

Previously, Browser Run shared infrastructure with Browser Isolation (BISO). While technically similar, BISO’s larger container images caused slower startups and longer development cycles. More importantly, BISO browsers were not optimally distributed globally, leading to latency and resiliency issues. BISO users typically run long, steady sessions, whereas Browser Run experiences short, spiky usage—this mismatch created scaling bottlenecks and availability delays. The migration to Containers solved all these problems.

4. The Smart Migration Strategy

We didn’t flip a switch overnight. Instead, we inserted a Worker into the request path to route some traffic to Container-powered browsers alongside the existing BISO ones. This dual support let us compare performance, catch bugs, and build confidence. We then rolled out Containers to Quick Actions first, followed by Workers binding connections for free accounts, then pay-as-you-go, and finally all contract customers. The result: a seamless transition with zero downtime and no user intervention.

5. Overcoming Scaling and Availability Bottlenecks

Initial deployments revealed issues with startup latency during usage spikes and uneven global availability. By leveraging Cloudflare’s new Durable Object–enabled Containers, we re-architected the system to handle rapid scaling. Browsers now spin up closer to users and are recycled efficiently, eliminating the previous bottlenecks. The architecture also ensures that bursty workloads no longer interfere with steady sessions from other services.

6. Faster Feature Development and Bug Fixes

With a dedicated container infrastructure, our engineering team can ship new features and fixes much more quickly. The old shared setup required careful coordination with BISO updates; now we control the entire stack. This means you’ll see regular improvements without waiting for major releases—all delivered transparently on Cloudflare’s global network.

7. No Changes Needed – It Works Today

This upgrade is fully backwards compatible. Your existing Workers bindings, Browser Run API calls, and Quick Action scripts continue to work exactly as before. No redeployment, no configuration update, no downtime. The performance and limit increases are automatically applied to your account. Simply continue using Browser Run as you always have—everything gets faster and more scalable instantly.

8. Use Cases That Benefit Most

End-to-end testing teams will see shorter test suite runtimes thanks to the 4x concurrency and faster response times. Security analysts can spin up more sandboxed browsers for URL investigations without throttling. AI agents that rely on web browsing can now execute parallel actions much quicker. And anyone using Browser Run for PDF rendering or content extraction will notice near-instant results even under heavy load.

9. We Built on Our Own Platform

Like many Cloudflare products, Browser Run now runs on Cloudflare’s own Containers service. This “eat our own dogfood” approach lets us identify and fix pain points before they affect external customers. It also ensures that the container features we release are battle-tested in production—benefiting both Browser Run users and anyone else deploying containers on the platform.

10. Looking Ahead: What This Means for the Future

The move to Containers is just the beginning. We now have a flexible foundation that will let us introduce even higher limits, new automation capabilities, and deeper integration with Cloudflare Workers and AI pipelines. Expect more granular billing, improved observability, and expanded regional availability. Browser Run is set to remain the go-to serverless browser platform for developers worldwide.

Conclusion: Browser Run’s rebuild on Cloudflare Containers delivers real, measurable improvements—higher concurrency, lower latency, and faster iteration—without any effort from you. Whether you’re testing, securing, or automating, these ten upgrades make the platform more powerful than ever. Explore the new capabilities today.