ZenRows Pricing: Build, Launch, Growth & Scale
Start on Free if you stay under 5,000 credits a month and 5 concurrent requests. Buy Build B1 ($19/month, or $16/month on the annual display) when easy or lightly rendered volume needs 45,000 credits. Step up inside Build, then Launch, as soon as JavaScript and protected weights — not raw URL counts — overflow the row you are on.
- Official families, checked November 6, 2026: Free $0 / 5,000 credits; Build monthly $19–$39 (B1 $19/45,000, B2 $29/80,000, B3 $39/120,000); Launch $69–$129 (L1 $69/250,000, L2 $99/500,000, L3 $129/700,000); Growth $199–$399; Scale $549–$2,999. Annual display is lower ($16–$33 / $58–$108 / $166–$333 / $458–$2,499) and is advertised as pay 10 months, get 12.
- Weights: standard 1, JS 5, premium proxies 10, protected (both) 25; residential 25,000 credits/GB; Browser = bandwidth + 5 credits/minute.
- Worth-it vs which-plan: this page picks a plan. Fit lives on the ZenRows review.
By Unfair Advantage · Updated November 6, 2026. Related: ZenRows review · ZenRows alternatives · Firecrawl vs ZenRows.
1. Who this pricing page is for
You already think a weighted scrape toolkit might be the product. You need the bill. This page maps official ZenRows prices and credit weights onto named workloads. It does not decide whether you wanted Markdown-for-agents or an actor platform — that is the review and the alternatives page.
Use this page when…
- You searched “ZenRows pricing” or “how much does ZenRows cost.”
- You need to know whether Free, Build, or Launch covers your mix of 1 / 5 / 10 / 25-credit requests.
- You want top-up math before you jump a family.
Leave this page when…
- You are still deciding if the toolkit is the right category — ZenRows review.
- You want leave paths — ZenRows alternatives.
- You want the Firecrawl fork — Firecrawl vs ZenRows.
UA did not generate a ZenRows invoice. Every figure below comes from the official pricing page and its schema.org JSON, checked November 6, 2026 (schema dateModified 2026-10-13). There is no affiliate button on this page.
2. Official plans and how credits work
The public page displays annual monthly rates first. Monthly billing is higher. Both are official; do not quote $16 as a month-to-month invoice if you did not pick annual.
| Family | Monthly billing | Annual display | Documented rows |
|---|---|---|---|
| Free | $0 | $0 | 5,000 credits, 5 concurrent, no card, no rollover, no top-ups. |
| Build | $19–$39 | $16–$33 | B1 $19 / 45,000 credits; B2 $29 / 80,000; B3 $39 / 120,000. |
| Launch | $69–$129 | $58–$108 | L1 $69 / 250,000; L2 $99 / 500,000; L3 $129 / 700,000. |
| Growth | $199–$399 | $166–$333 | A range — pick the vendor row that matches your credit target. |
| Scale | $549–$2,999 | $458–$2,499 | High-volume range. |
Official weights: standard request 1 credit; JavaScript rendering 5; premium proxies 10; JS + premium (protected) 25. Residential bandwidth 25,000 credits per GB. Browser sessions bill bandwidth plus 5 credits per minute. Failed requests are never charged; 404 and 410 count as successful/usable. Extract is currently described as free on top of Fetch. Batch is billed at the same rate as Fetch. Adaptive Stealth mode=auto starts light and bills only the setup that worked. Annual billing is advertised as pay 10 months, get 12.
3. Real cost by scenario
Calculations use official weights checked November 6, 2026. No retries. Adaptive Stealth can land below a “forced protected” estimate; we still show the forced number so you can see the ceiling.
Scenario A — 8,000 standard pages (no JS, no premium)
8,000 credits. Free holds 5,000, so you need Build B1 at $19/month (45,000 credits), or the $16 annual display if you prepay and the family is stable. Headroom: 37,000 credits — a lot, if the pages stay easy. If half of them later need JS, the month becomes 4,000 × 1 + 4,000 × 5 = 24,000 credits, still B1.
Scenario B — 8,000 JS-rendered pages
8,000 × 5 = 40,000 credits. Still Build B1 at $19, but only 5,000 credits remain. A 15% retry rate against pages that return usable 404s (which bill) would add 1,200 × 5 = 6,000 credits and overflow B1 into B2 at $29/month (80,000 credits). JS at this volume is a B1 story only if the site cooperates.
Scenario C — 4,000 protected pages (JS + premium)
4,000 × 25 = 100,000 credits. B2’s 80,000 is not enough. B3’s 120,000 is. Monthly cost: Build B3 at $39. If Adaptive Stealth resolves half of those URLs at the JS weight (5) and half at protected (25), you spend 2,000 × 5 + 2,000 × 25 = 60,000 credits — back to B2 at $29. That gap ($39 vs $29, and 100,000 vs 60,000 credits) is exactly why the vendor documents mode=auto. We will not promise your mix matches the happy half-and-half case.
Scenario D — 2,000 easy + 2,000 JS + 2,000 protected
2,000 × 1 + 2,000 × 5 + 2,000 × 25 = 2,000 + 10,000 + 50,000 = 62,000 credits → Build B2 at $29. Raise protected to 4,000 and keep the rest: 2,000 + 10,000 + 100,000 = 112,000 credits → still B3 at $39 (120,000). One more thousand protected pages (25,000 credits) would total 137,000 and need Launch L1 at $69 (250,000 credits).
Scenario E — 20 hours of Browser time plus 5,000 standard fetches
Browser time: 1,200 minutes × 5 = 6,000 credits, before bandwidth. Standard fetches: 5,000 credits. Combined fetch+time: 11,000 credits, which looks like a comfortable B1 — until residential bandwidth arrives. One residential GB is 25,000 credits. Two GB plus the 11,000 above is 61,000 credits (B2). Five GB plus 11,000 is 136,000 (Launch L1). Browser is two meters. Quoting only the 5-credits-per-minute line understates the bill whenever those minutes pull residential traffic.
Scenario F — Prototype on Free
5,000 credits and 5 concurrent requests, no top-ups. That is 5,000 standard pages, 1,000 JS pages, or 200 protected pages. A “protected-only” evaluation empties Free immediately. Design the sandbox as mostly standard and JS, with a handful of protected URLs, or you will learn nothing except that 200 × 25 = 5,000.
Worksheet
Credits = (standard URLs) + 5×(JS) + 10×(premium only) + 25×(protected), then add Browser minutes × 5 and 25,000 credits per residential GB. Compare to 5,000 / 45,000 / 80,000 / 120,000 / 250,000 / 500,000 / 700,000. Until you have Adaptive Stealth data, budget the ceiling (the weights you would force).
Example: 10,000 standard + 3,000 JS + 500 protected = 10,000 + 15,000 + 12,500 = 37,500 credits → B1 ($19). Raise protected to 2,000 and the total is 75,000 → B2 ($29). Raise it to 4,000 and the total is 125,000 → over B3, so Launch L1 at $69, even though most URLs were cheap. The expensive tail sets the plan.
4. Top-ups versus upgrading
Official materials: paid plans can buy top-ups up to 10× the period’s credits; unused top-up credits roll over once. Free has no top-ups. We do not have a public per-credit top-up sticker separate from that 10× cap, so we will not invent one. What we can say: a top-up is for a spike. If Scenario C (100,000 protected credits) is your new every-month baseline, sitting on B1 (45,000) and topping up 55,000 credits every cycle is using the spike tool as a plan. Move to B3 or Launch and reserve top-ups for the month a sitemap doubles.
Annual billing (pay 10, get 12): B1 at the $16 display is $192/year versus 12 × $19 = $228. Worth it if you will stay on Build; a bad prepay if next month’s protected mix is already a Launch problem.
5. Rollover and concurrency
Free: no rollover, no top-ups. Paid unused plan credits — the official Free line says no rollover there; paid top-up credits roll over once. Do not assume leftover Build credits behave like leftover top-up credits. If your finance team needs a rollover promise, read the vendor’s current wording for the exact SKU rather than extending the top-up rule to the whole plan.
Concurrency starts at 5 on Free. Higher families raise the cap on the vendor’s plan picker; we will not invent a number the public table we fetched did not list for every paid row. Check that figure on the plan you buy: extra credits will not clear a queue caused by the Free cap of 5.
6. Billing pitfalls
- Budgeting “pages” instead of weighted credits.
- Quoting the annual display as the monthly invoice.
- Forcing protected mode on every URL and then blaming the $39 or $69 invoice.
- Counting Browser minutes without GB.
- Treating 404/410 as free because failures are not charged.
- Using Free as if it had a top-up.
- Annual-prepaying Build the week before a protected-mode launch.
7. Which plan to pick
| Monthly shape | Published step |
|---|---|
| Under 5,000 credits, ≤5 concurrent, no need for top-ups | Free |
| Up to 45,000 credits (typical easy HTML or modest JS) | Build B1 $19 (or $16 annual display) |
| 45,000–80,000 credits | Build B2 $29 |
| 80,000–120,000 credits (often a protected-mode month) | Build B3 $39 |
| Toward 250,000 credits | Launch L1 $69 |
| 500,000 / 700,000 credits | Launch L2 / L3 $99 / $129 |
| Above that | Growth or Scale ranges on the official page |
Pick the plan for the weighted mix you will run next month, measure Adaptive Stealth on real URLs, then either top up a spike or step up a row. If the numbers already feel like the wrong category of expense, stop and reread the review: you may want a different tool, not a different ZenRows SKU.
8. FAQ
How much does ZenRows cost per month?
Free $0; Build $19–$39 monthly ($16–$33 annual display); Launch $69–$129 ($58–$108); Growth $199–$399 ($166–$333); Scale $549–$2,999 ($458–$2,499), checked November 6, 2026. Your invoice then depends on the 1 / 5 / 10 / 25 weights and on Browser or residential usage.
Why do I see $16 if Build starts at $19?
The public page highlights annual monthly rates. Monthly billing for B1 is $19 for 45,000 credits. Annual is advertised as pay 10, get 12.
Do unused credits roll over?
Not on Free. Paid top-up credits roll over once. Do not assume the same rule for unused plan credits without reading the SKU you are on.
How many credits is a protected request?
25, when JavaScript rendering and premium proxies are both used. JS alone is 5; premium proxies alone are 10.
Does a failed request cost credits?
Official materials say failed requests are never charged. 404 and 410 are treated as usable and do count.
Should I use Adaptive Stealth to lower the estimate?
For planning, no — budget the ceiling (the weights you would force) so you do not under-buy. For production, yes — official wording says mode=auto bills the setup that worked, which can land below that ceiling. After a week of real data, you can shrink the plan if the ceiling was pessimistic. Do not shrink it in advance and hope.
Do you have an affiliate link for ZenRows?
Not at the time this page was written. A hidden placeholder sits in the HTML for later; it is not visible and it does not point at a live vendor URL.
9. Sources
- ZenRows official pricing page (checked November 6, 2026)
- ZenRows official pricing page schema.org JSON, including monthly ranges and
dateModified2026-10-13 (checked November 6, 2026)