Is there a separate pricing for the browser rendering api? I can't find anything on how much it will
Is there a separate pricing for the browser rendering api? I can't find anything on how much it will cost
COh. It's free untill they make the pricing public.
source
While you won’t be billed for the Browser Rendering API yet, we want to be transparent with you about costs you start buildingBut from their
Running Serverless Puppeteer with Workers and Durable Objects blog post back from 09/28/2023 it will cost $0.10/browser sessionsource
CIt says
beta in the dashboard too. IDKCCan I start using browser-rendering-api in a production app yet?
CI'm trying to run the get started
But I get the error
Is there a working example I can try running? Cloudflare should fix their examples on the docs page.
screenshot code - linkBut I get the error
Cannot read properties of undefined (reading 'fetch')
Is there a working example I can try running? Cloudflare should fix their examples on the docs page.
Cloudflare Docs
By following this guide, you will create a Worker that uses the Browser Rendering API to take screenshots from web pages. This is a common use case …
CYou need a cloudflare workers paid account to get access to the browser rendering API. If you have that, then just visit the docs page to get started. FYI, it didn't "just work" for me.
HJust to confirm, you are using —remote, right?
CI'm running
wrangler devThe doc did not mention I should use --remote
HRun npx-to test your Worker locally before deploying to Cloudflare’s global network.wrangler dev --remote
- Test | Deploy a Browser Rendering Worker
HCSorry, 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 per months - where one unit = 30 seconds
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:
Requests: Alarm DO every 10 seconds = 259,200 pings / month. The first 1 million pings are free = $0 or $0.03888 (if you exceed free tier) - 259,200 requests / 1,000,000 = 0.2592 million requests * $0.15 = $0.03888Time: 30 days * 24 hours/day * 3600 seconds/hour = 2,592,000 secondsCompute Duration: The DO is active for 2,592,000 seconds. Converting to GB-seconds: 2,592,000 seconds * 128 MB / 1 GB = 331,776 GB-s. The first 400,000 GB-s are free = $0 or $4.1472 (if you exceed free tier) - 2,592,000 seconds * 128 MB / 1 GB => 331,776 GB-seconds / 1,000,000 => 0.331776 million GB-seconds * $12.50 = $4.1472Estimated 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
getRandomSession function in the reuse browser example, which filter out the existing connected browser sessions using connectionIdBut, in a worker I am just capturing a screenshot using
queue() with single page and closes that immediately. So I should be able to re-use the browser in multiple worker as there might be 10-15 pages without any issue I guess in same browser. Or it's limited to single connection only and I will get error if I try to use a browser which is currently in use on any other worker?
VI tried to use the reuse session example to capture screenshot for 100s of url, the
page.goto randomly freeze and worker stops processing any more URL from queue() or 15 minutesV
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
