Browserless · Rate Limits

Browserless Rate Limits

Rate-limit policy for the Browserless cloud service. Browserless enforces three primary control surfaces: (1) maximum concurrent browser sessions per token, (2) monthly unit allotments per plan, and (3) max-session-time per individual browser. Excess sessions are queued or rejected with HTTP 429. Unit overages apply per-tier overage pricing rather than throttling.

Browserless Rate Limits is the machine-readable rate-limit profile for Browserless on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 10 rate-limit definitions, across the free, prototyping, starter, scale, and enterprise tiers, measuring concurrent_sessions, units, and minutes.

The profile also includes response codes documented for throttled, quotaExceeded, and serviceUnavailable.

Tagged areas include Headless Browser, Browser Infrastructure, Web Automation, BrowserQL, and Puppeteer.

10 Limits Throttle: 429 Quota: 429
Headless BrowserBrowser InfrastructureWeb AutomationBrowserQLPuppeteerPlaywrightSeleniumRate LimitingQuotasThrottlingConcurrency

Limits

Free Tier Concurrency api-token
concurrent_sessions · instant
2
Free Tier Monthly Units api-token
units · month
1000
Free Tier Max Session Time session
minutes · session
1
Prototyping Tier Concurrency api-token
concurrent_sessions · instant
15
Prototyping Tier Monthly Units api-token
units · month
20000
Starter Tier Concurrency api-token
concurrent_sessions · instant
40
Starter Tier Monthly Units api-token
units · month
180000
Scale Tier Concurrency api-token
concurrent_sessions · instant
100
Scale Tier Monthly Units api-token
units · month
500000
Enterprise Concurrency contract
concurrent_sessions · instant
custom