Skip to content
CrawlfolioSourced research on web data for AI
Menu

Browserless charges in units, and a unit is up to 30 seconds of one browser connection. Plans run from $35 a month on monthly billing ($25 billed yearly) to $500 ($350), with 1,000 free units to start. Pricing, pricing.md, verified 2026-11-16.

Your decision is which plan, which billing cycle, and whether a per-hour vendor would bill your session length for less. Below I turn units into dollars per hour, per GB of proxy and per job, then work three monthly bills and set them against four other browser vendors.

Short on time?

Short on time? Here's my pick by volume

Just trying it
Free
1,000 units a month, 2 browsers, 2-minute sessions, no card. About 8 hours of browser time, or up to 1,000 short jobs.
Up to about 100K units a month
Prototyping, monthly at $35
Covers roughly 830 browser-hours or 100,000 short jobs once overage is counted. Go annual ($25) only when you're sure of the volume.
About 100K to 350K units a month
Starter, $200 monthly or $140 annual
180,000 units included: $0.093 to $0.133 per browser-hour inside the quota, 30 to 40 browsers, 30-minute sessions.
Heavy agent work
Scale, $500 monthly or $350 annual
500,000 units, 80 to 100 browsers, 60-minute sessions. Far above 4,170 hours a month, its $0.18 overage makes Steel or Cloudflare worth pricing.
Lots of jobs under 30 seconds
Browserless over a 1-minute-minimum vendor
A 20-second job bills 30 seconds here and a full minute on Browserbase. Long, idle agent sessions flip that.

Prices verified . Sponsors cannot buy a verdict or a position.

Browserless plans, monthly and annual billing

Verified

PlanMonthly billing / annual (per month)Units a monthOverage per unitBrowsers, monthly / annualMax sessionReplay storage
Free$0 / $01,000None (requests rejected)2 / 22 min1 day
Prototyping$35 / $2520,000$0.00205 / 1015 min7 days
Starter$200 / $140180,000$0.001730 / 4030 min30 days
Scale$500 / $350500,000$0.001580 / 10060 min90 days
EnterpriseCustom"Millions"CustomHundreds to thousandsCustomCustom

Source: Browserless pricing page and pricing.md, USD. Monthly prices and the monthly browser counts come from pricing.md; the HTML page shows the annual view.

This page sits in the agent browser hub. For features and session state side by side, see Browserbase vs Browserless; if you’re already leaving, Browserless alternatives sorts the options by reason.

Where are the monthly prices? #

In a file most people never open. The HTML pricing page loads on the annual view, “Pay Yearly” with “Save 30%”, and shows $25, $140 and $350 a month, each “billed annually”. Pricing, verified 2026-11-16.

Browserless also publishes the same page as markdown at browserless.io/pricing.md, and that file lists monthly billing: Prototyping $35, Starter $200, Scale $500. I’m using it as the vendor’s own statement of the monthly view.

It also clears up the “+5”, “+10” and “+20” next to the browser counts on the HTML page. Annual plans get 10, 40 and 100 concurrent browsers; monthly plans get 5, 30 and 80. The “+N” is the annual bonus, not something added on top of 10, 40 or 100.

What counts as a unit? #

A unit is “a block of browser time of up to 30 seconds per browser connection”, and longer runs use “an extra Unit for every 30 seconds”. Pricing, verified 2026-11-16.

The unit docs spell out the edges, and each one moves your bill:

  • Rounding up: “a session open for 31 seconds consumes 2 units”.
  • Idle time: it counts the same as active time, so a browser waiting on a slow page or an LLM is billing.
  • Reconnects: “Session-reconnects count as new browser connections and incur a fresh Unit charge”. The session docs add that “Each reconnect is a new browser connection, so it’s billed like any other connection”.
  • Held browsers: a browser you keep open “still occupies a concurrency slot”, and the plan’s max session is a hard deadline from browser start.
  • Failures: a request rejected before it starts (a 429, say) uses nothing; a run that fails midway bills the time it used.

Sources: unit consumption, standard sessions, pricing.

The vendor’s own worked example: a 30-second session plus 2 MB of residential proxy traffic uses 13 units, one for the time and 12 for the traffic. Unit docs.

What does a short job really cost? #

