Scraping API PricesHyperbrowser vs ZenRows
The managed-browser-hour boundary between unified credits and a shared scraper and browser balance.
Hyperbrowser
ZenRows
The difference
Both paths, one ruler
Hyperbrowser
Successes you want
100,000 pages
Your stated workload. Every vendor on this site is priced against this same number.
- ÷ 0.95
Attempts you are billed for
105,263 requests
Hyperbrowser bills failed fetches, so a 5% failure rate is billed work.
- × 1
What the meter counts
105,263 credits
One attempt is one billed unit for this workload.
- =
Cash per month
$105.26 /mo
Startup. Cheapest of every eligible purchase option, not the first plan that fits.
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.
ZenRows
Successes you want
100,000 pages
Your stated workload. Every vendor on this site is priced against this same number.
- × 1
Attempts you are billed for
100,000 requests
ZenRows does not bill failed fetches, so failures cost nothing here.
- × 5
What the meter counts
500,000 credits
One attempt is not one billed unit here: this workload multiplies by 5 before any money is involved.
- =
Cash per month
$129.99 /mo
Startup. Cheapest of every eligible purchase option, not the first plan that fits.
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.
Both ladders share one linear scale, topping out at 500,000 counted units, so a longer bar means more billed work rather than a different drawing.
These figures are for one stated workload: 100,000 JavaScript-rendered pages a month at a 95% success rate. The comparison below names where the answer changes.
The boundary
For managed browser time before proxy bandwidth and higher-level API operations are added, Hyperbrowser is cheaper below 700 browser hours a month and ZenRows is cheaper from 700 hours upward. Hyperbrowser includes 5,000 recurring credits, equal to 50 browser hours at 100 credits per hour, then its Startup bundle and purchased-credit overage make the browser-time bill equal to $0.10 per hour after the included block. ZenRows begins with a $69.99 monthly plan and meters Scraping Browser time at $0.09 per hour against the account balance. At 699 hours Hyperbrowser is $69.90; at 700 it is $70 while ZenRows remains within its $69.99 floor. (Hyperbrowser pricing, Hyperbrowser billing documentation, ZenRows pricing documentation, retrieved 2026-07-26)
That 700-hour line is valid only for time. Both products separately meter residential proxy traffic, and ZenRows publishes plan-specific Scraping Browser bandwidth treatment that is not normalized into its Universal Scraper request table. Hyperbrowser publishes 10,000 credits per residential gigabyte in addition to browser time. Even a modest traffic difference can move the combined crossover, so buyers should model hours and gigabytes as separate rows. (Hyperbrowser billing documentation, ZenRows pricing documentation, retrieved 2026-07-26)
Billing models side by side
Hyperbrowser assigns a fixed $0.001 value to one credit. Browser time, residential bandwidth, Fetch pages, proxy-enabled Fetch, Search, and JSON extraction can all draw from the same balance, although they use different credit rates. Subscription credits refresh on renewal, while directly purchased credits expire after twelve months. The public docs do not say whether failed browser sessions or failed Fetch pages consume credits. (Hyperbrowser pricing, Hyperbrowser billing documentation, retrieved 2026-07-26)
ZenRows combines two billing paths. Universal Scraper uses replacement credit rates for basic, JavaScript, premium-proxy, and protected requests, while Scraping Browser consumes elapsed browser time plus bandwidth from the account balance. Failed Universal Scraper requests and internal retries are free, while HTTP 404 and 410 are billed as successful responses. Unused monthly balance does not roll over. Those request rules do not establish failure treatment for an elapsed browser session, so no session success assumption appears in this comparison. (ZenRows pricing documentation, retrieved 2026-07-26)
What each does that the other does not
Hyperbrowser’s reviewed product exposes Fetch, location-aware Search, and token-shaped JSON extraction beside managed sessions under one fixed-value credit denomination. ZenRows uniquely pairs its managed Scraping Browser with Universal Scraper modes for ordinary, rendered, premium, and protected page delivery under the same commercial balance. Hyperbrowser is therefore the broader higher-level browser-agent toolkit in this pair, while ZenRows gives a buyer an explicit protected-result request path alongside interactive browser control. (Hyperbrowser, Hyperbrowser billing documentation, ZenRows, ZenRows pricing documentation, retrieved 2026-07-26)
Who should pick which
Pick Hyperbrowser below 700 browser hours when the recurring free allowance, smaller paid floor, or shared Fetch, Search, and extraction balance fits the workload. Pick ZenRows at 700 hours and above when browser time dominates and its account floor is already being used, or when Universal Scraper can handle a portion of the queue without browser control. Do not apply the hour boundary to a page-delivery job that can use Fetch or Universal Scraper, because those endpoints use page meters rather than session time. (Hyperbrowser pricing, Hyperbrowser billing documentation, ZenRows pricing documentation, retrieved 2026-07-26)
The unverified edge is the combined browser bill. Hyperbrowser does not publish failed-session treatment or a separate CAPTCHA meter, while ZenRows does not provide one plan-independent browser-bandwidth rate in the reviewed request-credit table. Run a representative session, record elapsed time and transferred gigabytes, and verify the observed debit before using the 700-hour line for procurement. (Hyperbrowser billing documentation, ZenRows pricing documentation, retrieved 2026-07-26)