Skip to content

Commit 8285609

Browse files
ToriLindsaysdnts
authored andcommitted
[Browser Rendering] Small pricing fixes (cloudflare#23805)
1 parent da8c28e commit 8285609

File tree

2 files changed

+13
-5
lines changed

2 files changed

+13
-5
lines changed

src/content/docs/browser-rendering/faq.mdx

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ To resolve: Pass your Browser binding into `puppeteer.launch`.
2020

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

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

2525
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.
2626

@@ -51,6 +51,12 @@ Returning an `HTMLElement` will not work.
5151

5252
:::
5353

54+
### What are the usage limits for Browser Rendering and how do I estimate my costs?
55+
56+
You can view the complete breakdown of concurrency caps, request rates, timeouts, and REST API quotas on the [limits page](/browser-rendering/platform/limits/).
57+
58+
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.
59+
5460
### Does Browser Rendering rotate IP addresses for outbound requests?
5561

5662
No. Browser Rendering requests originate from Cloudflares global network, but you cannot configure per-request IP rotation. All rendering traffic comes from Cloudflare IP ranges and requests include special headers [(`cf-biso-request-id`, `cf-biso-devtools`)](/browser-rendering/reference/automatic-request-headers/) so origin servers can identify them.

src/content/docs/browser-rendering/platform/limits.mdx

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ import { Render, Plan } from "~/components";
1414

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

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

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

26+
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.
27+
2628
## Workers Paid
2729

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

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

39-
[^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.
41+
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.
4042

4143
## Note on concurrency
4244

0 commit comments

Comments
 (0)