More than its run time. A 5-second job bills a full 30-second unit, six times its actual time, and a 31-second job bills 60 seconds (my arithmetic on the rule above).

That cuts both ways. Against a vendor with a one-minute minimum, the 30-second block is the finer meter; against one that bills by the second, it isn’t.

Set a timeout #

The current docs say the default connection timeout is 30 seconds and recommend setting it to stop runaway sessions. A 2022 Browserless post said 15 minutes, which would be 30 units. I’d trust the 2026 docs, and set the value explicitly anyway. Unit docs, 2022 post.

That 2022 post is where units began. On December 8, 2022, Browserless wrote that “A Unit is mostly equivalent to a Session”; the page now says it’s no longer current, and the 30-second definition replaced it.

So what does an hour cost? #

Between $0.084 and $0.24, depending on the plan and on staying inside the quota. One browser-hour is 3,600 ÷ 30 = 120 units. My arithmetic on list prices, verified 2026-11-16:

Plan Hours in the quota Per hour, quota fully used (monthly / annual) Per hour at overage
Free 8.3 $0 Not available
Prototyping 166.7 $0.21 / $0.15 $0.24 (120 × $0.0020)
Starter 1,500 $0.133 / $0.093 $0.204 (120 × $0.0017)
Scale 4,166.7 $0.12 / $0.084 $0.18 (120 × $0.0015)

Read the quota column carefully. Those rates hold only if every connection fills its 30-second blocks and you use the whole allowance. Short jobs and unused units push the real rate up.

The pattern matters for the vendor comparison further down. Inside a fully used quota, Browserless is cheap per hour; once you’re paying overage, it’s the most expensive of the per-hour vendors I priced.

Looking up at a tall stone-clad tower with tightly repeated vertical window strips and a column of mirrored glass panels at its corner, set against a pale sky
The same narrow strip, repeated floor after floor: an hour of browser time is 120 identical 30-second blocks, so the hourly rate depends on how many of them you actually fill. Photo: Wenxuan Zou / Unsplash · Unsplash License

What about proxies, captchas and the REST APIs? #

Everything is billed in the same units, so it all draws on one balance. Residential proxy traffic uses 6 units per MB, datacenter traffic 2 units per MB, and each successful captcha solve 10 units. Pricing, verified 2026-11-16.

Here’s what that means in dollars at each plan’s overage rate. My arithmetic, assuming 1 GB = 1,000 MB, because Browserless doesn’t define an MB:

Add-on Units Prototyping Starter Scale
Residential proxy, per GB 6,000 $12.00 $10.20 $9.00
Datacenter proxy, per GB 2,000 $4.00 $3.40 $3.00
Captcha, per successful solve 10 $0.020 $0.017 $0.015

Three rules soften this. Traffic through your own proxy (--proxy-server) uses no proxy units, failed captcha attempts “aren’t charged”, and datacenter proxies arrived in July 2026 at a third of the residential rate. Unit docs, changelog.

The REST endpoints have their own meters. A plain Smart Scrape fetch is 0.5 units per 30 seconds and a cached one 1 unit per 30 seconds. Predefined scrapers charge per call: 10 units for Zillow, 4 for a Google search, or 10 with JavaScript rendering, and only when they return data or a definitive not-found. Unit docs.

So 1,000 Google searches through the predefined scraper cost $6 at Scale’s overage rate and $8 at Prototyping’s, or $15 and $20 with rendering (my arithmetic). A /pdf call under 30 seconds is 1 unit, and screenshots and PDFs have no separate price.

The 2026 changelog shows how the product has grown: /smart-scrape, /search, /map and /crawl plus an MCP server in April, an /agent/run beta and up to 20 named API keys sharing one unit balance in August, and Zillow scrapers in November. Changelog.

Should you pay monthly or annually? #

Annual saves 28.6% on Prototyping and 30% on Starter and Scale, and adds concurrency, but it commits cash up front: $300, $1,680 or $4,200 for the year. My arithmetic on the pricing.md figures, verified 2026-11-16.

One rule makes switching expensive: a plan change resets the billing cycle to the date of the change and charges the full new plan amount. So I’d settle the volume on monthly billing first and commit only after that.

The other question is when to move up a plan. A bigger plan wins once the smaller one’s overage would cost more than the jump in base price. My break-evens, in units a month:

