Guide
Browserbase Pricing in 2026: Plans, Browser Hours, and Extras
Browserbase's 2026 plans, what a browser hour buys, the metered extras, and a like-for-like cost per 1,000 pages against datamint.
Browserbase charges for browser time. Each plan bundles browser hours and concurrent sessions, then meters proxy bandwidth, search calls, fetch calls, and agent runs on top. The plan fee buys a bundle; usage beyond it is billed separately, so the headline price is not the whole bill.
The plan details below come from Browserbase's pricing page, read on 15 November 2026. The page-level task estimate in the cost section is Browserbase's own, checked on 20 October 2026. Pricing changes; re-check the source before committing a budget.
The plans
| Plan | Monthly | Concurrent browsers | Browser hours | Proxy data | Agent runs | Search calls | Fetch calls |
|---|---|---|---|---|---|---|---|
| Free | $0 | 3 | 1 | Not listed | 3 | 1,000 | 1,000 |
| Developer | $20 | 25 | 100, then $0.12 per hour | 1 GB, then $12 per GB | 15 | 1,000, then $5 per 1,000 | 1,000, then $1 per 1,000 |
| Startup | $99 | 100 | 500, then $0.10 per hour | 5 GB, then $10 per GB | 50 | 1,000, then $5 per 1,000 | 10,000, then $0.50 per 1,000 |
| Scale | Custom | 250+ | 500+, usage-based | 5+ GB, usage-based | Custom | 10,000+, usage-based | 10,000+, usage-based |
Search calls have optional premium rates: $1 per 1,000 for Parallel Fast, $5 for Parallel Advanced, $7 for Exa Fast, and $12 for Exa Deep. Fetch calls on Developer are $1 per 1,000 standard, $4 with proxies, $4 with extraction, and $7 with both; Startup halves the standard rate and keeps the same add-on prices.
The free plan limits sessions to 15 minutes, retains data for 7 days, and does not include captcha solving or stealth mode. Search and fetch rates are 2 and 5 requests per second per project on Free through Startup; Scale is custom.
What a browser hour buys
A browser hour is one managed browser running for an hour, up to the plan's concurrency. It is not a page count. Browserbase's pricing page estimates 100 browser hours at roughly 3,000 page-level tasks, or about 30 tasks per browser hour.
At that estimate:
| Plan | Included hours | Approximate page-level tasks | Effective cost per 1,000 tasks |
|---|---|---|---|
| Free | 1 | 30 | $0 within the allowance |
| Developer | 100 | 3,000 | $6.67 |
| Startup | 500 | 15,000 | $6.60 |
Those figures are arithmetic from Browserbase's estimate, not measured throughput. If your agent thinks between actions, retries, or waits on slow pages, tasks per hour fall and the cost per task rises. A tight script that never idles gets more out of the hour.
The extras that move the bill
Four meters sit on top of browser hours:
- Proxy bandwidth starts at 1 GB on Developer, then $12 per GB. Startup includes 5 GB, then $10 per GB. A session that loads heavy pages can consume a gigabyte faster than the hour meter suggests.
- Search calls are bundled at 1,000 on Developer and Startup, then $5 per 1,000 at the default rate; premium search options cost more.
- Fetch calls start at 1,000 on Developer, then $1 per 1,000. Startup includes 10,000 and charges $0.50 per 1,000 after.
- Agent runs are capped per plan: 3 on Free, 15 on Developer, 50 on Startup.
- Sessions are limited to 15 minutes on Free, with 7-day data retention and no stealth or captcha solving.
A workflow that only drives the browser follows the headline number. One that also searches, fetches, and pushes proxy bandwidth can exceed it.
Is Browserbase free?
For evaluation, yes. The free plan includes one browser hour, three concurrent browsers, three agent runs, 1,000 search calls, and 1,000 fetch calls. Sessions are limited to 15 minutes, data is retained for 7 days, and stealth mode and captcha solving are unavailable.
One browser hour is roughly 30 page-level tasks at Browserbase's own estimate, enough to test a workflow but not to run one in production.
How Browserbase's pricing compares with datamint
The billing units differ, so start with what each service returns. Browserbase gives you a managed browser session; datamint takes a URL and returns Markdown or schema-validated JSON. If you need to click, type, and hold state across steps, Browserbase is the product for that.
For page extraction, datamint charges 1 credit for a static fetch, 5 for a headless render, 15 for stealth routing, and 2 more for a schema pass. Credits are $1 per 1,000:
| datamint request | Credits per page | Builder ($49 / 60,000) per 1,000 pages | Scale ($299 / 450,000) per 1,000 pages |
|---|---|---|---|
| Static fetch | 1 | $0.82 | $0.66 |
| Headless render | 5 | $4.08 | $3.32 |
| Stealth routing | 15 | $12.25 | $9.97 |
| Headless plus schema | 7 | $5.72 | $4.65 |
Against Browserbase's estimated $6.60 to $6.67 per 1,000 page-level tasks, datamint's headless render costs less per page at both paid tiers; its stealth tier costs more. The $4.08 rate buys a rendered page and clean output. The $12.25 rate adds routing through residential or mobile proxies with fingerprint mutation.
Browserbase's entry price is $20 a month against datamint's $49 Builder plan, so a small workflow is cheaper to start on Browserbase. datamint's free tier is 1,000 credits a month, while Browserbase's is one browser hour; the units do not compare directly. Browserbase meters proxy bandwidth and search separately, while datamint folds transport selection into the page credit.
For the full feature comparison, see Browserbase alternatives. To price a page workload at datamint's rates, see pricing or start with the free tier. For the other billing models in this stack, see the Firecrawl pricing guide and the Apify pricing guide.
Frequently asked questions
Is Browserbase free?
The free plan includes one browser hour, three concurrent browsers, three agent runs, 1,000 search calls, and 1,000 fetch calls, with 15-minute sessions, 7-day retention, and no stealth mode or captcha solving.
What counts as a browser hour?
One managed browser running for one hour. Concurrent sessions share the plan's concurrency limit, and each open session consumes the hour meter while it runs.
Why is my Browserbase bill higher than the plan price?
The plan fee bundles browser hours and concurrency; proxy bandwidth, search calls, fetch calls, and overage hours are metered on top. Proxy bandwidth in particular can move quickly on media-heavy pages.
Is Browserbase cheaper than datamint?
The units differ. Browserbase's own estimate puts 100 browser hours at roughly 3,000 page-level tasks, which makes its Developer plan about $6.67 per 1,000 tasks and Startup about $6.60. datamint's headless render is $4.08 per 1,000 pages at Builder and $3.32 at Scale; its stealth tier is $12.25 and $9.97. If you need a browser to drive, the two are different products, and the per-task comparison does not capture what Browserbase provides.
Does datamint provide a browser?
No. datamint returns Markdown or schema-validated JSON from a URL; it does not hand back a browser session for multi-step interaction. For clicking, typing, and stateful workflows, Browserbase or a similar browser service is the right layer.
Plan details were checked against Browserbase's pricing page on 15 November 2026; the 100-hours-to-3,000-tasks estimate was checked on 20 October 2026. Per-page figures are arithmetic from published rates, not measured bills. Vendor pricing changes; re-check the source before committing a budget.
datamint returns schema-validated JSON and LLM-ready Markdown from bot-defended sites through one API call, with routing across transport tiers handled on our side.