All products / Bright Data Browser API

Bright Data Browser API pricing

How Bright Data Browser API bills transferred traffic, what its public rate card omits, and which browser workloads fit.

Not comparablePrice recorded on 2026-07-25Older price from 2026-07-25; excluded from rankings1 vendor sourceSee the calculation
Available volumes
Included in this bill

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

Workload200 browser hours
Included in this billpublished session-time meter only
Bills failed fetchesnot published
per browser hournot computable for this state

What Bright Data Browser API counts

Nothing to count: Bright Data Browser API publishes no rate for metered browser session time. Its 1 published billing meter prices other work.

What you pay

Not comparable hereNot comparableThis product publishes no rate for this kind of work.no purchasable offerno published rate for browser.session_time
  1. Successes you want

    200 browser hours

    Your stated workload. Every vendor on this site is priced against this same number.

  2. ÷ 1

    Attempts you are billed for

    200 browser hours

    Bright Data Browser API bills failed fetches. This workload assumes none fail, so nothing is added here.

  3. Cash per month

    Not comparable here

    no published rate for browser.session_time

Bars share one linear scale across the 2 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.

Not comparable. This product publishes no rate for this kind of work.

no published rate for browser.session_time

This is a finding about what Bright Data Browser API publishes, not a gap in the data. It stays visible so a definitive market claim cannot quietly ignore it.

Published exact bills for comparable products

Same 200 metered browser-session hours a month, excluding separate proxy and model charges, ranked by what you would actually be billed. Unknown totals never enter the numeric order.

Every Bright Data Browser API plan

Published plans, with the offer this workload actually selects marked
PlanMonthlyIf billed yearlyPrepaid packIncludedSimultaneous sessions
Pay As You Go$0.00n/an/an/an/a
71 GB$499.00n/an/a71 gbn/a
166 GB$999.00n/an/a166 gbn/a
399 GB$1,999.00n/an/a399 gbn/a

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.

Every published way Bright Data Browser API charges
OperationCostsPerSource
proxy.residential_bandwidth8 usdgbsource

What Bright Data Browser API does not publish

What Bright Data Browser API is

Bright Data Browser API is a managed remote browser service with proxy routing and website-unblocking features built into the connection. It is intended for developers running browser automation through a WebSocket or HTTPS connection. Browserbase, Browserless, and Anchor Browser are its nearest commercial comparisons, but their public plans foreground browser hours, proprietary units, or task and infrastructure meters. Bright Data Browser API instead foregrounds traffic transferred through the managed browser. That distinction matters most for long interactive sessions and asset-heavy pages. Sources: Bright Data Browser API, Bright Data Browser API FAQ, Browserbase pricing, Browserless pricing, and Anchor pricing documentation, retrieved 2026-07-26.

How billing works

One billable unit is a gigabyte of traffic transferred through Browser API. The workload multiplier is therefore total browser traffic, not session count or elapsed browser time. Committed plans change the per-gigabyte rate, and premium domains can use a higher rate that appears in the customer’s Browser API configuration. The common buying mistake is to estimate cost from the number of pages or browser hours. Two workflows with the same page count can consume different bandwidth because page assets, downloads, media, and repeated navigation change the transferred bytes. Sources: Bright Data Browser API product and pricing page and Browser API FAQ, retrieved 2026-07-26.

What Bright Data does not publish for Browser API

  • The premium-domain rate before a buyer configures the relevant Browser API zone. Source reviewed: Browser API FAQ, retrieved 2026-07-26.
  • The traffic or account credit included in the advertised free trial. Source reviewed: Bright Data Browser API, retrieved 2026-07-26.
  • A numeric concurrency limit on the public Browser API pricing page. Source reviewed: Bright Data Browser API, retrieved 2026-07-26.
  • A refund or exclusion rule for transferred traffic from sessions that ultimately fail to deliver a useful result. Sources reviewed: Bright Data Browser API and Browser API FAQ, retrieved 2026-07-26.

Who it suits

Browser API suits teams that specifically need an interactive managed browser and can measure bytes transferred in a representative test. It can be easier to model when sessions are long but traffic stays controlled, because the public model does not add a separate browser-hour charge. It is less suitable for workflows that routinely load large assets or download files, and for procurement that must know premium-domain treatment before opening an account. The reason is the bandwidth meter: cost follows what moves over the connection, while the most sensitive domain-specific multiplier is not public. Sources: Bright Data Browser API and Browser API FAQ, retrieved 2026-07-26.

Answer

What Bright Data Browser API costs, what it publishes, and what it does not. Every figure sourced and dated.

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.