Cloudflare's Browser Run Gets Massive Performance Boost After Container Migration

Cloudflare today announced a major upgrade to its Browser Run service, now running on the company's own Container platform. The move delivers a 4x increase in concurrent browser limits and cuts response times by more than half, the company confirmed.

Developers can now spin up 60 browsers per minute via the Workers binding and run up to 120 concurrently—quadrupling the previous cap. Quick Action response times have dropped over 50%, and all improvements are live immediately with no configuration changes required.

“This is a game-changer for developers who rely on automated browsers for testing, security, and AI agent tasks,” said a Cloudflare spokesperson. “By rebuilding on Containers, we’ve eliminated the scaling bottlenecks that held us back.”

Background: What is Browser Run?

Browser Run lets developers programmatically control headless browser instances across Cloudflare’s global network. It supports end-to-end web testing, suspicious URL investigation, PDF rendering, screenshot capture, and content extraction.

Recently, it has become critical for AI agents that need to interact with the web. The service was originally built on shared infrastructure with Cloudflare’s Browser Isolation (BISO) product, which caused performance and reliability issues.

“BISO’s larger container images slowed startup, and its long, steady sessions clashed with Browser Run’s short, spiky usage,” the spokesperson explained. “We outgrew that setup.”

The Migration to Cloudflare Containers

Cloudflare began by inserting a Worker in the request path to route some users to Container-powered browsers, while others remained on BISO. This dual-support approach allowed the team to compare performance and isolate bugs.

“We needed to validate stability before rolling out fully,” the spokesperson said. “We gradually moved Quick Actions, then Workers binding connections—starting with free accounts, then pay-as-you-go, and finally contract customers—without any required action from existing users.”

Challenges Overcome: Performance and Scale

Previously, BISO browsers lacked optimal global distribution, which hurt resiliency and latency. The shared infrastructure created scaling bottlenecks and availability delays, especially during traffic spikes.

By moving to Durable Object (DO)-enabled Containers, Cloudflare resolved these issues. “The new architecture allows us to ship fixes and features faster than ever,” the spokesperson added. “We’re building on our own platform to feel and fix pain points before external customers do.”

What This Means for Developers

Developers using Browser Run now benefit from higher usage limits and significantly faster performance. The 120 concurrent browser capacity supports larger-scale testing and automation scenarios.

AI agents, in particular, gain a more responsive and reliable platform for web interactions. “This update makes Browser Run the go-to service for responsible, secure automated browsing at massive scale,” the spokesperson said.

No code changes or redeployments are needed. The improvements are live today across all plans.