TL;DR
Web scraping costs anywhere from $0 to several thousand dollars a month, and the spread is explained almost entirely by where the work happens. If the tool runs in your own browser, it's usually free or a one-off fee, because you're supplying the compute, the IP address, and the login session. If it runs on someone else's servers, you're paying for proxies, headless browsers, and bandwidth — and that's metered, typically as credits, rows, or API calls.
The practical answer for most people: if you're extracting from pages you can open yourself, a browser extension like ScrapeMaster does it for $0 with no row limit. You only need to start paying when you want extraction to happen on a schedule without you present, at a volume or from an IP range your own browser can't sustain.
The four pricing models
Almost every scraping product on the market is one of these. Knowing which one you're looking at tells you more than the headline price does.
1. Browser extension — free or one-time
The tool runs inside your Chrome tab. It sees the page exactly as you see it, using your session and your IP. There's no server bill for the vendor to pass on, which is why the free tier is usually genuinely free rather than a trial.
- Typical cost: $0, or a one-time $20–60 for a paid extension
- What you're limited by: your own patience and the tab staying open
- Where it fails: scheduled/unattended runs, very large crawls, sites that hard-block your residential IP
2. Per-row / credit-based SaaS
You buy credits; each extracted row, page, or "AI credit" burns some. This is the dominant model for no-code cloud scrapers.
- Typical cost: free tier of ~50–500 rows/month, then roughly $15–100/month for tens of thousands of rows
- The trap: credits are consumed by attempts, not successes on some platforms. A failed run on a page that changed layout can still cost you.
- The other trap: enrichment features (email finding, AI column generation) often burn credits at a much higher multiple than plain extraction
3. Per-request API
You send a URL, you get back HTML or parsed JSON. The vendor handles proxies, retries, and headless rendering. Priced per successful request, usually with tiers for "JavaScript rendering" and "premium/residential proxy" that cost several times a basic request.
- Typical cost: $30–500/month for 100k–1M basic requests; JS rendering commonly costs 5–25× a basic request
- Best for: engineers who already have a pipeline and want the proxy problem to go away
- Watch: the advertised price is nearly always the basic request. If your target needs JS rendering plus a residential proxy — and most modern sites do — model your real cost at the multiplied rate, not the headline
4. Managed / enterprise data delivery
You describe the dataset; the vendor delivers it on a schedule. Contracts, SLAs, an account manager.
- Typical cost: $1,000–10,000+/month, annual commitments common
- Best for: the data is a business input, and an outage is a revenue problem
- Reality check: most teams who think they need this actually need model 3 plus a week of engineering
What drives the price up
Vendors don't price on rows because rows are expensive. They price on rows because it's legible. The underlying costs are:
Proxies. This is the big one. Datacenter IPs are cheap and widely blocked. Residential and mobile IPs are billed per gigabyte and cost real money. Any tool that scrapes a well-defended site at volume is paying a proxy bill and passing it to you.
Headless browsers. Rendering JavaScript means running an actual browser per request. That's memory and CPU, and it's why "JS rendering" is a paid multiplier nearly everywhere.
Anti-bot handling. Solving or routing around challenges is a cost centre with its own vendors underneath it.
Maintenance. Sites change. Someone has to fix the selectors. In a managed product, that's the largest hidden line item and it's the one that justifies the subscription for teams without an engineer to spare.
Notice that a browser extension pays none of these. It uses your IP, your browser, your session — which is exactly why it can be free, and also exactly why it can't run at 3am without you.
Cost at three realistic volumes
Rough monthly figures for the same job at different scales. Treat these as orders of magnitude, not quotes — every vendor reprices and the multipliers move.
| Volume | Browser extension | Credit SaaS | Scraping API | Managed |
|---|---|---|---|---|
| 500 rows, once | $0 | $0 (free tier) | $0–5 | Not viable |
| 20k rows/month, attended | $0 | ~$30–80 | ~$20–60 | Not viable |
| 500k rows/month, scheduled | Not viable | ~$300–800 | ~$150–600 | $1,000+ |
| Defended site, residential IPs, daily | Not viable | Often blocked | $500–3,000 | $2,000+ |
The two "not viable" columns are the actual decision. Below roughly 20–50k rows a month, on pages you're willing to open yourself, a paid tool is buying you convenience and scheduling — not capability. Above that, or unattended, the extension genuinely can't do the job and you should pay.
Where free stops being free
Being honest about our own category: a browser extension is the wrong tool when
- You need it to run unattended. No tab open, no extraction. Scheduling requires a server.
- You're doing hundreds of thousands of pages. Your own connection and one browser tab are the bottleneck, and hammering a site from one residential IP is both rude and likely to get that IP blocked.
- The site blocks you specifically. Extensions don't rotate IPs. That's a proxy product's job.
- You need a guaranteed schedule with an SLA. Nobody's on call for a free extension.
If any of those describe you, pay for model 3 or 4. If none of them do — and for most sales, research, and analyst work, none of them do — you're evaluating paid tools for a problem you don't have.
What ScrapeMaster costs
Nothing. There's no paid tier, no row cap, no credit system, and no account.
It runs in a Chrome side panel, auto-detects repeating structures on the page in a couple of seconds, and gives you an editable table. It handles next-page buttons, load-more buttons, numbered pagination, and infinite scroll, and it can follow links into each item's detail page for deeper fields. Export is CSV, XLSX, or JSON, or straight to the clipboard for pasting into Google Sheets or a CRM.
The honest trade-off is the one in the section above: it's attended. You're in the tab while it works. That's the whole reason it can be free — you're supplying the infrastructure that a cloud vendor would otherwise have to buy and bill you for.
How the named tools compare
| Tool | Model | Free tier | Notes |
|---|---|---|---|
| ScrapeMaster | Extension | Unlimited, free | Attended only; no scheduling |
| Web Scraper.io | Extension + cloud | Extension free | Cloud scheduling is the paid part |
| Instant Data Scraper | Extension | Free | Simpler table grabbing, less control |
| Octoparse | Credit SaaS | Small free tier | Desktop app + cloud runs; scheduling included |
| ParseHub | Credit SaaS | Limited free | Long-standing; page-count limits bite early |
| Import.io | Managed | No | Enterprise contracts |
| Simplescraper | Credit SaaS | Small free tier | Extension front-end, cloud back-end |
| Thunderbit | Per-row credits | Small free tier | AI columns burn credits faster than plain rows |
We've written longer head-to-heads on several of these — see Thunderbit vs ScrapeMaster, the Web Scraper (webscraper.io) review, and the Instant Data Scraper review if you want the detail on one specifically.
Questions to ask before you pay
- Does this need to run when I'm not here? If no, you probably don't need a subscription.
- What's my actual monthly row count? Most people overestimate by 10×. Count one real week and multiply.
- Does the free tier's row limit reset, or is it a one-time trial? These get advertised identically.
- What does a failed run cost? Ask explicitly whether credits are consumed on failure.
- What's the JS-rendering and residential-proxy multiplier? For API products this is the real price.
- Can I export raw? If you can't get a plain CSV out, you're renting your own data.
Frequently asked questions
How much does web scraping cost per month?
It ranges from $0 for a browser extension you run yourself, to roughly $15–100/month for a credit-based no-code tool at tens of thousands of rows, $30–500/month for a scraping API, and $1,000+/month for managed data delivery. The main cost driver is whether extraction runs on your machine or on a vendor's servers with proxies.
Is there a genuinely free web scraper with no row limit?
Yes. Browser extensions that run locally, including ScrapeMaster, have no row cap because the vendor isn't paying for servers, proxies, or bandwidth — your browser does the work. The limitation is that extraction is attended: it happens while you have the tab open, not on a schedule.
Why are cloud scrapers so much more expensive than extensions?
Because they pay for things an extension doesn't: residential proxy bandwidth billed per gigabyte, headless browser instances for JavaScript rendering, anti-bot handling, and ongoing selector maintenance. Those costs get passed on as credits or per-request pricing.
What is a "credit" in web scraping pricing?
It's a vendor-defined unit, usually one extracted row or one page fetched — but definitions vary a lot. AI-generated columns and email-enrichment features often consume several credits each, and on some platforms failed attempts consume credits too. Always check whether credits are burned on failure before committing.
When is it worth paying for a web scraper?
When you need unattended scheduled runs, when your monthly volume exceeds what one browser tab can reasonably do (roughly 20–50k rows), when the target site blocks your IP and you need proxy rotation, or when you need an SLA. Below that threshold, paid tools are selling convenience rather than capability.
Does a free scraper mean my data is being sold?
Not necessarily, but it's the right question to ask. Check whether the tool sends extracted data to a server at all. A locally-run extension that never uploads has nothing to sell. Read the Chrome Web Store data-disclosure section on the listing before installing anything — it's a required disclosure and it's more informative than the marketing page.
Bottom line
The pricing question usually answers itself once you know whether you need unattended runs. If you're extracting from pages you can open — directories, listings, search results, tables — during your own working hours, that's a $0 problem, and paying a per-row subscription for it is buying scheduling you won't use.
If you genuinely need scale, schedules, or proxy rotation, budget for an API and model the cost with the JS-rendering multiplier included, not the headline basic-request price.
For everything else: ScrapeMaster is free, has no row limit, requires no account, and exports to CSV, XLSX, JSON, or your clipboard.
If your extraction ends with "and now turn this into a report someone will read," Convert: Anything to PDF converts the CSV to a formatted PDF locally, without uploading it anywhere.