Move Monthly billing Annual billing Formula (monthly case)
Prototyping to Starter 102,500 77,500 $35 + $0.002 × (U − 20,000) = $200
Starter to Scale about 356,500 about 303,500 $200 + $0.0017 × (U − 180,000) = $500

That’s why the VerdictBox splits at about 100,000 and 350,000 units. Below 102,500 units on monthly billing, Prototyping plus overage is cheaper than Starter, even though Starter’s per-unit rate looks better.

What would my bill be? #

Here are three workloads, each checked against the plan’s session cap and browser count. These are hypothetical inputs and my arithmetic on list prices, verified 2026-11-16, not invoices.

Workload Units Best plan Monthly billing Annual (per month)
Small: 10,000 jobs × 20 s, no proxy 10,000 Prototyping $35 $25
Medium: 100,000 jobs × 45 s, 5 GB residential 230,000 Starter $285 $225
Agent load: 30,000 sessions × 10 min, 20 GB residential 720,000 Scale $830 $680

A small scraping job #

10,000 jobs of 20 seconds each bill one unit apiece: 10,000 units. Prototyping’s 20,000 cover it with 10,000 to spare, so the bill is $35 monthly or $25 on annual billing. Free’s 1,000 units don’t fit.

The jobs add up to about 56 browser-hours, well within 5 browsers and the 15-minute session cap.

A medium job with proxies #

100,000 jobs of 45 seconds each bill two units apiece: 200,000 units. Add 5 GB of residential traffic at 6 units per MB, 30,000 units, for 230,000 in total.

Starter includes 180,000, so 50,000 units go to overage at $0.0017: $85. The bill is $285 monthly, or $225 on annual billing. Prototyping would cost $35 + 210,000 × $0.002 = $455, and Scale $500 or $350.

The run time is about 1,250 browser-hours, an average of under 2 browsers busy at once, so Starter’s 30 browsers and 30-minute cap fit easily.

A heavy agent workload #

30,000 agent sessions of 10 minutes each bill 20 units apiece: 600,000 units. Add 20 GB of residential traffic, 120,000 units, for 720,000.

Scale includes 500,000, so 220,000 units go to overage at $0.0015: $330. The bill is $830 monthly, or $680 on annual billing. Starter would cost $200 + 540,000 × $0.0017 = $1,118.

That’s 5,000 browser-hours. Ten-minute sessions fit inside Scale’s 60-minute cap, and the average load is about 7 browsers, though your peaks decide whether 80 or 100 is enough.

Is it cheaper than per-hour browsers? #

Only in some cases. At overage rates Browserless costs more per hour than every per-hour vendor I priced; inside a fully used Starter or Scale quota on annual billing it costs less than Browserbase or Hyperbrowser; and for jobs under 30 seconds its billing block is finer than Browserbase’s one-minute minimum.

An older shortcut said that above about a minute per session, Browserbase or Hyperbrowser are cheaper. That holds only at overage. The dividing line is quota versus overage, plus job length.

Vendor and plan Browser time at overage Included time, fully used Billing step Residential proxy Heavy agent bill (5,000 h, 20 GB)
Browserless Scale $0.18/h $0.12/h monthly, $0.084/h annual 30 s per connection $9.00/GB $830 monthly, $680 annual
Browserless Starter $0.204/h $0.133/h monthly, $0.093/h annual 30 s per connection $10.20/GB $1,118 monthly
Browserbase Developer $0.12/h $0.20/h ($20 for 100 h) Per minute, 1-minute minimum $12/GB after 1 GB Not worked
Browserbase Startup $0.10/h About $0.20/h ($99 for 500 h) Per minute, 1-minute minimum $10/GB after 5 GB $699
Hyperbrowser $0.10/h (100 credits) Plan fees not on the page Not stated $10/GB $700 (credit rates only)
Steel Scale $0.08/h $100 a month of credits Not stated $6/GB About $670
Cloudflare Browser Run $0.09/h after 10 h 10 h on Workers Paid Monthly total rounded to the hour No price on the page $449.10 (browser time only)
Bright Data Browser API Billed per GB Scale $499 includes 71 GB Per GB $8/GB pay-as-you-go Not like-for-like

