I have taken 226 screenshots today Does it mean I wasted $22.6 š
I have taken 226 screenshots today
Does it mean I wasted $22.6
Does it mean I wasted $22.6
MYou get 500 included.
TBut if I do that daily 
RCan you use proxies ?
Athey are working on keeping the session alive for longer. I saw a github branch https://github.com/cloudflare/puppeteer/commits/add_keep_alive_option by @sc
GitHub
Puppeteer Core fork that works with Cloudflare Browser Workers - Commits Ā· cloudflare/puppeteer
Abut best way is to just use durable objects I think. You can use the same session for parallel requests.
JI've filed https://github.com/cloudflare/puppeteer/issues/36 but it would be really good to see some upstream updates for this now that Browser Rendering has hit GA
GitHub
It seems like this fork of puppeteer is based on v17.0.0 (released August 2022), whereas the latest version is v22.6.3 (released yesterday, April 2024) Specifically, I'm looking to get deeper J...
Cdo we still need to request access here?
JYou don't. Browser Rendering is now available on all Workers paid plans
Cahhhhh think i missed that in the docs
Cthanks
.How can i find the browsers overview in the dashboard?
.I have gone through all sections and i cannot see where i can find that? I had beta access before but now i just cannot find it
.
JThe dashboard UI isn't enabled yet
.Oh
Aseems like it was enabled today... already used 300 session in 8 days while testing...
Ahopefully we will get the timeout option soon!
YFrom what I remember of sifting through the git log, the puppeteer version is tied to the Chrome version, and this is the version of puppeteer that matches the version of Chrome currently running on the Browser Rendering API. But I may be mistaken.
JQuite possible. It appears to be Chrome 110 when I last looked, but some kind of strategy and commitment to updates would be good.
CIs 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 devCThe doc did not mention I should use --remote
HRun npx-wrangler dev --remoteto test your Worker locally before deploying to Cloudflareās global network.
- 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
