ZenRows has reorganized its pricing more than once, and most of the pages that rank for this search describe an older version. The current model has one shared credit balance across everything ZenRows sells (Fetch, Extract, Batch and Browser Sessions) and a plan ladder where each plan comes in three sizes. That is flexible, but it makes the cost of a page hard to see at a glance.
This piece converts it. The plans, rungs and credit costs were read from zenrows.com/pricing and the machine readable version ZenRows publishes alongside it, on 28 September 2026. Vendors in this market change prices several times a year, so check the live page before you sign.
The ZenRows plans and their volume rungs
Every paid plan bills only successful requests (a 404 or 410 counts as a success), includes every product and interface, and allows up to four credit top ups per billing period. What changes between plans is concurrency and support. What changes between rungs of the same plan is only the credit allowance. Prices below are month to month.
| Plan and rung | Per month | Credits | Concurrency | USD per 1,000 credits |
|---|---|---|---|---|
| Build, 45K | 19 USD | 45,000 | 20 | 0.422 |
| Build, 80K | 29 USD | 80,000 | 20 | 0.363 |
| Build, 120K | 39 USD | 120,000 | 20 | 0.325 |
| Launch, 250K | 69 USD | 250,000 | 50 | 0.276 |
| Launch, 500K | 99 USD | 500,000 | 50 | 0.198 |
| Launch, 700K | 129 USD | 700,000 | 50 | 0.184 |
| Growth, 1.2M | 199 USD | 1,200,000 | 100 | 0.166 |
| Growth, 2M | 279 USD | 2,000,000 | 100 | 0.140 |
| Growth, 3M | 399 USD | 3,000,000 | 100 | 0.133 |
| Scale, 5M | 549 USD | 5,000,000 | 200 | 0.110 |
| Scale, 8M | 749 USD | 8,000,000 | 200 | 0.094 |
| Scale, 12.5M | 999 USD | 12,500,000 | 200 | 0.080 |
There is also a Free plan with 5,000 credits every month, no card and 5 concurrent requests, and an Enterprise plan priced on committed volume with 400 to 1,000 or more concurrent requests, an SLA and SOC 2 and ISO 27001 paperwork. Support steps up from email on Build to chat on Launch and priority on Growth and Scale.
Monthly or annual billing and the 16 USD question
The pricing page opens with the annual toggle already switched on, so the first numbers a visitor sees are 16, 57, 165 and 456 USD. Those are monthly equivalents of a yearly payment. ZenRows' annual deal is pay for 10 months and get 12, about 17 percent off, with the full year's credits available up front.
Month to month, the same entry rungs are 19, 69, 199 and 549 USD. Several review sites quote the annual figures as if they were the monthly price, so if you are budgeting a pilot you will cancel after two months, use the higher numbers. If you are confident in a year of volume, the discount is real and you can take every per 1,000 figure in this article down by about a sixth.
The credit multipliers that decide your bill
A plain request costs 1 credit. The switches that get you past modern sites multiply it. These are ZenRows' own published costs.
| Request type | Credits |
|---|---|
| Standard request | 1 per page |
| JavaScript rendering | 5 per page |
| Premium (residential) proxy | 10 per page |
| JavaScript rendering plus premium proxy | 25 per page |
| Residential bandwidth | 25,000 per GB |
| Browser Sessions | bandwidth plus 5 per minute |
| Extract and Batch | no extra charge beyond the fetch |
ZenRows describes the bandwidth rate as roughly 1,000 hard protected pages per GB, which is the same 25 credits a page as the rendered plus premium combination. That is a useful sanity check: for a protected site, plan on 25 credits a page whichever way you are billed. For an ordinary modern retail or listings site that needs a browser but not a residential address, plan on 5.
ZenRows cost per 1,000 pages, every plan and request type
Price per credit times the multiplier gives the number that belongs in a budget. All figures are USD per 1,000 successful pages on monthly billing, shown for the first and last rung of each plan.
| Plan rung | Standard (1) | JS rendering (5) | Premium proxy (10) | JS plus premium (25) |
|---|---|---|---|---|
| Build, 19 USD | 0.42 | 2.11 | 4.22 | 10.56 |
| Build, 39 USD | 0.33 | 1.63 | 3.25 | 8.13 |
| Launch, 69 USD | 0.28 | 1.38 | 2.76 | 6.90 |
| Launch, 129 USD | 0.18 | 0.92 | 1.84 | 4.61 |
| Growth, 199 USD | 0.17 | 0.83 | 1.66 | 4.15 |
| Growth, 399 USD | 0.13 | 0.67 | 1.33 | 3.33 |
| Scale, 549 USD | 0.11 | 0.55 | 1.10 | 2.75 |
| Scale, 999 USD | 0.08 | 0.40 | 0.80 | 2.00 |
In pages per month, the 19 USD Build rung buys 45,000 plain pages, 9,000 rendered ones or 1,800 protected ones. The Free plan's 5,000 credits cover 200 protected pages, which is enough to find out whether ZenRows gets through on your hardest target, and not much more.
The breakeven against flat per request pricing
Our plans charge one rate for every successful page, rendered or not, protected or not: 0.98 USD per 1,000 on the 49 USD Starter plan, 0.60 on Growth at 149 USD and 0.33 on Scale at 499 USD. Divide those by ZenRows' price per credit and you get the average credits per page at which the two cost the same.
Against the rungs nearest in price, the breakeven sits between about 2.3 and 5 credits a page. Starter at 0.98 matches Build 19 at 2.3 credits, Launch 69 at 3.6 and Launch 99 at 4.9. Growth at 0.60 matches Launch 99 at 3.0 and Growth 199 at 3.6. Scale at 0.33 matches Scale 549 at 3.0 and Scale 999 at 4.1.
That is the detail the review sites miss. A single JavaScript rendered page costs 5 credits on ZenRows, which is at or past the breakeven on every rung. So the question is not whether flat pricing wins for protected sites (it does, by a wide margin) but whether your workload is mostly plain HTML. If more than a small share of your pages need a browser, the multiplier model costs more.
Real budgets, ZenRows against flat per request pricing
Five realistic monthly workloads, each priced at the cheapest ZenRows rung whose credits cover it on monthly billing, against the cheapest of our plans that covers the page count.
| Monthly workload | Credits needed | ZenRows | Flat per request |
|---|---|---|---|
| 250,000 static pages | 250,000 | 69 USD, Launch | 149 USD, Growth |
| 50,000 rendered pages | 250,000 | 69 USD, Launch | 49 USD, Starter |
| 50,000 protected pages, rendered and premium | 1,250,000 | 279 USD, Growth 2M | 49 USD, Starter |
| 200,000 rendered pages, one in five protected | 1,800,000 | 279 USD, Growth 2M | 149 USD, Growth |
| 1,000,000 rendered pages | 5,000,000 | 549 USD, Scale | 499 USD, Scale |
The first row is honest and it matters: for static pages at volume ZenRows is less than half our price. Every other row goes the other way, and the protected row by more than five times. It is the same pattern we found converting ScrapingBee's credits and ScraperAPI's credits: multipliers are cheap for easy pages and expensive for the pages that actually cost money to fetch.
Where ZenRows is the right buy
Plain HTML at volume. At 0.08 to 0.20 USD per 1,000 on the larger rungs, static pages are cheaper on ZenRows than on our Scale plan, and we would not argue otherwise.
Concurrency at the entry level. The 19 USD Build rung runs 20 requests at once, against 5 on our Starter plan. If your job is many small, fast requests on a small budget, that matters more than the per page rate.
Interactive browser work. Browser Sessions let you drive a remote browser through logins, clicks and multi step flows, billed by bandwidth and minutes. That is a different product from a one request, one page API, and if your workflow needs it, it belongs in the comparison. The Free plan, with 5,000 credits every month rather than a one time trial, is also a genuinely useful way to keep a small internal tool running at no cost.
Where flat per request pricing wins
Rendered pages and protected sites, which is where most commercial scraping budgets go. A retailer behind Cloudflare, a travel site behind Akamai or a ticketing site behind DataDome is a 25 credit page on ZenRows. On a flat plan it costs what a static page costs, and refused attempts are not billed.
It also wins on forecasting. With multipliers, the bill depends on how many of your requests end up needing premium proxies, and that share moves every time a target changes its defenses. Pricing teams feel this most: a competitor price feed that quietly moves from 5 to 25 credits a page after a site upgrade can blow a quarter's budget in a week. If what you really need is the price alerts rather than the raw pages, a competitor price monitoring tool may be the simpler buy. If you need the data in your own pipeline, a flat rate turns the budget into pages times a number.
Most workloads are a mix. Run your real target list through ZenRows' free credits and through our plans for a day, then read the average credits per page from the ZenRows dashboard. Below about 3, ZenRows is likely cheaper. Above 5, flat pricing is.
Questions buyers ask
How much does ZenRows cost per month? On monthly billing, Build costs 19, 29 or 39 USD, Launch 69, 99 or 129 USD, Growth 199, 279 or 399 USD and Scale 549, 749 or 999 USD, for 45,000 up to 12.5 million credits. Paying annually cuts every price by about 17 percent. A Free plan gives 5,000 credits a month.
How much does ZenRows cost per 1,000 pages? Between about 0.08 and 10.56 USD. A plain page costs 1 credit, a rendered page 5, a premium proxy page 10 and a rendered page on premium proxies 25. On the 69 USD Launch rung that is 0.28, 1.38, 2.76 and 6.90 USD per 1,000 pages.
Does ZenRows have a free plan? Yes. The Free plan gives 5,000 credits every month with no card and 5 concurrent requests, with no rollover and no top ups. Some older reviews describe a 14 day trial instead; the current pricing page calls it a free plan, not a trial.
Does ZenRows charge for failed requests? No. Only successful requests use credits, and 404 and 410 responses count as successful. ScrapingBee, ScraperAPI, Zyte and we bill the same way, so it is standard in this market rather than a reason to pick one vendor.
Is ZenRows cheaper than ScrapingBee? Close, and it depends on the rung. At 49 USD ScrapingBee gives 250,000 credits, which ZenRows matches at 69 USD, while the multipliers for rendering (5) and rendering with premium proxies (25) are the same. ZenRows has more rungs in between, which helps if your volume falls between ScrapingBee's plans. The full numbers are in our ScrapingBee breakdown, alongside the Zyte, Oxylabs, Bright Data and Decodo conversions.
What happens when I run out of ZenRows credits? On a paid plan you can buy top ups up to four times per billing period, and unused top up credits roll into the next period. Unused plan credits also roll over once. On the Free plan you wait for the next month or upgrade.