ZenRows Pricing: Real Cost per 1,000 Pages

The ZenRows pricing page leads with four prices: $16, $57, $165 and $456 a month. They are the yearly-billed rate for the first rung of each tier, and each tier actually has three rungs, so the headline grid shows four of the twelve paid plans. The month-to-month price of those four is $19, $69, $199 and $549.

Everything below was read from zenrows.com/pricing and the pricing page of the ZenRows documentation in September 2026, never from a review aggregator. Where the two ZenRows sources disagree, and on annual totals they do by a few dollars, we say so rather than pick one.

ZenRows pricing plans

The documentation lists the full ladder. Each tier has three rungs, and concurrency is set by tier rather than by rung, so moving from Launch L1 to L3 buys credits but not parallelism.

Basic is a 1 credit request, rendered is 5 credits, and protected means JavaScript rendering plus premium proxies at 25 credits. The last three columns are our arithmetic from the monthly price and the credit allowance, not figures ZenRows publishes.

How much does ZenRows cost per request?

It depends almost entirely on which flags you set, and the spread is 25 to 1. A standard request costs 1 credit. Turning on JavaScript rendering makes it 5. Premium proxies alone make it 10, and rendering plus premium proxies, which is what ZenRows calls a protected request, makes it 25. On Launch L2 that is the difference between $0.20 and $4.95 per 1,000 pages for the same URL.

So the useful way to budget is not to ask how many credits you need. It is to sort your target list into those three buckets first. A catalog of static product pages and a list of retail sites behind Cloudflare can sit on the same plan, and one will cost twenty-five times as much per page as the other.

Bandwidth products are metered differently again. Residential proxies cost 25,000 credits per GB on every plan, and Browser Sessions cost 25,000 credits per GB plus 5 credits for every minute a session stays open. ZenRows gives its own rule of thumb that 1 GB is roughly 1,000 protected pages, which is consistent with the 25 credit protected rate. A long-lived browser session that mostly waits is cheap in bandwidth and not in minutes, so keep sessions short.

Which ZenRows plan is the best value?

This is where the hidden rungs matter. Inside every tier, the first rung is the worst value, and the drop to the second rung is steep. The sharpest one on the ladder is Launch: L1 is $69 for 250,000 credits, and L2 is $99 for 500,000. Thirty dollars more buys twice the credits, and the price per credit falls 28 percent.

The headline grid only shows first rungs, which is why it is easy to buy L1 without realizing L2 exists. If your forecast lands anywhere between about 200,000 and 500,000 credits a month, L2 is almost always the right purchase over L1 plus a top-up.

Crossing a tier boundary buys something the rungs do not: concurrency. Build runs 20 concurrent requests, Launch 50, Growth 100 and Scale 200. If your job is a nightly batch that has to finish in a window, concurrency may bind before credits do, and the cheapest correct plan is the first rung of the tier that gives you the parallelism rather than the top rung of the tier below.

Does ZenRows charge for failed requests?

No, and that is a real advantage. ZenRows charges only for successful requests, so failed and retried attempts do not draw down the balance. The one qualification is that HTTP 404 and 410 responses count as successful, because in the documentation's words the request completed correctly and returned valid data. If your URL list is stale, and scraped URL lists usually are, you pay full rate for every dead page. Validate the list before a large run, not after.

What happens when ZenRows credits run out?

On a paid plan you can buy top-ups at any time to keep running, up to four times per billing period, and unused top-up credits roll into the next period. Unused plan credits also carry into the next billing period, once. On Free there are no top-ups at all: you wait for the monthly refresh or upgrade.

Four top-ups a period is a limit worth planning around rather than discovering. It also means a crawler stuck in a retry loop against a site that suddenly started demanding premium proxies can put several unplanned charges on the company card before anyone looks at the dashboard. Most teams handle that with a hard cap in their own code, and finance teams that already run real-time alerts on vendor card spend tend to catch it the same day rather than at month end.

Is ZenRows billed monthly or annually?

Either. Paying yearly gives two months free, which ZenRows describes as pay for 10, get 12, and it delivers the whole year's credit allowance up front as a single balance you can draw down at any pace. That second part is genuinely useful for bursty work: a team that scrapes heavily for one quarter and lightly for the rest can use a year of credits in three months without being on a large monthly plan all year.

The annual totals differ slightly between the two ZenRows sources. The documentation lists $190 a year for Build B1 and the pricing page shows $192, and the same few-dollar gap appears on the other tiers. It does not change any decision, but confirm the figure at checkout rather than from a screenshot.

Is ZenRows cheaper than a crawl API?

On static pages, often yes. At the same $99, ZenRows Launch L2 buys 500,000 basic requests, which is $0.20 per 1,000, while our Startup plan is $99 for 250,000 pages at $0.40. If your targets serve their content in the initial HTML and you are happy to parse it yourself, the ZenRows basic rate is the cheaper line item and we would not argue otherwise.

On rendered pages the order flips. ClawEngine includes rendering in one page of allowance, so $39 on Hobby buys 50,000 pages against 24,000 rendered pages on Build B3 at the same price, $99 buys 250,000 against 100,000, and $399 on Scale buys 1,500,000 against 600,000 on Growth G3. Per 1,000 rendered pages that is $0.78, $0.40 and $0.27 here, against $1.63, $0.99 and $0.67.

The row that decides it for many buyers is not in that table. ZenRows is built to get through Cloudflare, DataDome and PerimeterX, and we do not defeat anti-bot systems at all: we work on public and permitted pages only. If your targets fight back, ZenRows at 25 credits a protected page is the relevant price and ours is not an option. There is also no free tier here, while ZenRows gives 5,000 credits a month to evaluate with.

Where we win is output and the work after the fetch. ZenRows returns the page, and the cleaning and structuring for a model is still yours. ClawEngine returns clean markdown or typed JSON against a schema you send, from the same call that rendered the page, which is why teams feeding a retrieval index or an agent usually price the engineering time as well as the credits. The JavaScript rendering API page shows what that single call returns.

If you are still choosing between the anti-bot specialists, our ZenRows vs ScrapingBee comparison puts the two credit tables side by side, and ZenRows alternatives covers the wider field. For a platform with a very different meter, Diffbot pricing per page and per entity shows how a plan gate can matter more than a rate, and our web scraping API pricing breakdown puts every model in the category on one page.