How much proxy traffic do you need? A quick way to size your plan
Short answer, November 13, 2026: multiply the pages you load a month by the average page weight. 100,000 product pages of HTML is roughly 25 GB; the same pages in a headless browser with images can reach 150 to 300 GB
Residential and mobile proxies are billed per GB, so the plan you need depends on traffic, not on the number of requests. Most teams overbuy because they guess. Ten minutes of measuring saves a plan size
The formula
Monthly traffic = pages a month × average page weight. Measure page weight on 20 to 50 real pages from your target sites with your scraper’s actual settings, because the same page can weigh 0.2 MB as HTML and 3 MB with images and scripts
| Task | Example volume | Page weight | Traffic a month |
|---|---|---|---|
| Web scraping, HTML only | 100,000 pages | ≈ 0.25 MB | ≈ 25 GB |
| Web scraping, headless browser | 100,000 pages | 1.5 to 3 MB | 150 to 300 GB |
| Price monitoring | 5,000 products × 2 checks a day | ≈ 0.2 MB | ≈ 60 GB |
| SEO rank tracking | 1,000 keywords × 2 locations, daily | ≈ 0.3 MB | ≈ 18 GB |
| Ad verification | 100 placements × 3 cities, daily | ≈ 1 MB | ≈ 9 GB |
These are our rough estimates for planning. Measure your own pages during a trial before you commit to a large plan
Five ways to cut the bill
- Block images, fonts and video in your scraper: often several times less traffic
- Use a site’s JSON endpoints or official API where available: often under 50 KB a request
- Deduplicate URLs before fetching and skip pages that have not changed
- Use datacenter proxies for sites that accept them, residential only where needed
- Pick the plan at your real volume: per-GB rates fall on bigger plans
Calculate your monthly cost · Proxies for web scraping · Proxies for price monitoring