ScraperFlyAI-ready Web Data API
Start free

pricing

Pricing built for testing first and scaling when the workload is proven

ScraperFly pricing keeps the buying path practical: start with free credits, use pay-as-you-go packs for uneven work, and choose monthly credits when production volume becomes steady.

Free

Free

Try ScraperFly with enough credits to run real test requests.

$01000 credits included

  • No card required
  • API access for testing
  • Upgrade only when you need more volume
Free sign up
No subscription

Pay as you go

Buy credits once and spend them whenever your project needs them.

Credit packsNo monthly commitment

  • Credits stay available until used
  • Best for uneven workloads
  • Switch here automatically if a subscription payment fails
Free sign up
Monthly

Solo

A compact monthly plan for small recurring scraping jobs.

$9.9910,000 credits every month

  • Unused credits roll over
  • Good for scheduled jobs and small monitors
  • Cancel or change plan from the customer portal
Free sign up
Monthly Popular

Growth

The balanced plan for teams running weekly scraping workflows.

$19.9930,000 credits every month

  • Unused credits roll over
  • Best default for production experiments
  • Enough room for rendering and premium routing when needed
Free sign up
Monthly

Team

Higher monthly credit volume for monitoring and production pipelines.

$49.99100,000 credits every month

  • Unused credits roll over
  • Built for frequent production workloads
  • Use the same dashboard, logs, and customer portal controls
Free sign up

Need more volume or custom limits? Contact support and we will map a plan around your targets, rendering mix, and routing needs.

Pricing logic

Understand what makes a scraping request lighter or heavier before you scale it

ScraperFly pricing should be read as delivery effort, not as a flat page counter. A simple HTML fetch is lighter; rendering, session state, premium routing, and geo-specific delivery add more work only when the target requires them.

A lightweight HTML request returning a simple response
01

Basic fetch

Use a basic fetch when public HTML already contains the fields you need.

Lightest request profile; keep it when the response is complete.

JavaScript rendering producing a complete DOM
02

Rendering

Use rendering when raw HTML is a shell and JavaScript completes the page.

Heavier profile; use it only when browser output changes the result.

Several requests preserving cookies and visitor state
03

Stateful session

Use sessions when cookies, consent, locale, or pagination change the response.

Heavier state profile; preserve it only when continuity matters.

Request routing through geo and higher quality routes
04

Premium routing & geo

Use premium routing or geo only when origin, country, reputation, or regional content changes the result.

Heaviest routing profile; apply it only to targets that prove they need it.

What makes a request heavier

More infrastructure work

Browser rendering, routing choices, and longer waits mean the platform has to do more than return a simple response.

More target uncertainty

Redirects, empty states, rate limits, and challenge pages often require stronger delivery options or retries.

More state to preserve

Cookies, sessions, consent, and multi-page flows add moving parts that a plain stateless fetch does not have.

More evidence to return

Screenshots, PDFs, rendered output, and richer response artifacts are useful, but they are heavier than plain HTML.

How to keep request weight predictable

Sample before scale

Test a small URL set first and group targets by the lightest profile that returns complete data.

Do not render by default

Inspect raw HTML before turning on rendering. Many public pages already contain the data you need.

Escalate by evidence

Move up only when the response shows missing content, state dependency, geo variance, or routing problems.

Measure useful results

Optimize around valid records delivered, not raw request volume. A lighter profile is best only when it stays complete.