Sources, all verified 2026-11-16: Browserless, Browserbase pricing and billing docs, Hyperbrowser, Steel, Cloudflare, Bright Data. The per-hour and bill columns are my arithmetic.

How I worked the 5,000-hour bill elsewhere #

Same workload as the heavy agent bill: 5,000 browser-hours and 20 GB of proxy traffic, list prices only.

  • Browserbase Startup: $99 + 4,500 hours × $0.10 + 15 GB × $10 = $699.
  • Hyperbrowser: 5,000 × $0.10 + 20 × $10 = $700 at its credit rates (“1 credit = $0.001”); the page I opened shows no plan fee.
  • Steel Scale: $250 + ($400 hours + $120 proxy − $100 included credits) = about $670, assuming the monthly credits offset usage, which I couldn’t confirm.
  • Cloudflare Workers Paid: 4,990 hours × $0.09 = $449.10 for browser time only. The page lists no proxy price, browsers beyond 10 concurrent (a monthly average of daily peaks) cost $2.00 each, and I didn’t open the Workers Paid base fee.

So at this size, Browserless Scale on annual billing ($680) lands in the same band as Browserbase, Hyperbrowser and Steel, and monthly billing ($830) sits above them. Cloudflare is cheapest on browser time if you don’t need a managed proxy. Its own plan details are in my Cloudflare Browser Run pricing breakdown.

Where the 30-second block wins, and where it doesn’t #

Take 10,000 jobs of 20 seconds. Browserless bills 10,000 units, about 83 hours of billed time; Browserbase bills 10,000 minutes, about 167 hours, because of its one-minute minimum (my arithmetic; Browserbase billing).

At 45 seconds the advantage disappears, because both vendors bill a full minute. On the medium workload above, Browserbase Startup would be $99 + 1,166.7 hours × $0.10 = $215.67, with the 5 GB of proxy inside its allowance, against Browserless Starter at $285 monthly or $225 annual. That assumes 45 seconds rounds to one minute; Browserbase doesn’t state the rounding direction.

My Browserbase pricing breakdown has that vendor’s plans in full.

What does the free tier include? #

1,000 units a month, 2 concurrent browsers and sessions up to 2 minutes, with “No card required”. The 2-minute cap was raised from 1 minute in September 2026. Pricing, changelog, verified 2026-11-16.

1,000 units is about 8 hours of fully used 30-second blocks, or up to 1,000 short jobs. Replays are kept for 1 day and logs are searchable for 8 hours. pricing.md.

Two different limits apply. When the free units run out, “Free plans reject incoming requests after the threshold is met” rather than bill overage. When you exceed your browser count, the cloud “automatically queues up to twice your concurrency limit”. pricing.md, terminology.

The cloud runs in three regions: San Francisco, London and Amsterdam (production-sfo, -lon and -ams.browserless.io). There’s no Asia-Pacific region; for a country-specific exit you’d use the residential proxy’s proxyCountry option. Connection URLs.

Can you self-host Browserless instead? #

Yes, but the free licence doesn’t cover most commercial use. The repository is “dual-licensed under the MongoDB Server-Side Public License OR the browserless commercial license”. LICENSE, verified 2026-11-16.

The README calls the open-source build “Free for non-commercial uses” and says you need the commercial licence to build closed-source commercial apps or run closed-source CI. Repository. The commercial licence price isn’t published; it’s sold through Enterprise, which also lists a private server or your own infrastructure, “Extensive datacenter locations including EU”, SOC 2 Type II, a HIPAA BAA and a DPA. Pricing.

Some features don’t come with the image at all. The README lists BrowserQL, Session Replay and Persistent Sessions for the cloud or Enterprise only. The open image (ghcr.io/browserless/chromium) defaults to 10 concurrent browsers and a queue of 10. Terminology.

The project is active: v2.63.1 shipped on November 13, 2026, and v2.60.0 on November 6 added support for Playwright 1.65. Releases. The operating cost of running your own fleet is a separate question, covered in self-hosted vs managed browsers.

How do you stop a surprise bill? #

Set the overage spend limit. Since September 2026 the Billing page has one, and a limit of $0 stops you at your allowance; it resets each cycle and pauses new sessions when it’s hit. Changelog, pricing.md, verified 2026-11-16.

