Which web scraping tool costs the least per successful page in 2026?

Every scraper starts at $19 a month. The real question is how many pages that buys on your target site.

Most "best scraper" lists are written by companies that sell one. They rank their own product first and quote the plan price. That price tells you very little. On a site behind bot protection, a single page can burn 25 times the credits of a plain HTML page. So we compared six extraction tools on the numbers that actually hit your card: the cost of 10,000 successful pages, how each one copes with Cloudflare, and the legal lines you should not cross.

The short answer: Apify if you don't code and someone has already built a scraper for your site. Firecrawl if the data feeds an LLM or an AI agent. ScrapingBee if you write your own code and want a bill you can predict. Octoparse for point-and-click on your desktop, Browse AI to monitor a handful of pages, and Zyte API for high volume billed only on success.

Shopping for proxy networks rather than extraction tools? Our ranking of web scraping tools and proxies covers that separately.

Romain CochardCEO, Hack'celeration
Updated 20266extraction tools ranked10,000pages in every cost estimate3families: no-code, API, open source

The ranking is editorial: a sponsored spot is always labeled on its card, and no affiliate link changes a score.

At a glance

6 extraction tools compared on cost per page

The price column shows the entry plan from each vendor's official pricing page, or from our full review when the tool has one. Rank follows the most common buyer (a growth or data team without a full-time scraping engineer), not just the score.

Best forWhat it does bestFree planTeam sizeVisit
1ApifyBest without codeReady-made scraper for most big sites4.2/5Free ($5 credit), Starter $39/mo✓Growth, ops, developersVisit →
2FirecrawlBest for AI pipelinesLLM-ready markdown or JSON4.1/5Free (1,000 credits), Hobby $19/mo✓Developers, AI productsVisit →
3ScrapingBeeBest API for developersJS rendering and proxies in one call3.9/51,000 free credits, Hobby $19/mo—Developers, small data teamsVisit →
5Browse AIBest for page monitoringAlerts when a page changes3.8/5Free (50 credits), Personal $48/mo✓Marketing, price trackingVisit →
6Zyte APIBest for high volumeBilled per successful response3.8/5$5 free, from $0.13 per 1,000 responses—Data teams, millions of pagesVisit →
4OctoparseBest desktop no-codePoint-and-click, free local runs3.7/5Free locally, Standard from $69/mo billed annually✓Non-technical usersVisit →

US dollar prices, excluding sales tax, read on each vendor's pricing page in 2026. Apify and Browse AI prices and scores come from our full reviews. A credit is not a page: see the 10,000-page math further down.

How we scored

How we compared and scored

You can't compare scrapers on their homepages. Every vendor shows a starting price and a credit count. What moves the bill is what one credit buys on your target: a plain HTML page, a page that needs JavaScript rendering, or a page behind an anti-bot wall that needs a residential proxy (an IP address that looks like a home connection).

We read each vendor's official pricing grid, their credit consumption rules and cancellation terms, plus the harshest user feedback we could find on Hacker News, GitHub issues and review sites. For every tool we worked out the cost of 10,000 pages, easy and hard where the grid allows. Apify and Browse AI scores come from their full reviews; Firecrawl, Octoparse and Zyte scores match those already published on our alternatives pages; ScrapingBee's score is set for this ranking.

What we left out, and why. Proxy-first vendors (Bright Data, Oxylabs, Thordata) mainly sell network access and live on their own ranking. PhantomBuster is built for LinkedIn and social automation, with account restriction risk. ScraperAPI, ParseHub and Thunderbit did not show a pricing grid we could read on their official pages. Open source (Scrapy, Playwright, Crawlee) is free to license but not free to run; it gets its own step in the playbook below.

  1. Real cost per pageCredits per easy and per protected page, rollover, extras such as proxy and storage.
    30%
  2. Bot protection handlingJavaScript rendering, proxy rotation, whether failures are billed.
    25%
  3. Time to first clean fileHow fast a non-engineer gets usable data.
    20%
  4. Output formatsCSV, JSON, markdown, push to Google Sheets or an API.
    15%
  5. Commercial termsReal free tier, trial, commitment, ease of cancelling.
    10%
