Scraping API PricesAll products / Cloudflare Browser Rendering
Cloudflare Browser Rendering pricing
What Cloudflare Browser Run does, how browser time and concurrency are metered, how to buy it, and priced cloud-browser alternatives.
Every available option was priced in advance from published vendor rules. Changing a control only switches between those checked options; nothing is sent anywhere and no account is needed.
Your job
What Cloudflare Browser Rendering counts
Nothing to count: Cloudflare Browser Rendering publishes no rate for a page fetch. Its 2 published billing meters price other work.
What you pay
Successes you want
100,000 pages
Your stated workload. Every vendor on this site is priced against this same number.
- × 1
Attempts you are billed for
100,000 requests
Cloudflare Browser Rendering does not bill failed fetches, so failures cost nothing here.
- ∅
Cash per month
Not comparable here
no published rate for request.basic
Bars share one linear scale across the 2 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.
Not comparable. This product publishes no rate for this kind of work.
no published rate for request.basic
This is a finding about what Cloudflare Browser Rendering publishes, not a gap in the data. It stays visible so a definitive market claim cannot quietly ignore it.
Published exact bills for comparable products
Same 100,000 JavaScript-rendered pages a month at a 95% success rate, ranked by what you would actually be billed. Unknown totals never enter the numeric order.
Every Cloudflare Browser Rendering plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Workers Paid | Not published | n/a | n/a | 10 browser_hour | 10 |
What consumes a unit
This is where a bill actually grows. One operation is not one billed unit, and the multiplier is published here rather than on the pricing page.
| Operation | Costs | Per | Source |
|---|---|---|---|
| browser.session_time | 0.09 usd | browser_hour | source |
| browser.concurrent_slot | 2 usd | monthly_average_browser | source |
What Cloudflare Browser Rendering does not publish
- The Workers Paid base-plan price is not a Browser Run-specific price and is not recorded here.
- Failure billing outside the documented waitForTimeout case is not published.
Product scope and returned result
Cloudflare renamed Browser Rendering to Browser Run. The product runs browser work inside Cloudflare’s developer platform. Quick Actions expose bounded operations, while Puppeteer, Playwright, and Chrome DevTools Protocol sessions provide direct browser control. The response depends on the operation: a Quick Action can return rendered page material, while a direct session returns control of a remote browser rather than one universal extraction schema. (Browser Run overview and pricing, retrieved 2026-07-26).
This makes Browser Run different from a request-only scraping API. It is useful when code needs browser execution, screenshots or rendered content in the Workers environment. It does not publish a single price per extracted page because it charges for browser duration and, for direct sessions, simultaneous capacity. (Browser Run pricing, retrieved 2026-07-26).
Every recorded meter
The first meter is browser session time. Workers Paid includes 10 browser hours per month and then charges $0.09 per additional browser hour. Quick Actions use only this time meter. Cloudflare totals daily seconds, adds the daily totals for the billing cycle, and rounds the monthly result to the nearest whole hour. (Browser Run pricing, retrieved 2026-07-26).
The second meter is monthly-average concurrent browsers for direct Puppeteer, Playwright, or CDP sessions. Workers Paid includes 10 and then charges $2 for each additional average browser. Cloudflare calculates that average from each day’s peak concurrency. Browser time and concurrency add for direct sessions. (Browser Run pricing, retrieved 2026-07-26).
The Free allowance is 10 browser minutes per day and three concurrent browsers. Cloudflare explicitly says a Quick Action ending in a waitForTimeout error does not add billable browser hours, but the reviewed page does not generalize that rule to every failure type. Workers Paid Quick Actions are limited to 10 requests per second as of March 2026. (Browser Run pricing and Cloudflare changelog, retrieved 2026-07-26).
Contract path and price status
Browser Run does not require a browser-specific quote. A buyer creates or uses a Cloudflare account, chooses Workers Free or Workers Paid in the dashboard, and enables Browser Run in a Worker. No separate Browser Run minimum commitment or time-limited trial is published. The Free plan is the evaluation path. (Browser Run pricing, retrieved 2026-07-26).
The source is current first-party documentation, last updated April 21, 2026. It exposes the two usage rates but not the underlying Workers Paid base-plan price in the Browser Run product record. That is why this record has no fixed monthly product price: Browser Run is an attached usage feature, not a standalone monthly browser subscription. (Browser Run pricing, retrieved 2026-07-26).
Priced alternatives
- Browser Use Cloud has a $0 per month Pay As You Go entry plan, funded with prepaid usage credits. (Browser Use pricing, retrieved 2026-07-26).
- Lightpanda Cloud Builder starts at $19 per month and includes 300 browser hours. (Lightpanda pricing, retrieved 2026-07-26).
- Apify Starter starts at $29 per month and can run browser-backed Actors against a prepaid platform balance. (Apify pricing, retrieved 2026-07-26).
Answer
What Cloudflare Browser Rendering costs, what it publishes, and what it does not. Every figure sourced and dated.
Recorded 2026-07-25 from the vendor's own pricing page.We could not confirm this price in the latest check, so it remains visible for context but cannot lead a price ranking. Check the vendor's pricing page before buying.