The same release added the unit cost of each run to the request logs, which is the easiest way to learn your real per-job rate. Overage emails arrive at most once an hour, so don’t rely on them as an alarm.

Then close the leaks the unit rules create: set timeout, close sessions when the job ends, and avoid reconnect loops, since every reconnect starts a new unit. GitHub issues about timeouts (#4096, “TIMEOUT param ignored?”, and #3831, a browser closed after exactly 300 seconds) are closed and date from 2024, so I’d read them only as a reason to set the value explicitly. Issues.

What do other pricing pages get wrong? #

The main one: several say monthly prices aren’t published. They are, in Browserless’s own pricing.md.

Corrections, checked on November 16, 2026

  • Activepieces (November 12, 2026) lists paid base prices as “Not confirmed”. Both billing views are public. Activepieces
  • Send.win gives residential proxy at $12.29/GB and datacenter at $4.10/GB from unnamed “third-party estimates”. Browserless’s own unit rates give $12.00 and $4.00 at Prototyping overage, less on bigger plans. Send.win
  • Toolradar lists only the annual prices and never says what a unit is. Toolradar
  • CostBench lists the $35/$200/$500 monthly prices, then also says there’s “no monthly billing option available”. CostBench

What Browserless doesn't publish

  • The price of the commercial self-hosting licence, or of Enterprise.
  • Whether a proxy MB is 1,000,000 or 1,048,576 bytes.
  • Any uptime figure or SLA on the pages I read, and I found no independent reliability data.

What do users say about the price? #

Very little I could find. G2 and Capterra returned 403 errors, two searches turned up no Reddit thread on Browserless pricing, and Hacker News mentions are mostly stack lists.

The one 2026 cost comment, from a user pitching a self-hosted rival on March 4, put it as “Firecrawl charges ~$100/mo, Browserless ~$200/mo”. HN. That matches Starter’s monthly price but tells you nothing about usage.

The fair version of the main complaint comes from a competitor. Scrapfly says “Slow pages = more units consumed”, which is just the idle-time rule above restated. Scrapfly.

On the vendor side, the operator posted on November 11 that “I’ve been running browserless.io for the past 9 years”, and the founder’s November post describes the company as solo-founded, bootstrapped and “self-funded”. HN, Browserless blog.

A lattice of thin bronze-toned metal rods bent into repeating diamond and triangle shapes, mounted in front of a pitted grey concrete wall
A thin lattice over bare concrete: the public pages and user comments cover only part of the picture, so price your own workload before you trust anyone's summary, mine included. Photo: Emmett Husmann / Unsplash · Unsplash License

Which plan should you pick? #

Just trying it: Free. 1,000 units, 2 browsers and 2-minute sessions are enough to see whether your script works on Browserless, with no card.

Up to about 100,000 units a month: Prototyping on monthly billing, $35. That’s roughly 830 browser-hours or 100,000 short jobs before Starter would be cheaper. Switch to annual ($25) only once you’re sure, because a plan change resets the cycle.

About 100,000 to 350,000 units a month: Starter, $200 monthly or $140 annual. Inside the quota that’s $0.093 to $0.133 per browser-hour, with 30 or 40 browsers and 30-minute sessions.

Heavy agent work, above about 350,000 units: Scale, $500 monthly or $350 annual, with 60-minute sessions and 80 or 100 browsers. If you’d run far past its roughly 4,170 included hours, the $0.18 overage makes Steel ($0.08 an hour) or Cloudflare ($0.09, no managed proxy) worth pricing out.

Many jobs under 30 seconds: Browserless, because its 30-second block bills them for less than a one-minute minimum. Long, mostly idle agent sessions at overage: price Browserbase or Steel first.

If I were starting today, I’d take monthly Prototyping, set the overage spend limit, and read the per-run unit cost in the request logs for two weeks. I’d move to annual Starter or Scale only once usage sat above the break-even. For the wider field, see the best cloud browsers for AI agents.

FAQ

How much is one Browserless unit in dollars?

Inside a plan's allowance it depends on how much of the allowance you use. Above it, a unit costs $0.0020 on Prototyping, $0.0017 on Starter and $0.0015 on Scale. One unit buys up to 30 seconds of one browser connection, so an hour is 120 units: $0.24, $0.204 or $0.18 at overage, verified 2026-11-16.

Does Browserless have a free plan?

Yes. Free gives 1,000 units a month, 2 concurrent browsers and sessions up to 2 minutes, with no card required. When the units run out, free plans reject requests rather than bill overage.

Is Browserless billed monthly or only annually?

Both. The pricing page opens on the annual view ($25, $140 and $350 a month, billed yearly), but Browserless's own pricing.md lists monthly billing at $35, $200 and $500. Annual saves 28.6% on Prototyping and 30% on Starter and Scale, and adds concurrency.

Do reconnects cost extra?

Yes. Browserless says session reconnects count as new browser connections and incur a fresh unit charge, so a script that reconnects every 10 seconds pays a full 30-second unit each time.

How much do Browserless proxies cost per GB?

Residential proxy traffic uses 6 units per MB and datacenter traffic 2 units per MB. At overage rates that's $12.00, $10.20 or $9.00 per residential GB and $4.00, $3.40 or $3.00 per datacenter GB on Prototyping, Starter and Scale (my arithmetic, 1 GB = 1,000 MB). Traffic through your own proxy uses no proxy units.

Can I self-host Browserless for free?

Only under the SSPL-1.0 licence, which the README describes as free for non-commercial uses. Building a closed-source commercial app or running closed-source CI needs the commercial licence, whose price isn't published.

Which regions does Browserless run in?

San Francisco, London and Amsterdam on the cloud plans. There's no Asia-Pacific region; you can pick an exit country through the residential proxy's proxyCountry option. Enterprise lists more datacenter locations, including the EU.

Sources

26 sources, accessed .

Official pricing, docs, changelogs and status pages 15

  1. Browserless pricing page (annual view) browserless.io · accessed
  2. Browserless pricing.md (monthly and annual, FAQ) browserless.io · accessed
  3. Browserless docs: unit consumption docs.browserless.io · accessed
  4. Browserless docs: standard sessions docs.browserless.io · accessed
  5. Browserless docs: connection URLs and regions docs.browserless.io · accessed
  6. Browserless docs: terminology (concurrency and queue) docs.browserless.io · accessed
  7. Browserless changelog browserless.io · accessed
  8. Browserless blog: unit-based pricing (Dec 8, 2022) browserless.io · accessed
  9. Browserless blog: It's been 9 years (Nov 2026) browserless.io · accessed
  10. Browserbase pricing browserbase.com · accessed
  11. Browserbase docs: plans and billing docs.browserbase.com · accessed
  12. Hyperbrowser docs: pricing (credit rates) hyperbrowser.ai · accessed
  13. Cloudflare Browser Run pricing developers.cloudflare.com · accessed
  14. Steel pricing steel.dev · accessed
  15. Bright Data Browser API pricing brightdata.com · accessed

GitHub code, issues and releases 4

  1. Browserless LICENSE (SSPL-1.0 or commercial) github.com · accessed
  2. Browserless repository and README github.com · accessed
  3. Browserless releases (v2.63.1, Nov 13, 2026) github.com · accessed
  4. Browserless issues about timeouts github.com · accessed

Review platforms 2

  1. Toolradar: Browserless pricing toolradar.com · accessed
  2. CostBench: Browserless costbench.com · accessed

Community discussions 2

  1. Hacker News comment on Browserless cost (Mar 4, 2026) news.ycombinator.com · accessed
  2. Hacker News comment by the Browserless operator (Nov 11, 2026) news.ycombinator.com · accessed

Other blogs 3

  1. Activepieces: Browserless pricing plans and overage costs (Nov 12, 2026) activepieces.com · accessed
  2. Send.win: how to estimate Browserless pricing blog.send.win · accessed
  3. Scrapfly: Browserless alternative (competitor page) scrapfly.io · accessed

Last updated: 16 November 2026. Researched and drafted with AI tools; human editorial review and publication approval are pending.

What readers say

Used one of the tools in this guide? Tell other readers how it went. I read every review before it goes up, and I never turn one down for being negative. How reviews work.

No reader reviews yet. Yours could be the first.

Write a review
Your rating

What did you use it for, what worked, and what didn't? 30 to 1500 characters. Please don't include links.

Your connection to the company

Your review appears with the name you enter, after I approve it. I don't ask for your email. Privacy.