6tools ranked
2scores from our full reviews
2026pricing grids reread

The ranking is editorial: a sponsored spot is always labeled on its card, and no affiliate link changes a score.

1
Best data extraction tool without code

Apify

4.2/5

Apify runs "Actors": prebuilt scrapers published in a public Store that you launch by filling in a form. For a popular site there is almost always an Actor already. Paste a URL, set how many results you want, and download CSV or JSON.

The bill has two layers. Your plan sets a monthly credit and a compute unit (CU) price: $0.30 on Free, $0.25 on Scale, $0.20 on Business. On top, many Actors charge per result at a price their developer chooses. For Google Maps, that ranges from $1 to $9.99 per 1,000 results depending on which Actor you pick. Two Actors that do the same job can differ tenfold.

Users like the per-run spending caps, which stop a runaway job from draining your balance. The complaints are consistent too: community Actors vary a lot in quality, finding the right one takes time, and pay-as-you-go "adds up" once proxies and storage, billed separately, join the party.

Tip: before you order 10,000 results, run the Actor on 100 and read the cost in the run history. Multiply by 100. Then try a second Actor for the same site and compare.

Standout features
  • Store of ready-made scrapers for common sites
  • Spending cap per run
  • API, webhooks and scheduling for automation
+Pros
  • ✓Zero code for common jobs
  • ✓Free plan good enough for a real trial
  • ✓Developers can publish their own Actors
−Cons
  • ✗Community Actors vary in quality
  • ✗Hard to forecast: CU, proxy, storage and Actor fees stack up
Verdict

The best starting point if you don't code, because the scraper often exists already. Watch the Actor's own price: that's what drives the bill.

See Apify plans →Read our Apify review
2
Best scraper for AI and LLM pipelines

Firecrawl

4.1/5

Firecrawl turns a web page into clean markdown (the format language models read best) or into structured JSON that follows a schema you define. It can also crawl a whole site from one starting URL. Reach for it when the data ends up in an LLM rather than a spreadsheet.

Its grid is one of the easiest to read: 1 credit per page. Hobby gives 5,000 credits for $19, Standard 100,000 for $99, Growth 500,000 for $399. Two catches. JSON output costs 4 extra credits per page, 5 in total. And unused credits expire at month end, except on Scale (one month) and Enterprise.

There is an open source version you can self-host. On GitHub, several issues describe the self-hosted build getting blocked by Cloudflare on sites the cloud version handles. The managed anti-blocking layer is what you pay for, and the free build does not include it.

Tip: if you only need the text, stick to markdown. You pay a fifth of the JSON price, and an LLM can pull fields out of markdown perfectly well afterwards.

Standout features
  • LLM-ready markdown or JSON output
  • Full-site crawl from one URL
  • Open source version available
+Pros
  • ✓Readable grid: 1 credit per page
  • ✓1,000 free pages, no commitment
  • ✓One call returns clean text, no parser to write
−Cons
  • ✗JSON output at 5 credits per page
  • ✗Credits expire monthly except on Scale
  • ✗Self-hosted build weaker against bot walls
Verdict

The natural pick for an AI project: clean text without writing a parser. For a price-tracking spreadsheet, something else will be cheaper.

See Firecrawl plans →
3
Best web scraping API for developers

ScrapingBee

3.9/5

ScrapingBee is an API. Your code sends a URL; you get back the page HTML, rendered in a real browser when needed, fetched through a proxy it picks. You keep control of parsing and offload the part that breaks most often.

Mind the multiplier. A plain request costs 1 credit. JavaScript rendering, 5 credits. Premium proxies, 10 or 25 credits depending on options. So the 250,000 credits in Freelance are 250,000 easy pages, or 10,000 hard ones. On the plus side, the pricing page says you pay for successful requests.

Concurrency runs from 25 parallel requests on Hobby to 100 on Startup. For a small team, Hobby at $19 easily covers 10,000 plain pages a month (10,000 of 75,000 credits).

Tip: don't turn on JavaScript rendering by default. Fetch the page without it first, check whether the data is already in the HTML, and only pay for the browser on pages that really need it. On an e-commerce catalog that's often the gap between Hobby and Startup.

