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, in the API Commons Rate Limits shape.
It captures 10 rate-limit definitions, across the free, prototyping, starter, scale, and enterprise tiers, measuring concurrent_sessions, units, and minutes.
Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes response codes documented for throttled, quotaExceeded, and serviceUnavailable.
Tagged areas include Headless Browser, Browser Infrastructure, Web Automation, BrowserQL, and Puppeteer.
limitremainingresetretryAfter
generated, dated 2026-05-25.
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.