Skip to content

Update limits.mdx #26332

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

Open
wants to merge 2 commits into
base: production
Choose a base branch
from
Open

Update limits.mdx #26332

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ffd78a5
Update limits.mdx
kathayl Nov 5, 2025
47d7b75
Update limits.mdx
kathayl Nov 5, 2025
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
11 changes: 7 additions & 4 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 @@ -44,10 +44,10 @@ The limits for Browser Rendering will continue to be raised over time. In the me
| Concurrent browsers per account (Workers Bindings only) | 30 per account [^1] [^2] |
| New browser instances per minute (Workers Bindings only) | 30 per minute [^1] [^2] |
| Browser timeout | 60 seconds |
| Total requests per min (REST API only) | 180 per minute [^1] [^2] |
| Total requests per min (REST API only) | 180 per minute [^2] [^3] |

[^1]: Rate limits are enforced with a fixed **per-second fill rate**. For example, a limit of 180 requests per minute translates to **3 requests per second**. This means you cannot send all 180 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.
[^2]: Rate limits are enforced with a fixed **per-second fill rate**. For example, a limit of 180 requests per minute translates to **3 requests per second**. This means you cannot send all 180 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 at a per-second rate.
[^3]: 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 Expand Up @@ -84,7 +84,10 @@ If you recently upgraded to the [Workers Paid plan](/workers/platform/pricing/)

### Error: `429 Too many requests`

When you make too many requests in a short period of time, Browser Rendering will respond with HTTP status code `429 Too many requests`.
When you make too many requests in a short period of time, Browser Rendering will respond with HTTP status code `429 Too many requests`.

Rate limits are enforced with a fixed **per-second fill rate**. For example, a limit of 180 requests per minute translates to **3 requests per second**. This means you cannot send all 180 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 at a per-second rate.

The response includes a `Retry-After` header, which specifies how many seconds to wait before retrying. You can view your account's rate limits on the [Limits](/browser-rendering/platform/limits/) page.

The example below demonstrates how to handle rate limiting gracefully by reading the `Retry-After` value and retrying the request after that delay.
Expand Down
Loading