Standout features
  • JS rendering and proxy rotation in one call
  • Billing on successful requests
  • Up to 100 concurrent requests on Startup
+Pros
  • ✓Low entry price for plain pages
  • ✓You keep your own parsing code
  • ✓1,000 credits to try, no card
−Cons
  • ✗You need to code
  • ✗Cost multiplied by 25 on the most protected pages
Verdict

The most predictable bill for a developer, as long as you control the options that multiply credits.

See ScrapingBee plans →
4
Best desktop no-code scraper

Octoparse

3.7/5

Octoparse is a desktop app. You open the page in its built-in browser, click a price, a title and the "next" button, and it works out the pattern. It also ships templates for common sites. It's the most visual approach in this ranking.

The free plan is real: 10 tasks, one device, runs on your machine, up to 10,000 rows per export and 50,000 rows a month. Cloud runs (on Octoparse servers, laptop closed) start with Standard, from $69 a month billed annually for 100 tasks and 3 parallel cloud processes. Professional is $249 a month billed annually.

The catch is commercial as much as technical. Octoparse's own billing docs say a trial turns paid unless you cancel before it ends, and you must cancel on the website, at least a day before renewal, not through PayPal. On review sites, users describe being charged after a trial and refused a refund. Pagination setup is called "not very intuitive", and some runs come back incomplete.

Tip: stay on the free plan as long as your computer can stay on during the run. If you start the trial, set a reminder two days before it ends.

Standout features
  • Click-to-select data in a built-in browser
  • Templates for common sites
  • Free plan with local runs
+Pros
  • ✓No code at all
  • ✓Free up to 50,000 rows a month locally
  • ✓Support praised as quick in reviews
−Cons
  • ✗Trial auto-converts unless cancelled
  • ✗Cloud only on paid plans, priced annually
Verdict

The easiest way to scrape without code from your own machine. Note the trial end date: that's where most bad experiences start.

See Octoparse plans →
5
Best tool for monitoring web pages

Browse AI

3.8/5

Browse AI works with "robots" you record by showing it what you want on a page. It then reruns them on a schedule and sends the results to Google Sheets or a webhook. Its sweet spot is monitoring: it tells you when a price or a block of text changes.

The free plan gives 50 credits a month across 2 sites, enough to confirm it can read your page. Personal is $48 a month and Professional $87 a month. A task can run 5 minutes max on Free and 60 minutes on paid plans, and data is kept for 90 days.

The downside: per-credit pricing gets expensive once you go past a few hundred pages. Negative reviews mention slow support, password resets that never arrive and charges after cancelling. The vendor's claim that robots adapt to site changes on their own is worth checking on your own pages.

