Browserbase Pricing in 2026: Plans, Overage and Worked Monthly Costs

Browserbase's pricing page lists four plans: Free ($0), Developer ($20 a month), Startup ($99 a month) and Scale (custom). Developer includes 100 browser hours and 25 concurrent browsers, then charges $0.12 per extra hour; Startup includes 500 hours and 100 concurrent browsers, then $0.10 per hour. Proxy traffic, Search and Fetch are billed on top, and the page lists monthly prices only.

TestMu AI (formerly LambdaTest) makes Browser Cloud, which competes with Browserbase on price. Every Browserbase number on this page is Browserbase's own, taken from its pricing page and docs, and the worked costs show the arithmetic so you can redo it with your own usage.

Browserbase Pricing Plans (2026)

Every row comes from Browserbase's pricing page on November 5, 2026, except session length on paid plans, which comes from its timeouts doc; that doc gives one 6-hour maximum and doesn't vary it by paid plan.

Browserbase's pricing page also says every plan scales past its included usage with no caps or throttling, billed at the plan's rate, so a busy month raises the bill rather than stopping your agents.

Is Browserbase Free?

Yes, there is a free plan, and it is sized for trying the product. Browserbase's pricing page lists 1 browser hour a month, 3 concurrent browsers, 15-minute sessions, 3 agent runs, 1,000 Search calls, 1,000 Fetch calls and $5 of model tokens.

There is no stealth, CAPTCHA solving or proxy traffic on Free, so sites with bot protection will often block it. Test against an unprotected page first, then move to Developer before you judge success rates.

What Else Does Browserbase Charge For?

Browserbase's pricing page bills these next to browser time:

• Search API - $5 per 1,000 searches by default. Other engines cost $1 (Parallel Fast), $5 (Parallel Advanced), $7 (Exa Fast) or $12 (Exa Deep) per 1,000.
• Fetch API - $1 per 1,000 calls on Developer, and $0.50 per 1,000 on Startup after 10,000 included calls. Proxies or extraction add $4 per 1,000, and both together add $7.
• Model Gateway - pay as you go at market price for the models you call through Stagehand.
• Functions - deploying your agent next to the browser is included on all four plans.
• Director - Browserbase describes it as free to try and lists no separate price on the pricing page.

Worked Examples: What Does Browserbase Cost per Month?

Each row uses list prices on November 5, 2026 and counts browser time only unless proxy traffic is stated. The plan is the cheapest one that allows the stated concurrency.

Concurrency usually decides the plan, not hours. On browser time alone, Developer stays cheaper than Startup up to about 2,050 hours a month, but it stops at 25 concurrent browsers, so a team running 50 agents in parallel needs Startup even at 200 hours.

Proxy traffic usually decides the bill. At $10 to $12 per GB it can pass the browser-hour cost quickly on image-heavy sites: in the 20 GB row, 15 GB of extra proxy traffic costs $150, about as much as the plan and the overage hours combined ($149).

How Does Browserbase Compare on Price?

The figures come from each vendor's pricing page on November 5, 2026. Browser hour means the list rate after any included usage.

Browserbase's per-hour price is higher than Browser Use's and Steel Scale's; its plans also include Search, Fetch, Functions and fixed concurrency. Whether that is worth it depends on how much of the platform you will use. For the trade-offs beyond price, read Browserbase vs Browser Use, Browser Cloud vs Browserbase and our Browserbase alternative page.

TestMu AI Browser Cloud doesn't publish the hours or parallels behind its $29 plan yet, so it can't be priced per hour against the others. It earns a place on a shortlist when agents must open localhost, staging or VPN-only apps, since its built-in tunnel handles that with no third-party tool.

How to Keep a Browserbase Bill Down

Agent workloads are hard to forecast because an agent decides how much work to do while it runs, a point made from the infrastructure side in agent runs break cloud cost assumptions. These steps keep the variable part small:

• Release sessions as soon as a task ends - billing follows browser time.
• Block images and media - on scraping tasks this cuts proxy GB, the line that grows fastest.
• Use Fetch instead of a browser - for pages that don't need JavaScript, Fetch is priced per 1,000 calls, not per hour.
• Set a session timeout per task - so a stuck agent doesn't run to the 6-hour maximum.
• Size for peak concurrency first - then check whether your hours push you to the next plan anyway.

Conclusion

Write down your peak concurrent sessions, monthly browser hours and expected proxy GB, then run them through the worked-cost table above to see which Browserbase plan you land on. Re-check Browserbase's pricing page before you sign, since plans can change. If your agents also need private apps, compare the tunnel setup in the What is Browser Cloud guide.

Giving an AI agent a browser? TestMu AI's Browser Cloud runs each task in a real, isolated Chrome session with video, console and network logs for every run.

To run your first session, register, or

book a demo

for a full walkthrough of the product.