> Run npx `wrangler dev --remote` to test your Worker locally before deploying to Cloudflare’s globa
Run npx-to test your Worker locally before deploying to Cloudflare’s global network.wrangler dev --remote
- Test | Deploy a Browser Rendering Worker
H
CSorry, I missed that. It works.
Do you know if the browser rendering API is currently charged? Will I have to pay if I use it in production?
Do you know if the browser rendering API is currently charged? Will I have to pay if I use it in production?
HBrowser Rendering is now available to all customers with a paid Workers plan. Each account is limited to running two new browsers per minute and two concurrent browsers at no cost during this period. Check our developers page to get started.- Browser Rendering API GA, rolling out Cloudflare Snippets, SWR, and bringing Workers for Platforms to all users | The Cloudflare Blog
CTy. Again, sorry for not reading through the whole announcement.
HAll good!
CHow would pricing evolve for long running browser sessions?
For example, an automated testing browser session + queue. I will only run a single browser session and use a queue to manage my tasks. But in this case a browser session can exist for multiple minutes.
Is it currently possible to run a long running browser session on cf api?
For example, an automated testing browser session + queue. I will only run a single browser session and use a queue to manage my tasks. But in this case a browser session can exist for multiple minutes.
Is it currently possible to run a long running browser session on cf api?
CPricing for existing headless browser APIs like browserless.io depend on
units
AWith do's, if you manage it properly, you should be able to use 2 sessions to get as many units as are on the start plan
C(180,000 units * 30 seconds)/ 60 seconds / 60 minutes / 24 hours = 62.5 days
So two browser sessions + a lot of DO million seconds.
So two browser sessions + a lot of DO million seconds.
CQuick math to run a browser session for a whole month:
Cost Estimate for 1 Month
Browser Sessions: 1 session for the whole month = $0 or $0.1 (if you exceed free tier)
Durable Objects Costs:
Estimated Total for 1 Month:
Cost Estimate for 1 Month
Browser Sessions: 1 session for the whole month = $0 or $0.1 (if you exceed free tier)
Durable Objects Costs:
RequestsTimeCompute DurationEstimated Total for 1 Month:
- $5 (workers paid plan)
- $4.28608 (if you exceed free tier)
CCBut concurrency is the key here. I don't have a usecase where I need to run a single session for a month - but instead use cloudflare's infra to many handle requests for a product (eg screenshot api). So only after cloudflare let us run 500 concurrent sessions will it be really useful.
Ayou know that you can run current requests on 1 do / 1 browser session? I am easily running 25ish current requests on one browser session. It just opens multiple pages and closes them after its done
CYou are already using it in production?
RIm curious on that also
AI had a hard time crashing it. I set the limit to 25 for myself to be save.
Also using it in production.
I did test it once with 100 to 1000 current pages. Crashed around 200ish.
Also using it in production.
I did test it once with 100 to 1000 current pages. Crashed around 200ish.
AI did page to pdf and page to screenshot and rxtracting page dom
Ron all 200 ?
JI don't know whose job this is, but there should be a space in the title 
J
Cthis is the channel for browser rendering api. The community forums have a generic feedback category
AWhats the timeline for expanding the limits for the amount of sessions allowed?
AAnyway to request higher limits? Happy to pay!
JIf I execute a Javascript function on a webpage using browser rendering and it will take too long to complete it so in this situation what will be the behaviour of a Cloudflare worker, like it will wait for the completion of that function which is been executed in browser session or it will simply kill itself due to some kind of timeout error or we can leave the browser session open and doing the work and leave the worker?
Jinteresting , it mean we can force a browser session to stay open as long as we want
DDid this become an open beta?
JIt’s now generally available to all workers paid plans
VCan I connect the same browser in multiple workers? I see the
But, in a worker I am just capturing a screenshot using
getRandomSessionconnectionIdBut, in a worker I am just capturing a screenshot using
queue()
VI tried to use the reuse session example to capture screenshot for 100s of url, the
page.gotoqueue()
Veven when I have timeout set explicitly in page.goto
const response = await page.goto(url, {
timeout: 15000,
waitUntil: "domcontentloaded",
});
const response = await page.goto(url, {
timeout: 15000,
waitUntil: "domcontentloaded",
});
VThe puppeteer has 30000 ms by default on launch, so is should timeout. instead the worker goes unresponsive for 15 minutes
AAny eta for:
- Customizing session timeout (i saw a branche for that on github)
- Getting more sessions?
Awhats the method to check for memory usage?
JI think browser.pages() is not able to detect how many pages are open in the current session. Is it a known bug?
JI have one page which is running currently but when I am executing the browser.pages() on same session its returning me a empty array ( length 0 )
Aawesome! 1 will help a lot!
Jwe implemented a cron trigger in the worker which is using browser-rendering api to execute specific commands to ensure session continuity. However, as shown in the screenshot, the connection that started at 4:42:23 will end at 4:42:25. Just three seconds after the end, the browser closes at 4:42:28, citing idle as the reason.
According to the documentation,
According to the documentation,
A browser instance gets killed if it does not get any command for 60 seconds, freeing one instance.
BIm testing the browserless api with the example screenshot worker. I cant get it to work when accessing a map tile url. It seems webgl is not supported by chromium. Has anyone been able to find a workaround for this? My hope is to use a browserless worker to make screenshots of maps for users.
Jmay be you can try using Google maps lite mode
https://www.google.com/maps/?force=litehttp://maps.google.com/?force=canvasBThanks but I'm trying to grab a screenshot of my own tileservice that use maplibre to render vector tiles to the browser. Maplibre uses webgl and when I grab a screenshot of the url I get a white blank screenshot.
I saw others ask about using webgl in browserless workers and it seems it hasnt been solved yet.
I saw others ask about using webgl in browserless workers and it seems it hasnt been solved yet.
MIt gives me error
text: 'workers.api.error.no_access_to_browser_worker [code: 10088]' Is this still in Private Beta?