JavaScript rendering
Executing a page's JavaScript in a real browser before returning the HTML, so content that only exists after scripts run is captured.
Why it costs you money
It is the difference between a page and an empty shell, and it is billed as a premium. ZenRows draws 5 credits for a rendered request against 1 for a plain one, and ScrapingBee enables it by default so a basic request already costs 5. The need is not hypothetical: collecting evidence for this site, one vendor's terms page returned 1.9 MB of HTML and zero characters of readable text until a browser ran it. If the pages you want are built this way, the rendered rate is your real rate.
See it in the data
Related terms
- Credit (scraping API)Scraping APIs bill in credits, and one credit buys different amounts of work depending on the request. What each provider charges, with sources.
- Success-only billingSome scraping APIs charge only for requests that succeed. On a per-request product that is the largest single swing in what you pay.
- Concurrency limitThe cap on how many requests you can have in flight at once. Often the real constraint on a scraping job, not price.
- Every term we define