Home / Web scraping APIs / Scrape.do
Scrape.do pricing
100,000 JavaScript-rendered pages a month cost $99.00 on Scrape.do's Pro plan, with room to grow to 250,000 pages on the same plan.
Checked Oct 12, 2026 on Scrape.do's own pricing page
- Hobby
- Pro
- Business
- Advanced
Your workloadType an exact volume, change the success rate or copy a link to this jobEdit
Every available option was priced in advance from published vendor rules. Changing a control only switches between those checked options; nothing is sent anywhere and no account is needed.
Every Scrape.do plan
| Plan | Covers | Billed monthly | Billed yearly, per month | Included | Past the allowance | Concurrent |
|---|---|---|---|---|---|---|
| Hobby | 10K to 50K pages | $29.00 | $24.17saves 17% | 250,000 credits | move to a bigger plan | 10 |
| Pro fits your volume | 100K to 250K pages | $99.00 | $82.50saves 17% | 1,250,000 credits | move to a bigger plan | 50 |
| Business | 500K pages | $249.00 | $207.50saves 17% | 3,500,000 credits | move to a bigger plan | 100 |
| Advanced | 1M pages | $699.00 | $582.50saves 17% | 10,000,000 credits | move to a bigger plan | 200 |
Yearly billing is arranged through Scrape.do's support by chat or email, not at checkout.
Your job
What Scrape.do bills you for
What you pay
Scrape.do is also sold as one of the SERP APIs (100,000 standard searches a month: $99.00 on Pro) and one of the AI extraction APIs (100,000 AI extraction operations a month: no public price).
About this price and its sources
How Scrape.do bundles proxy and rendering modes into successful-request credit costs, what remains unknown, and who fits.
Cite this price
100,000 JavaScript-rendered pages a month cost $99.00 on Scrape.do's Pro plan, with room to grow to 250,000 pages on the same plan. Price read from https://scrape.do/pricing/ on Oct 12, 2026. Scraping API Prices, https://scrapingapiprices.com/scrape-do-pricing
How the bill builds up
- Base rate1 creditper request
- → JavaScript rendering5 creditsper request; replaces the base rate
- × Premium proxyNot requiredNot part of this workload
- ÷ Success rate1Failed requests are not billed
- = Billed units per page you keep5 creditsFrom this bill’s calculation
- = per 1,000 pages kept$0.99Pro, billed monthly
Credits and multipliers
JavaScript rendering
Billed failures
Success rate
Concurrency
Free tier
Renews monthly The bill at your volume
100,000 pages per month · $99.00
Read the chart as a table
| Volume | Bill | Offer |
|---|---|---|
| 10,000 | $29.00 | Hobby |
| 25,000 | $29.00 | Hobby |
| 50,000 | $29.00 | Hobby |
| 100,000 | $99.00 | Pro |
| 250,000 | $99.00 | Pro |
| 500,000 | $249.00 | Business |
| 1,000,000 | $699.00 | Advanced |
Follow each billed unit
-
Successes you want
100,000 pages
Your stated workload. Every vendor on this site is priced against this same number.
- × 1
Attempts you are billed for
100,000 requests
Scrape.do does not bill failed fetches, so failures cost nothing here.
- × 5
What the meter counts
500,000 credits
One attempt is not one billed unit here: this workload multiplies by 5 before any money is involved.
- =
Cash per month
$99.00 /mo
Pro: the cheapest way to buy this volume, not just the first plan big enough.
Bars share one linear scale across the 3 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.
100,000 pages divided by 95% success → 500,000 credits → Pro $99.00/mo = $0.99 per 1,000 pages kept
What makes it cost more
One page is not always one billed unit. These are Scrape.do's published charges for each kind of work; failed requests are not billed.
| Work | Costs | Per | Source |
|---|---|---|---|
| A standard page | 1 credit | request | source |
| JavaScript rendering | 5 credits | request | source |
| Residential proxies | 10 credits | request | source |
| Mobile proxies | 10 credits | request | source |
| Amazon pages | 1 credit | request | source |
| Google pages | 10 credits | request | source |
| Linkedin pages | 30 credits | request | source |
| JavaScript rendering with residential proxies | 25 credits | request | source |
Limits and terms
What Scrape.do publishes beyond the price: the limits a job runs into and the terms that change what a plan is worth. Each line links the page it comes from and the day it was read.
Speed, concurrency and sessions
- Async API concurrency is limited to 30 percent of the plan's regular concurrency pool. source, read Sep 2, 2026
Credits, renewal and billing
- Annual billing (ten months for twelve) is currently set up manually: contact support through chat or email to switch. source, read Oct 9, 2026
Cheaper for this job
Same 100,000 JavaScript-rendered pages a month at a 95% success rate, ranked by what you would actually be billed. APIs without a full public price aren't ranked.
What Scrape.do does not publish
- Scrape.do doesn't publish its full per-domain cost table.
- Scrape.do doesn't say when the free allowance renews.
- A complete live table of every domain-specific default and its resulting bundle cost (request-cost documentation, Jul 26, 2026).
- The renewal period for the free allowance in the readable pricing text (Scrape.do pricing, Jul 26, 2026).
- Effective annual plan amounts. The page directs buyers to support for annual discounts (Scrape.do pricing, Jul 26, 2026).
What Scrape.do is
Scrape.do provides a general web scraping API and a separate set of ready-made APIs for named targets such as Google, Amazon, YouTube, Maps, Shopping, Flights, Hotels, News, Trends, and ChatGPT. The general endpoint handles proxy rotation, headers, JavaScript rendering, interactions, and blocking countermeasures, while ready-made endpoints return parsed JSON for supported targets. It is for developers who want either page retrieval or a predefined target schema without operating browser and proxy infrastructure. Source: Scrape.do product page, checked Jul 26, 2026.
ScraperAPI, ScrapingBee, and ZenRows are the nearest named comparisons. All three sell managed page retrieval, but Scrape.do’s relevant distinction is its explicit replacement bundles for proxy and rendering modes alongside target-specific ready APIs. This means the buyer chooses a documented request class instead of assuming every feature creates an independent additive fee. Sources: ScraperAPI pricing, ScrapingBee pricing, ZenRows pricing, and Scrape.do request costs, checked Jul 26, 2026.
How billing works
One unit is a credit, but one successful request can consume different numbers of credits. A basic datacenter request is the base class. JavaScript rendering (5 credits), residential or mobile routing (10), the two together (25, not the larger of the two) and ready-made targets select higher published request bundles. Per-domain server defaults can override the requested mode, and the response cost header reports the observed charge. Billable responses include HTTP 2xx, 400, 404, and 410; other failed or blocked responses are not charged. The common buying mistake is to price from the parameter sent by the client rather than the bundle Scrape.do actually applies to that domain. Source: Scrape.do request-cost documentation, checked Oct 12, 2026.
Who it suits
Scrape.do suits teams that can inspect the returned cost header and want general retrieval plus ready-made target APIs in one account. It is less suitable when procurement must know every domain’s exact credit class before testing, or when the buyer assumes a requested low-cost mode cannot be upgraded by server defaults. The reason is that the bundle rules are published, but the domain-level selection table is not complete in the public material. Sources: Scrape.do, pricing, and request costs, checked Jul 26, 2026.
Scrape.do head to head
Both bills for the same job, and the volume where the cheaper one changes.