Skip to content

Update limits.mdx #24747

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 28, 2025
Merged

Update limits.mdx #24747

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 8 additions & 5 deletions src/content/docs/browser-rendering/platform/limits.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,9 @@ To increase this limit, you will need to [upgrade to a Workers Paid plan](/worke
| Concurrent browsers per account (Workers Bindings only) | 3 per account |
| New browser instances per minute (Workers Bindings only) | 3 per minute |
| Browser timeout | 60 seconds |
| Total requests per min (REST API only) | 6 per minute |
| Total requests per min (REST API only) | 6 per minute [^1] |

[^1]: Rate limits are enforced with a fixed **per-second fill rate**. For example, a limit of 60 requests per minute translates to **1 request per second**. This means you cannot send all 60 requests at once; the API expects them to be spread evenly over the minute. If your account has a custom higher limit, it will also be enforced as a per-second rate.

:::note[Note on browser timeout]
By default, a browser will time out if it does not get any [devtools](https://chromedevtools.github.io/devtools-protocol/) command for 60 seconds, freeing one instance. Users can optionally increase this by using the [`keep_alive` option](/browser-rendering/platform/puppeteer/#keep-alive). `browser.close()` releases the browser instance.
Expand All @@ -35,12 +37,13 @@ The limits for Browser Rendering will continue to be raised over time. In the me

| Feature | Limit |
| -------------------------------------- | ------------------- |
| Concurrent browsers per account (Workers Bindings only) | 10 per account [^1] |
| New browser instances per minute (Workers Bindings only) | 10 per minute [^1] |
| Concurrent browsers per account (Workers Bindings only) | 10 per account [^2] |
| New browser instances per minute (Workers Bindings only) | 10 per minute [^2] |
| Browser timeout | 60 seconds |
| Total requests per min (REST API only) | 60 per minute [^1] |
| Total requests per min (REST API only) | 60 per minute [^1] [^2] |

[^1]: Contact our team to request increases to this limit.
[^1]: Rate limits are enforced with a fixed **per-second fill rate**. For example, a limit of 60 requests per minute translates to **1 request per second**. This means you cannot send all 60 requests at once; the API expects them to be spread evenly over the minute. If your account has a custom higher limit, it will also be enforced as a per-second rate.
[^2]: Contact our team to request increases to this limit.

:::note[Note on browser timeout]
By default, a browser will time out if it does not get any [devtools](https://chromedevtools.github.io/devtools-protocol/) command for 60 seconds, freeing one instance. Users can optionally increase this by using the [`keep_alive` option](/browser-rendering/platform/puppeteer/#keep-alive). `browser.close()` releases the browser instance.
Expand Down