Skip to content

[Browser Rendering] Small pricing fixes #23805

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 2 commits into from
Jul 21, 2025
Merged

[Browser Rendering] Small pricing fixes #23805

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0e4f9a4
[Browser Rendering] Small pricing fixes
ToriLindsay Jul 18, 2025
a2e9d78
Merge branch 'production' into tori/browser-rendering-pricing-updates
ToriLindsay Jul 21, 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
6 changes: 3 additions & 3 deletions src/content/docs/browser-rendering/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ To resolve: Pass your Browser binding into `puppeteer.launch`.

### Will Browser Rendering bypass Cloudflare's Bot Protection?

No, Browser Rendering requests are always identified as bots by Cloudflare and do not bypass Bot Protection.
No, Browser Rendering requests are always identified as bots by Cloudflare and do not bypass Bot Protection.

If you are attempting to scan your **own zone** and need Browser Rendering to access areas protected by Cloudflare’s Bot Protection, you can create a [WAF skip rule](/waf/custom-rules/skip/) to bypass the bot protection using a header or a custom user agent.

Expand Down Expand Up @@ -51,11 +51,11 @@ Returning an `HTMLElement` will not work.

:::

### What are the usage limits and pricing tiers for Cloudflare Browser Rendering and how do I estimate my costs?
### What are the usage limits for Browser Rendering and how do I estimate my costs?

You can view the complete breakdown of concurrency caps, request rates, timeouts, and REST API quotas on the [limits page](/browser-rendering/platform/limits/).

By default, idle browser sessions close after 60 seconds of inactivity. You can adjust this with the [`keep_alive` option](/browser-rendering/platform/puppeteer/#keep-alive).
You can monitor your Browser Rendering usage in the [Cloudflare dashboard](https://dash.cloudflare.com). Go to **Compute (Workers)** > **Browser Rendering**. Then, you can use [the pricing page](/browser-rendering/platform/pricing/) to estimate your costs.

#### Pricing

Expand Down
10 changes: 6 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 @@ -14,7 +14,7 @@ import { Render, Plan } from "~/components";

Users on the [Workers Free plan](/workers/platform/pricing/) are limited to **10 minutes of browser rendering usage per day**.

To increase this limit, you’ll need to [upgrade to a Workers Paid plan](/workers/platform/pricing).
To increase this limit, you will need to [upgrade to a Workers Paid plan](/workers/platform/pricing).

| Feature | Limit |
| -------------------------------------- | --------------- |
Expand All @@ -23,6 +23,8 @@ To increase this limit, you’ll need to [upgrade to a Workers Paid plan](/worke
| Browser timeout | 60 seconds [^2] |
| Total requests per min (REST API only) | 6 per minute |

By default, a browser instance gets killed 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.

## Workers Paid

<Render file="limits-increase" product="browser-rendering" />
Expand All @@ -31,12 +33,12 @@ To increase this limit, you’ll need to [upgrade to a Workers Paid plan](/worke
| -------------------------------------- | ------------------- |
| Concurrent browsers per account (Workers Bindings only) | 10 per account [^1] |
| New browser instances per minute (Workers Bindings only) | 10 per minute [^1] |
| Browser timeout | 60 seconds [^2][^1] |
| Total requests per min (REST API only) | 60 per minute |
| Browser timeout | 60 seconds [^2] |
| Total requests per min (REST API only) | 60 per minute [^1] |

[^1]: Contact our team to request increases to this limit.

[^2]: By default, a browser instance gets killed 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.
By default, a browser instance gets killed 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.

## Note on concurrency

Expand Down