Browser Run levels up: 200 concurrent browsers, 3x faster spin-up!

Hi, it's me! Today I found a small-but-useful update to Cloudflare's headless browser automation service. Let's take a look!

Cloudflare Changelog developers.cloudflare.com

What was announced?

The Cloudflare Changelog announced higher default limits for Browser Run. Browser Run lets you automate headless browsers on Cloudflare's global network — you can run full browser sessions for interactive workflows, or use Quick Actions for one-shot tasks like screenshots, PDFs, and capturing page content. Starting August 20, 2026, Workers Paid plan users get higher default limits.

The story so far

Until now, the default limits for Workers Paid plan users were:

• Concurrent browsers: 120
• New browser instances launched: 1 per second
• Quick Actions requests: 10 per second

Workloads that needed to run many browser sessions in parallel, or that hit Quick Actions repeatedly, could bump into these limits.

What changes

The new default limits are:

• Concurrent browsers: 120 → 200
• New browser instances launched: 1 → 3 per second
• Quick Actions requests: 10 → 30 per second

Concurrency is up about 1.7x, while launch speed and Quick Actions throughput both tripled. You can now run hundreds of browser sessions in parallel, spin up new browsers faster, and process three times as many Quick Actions per second.

Dive Deep

These are default limits, not hard maximums. If your workload needs even more concurrent browsers, you can request higher limits from Cloudflare.

Wrap-up

• Browser Run's default limits for Workers Paid plan users were raised
• Concurrent browsers: 120 → 200
• New browser launches: 1 → 3 per second
• Quick Actions: 10 → 30 per second
• These are defaults, and you can request even higher limits if needed

If you're running scraping or screenshot pipelines on Cloudflare's Browser Run, this update quietly makes your life easier!