Scraping API PricesAll products / BrowserCloud
BrowserCloud pricing
How BrowserCloud uses one credit pool across browser and HTTP operations, what is not public, and which workloads fit.
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 BrowserCloud counts
What you pay
Successes you want
100,000 pages
Your stated workload. Every vendor on this site is priced against this same number.
- ÷ 0.95
Attempts you are billed for
105,263 requests
BrowserCloud bills failed fetches, so a 5% failure rate is billed work.
- × 1
What the meter counts
105,263 credits
One attempt is one billed unit for this workload.
- =
Cash per month
$19.00 /mo
Hobby. Cheapest of every eligible purchase option, not the first plan that fits.
Bars share one linear scale across the 3 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.
100,000 pages divided by 95% success → 105,263 credit → Hobby $19.00/mo = $0.19 per 1,000 pages kept
The arithmetic, line by line
- pages: 1 credit per pagesource
- request.js_render: no multiplier published, treated as included
- billed on up to 105,263 attempts, not 100,000 successes, because failure billing is not published; conservatively assumes every attempt consumes quotasource
- consumes 105,263.16 credit per month
- cheapest way to buy that: Hobby, 120,000 included = $19.00 per monthsource
- 14,737 of the included allowance goes unused, 12% of what you buy
Every BrowserCloud plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Hobby your job | $19.00 | n/a | n/a | 120,000 credit | 5 |
| Startup | $99.00 | n/a | n/a | 1,000,000 credit | 50 |
| Business | $249.00 | n/a | n/a | 3,000,000 credit | 100 |
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 |
|---|---|---|---|
| request.basic | 1 credit | page | source |
| request.screenshot | 5 credit | screenshot | source |
| proxy.datacenter_bandwidth | 12 credit | mb | source |
| proxy.residential_bandwidth | 80 credit | mb | source |
| browser.session_time | 1000 credit | browser_hour | source |
What BrowserCloud does not publish
- Overage pricing is not published.
- Failure billing is not published.
- Meter-combination behavior is not published.
What BrowserCloud is
BrowserCloud provides hosted browsers for automation frameworks and HTTP endpoints for page scraping, screenshots, PDF generation, and custom scripts. Its documentation includes connections for Playwright, Puppeteer, Browser Use, and other automation tools. Browserless, Browserbase, and Steel are the nearest named competitors. BrowserCloud’s commercial distinction is one shared credit pool covering browser time, HTTP operations, and built-in proxy bandwidth, rather than separate plan allowances for each product family. Sources: BrowserCloud pricing, BrowserCloud documentation, Browserless pricing, Browserbase pricing, and Steel, retrieved 2026-07-26.
How billing works
One unit is a BrowserCloud credit. The same pool can be consumed by active browser time, a page scrape, a screenshot, a generated PDF, or proxy traffic. Those operations do not consume credits at the same pace: media-generation operations require more credits than a basic page scrape, and residential traffic consumes the pool faster than datacenter traffic. The common buying mistake is to read the plan’s displayed browser hours, scrape count, screenshot count, PDF count, and proxy traffic as simultaneous included allocations. They are equivalent maximums against one shared pool, so spending credits on one reduces what remains for the others. Source: BrowserCloud pricing, retrieved 2026-07-26.
What BrowserCloud does not publish
- Self-serve overage behavior after the monthly credit pool is exhausted. Source reviewed: BrowserCloud pricing, retrieved 2026-07-26.
- Whether failed sessions, blocked pages, or unsuccessful HTTP operations consume credits. Sources reviewed: BrowserCloud pricing and BrowserCloud documentation, retrieved 2026-07-26.
- A general rule stating whether browser time, proxy traffic, and an HTTP operation add together when used in one workflow. Sources reviewed: BrowserCloud pricing and BrowserCloud documentation, retrieved 2026-07-26.
- A public fixed rate for enterprise or dedicated-cluster configurations. Source reviewed: BrowserCloud pricing, retrieved 2026-07-26.
Who it suits
BrowserCloud suits teams that want one account for browser sessions and common HTTP rendering operations, especially when they can track the shared credit balance by operation. It is less suitable for procurement that requires published overage and failure rules, or for a mixed workflow whose combination of browser time, screenshots, and proxy traffic has not been tested. The reason is that a shared pool is flexible but obscures the output quantity unless the buyer models the exact operation mix. Sources: BrowserCloud pricing and BrowserCloud documentation, retrieved 2026-07-26.
Answer
Under the disclosed conservative assumptions, BrowserCloud costs $19.00 for 100,000 JavaScript-rendered pages on its Hobby offer. It is excluded from cheapest claims until the missing billing rule is published.
Recorded 2026-07-25 from the vendor's own pricing page.The published price on this page matched the vendor page when it was rechecked.