ZenRows review75 of 100, good
5,000 free credits a month without a card, Build at $16 for 45,000, and one shared balance where a standard page is 1 credit, a JavaScript page 5 and a hard-protected one 25.
Reviewed 2026-09-18 by Phillip Paul Inker. Facts re-read 2026-09-18. 2 sources. www.zenrows.com. Brand searches: 6,600 a month worldwide (Google, read 2026-09-18).
A clear ladder: five paid tiers from $16 to $456, concurrency printed on each, rollover on paid plans, and the credit rule stated in one sentence. What is missing is any success or latency figure; the word on the page is reliable, not a number.
Best for: Teams that want a free monthly allowance to test on and a plan ladder they can read in a minute.
Build is $16 a month for 45,000 credits, $0.36 per 1,000 standard pages; a JavaScript page costs five credits, $1.78 per 1,000. Scale is $456 for 5,000,000, $0.09 per 1,000. Annual billing saves 17%.
Standard, JavaScript and hard-protected fetches from one balance, a residential network at scale from Growth, Extract at no cost beyond the Fetch it uses, and Batch at the same per-request rate; SOC 2 and ISO 27001 on Enterprise.
Concurrency is printed per plan, 5 free to 200 on Scale and 400 to 1,000+ on Enterprise, and only successful requests are charged; no success rate or latency figure.
The documentation names SDKs for Python and Node.js, a CLI, an MCP server and Playwright and Puppeteer lanes.
Credits, concurrency, support level, rollover and the credit rule for the three page classes sit on the pricing page without an account; prices in US dollars.
5,000 free credits every month without a card, top-ups and rollover on paid plans, a monthly refresh with no rollover on Free; refund terms not on the pages read.
Every scraper in the database on one axis, rank 5 of 14. The zones are the grades.
Google Ads Keyword Planner, worldwide searches for “zenrows”, read 2026-09-18. Demand, not quality: the rubric ignores it.
- 5,000 free credits every month, no card
- The credit rule for the three page classes is one sentence on the page
- Rollover on paid plans
- Concurrency printed on every tier
- A hard-protected page costs 25 credits, $8.89 per 1,000 on Build
- No success rate or latency published
- Refund terms not on the pages read
- Plans
- Free $0 (5,000 credits, 5 concurrent), Build $16 (45,000, 20), Launch $57 (250,000, 50), Growth $165 (1,200,000, 100), Scale $456 (5,000,000, 200), Enterprise custom (400 to 1,000+) [1]
- Credit rule
- About 250,000 standard pages, 50,000 with JavaScript, or 10,000 hard-protected from a 250,000-credit balance [1]
- Annual billing
- Save 17% [1]
- Rollover
- Top-ups plus one month rollover on Build, top-ups plus rollover from Launch; none on Free [1]
- Extract and Batch
- Extract adds no cost beyond the Fetch request it uses; Batch bills at the same per-request rate [1]
- Enterprise
- SLA, SOC 2, ISO 27001, DPA, dedicated account manager [1]
- Integration
- Python and Node.js SDKs, CLI, MCP server, Playwright and Puppeteer, per the documentation [2]
| Challenge | Price | Unit | Note | |
|---|---|---|---|---|
| 1,000 requests, entry plan | $0.36 | per 1,000 standard pages, Build at $16 a month for 45,000 credits | $1.78 per 1,000 with JavaScript, five credits each; 20 concurrent requests | [1] |
| 1,000 requests, mid plan | $0.23 | per 1,000 standard pages, Launch at $57 a month for 250,000 credits | 50 concurrent requests, chat support | [1] |
| JavaScript rendering | 5 credits | per page | 1 credit for a standard page, 25 for a hard-protected one, from the one shared balance | [1] |
| Free tier | $0 | 5,000 credits a month, no card, 5 concurrent requests | Monthly refresh, no rollover | [1] |
What the plan page says
Six tiers. Free is $0 for 5,000 credits a month with no card, everything unlocked, 5 concurrent requests, community support and a monthly refresh without rollover. Build is $16 a month for 45,000 credits and 20 concurrent requests with email support and one month of rollover; Launch $57 for 250,000 and 50 with chat support; Growth $165 for 1,200,000 and 100 with priority support and the residential network at scale; Scale $456 for 5,000,000 and 200 with committed capacity options. Enterprise is custom: unlimited volume, 400 to 1,000+ concurrency, an SLA, SOC 2, ISO 27001 and a DPA. Annual billing saves 17%; prices are in US dollars.
One balance, three page classes
The page states the rule under the credit slider: a 250,000-credit balance runs about 250,000 standard pages, 50,000 with JavaScript, or 10,000 hard-protected, all from one shared balance. That is 1, 5 and 25 credits. Extract adds nothing beyond the Fetch request it uses and Batch bills at the same per-request rate, so the multiplier is the whole price story.
Integration and terms
The documentation hub names Python and Node.js SDKs, a CLI, an MCP server and Playwright and Puppeteer lanes. Terms on the pricing page: pay only for successful requests, a free tier that refreshes monthly, top-ups and rollover on paid tiers. A refund policy was not on the pages read.
Questions people ask
What does the free tier include?
5,000 credits a month with no card, everything unlocked, 5 concurrent requests and community support; the balance refreshes monthly and does not roll over, per the pricing page.
How many credits does a JavaScript page cost?
Five, per the rule on the pricing page: a 250,000-credit balance runs about 50,000 pages with JavaScript. A hard-protected page is 25.
Do unused credits roll over?
On Build, top-ups plus one month of rollover; from Launch, top-ups plus rollover; never on Free, per the pricing page.
- The pricing page draws its content by script; it was read in a browser on our server.
- Refund terms were not on the pages read.
- The per-1,000 figures are the plan price divided by its credits, our arithmetic on the vendor's numbers.
- [1]ZenRows pricing ZenRows, read 2026-09-18.
“Free $0 /mo 5,000 credits/month · no card 5 concurrent requests. Build $16 /mo 45K credits/month 20 concurrent requests Top ups + 1 month rollover. Launch $57 /mo 250K credits/month 50 concurrent requests. Growth $165 /mo 1.2M credits/month 100 concurrent requests. Scale $456 /mo 5M credits/month 200 concurrent requests. Runs about 250K standard pages, 50K with JavaScript, or 10K hard-protected, all from one shared balance. SAVE 17%.”
- [2]ZenRows documentation ZenRows, read 2026-09-18.
“SDKs, CLI, MCP, Python, Node.js, Playwright, Puppeteer named on the documentation hub.”
Badge for ZenRows’s own site
Certificate SC-85521A, valid until 2027-09-18. Every badge links to it, so a reader can check the score is genuine. Eight looks on the badges page.
Shows ZenRows’s current score, 75 of 100, good. Dark card, for most pages. It links to certificate SC-85521A, valid until 2027-09-18, and changes by itself when the review does.
<a href="https://scraper-reviews.com/certificate/SC-85521A"
title="ZenRows certificate SC-85521A on Scraper Reviews">
<img src="https://scraper-reviews.com/badge/scrapers/zenrows.png"
width="320" height="84"
alt="ZenRows: 75 of 100 on Scraper Reviews"
loading="lazy">
</a>Compared head to head
Other scrapers
Scrape.dosubscriptionThe most legible pricing in this database: the plan card prints the price per 1,000 credits, the documentation prints what each request type and each named domain costs, and only successful requests count. A 99.98% success figure on the homepage is a claim, not a method.
Decodoper requestThe pricing table answers the question every other vendor makes you compute: standard proxies, standard with JavaScript, premium proxies, premium with JavaScript, each priced per 1,000 requests on each plan, with the rate limit beside it. A free starter plan and a 14-day money-back line finish it.
ScrapingBeesubscriptionThe credit table is the review: a plain request is one credit, the default headless-browser request five, premium proxies ten, both together twenty-five, stealth proxies seventy-five. Cheap for plain fetches, ordinary once JavaScript and premium proxies are on.
Run a scraping API?Get it on the record.
Send us the pages that state your prices, credit costs and limits. We read them, score them on the public rubric, and publish the review with the date.