You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/browser-rendering/faq.mdx
+21-10Lines changed: 21 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,17 +18,9 @@ This error occurs because your Puppeteer launch is not receiving the Browser bin
18
18
19
19
1. Pass your Browser binding into `puppeteer.launch`, for example:
20
20
21
-
```
22
-
import browser from '@cloudflare/workers-browser-rendering';
23
-
const browserInstance = await puppeteer.launch({
24
-
browserWSEndpoint: browser.endpoint,
25
-
// other options
26
-
});
27
-
```
21
+
2. Ensure your account is on a [Workers Paid plan](https:/workers/platform/pricing/) so that Browser Rendering is enabled.
28
22
29
-
2. Ensure your account is on a [Workers Paid plan](https://developers.cloudflare.com/workers/platform/pricing/) so that Browser Rendering is enabled.
30
-
31
-
### Will browser rendering bypass Cloudflare's Bot Protection?
23
+
### Will Browser Rendering bypass Cloudflare's Bot Protection?
32
24
33
25
No, Browser Rendering requests are always identified as bots by Cloudflare and do not bypass Bot Protection. Additionally, Browser Rendering respects the robots.txt protocol, ensuring that any disallowed paths specified for user agents are not accessed during rendering.
34
26
@@ -60,3 +52,22 @@ Keep in mind that `page.evaluate` can only return primitive types like strings,
60
52
Returning an `HTMLElement` will not work.
61
53
62
54
:::
55
+
56
+
### What are the usage limits and pricing tiers for Cloudflare Browser Rendering and how do I estimate my costs?
57
+
58
+
#### Usage Limits
59
+
60
+
| Plan | Concurrent Browsers | New Instances/min | Browser Timeout | REST API Calls/min |
|**Free**| 3 per account | 3 per minute | 60 s | 6 per minute |
63
+
|**Paid**| 10 per account | 10 per minute | 60 s | 60 per minute |
64
+
65
+
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).
66
+
67
+
#### Pricing
68
+
69
+
Browser Rendering is currently free up to the limits above until billing begins. Pricing will be announced in advance.
70
+
71
+
### Does Browser Rendering rotate IP addresses for outbound requests?
72
+
73
+
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.
0 commit comments