Home / Cloud browsers / Browserbase
Browserbase pricing
200 browser hours a month cost $32.00 on Browserbase's Developer plan.
Checked Oct 12, 2026 on Browserbase's own pricing page
- Developer
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.
The Browserbase plans from 20 to 2K
| Plan | Covers | Billed monthly | Billed yearly, per month | Included | Concurrent |
|---|---|---|---|---|---|
| Developer fits your volume | 20 to 2K browser hours | $20.00 | not offered | 100 browser hours | 25 |
All 6 Browserbase plans, with what each charges past its allowance, are further down.
Your job
What Browserbase bills you for
What you pay
Every Browserbase plan
| Plan | Billed monthly | Billed yearly, per month | Included | Past the allowance | Concurrent requests |
|---|---|---|---|---|---|
| Developer fits your volume | $20.00 | not offered | 100 browser hours | $0.12 per browser hour | 25 |
| Developer — Search | $20.00 | not offered | 1,000 requests | $7.00 per 1,000 requests | 25 |
| Developer — Extract | $20.00 | not offered | 1,000 requests | $4.00 per 1,000 requests | 25 |
| Startup | $99.00 | not offered | 500 browser hours | $0.10 per browser hour | 100 |
| Startup — Search | $99.00 | not offered | 1,000 requests | $7.00 per 1,000 requests | 100 |
| Startup — Extract | $99.00 | not offered | 10,000 requests | $4.00 per 1,000 requests | 100 |
Browserbase is also sold as one of the web search APIs (100,000 standard searches a month: $713.00 on Developer — Search) and one of the AI extraction APIs (100,000 AI extraction operations a month: $416.00 on Developer — Extract).
About this price and its sources
How Browserbase separates browser, web API, agent, and proxy usage, what remains unclear, and which teams fit.
Cite this price
200 browser hours a month cost $32.00 on Browserbase's Developer plan. Price read from https://www.browserbase.com/pricing on Oct 12, 2026. Scraping API Prices, https://scrapingapiprices.com/browserbase-pricing
How the bill builds up
- Base rate1 browser hourper 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 hour1 browser hourFrom this bill’s calculation
- = per browser hour$0.16Developer, billed monthly
Credits and multipliers
JavaScript rendering
Billed failures
Success rate
Concurrency
Free tier
Renews monthly The bill at your volume
200 browser hours · $32.00
Read the chart as a table
| Volume | Bill | Offer |
|---|---|---|
| 20 | $20.00 | Developer |
| 50 | $20.00 | Developer |
| 100 | $20.00 | Developer |
| 200 | $32.00 | Developer |
| 500 | $68.00 | Developer |
| 1,000 | $128.00 | Developer |
| 2,000 | $248.00 | Developer |
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
What the meter counts
200 browser hours
One attempt is one billed unit for this workload.
- =
Cash per month
$32.00 /mo
Developer: 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 → Developer $32.00/mo = $0.16 per browser hour
What makes it cost more
One page is not always one billed unit. These are Browserbase's published charges for each kind of work.
| Work | Costs | Per | Source |
|---|---|---|---|
| Browser session time | 1 browser hour | browser hour | source |
| A search | 1 request | request | source |
| AI extraction | 1 request | request | source |
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 7; see the rest.
What Browserbase is
Browserbase is cloud infrastructure for browser automation and web agents. Its platform includes hosted browsers, Agent runs, Search and Fetch APIs, identity and proxy capabilities, a model gateway, and observability. Stagehand, Browserbase’s open-source agent framework, adds higher-level browser actions and extraction. Browserless, Anchor Browser, and Browser Use Cloud are the closest named comparisons. Browserbase is distinguished by combining raw browser infrastructure, Stagehand, and separate web data APIs under one account rather than presenting only a browser-hour service or only an agent-task service. Sources: Browserbase pricing, Browserless pricing, Anchor Browser, and Browser Use pricing, checked Jul 26, 2026.
How billing works
The subscription contains several separate allowances. Browser sessions consume browser hours, Search consumes search calls, Fetch and Extract consume their own calls, and built-in proxy use consumes bandwidth. These meters can have different overage rates. Created browser sessions have a minimum billing period, and a keep-alive session continues to consume time until it is released or reaches its timeout. The common buying mistake is to treat the plan as one flexible credit pool. Unused browser hours do not automatically pay for more Search, Fetch, Extract, Agent, or proxy usage. Sources: Browserbase pricing, cost optimization documentation, and keep-alive documentation, checked Jul 26, 2026.
What Browserbase does not publish clearly
- A fixed public overage rate for Agent runs (Browserbase pricing, Jul 26, 2026).
- Whether failed Search, Fetch, or Extract calls are excluded from billing (Browserbase pricing, Jul 26, 2026).
- One reconciled no-proxy Fetch overage for the Startup plan. The plan card and comparison table show different figures (Browserbase pricing, Jul 26, 2026).
- A way to exchange unused allowance from one meter for another on self-serve plans (Browserbase pricing, Jul 26, 2026).
Who it suits
Browserbase suits development teams that want Playwright, Puppeteer, Selenium, or Stagehand on managed browser infrastructure and may also use search, fetch, models, identities, or proxies from the same provider. It is less suitable for a buyer who needs one success-only request unit, or for automation that leaves sessions idle without strict release handling. The reason is that Browserbase exposes a broad platform through separate meters, and elapsed browser time remains billable even when an unfinished workflow produces no useful output. Sources: Browserbase pricing, cost optimization documentation, and session timeout documentation, checked Jul 26, 2026.
Browserbase head to head
Both bills for the same job, and the volume where the cheaper one changes.