Home / Cloud browsers / BrowserCloud
BrowserCloud pricing
200 browser hours a month cost $99.00 on BrowserCloud's Startup plan, with room to grow to 1,000 browser hours on the same plan.
Checked Oct 12, 2026 on BrowserCloud's own pricing page
- Hobby
- Startup
- Business
Your workloadType an exact volume or copy a link to this jobEdit
published session-time meter only
Fixed for this page; volume is the control.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.
Every BrowserCloud plan
| Plan | Covers | Billed monthly | Billed yearly, per month | Included | Past the allowance | Concurrent |
|---|---|---|---|---|---|---|
| Hobby | 20 to 100 browser hours | $19.00 | not offered | 120,000 credits | move to a bigger plan | 5 |
| Startup fits your volume | 200 to 1K browser hours | $99.00 | not offered | 1,000,000 credits | move to a bigger plan | 50 |
| Business | 2K browser hours | $249.00 | not offered | 3,000,000 credits | move to a bigger plan | 100 |
Your job
What BrowserCloud bills you for
What you pay
BrowserCloud is also sold as one of the web scraping APIs (100,000 JavaScript-rendered pages a month: $19.00 on Hobby).
About this price and its sources
How BrowserCloud uses one credit pool across browser and HTTP operations, what is not public, and which workloads fit.
Cite this price
200 browser hours a month cost $99.00 on BrowserCloud's Startup plan, with room to grow to 1,000 browser hours on the same plan. Price read from https://www.browsercloud.io/pricing on Oct 12, 2026. Scraping API Prices, https://scrapingapiprices.com/browsercloud-pricing
How the bill builds up
- Base rate1000 creditsper browser hour
- × JavaScript renderingNot requiredNot part of this workload
- × Premium proxyNot required
- ÷ Success rate1Failure billing is not published; this is an assumption
- = Billed units per browser hour1000 creditsFrom this bill’s calculation
- = per browser hour$0.50Startup, billed monthly
Credits and multipliers
JavaScript rendering
Billed failures
Success rate
Concurrency
Free tier
Renews monthly The bill at your volume
200 browser hours · $99.00
Read the chart as a table
| Volume | Bill | Offer |
|---|---|---|
| 20 | $19.00 | Hobby |
| 50 | $19.00 | Hobby |
| 100 | $19.00 | Hobby |
| 200 | $99.00 | Startup |
| 500 | $99.00 | Startup |
| 1,000 | $99.00 | Startup |
| 2,000 | $249.00 | Business |
Follow each billed unit
-
Successes you want
200 browser hours
Your stated workload. Every vendor on this site is priced against this same number.
- ÷ 1
Attempts you are billed for
200 browser hours
Failure billing is not published. This workload assumes no failures, so the missing rule does not change the bill.
- × 1,000
What the meter counts
200,000 credits
One attempt is not one billed unit here: this workload multiplies by 1000 before any money is involved.
- =
Cash per month
$99.00 /mo
Startup: the cheapest way to buy this volume, not just the first plan big enough.
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.
200 browser hours → 200,000 credits → Startup $99.00/mo = $0.50 per browser hour
What makes it cost more
One page is not always one billed unit. These are BrowserCloud's published charges for each kind of work.
| Work | Costs | Per | Source |
|---|---|---|---|
| A standard page | 1 credit | page | source |
| A screenshot | 5 credits | screenshot | source |
| Datacenter proxy traffic | 12 credits | MB | source |
| Residential proxy traffic | 80 credits | MB | source |
| Browser session time | 1,000 credits | browser hour | source |
Limits and terms
What BrowserCloud publishes beyond the price: the limits a job runs into and the terms that change what a plan is worth. Each line links the page it comes from and the day it was read.
Speed, concurrency and sessions
- Free sessions are limited to 15 minutes. source, read Jul 26, 2026
What you may do with the results, and how long they are kept
- Data retention is 7 days on Free and 30 days on Hobby, Startup, and Business. source, read Jul 26, 2026
Cheaper for this job
Same 200 metered browser-session hours a month, excluding separate proxy and model charges, ranked by what you would actually be billed. APIs without a full public price aren't ranked. Showing 6 of 8; see the rest.
What BrowserCloud does not publish
- Overage pricing is not published.
- See the note above.
- Meter-combination behavior is not published.
- Self-serve overage behavior after the monthly credit pool is exhausted (BrowserCloud pricing, Jul 26, 2026).
- Whether failed sessions, blocked pages, or unsuccessful HTTP operations consume credits. Sources reviewed: BrowserCloud pricing and BrowserCloud documentation, checked Jul 26, 2026.
- 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, checked Jul 26, 2026.
- A public fixed rate for enterprise or dedicated-cluster configurations (BrowserCloud pricing, Jul 26, 2026).
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, checked Jul 26, 2026.
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, checked Jul 26, 2026.
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, checked Jul 26, 2026.