How many credits does a JavaScript page cost?
A page rendered with JavaScript costs from 1 credit (Hyperbrowser) to 20 credits (ScrapeLens) on the 16 web scraping APIs here that bill in credits; 5 credits is the most common rate, on 7 of them. A credit buys different work on each API, so compare what a page costs in dollars, not in credits.
Worked out from each vendor's own pricing page; each vendor page on this site shows the day its price was read.| API | Plain page | With JavaScript | Protected sites |
|---|---|---|---|
| Hyperbrowser | 1 | 1 | not published |
| Crawlbase | 1 | 2 | not published |
| Scrape.do | 1 | 5 | 10 residential proxies |
| ScrapeOwl | 1 | 5 | 10 residential proxies |
| ScrapingBee | 1 | 5 | 75 stealth mode |
| ScrapingBot | 1 | 5 | 75 stealth mode |
| ScrapingDog | 1 | 5 | not published |
| WebScraping.AI | 1 | 5 | 10 residential proxies |
| ZenRows | 1 | 5 | 10 premium proxies |
| ScrapeBadger | 2 | 6 | 9 residential proxies |
| Scrapfly | 1 | 6 | not published |
| HasData | 1 | 10 | 5 residential proxies |
| ScrapeOps | 1 | 10 | not published |
| ScraperAPI | 1 | 10 | 10 premium proxies |
| ScrapingAnt | 1 | 10 how it combines is not published | 25 residential proxies |
| ScrapeLens | 20 | 20 | not published |
A rendered page uses the same credit balance as a plain one, at its own rate; where a vendor charges a protected-site mode on top of rendering, the protected figure is that mode's own rate as published. The credit converter turns any balance into pages on each API.
Why a rendered page costs more
Rendering a page means running a real browser: loading the page’s scripts, waiting for the content and returning the finished HTML. That takes far more compute than fetching the raw HTML, so vendors that bill in credits charge a rendered page several credits where a plain page costs one. Some add the rendering credits to the plain request, others multiply it, and a few replace it; each vendor’s own rule is used here.
Credits are not a common currency
Five credits on one API and five on another are not the same price, because each vendor sells its credits at its own rate and in its own plan sizes. Compare what a thousand rendered pages cost in dollars on the plan your volume needs: the calculator does that for every API, and the credit converter turns any credit balance into pages on each one.
Protected-site modes (premium or residential proxies, or a stealth mode) are the third rate most vendors publish. The table gives that mode’s own published rate; on some APIs it is charged on top of rendering, on others it includes it, as each vendor page explains.