Free tools
Scraping Cost Calculator
Estimate the bandwidth, proxy plan and cost per 1,000 usable pages for your scraping project. Model failed attempts, browser-rendered pages and your own success rate. Free, runs in your browser, no sign-up.
Your workload
Every number below is an assumption you control. Nothing leaves your browser.
Priced with our current per-GB plans.
Pages that return the data you actually need.
HTML over plain HTTP. Compressed HTML is often 50–300 KB.
Scripts, images and API calls add up. Blocking images and fonts cuts this sharply.
Share of attempts that return usable data. Failed attempts still use traffic, so this is the biggest driver of cost. Measure your own.
Advanced assumptions
Block pages and timeouts are often smaller than real pages. 100% is the conservative default.
- Cost per 1,000 usable pages
- $0.24
- Monthly traffic
- 23.53 GB
- Total attempts
- 117,647
Proxy traffic at our plan rate. Excludes compute, engineering and any retries beyond the usable result rate you set.
235 KB per usable page
1.18 per usable page
Same workload on mobile proxies: $0.47 per 1,000 usable pages on the 25 GB plan. Success rate may differ between proxy types, so adjust it for each.
Plan you would need
25 GB · $25.00/month
Uses about 94% of the plan at $1/GB. Unused data rolls over, and the smallest plan is $25 for 25 GB.
Explore residential plansShare this calculation
How it works
How the estimate is built
The calculator turns pages per month into traffic, then into the plan you would need. Each step is a formula you can check by hand.
Usable pages become attempts
Not every request returns usable data. At an 85% usable result rate you need 1 ÷ 0.85 ≈ 1.18 attempts per usable page, and failed attempts still use traffic.
Attempts become traffic
Traffic per attempt blends your static and browser-rendered page sizes by the share of pages that need JavaScript. Failed attempts are counted at the size you set, 100% by default.
Traffic becomes a plan and a cost
Monthly GB is matched to the smallest per-GB plan that covers it, for residential or mobile proxies, using the live rate for that tier. Cost per 1,000 usable pages is that proxy cost divided by your usable pages.
Worked examples
Three workloads, calculated
Same formulas, very different bills. Numbers use the calculator defaults and residential per-GB rates unless stated, and exclude compute, engineering and any retry logic beyond the usable result rate.
Static product pages, lightly protected
100,000 usable pages a month, 200 KB per page, 85% usable result rate. Attempts: 117,647. Traffic: about 23.5 GB, which fits the 25 GB plan ($25/month). Proxy cost per 1,000 usable pages: about $0.24.
100,000 × (1 ÷ 0.85) × 200 KB ≈ 23.5 GB30% of pages need a browser
Same 100,000 usable pages and 85% usable rate, but 30% need JavaScript rendering at 1,500 KB. Blended page size: 590 KB. Traffic: about 69 GB, so the 100 GB plan ($100/month). Proxy cost per 1,000 usable pages: about $0.69, before browser compute.
(0.7 × 200 + 0.3 × 1,500) KB × 1.18 × 100,000 ≈ 69 GBHeavily protected target
1,000,000 usable static pages a month at 200 KB, but only 50% of attempts return usable data. Attempts: 2,000,000. Traffic: 400 GB, so the 500 GB plan ($500/month). Proxy cost per 1,000 usable pages: $0.40. If failed attempts are small block pages, lowering the failed attempt size in the advanced options reduces this.
1,000,000 × (1 ÷ 0.50) × 200 KB = 400 GBIllustrative inputs, not measured success-rate forecasts. Your page sizes and success rate depend on the target site and your setup.
Getting accurate inputs