Live
Cloudflare Images Analytics Dashboard Adds 30‑Day Delivery VisibilityAmazon ECS Adds Native Blue/Green, Canary, and Linear Deployments for Safer Container RolloutsGemini agentic tools add LLM‑driven automation to Partner Marketing StudioGitHub Actions makes RHEL 9/10 runner images generally available for larger workloadsIntegrating Decider Models to Reduce Latency and Cost in AI Agent WorkflowsAWS Emulator Enables Local Testing of 200+ Services, but Lacks IAM ValidationSageMaker AI monitoring adds automatic latency drift, idle GPU, and configuration gap detection for inference endpointsEmbedding Proactive Governance into Enterprise‑Scale Agentic AICloudflare Images Analytics Dashboard Adds 30‑Day Delivery VisibilityAmazon ECS Adds Native Blue/Green, Canary, and Linear Deployments for Safer Container RolloutsGemini agentic tools add LLM‑driven automation to Partner Marketing StudioGitHub Actions makes RHEL 9/10 runner images generally available for larger workloadsIntegrating Decider Models to Reduce Latency and Cost in AI Agent WorkflowsAWS Emulator Enables Local Testing of 200+ Services, but Lacks IAM ValidationSageMaker AI monitoring adds automatic latency drift, idle GPU, and configuration gap detection for inference endpointsEmbedding Proactive Governance into Enterprise‑Scale Agentic AI
Cloudflare

Cloudflare Browser Run Capacity Expansion for Parallel Automation

AI SummaryPowered by AI

Browser Run on Cloudflare has increased default concurrency limits to support hundreds of parallel headless sessions and faster instance launches. This expansion allows platform teams to scale interactive workflows, scraping tasks, or content capture without hitting previous bottlenecks.

Cloudflare Browser Run is expanding its operational capacity for automated browser workloads on the global network. The service now supports significantly higher default limits for concurrent browsers and instance launch rates compared to prior configurations.

What Changed

The primary update involves a revision of published resource defaults available to users on Workers Paid plans. Previously, teams were restricted to 120 concurrent browser sessions with one new instance launched per second; these limits have been raised to allow up to 200 concurrent browsers and three instances per second.

Additionally, the throughput for Quick Actions—such as generating screenshots or capturing page content into PDFs—has increased from ten requests per second to thirty. These adjustments represent default thresholds rather than absolute maximums of the infrastructure.

Architecture and Operational Implications

Scalability Patterns:

  • Parallelism Strategy: Platform engineers can now design workflows that rely on higher degrees of parallelization without requiring immediate limit requests. This is particularly relevant for batch processing tasks like large-scale scraping or multi-region testing.

The ability to launch new browser instances faster reduces the latency between triggering a task and acquiring an available session, which improves throughput in CI/CD pipelines that depend on visual verification steps.

What This Means For Practitioners

If your current workload is constrained by these specific limits, you may now be able to proceed with existing automation scripts without architectural changes. However, practitioners should monitor their actual usage against the new defaults; if demand exceeds 200 concurrent sessions or three instances per second again, a limit increase request remains necessary.

For teams managing complex interactive workflows across Cloudflare's edge network, this change reduces friction in scaling browser automation horizontally. Review your current concurrency requirements to determine if you are ready for the expanded capacity immediately.

Originally published atCloudflare Developer Platform