Scraping API PricesAll products / Browserless
Browserless pricing
How Browserless Units cover browser time, proxies, and CAPTCHA attempts, what conflicts publicly, and who it suits.
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.
Your job
What Browserless counts
What you pay
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
Browserless bills failed fetches. This workload assumes none fail, so nothing is added here.
- × 120
What the meter counts
24,000 credits
One attempt is not one billed unit here: this workload multiplies by 120 before any money is involved.
- =
Cash per month
$33.00 /mo
Prototyping. 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.
200 browser hours → 24,000 credit → Prototyping $33.00/mo = $0.17 per browser hour
Every Browserless plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Prototyping your job | Not published | $25.00 | n/a | 20,000 credit | 10 |
| Starter | Not published | $140.00 | n/a | 180,000 credit | 40 |
| Scale | Not published | $350.00 | n/a | 500,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 |
|---|---|---|---|
| browser.session_time | 1 credit | 30 browser_second | source |
| proxy.residential_bandwidth | 6 credit | mb | source |
| proxy.datacenter_bandwidth | 2 credit | mb | source |
| request.captcha_solve | 10 credit | attempt | source |
What Browserless does not publish
- Monthly-billing list prices were not obtainable from the public page text.
- CAPTCHA success billing conflicts between the pricing page and unit-consumption documentation.
What Browserless is
Browserless is a hosted browser platform with browser sessions, BrowserQL, browser-oriented APIs, built-in proxies, and CAPTCHA solving. It supports developers who want to connect automation code to managed browsers without operating the browser fleet themselves. Browserbase, Bright Data Browser API, and BrowserCloud are the nearest named alternatives. Browserless differs commercially by calling its shared billing credit a Unit and using that balance for browser time plus selected network and anti-bot services. Sources: Browserless pricing, Browserless unit documentation, Browserbase pricing, Bright Data Browser API, and BrowserCloud pricing, retrieved 2026-07-26.
How billing works
One Unit is the accounting credit deducted from the plan balance. Browser time consumes Units in started time increments, so partial increments round upward. Built-in residential and datacenter proxy traffic consume additional Units per transferred data, and CAPTCHA solving can also consume Units. These meters add when the workflow uses them together. The common buying mistake is to convert the entire allowance into browser hours and stop there. A proxied or CAPTCHA-heavy session consumes its elapsed-time Units plus the relevant traffic or solve usage, and short sessions are affected by time rounding. Sources: Browserless unit-consumption documentation and Browserless proxy documentation, retrieved 2026-07-26.
What Browserless does not publish consistently
- One CAPTCHA failure rule. The unit documentation describes charging attempts even when they fail, while the pricing page describes successful solves. Sources reviewed: unit-consumption documentation and Browserless pricing, retrieved 2026-07-26.
- Monthly-billing list prices in the public page text reviewed here; the visible self-serve figures are presented as effective monthly amounts under annual billing. Source reviewed: Browserless pricing, retrieved 2026-07-26.
- One success-only rule for browser sessions. Time is consumed while the session runs, regardless of whether the automation ultimately yields useful data. Source reviewed: Browserless unit-consumption documentation, retrieved 2026-07-26.
- A single output-based conversion from Units to pages or completed tasks. Sources reviewed: Browserless pricing and unit-consumption documentation, retrieved 2026-07-26.
Who it suits
Browserless suits developers who want managed browser connections, BrowserQL, and optional built-in proxy or CAPTCHA services in one balance. It fits best when session duration and proxy traffic can be observed and capped. It is less suitable for buyers who need a fixed cost per successful page, or for high-bandwidth automation that has not been modeled alongside time usage. The reason is that Units are additive infrastructure consumption, not a guarantee of completed output. Sources: Browserless pricing, unit-consumption documentation, and proxy documentation, retrieved 2026-07-26.
Answer
Browserless's dated 2026-07-25 price snapshot gives $33.00 for 200 browser hours on its Prototyping offer. This older figure is excluded from rankings; check the vendor before buying.
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.