Scraping API PricesAll products / Scrapfly
Scrapfly pricing
How Scrapfly adds proxy class, JavaScript, and excess bandwidth to request credits, including failure protection and buyer fit.
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.
Your job
What Scrapfly counts
What you pay
Successes you want
100,000 pages
Your stated workload. Every vendor on this site is priced against this same number.
- ÷ 0.95
Attempts you are billed for
105,263 requests
Scrapfly bills failed fetches, so a 5% failure rate is billed work.
- × 6
What the meter counts
631,579 credits
One attempt is not one billed unit here: this workload multiplies by 6 before any money is involved.
- =
Cash per month
$100.00 /mo
Pro. Cheapest of every eligible purchase option, not the first plan that fits.
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 → 631,579 credit → Pro $100.00/mo = $1.00 per 1,000 pages kept
The arithmetic, line by line
- pages: 1 credit per requestsource
- request.js_render: 5 credit per requestsource
- billed on 105,263 attempts, not 100,000 successes, because this vendor charges for failed requestssource
- consumes 631,578.95 credit per month
- cheapest way to buy that: Pro, 1,000,000 included = $100.00 per monthsource
- 368,421 of the included allowance goes unused, 37% of what you buy
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. Unknown totals never enter the numeric order.
Every Scrapfly plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Discovery | $30.00 | n/a | n/a | 200,000 credit | 5 |
| Pro your job | $100.00 | n/a | n/a | 1,000,000 credit | 20 |
| Startup | $250.00 | n/a | n/a | 2,500,000 credit | 50 |
| Enterprise | $500.00 | n/a | n/a | 5,500,000 credit | 100 |
What consumes a unit
This is where a bill actually grows. One operation is not one billed unit, and the multiplier is published here rather than on the pricing page.
| Operation | Costs | Per | Source |
|---|---|---|---|
| request.basic | 1 credit | request | source |
| request.residential_proxy | 25 credit | request | source |
| request.js_render | 5 credit | request | source |
What Scrapfly does not publish
- No public annual price was obtainable.
- No public affiliate terms were obtainable.
What Scrapfly is
Scrapfly is a developer platform for page scraping and structured extraction with proxy routing, JavaScript rendering, browser actions, and an automatic scraping-protection option. The buyer sends a scrape request and can choose datacenter or residential access, rendering, extraction, and other controls rather than running the underlying network and browser fleet. It is for engineering teams that want a configurable API and are prepared to observe how page size and automatic protection affect consumption. Sources: Scrapfly and Scrapfly billing documentation, retrieved 2026-07-26.
ScraperAPI, ScrapingBee, and ZenRows are the nearest named competitors. Each provides managed web access, but Scrapfly stands apart in its public formula: proxy class sets the base credit cost, JavaScript adds credits, excess request or response data adds bandwidth credits, and automatic protection may upgrade the proxy class. Sources: ScraperAPI pricing, ScrapingBee pricing, ZenRows pricing, and Scrapfly billing documentation, retrieved 2026-07-26.
How billing works
One unit is one credit. A datacenter request and a residential request have different replacement base costs. JavaScript rendering adds credits to either base. Text or structured responses above the included size, large request bodies, and browser responses above their included size consume additional bandwidth credits in fixed data increments. Automatic Scraping Protection can change the proxy class and therefore the base cost. Failure protection normally excludes eligible HTTP 4xx and 5xx responses, but listed client-error statuses remain billable, and protection can be disabled when eligible failures exceed the published fairness threshold over its measurement window. The common buying mistake is to budget by request count alone. Proxy class, rendering, transferred data, and protection escalation can all change the credits used by one request. Source: Scrapfly billing documentation, retrieved 2026-07-26.
What Scrapfly does not publish
- Annual self-serve pricing. Source reviewed: Scrapfly pricing, retrieved 2026-07-26.
- Public affiliate terms. Source reviewed: Scrapfly pricing, retrieved 2026-07-26.
- A domain-by-domain forecast of when Automatic Scraping Protection will upgrade the proxy pool. The billing guide explains the billing consequence, not a preflight classification table. Source reviewed: Scrapfly billing documentation, retrieved 2026-07-26.
Unused credits do not roll over, and pay-as-you-go has a default cap tied to the monthly quota. Source: Scrapfly pricing, retrieved 2026-07-26.
Who it suits
Scrapfly suits teams that can measure response sizes and proxy-class selection in a representative test and want explicit handling of eligible failures. It is less suitable for buyers who need a fixed credit cost per URL regardless of payload size or automatic protection decisions. The reason is that its billing follows actual retrieval resources more closely than a single request counter. Sources: Scrapfly pricing and billing documentation, retrieved 2026-07-26.
Answer
Scrapfly's dated 2026-07-26 price snapshot gives $100.00 for 100,000 JavaScript-rendered pages on its Pro offer. This older figure is excluded from rankings; check the vendor before buying.
Recorded 2026-07-26 from the vendor's own pricing page.We could not confirm this price in the latest check, so it remains visible for context but cannot lead a price ranking. Check the vendor's pricing page before buying.