Tip: point Browse AI at the pages that matter (a competitor's 50 best sellers), not a whole catalog. For 10,000 pages, a simple per-request API is cheaper.

Standout features
  • Record a robot in a few clicks
  • Change alerts on monitored pages
  • Data kept for 90 days
+Pros
  • ✓Fastest setup in this ranking
  • ✓Free plan to validate your page
  • ✓Direct export to Google Sheets
−Cons
  • ✗Expensive as volume grows
  • ✗Support called slow in negative reviews
Verdict

Great for keeping an eye on a handful of pages. Not built to vacuum up a catalog.

See Browse AI plans →Read our Browse AI review
6
Best scraping API for high volume

Zyte API

3.8/5

Zyte API works as a single call: send the URL, and Zyte picks the proxy, the browser and the unblocking strategy for that site.

Its pricing is the most honest on one point. You pay per 1,000 successful responses, across five difficulty tiers. A plain HTTP request is $0.13 per 1,000 on pay-as-you-go, an advanced one $1.27. With browser rendering, it's $1.01 to $16.08 per 1,000. Monthly commitments of $100, $200 or $500 bring those down, as low as $0.06 and $7.68.

In practice, 10,000 easy pages cost $1.30, and 10,000 heavily protected pages with a browser about $160.80. That 1-to-100+ spread shows the target site sets the price far more than the tool does.

The limit: you need a developer, and the tiered grid takes a few trial runs to see which tier your site lands in. Tip: spend the free $5 on a few hundred pages, check the tier you were billed, then size your monthly budget.

Standout features
  • Billed per successful response
  • Five price tiers by site difficulty
  • Discounts with monthly commitment
+Pros
  • ✓Cheapest in this ranking on easy pages
  • ✓Failures aren't billed
  • ✓Big discounts with commitment
−Cons
  • ✗Developers only
  • ✗Hard to forecast before a trial run on your site
Verdict

Past a few hundred thousand pages a month, this is the bill that tracks most closely with the data you actually get.

See Zyte plans →
Cost, bots, law

Three questions the vendor lists never ask

"From $19" means nothing until you know what a credit buys on your site, whether the tool gets past the bot wall, and whether you're allowed to collect that data. Here's how the ranked tools stack up.

What 10,000 pages really cost

Plain HTML pages: Zyte API $1.30 on pay-as-you-go, ScrapingBee Hobby $19 (10,000 of 75,000 credits), Firecrawl Standard $99 (Hobby stops at 5,000 pages), Web Scraper Cloud Professional $100 a month billed annually (20,000 URLs; the $50 Project plan stops at 5,000). Protected pages change everything. At ScrapingBee, JavaScript plus premium proxy at 25 credits means 250,000 credits, so the $49 Freelance plan. At Zyte, about $160.80 with a browser on the hardest tier. At Firecrawl, JSON output turns 10,000 pages into 50,000 credits, still inside Standard. At Apify, add the plan, compute units and the Actor's own fee: $10 to $99.90 for 10,000 Google Maps results depending on the Actor.

What gets past bot protection, and what breaks

Cloudflare and its Turnstile check are the wall developers mention most. Headless Selenium often fails there, and even a clean residential IP can get challenged, because the site owner sets the challenge level. Managed APIs (ScrapingBee, Zyte, Firecrawl cloud) get through more often than self-hosted tools; that's what you're paying for. One trap Hacker News users keep flagging: some sites serve fake content to bots. A 200 status proves nothing, so always spot-check what you collected.

Where US law stands

Scraping public data is not a crime by default in the US, but it's not a free-for-all. In hiQ v. LinkedIn (Ninth Circuit, 2022), the court found that accessing public pages is not "unauthorized access" under the CFAA; the case later ended in a settlement. In Meta v. Bright Data (Northern District of California, 2024), the court held that Meta's terms did not bar logged-out scraping of public data, a district ruling that does not bind other courts. Logged-in scraping, where you've accepted the site's terms, is riskier. Personal data brings privacy law into play, and if you scrape EU residents, GDPR applies. For a real project, run it past a lawyer.

  • Run the tool on 100 pages of your target site before picking a plan, and note the credits used.
  • Check whether failed requests are billed and whether unused credits roll over.
  • See if the data sits in the raw HTML: skipping JavaScript rendering can cut the cost by up to five times.
  • Read the target site's robots.txt and terms, and write down what you concluded.
  • Avoid scraping behind a login unless you've weighed the terms you agreed to.
  • Set a spending cap or a trial-end reminder the day you sign up.
Run your project

Your first scraping project in six steps

Most scraping projects fail for a boring reason: the tool gets picked before anyone checks what the target site demands. These steps come from the mistakes users describe most often in forums and reviews.

01

Write down the exact fields and the volume

First

"Competitor prices" isn't a spec. "Price, stock and URL for 2,000 products on 4 sites, once a week" is. That gives you a monthly volume (8,000 pages here), which tells you the plan.

Decide the output too: a Google Sheet, a CSV, or JSON for a database or an LLM.

Pin down
Fields, sites, frequency, volume
02

Check whether the data is in the raw HTML

Cost

Right-click, "View page source", search for a price you can see on screen. If it's there, a plain request is enough. If it only shows up after the page loads, you need a browser, and most APIs charge five times more for that.

This two-minute check beats any comparison table: it tells you which price column you're in.

Cost gap
5x with JS rendering at ScrapingBee
03

Pick the tool family before the tool

Choice

No code: Apify if an Actor exists for your site, Octoparse or Browse AI if not. You code: ScrapingBee or Zyte to fetch HTML, Firecrawl if the output feeds an AI. You have an engineer and time: open source.

For a one-off job on a single page, the free Web Scraper Chrome extension is often enough, no account needed.

One-off
Web Scraper extension, free
04

Decide whether open source really pays off

Code

Scrapy (Python), Playwright (browser automation) and Crawlee (JavaScript) cost nothing to license. The cost moves elsewhere: servers, proxies and, above all, maintenance when the site changes or adds a bot wall.

Firecrawl's GitHub issues make the point: the self-hosted build fails on sites the cloud version handles. Open source is unbeatable for simple sites at high volume, much less so for protected ones.

Hidden cost
Hosting, proxies, upkeep
05

Run a 100-page pilot and check it by hand

Quality

Run 100 pages, open 10 rows at random and compare them to the live site. You're checking three things: fields are right, pagination kept going, and no page came back empty or fake.

Note the credits used and multiply by your monthly volume. That's your real budget.

Check
10 rows out of 100 against the site
06

Plan for breakage from day one

Upkeep

A selector breaks the day the site ships new markup. Set an alert when the row count drops sharply, so you don't find out from a wrong report.

Keep a log of the sites you hit, the robots.txt you read and how long you keep the data. If anyone asks, you'll have the answer.

Alert
Sharp drop in row count
FAQ · 8 questions

Web scraping tools · FAQ

  • Which free extraction tool fits your monthly volume?
    For a one-off job, the Web Scraper Chrome extension, free when it runs locally. For regular no-code work, Octoparse's free plan (10 tasks, 50,000 rows a month locally) or Apify's ($5 of credit). For developers, Firecrawl gives 1,000 pages and ScrapingBee 1,000 credits. Past a few thousand pages a month, no free tier holds up.
  • Is web scraping legal in the US?
    Scraping public pages is generally not a crime: hiQ v. LinkedIn (2022) held that it isn't unauthorized access under the CFAA. But terms of service and privacy law still apply, and scraping behind a login is riskier. If you collect data on people in the EU, GDPR applies too. For a commercial project, get a lawyer's read.
  • Why is my credit bill higher than I expected?
    Because a credit is not a page on hard sites. At ScrapingBee, JavaScript rendering costs 5 credits and premium proxies up to 25. At Firecrawl, JSON output costs 5 credits instead of 1. At Apify, proxy and storage come on top of compute units. Always run a 100-page pilot before you pick a plan.
  • Do I need proxies to scrape a website?
    Not for a simple site at low volume. You do once the site rate-limits by IP or blocks data center addresses. APIs like ScrapingBee, Zyte and Firecrawl bundle proxy rotation in their price. If you need a proxy network on its own, our ranking of web scraping tools and proxies compares the providers.
  • Can I scrape LinkedIn safely?
    Not without risk. Users of LinkedIn automation tools report warnings and restricted accounts even when they stay under the suggested limits. Scraping while logged in means you've accepted LinkedIn's terms, and the hiQ case did not make that safe. Keep to the data you need and expect account risk.
  • Scrapy or a paid tool: which should I pick?
    Scrapy if you have an engineer, lightly protected sites and high volume: the license is free and cost per page gets very low. A paid tool if sites are protected or nobody can maintain the code. In between, an API like Zyte or ScrapingBee keeps your code and only offloads the part that gets blocked.
  • Which tool should I use to feed web pages to ChatGPT or an AI agent?
    Firecrawl, because it returns markdown, the format language models read best, or JSON shaped to your schema. Stay on markdown when you can: 1 credit per page instead of 5. Then let the model pull the fields it needs.
  • How do I stop a scraper from breaking when the site changes?
    You don't stop it, you catch it fast. Alert on a sharp drop in row count or on fields coming back empty. Prefer stable selectors (an ID, a data attribute) over position on the page. Tools that promise AI self-healing, like Browse AI, are worth checking on your own pages first.
Hack'celeration Lab

Get the next ranking in your inbox

No spam. Unsubscribe anytime.