Home / Web scraping APIs / Scrapfly
Scrapfly pricing
100,000 JavaScript-rendered pages a month cost $100.00 on Scrapfly's Pro plan, with room to grow to 158,333 pages on the same plan.
Checked Oct 12, 2026 on Scrapfly's own pricing page
- Discovery
- Pro
- Startup
- Enterprise
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 Scrapfly plan
| Plan | Covers | Billed monthly | Billed yearly, per month | Included | Past the allowance | Concurrent |
|---|---|---|---|---|---|---|
| Discovery | 10K to 25K pages | $30.00 | not offered | 200,000 credits | move to a bigger plan | 5 |
| Pro fits your volume | 50K to 100K pages | $100.00 | not offered | 1,000,000 credits | $0.35 per 1,000 credits | 20 |
| Startup | 250K to 500K pages | $250.00 | not offered | 2,500,000 credits | $0.20 per 1,000 credits | 50 |
| Enterprise | 1M pages | $500.00 | not offered | 5,500,000 credits | $0.12 per 1,000 credits | 100 |
Scrapfly's pricing page says failed requests are never charged and its billing documentation lists charged failure statuses; at this volume it makes no difference, because even if every failed attempt were charged the Pro plan's 1,000,000 credits cover the job for $100.
Your job
What Scrapfly bills you for
What you pay
Scrapfly is also sold as one of the AI extraction APIs (100,000 AI extraction operations a month: no public price).
About this price and its sources
How Scrapfly adds proxy class, JavaScript, and excess bandwidth to request credits, including failure protection and buyer fit.
Cite this price
100,000 JavaScript-rendered pages a month cost $100.00 on Scrapfly's Pro plan, with room to grow to 158,333 pages on the same plan. Price read from https://scrapfly.io/pricing on Oct 12, 2026. Scraping API Prices, https://scrapingapiprices.com/scrapfly-pricing
How the bill builds up
- Base rate1 creditper request
- → JavaScript rendering6 creditsper request; replaces the base rate
- × Premium proxyNot requiredNot part of this workload
- ÷ Success rate0.95Failure billing is not published; this is an assumption
- = Billed units per page you keep6.3158 creditsFrom this bill’s calculation
- = per 1,000 pages kept$1.00Pro, 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 · $100.00
Read the chart as a table
| Volume | Bill | Offer |
|---|---|---|
| 10,000 | $30.00 | Discovery |
| 25,000 | $30.00 | Discovery |
| 50,000 | $100.00 | Pro |
| 100,000 | $100.00 | Pro |
| 250,000 | $250.00 | Startup |
| 500,000 | $381.58 | Startup |
| 1,000,000 | $597.89 | Enterprise |
Follow each billed unit
-
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
Failure billing is not published, so this assumes all 105,263 attempts are billed.
- × 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: 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 → 631,579 credits → Pro $100.00/mo = $1.00 per 1,000 pages kept
The arithmetic, line by line
- pages: 1 credit per request source
- JavaScript rendering: 6 credits per request source
- billed on up to 105,263 attempts, not 100,000 successes, because failure billing is not published; conservatively assumes every attempt consumes quota; either failure rule selects the same plan at $100.00 source
- consumes 631,578.95 credits per month
- cheapest way to buy that: Pro, 1,000,000 included = $100.00 per month source
- 368,421 of the included allowance goes unused, 37% of what you buy
What makes it cost more
One page is not always one billed unit. These are Scrapfly's published charges for each kind of work.
| Work | Costs | Per | Source |
|---|---|---|---|
| A standard page | 1 credit | request | source |
| JavaScript rendering | 6 credits | request | source |
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. Showing 6 of 11; see the rest.
What Scrapfly does not publish
- Annual self-serve pricing (Scrapfly pricing, Jul 26, 2026).
- Public affiliate terms (Scrapfly pricing, Jul 26, 2026).
- 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 (Scrapfly billing documentation, Jul 26, 2026).
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, checked Jul 26, 2026.
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, checked Jul 26, 2026.
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, checked Jul 26, 2026.
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, checked Jul 26, 2026.
Scrapfly head to head
Both bills for the same job, and the volume where the cheaper one changes.