Skip to content
IPTested
Guides / Guide

How Much Residential Proxy Bandwidth Do You Need? Estimate It, Then Cut It

A simple formula (pages × page weight × retry rate) to estimate residential proxy GB, a worked example for 10,000 product pages a day, and seven ways to cut usage before you buy a plan.

IPTested Editorial · ·Updated 2026-10-28 ·5 min read

Rotating residential proxies are almost always sold by the gigabyte, and most people pick a plan size by gut feel. Undershoot and your job dies halfway through the month. Overshoot and the unused traffic expires.

You can avoid both with about 30 minutes of measurement. This guide gives you the formula, a worked example, and seven ways to cut usage before you spend anything.

How providers meter traffic

On a pay-per-GB plan you pay for the data that passes through the provider's gateway: HTML, images, scripts, JSON responses, all of it. A few details change the math:

  • Metering rules vary. Whether uploads count, how headers and TLS handshakes are treated, and whether a GB is 1,000 or 1,024 MB all depend on the provider. Check their docs, and add a 10–20% buffer to any estimate.
  • Failed requests still cost money. A block page or a CAPTCHA page has to be downloaded too.
  • Expiry decides how expensive "buying extra" is. DataImpulse says its traffic never expires. Novada residential is a monthly subscription with traffic valid for 30 days, and card payments auto-renew. Webshare's help center says monthly bandwidth doesn't roll over and resets each billing cycle. (All as listed on 2026-10-05.)

The estimate formula

Monthly GB = pages per day × MB per page × retry factor × days ÷ 1,000

Two inputs need real numbers, not guesses.

MB per page. Measure it yourself:

  1. Open Chrome DevTools, go to the Network tab and tick Disable cache.
  2. Reload a representative target page.
  3. Read the transferred figure in the status bar at the bottom. That's bytes over the wire. Ignore the resources figure, which is the uncompressed size.
  4. Repeat on five to ten pages and average them. Do it once for a full browser load and once for the HTML document alone, because those are the two ways you might scrape.

Retry factor. Run a small pilot for a day and divide total requests by successful requests. A 15% failure rate gives a factor of 1.15.

Worked example: 10,000 product pages a day

The page weights below are assumptions for illustration. Swap in your own measurements.

Approach MB per page (assumed) Retry factor Per day Per month (30 days)
Headless browser, full page load 1.2 MB 1.15 ~13.8 GB ~414 GB
HTML only 0.18 MB 1.15 ~2.1 GB ~62 GB

Same job, very different bill. At DataImpulse's listed $1/GB, that's roughly $414 versus $62 a month. Optimize first, then buy.

Seven ways to cut usage

1. Skip the browser when you can. Product data often sits in the HTML or in an embedded JSON blob. A plain HTTP client fetches the document without the images, fonts and third-party scripts.

2. If you need a browser, block heavy resources. In Playwright for Python:

async def block_heavy(route):
    if route.request.resource_type in {"image", "font", "media"}:
        await route.abort()
    else:
        await route.continue_()

await page.route("**/*", block_heavy)

Test that the page still renders the data you need. Some sites lazy-load content that depends on blocked resources.

3. Prefer official APIs and the JSON endpoints behind the page. They usually return far fewer bytes than a rendered page, and they break less often.

4. Only fetch what changed. Use sitemap lastmod dates to skip unchanged URLs, and send conditional requests (If-None-Match with an ETag, or If-Modified-Since). A 304 Not Modified response is tiny.

5. Cache locally. If several jobs hit the same page on the same day, fetch it once.

6. Cap retries. Use a retry limit with exponential backoff. When the failure rate jumps, stop and investigate. Retrying harder just buys more block pages.

7. Don't send everything through residential IPs. Low-risk targets often work fine on datacenter proxies, which cost much less. DataImpulse lists datacenter traffic at $0.50/GB.

Be a good citizen. Check the target's robots.txt and terms before you scrape, and keep request rates modest. Fewer requests are cheaper for you and lighter on the site.

Matching the plan to the estimate

Once you have a monthly number with a buffer, the shape of your usage matters as much as the size:

Your usage pattern Start with Why (as listed on 2026-10-05)
Irregular or project-based DataImpulse $1/GB residential that never expires; a $5 intro plan for testing
Steady month to month Novada 25 GB for $50/mo, down to $1.3/GB on the 1 TB tier; 30-day validity
High volume, price-sensitive Thordata $0.65/GB is a sale price (regular $1.05); conditional 7-day refund
Fixed monthly allowance Webshare From $3.50/mo, down to $1.40/GB at volume; no rollover

Prices change often, so confirm on each provider's pricing page before ordering. For expiry rules, session lengths and refund terms side by side, see Best Rotating Residential Proxies. For raw price per GB across proxy types, see Cheapest Proxies in 2026 or the proxy comparison table.

Not scraping, just working inside browser profiles? The math is different. GoLogin's help center publishes rough per-profile estimates, for example 0.5–1.5 GB a month for e-commerce browsing, and suggests multiplying profiles by GB per profile. Treat those as GoLogin's ballpark figures, not measurements. Long-lived accounts usually belong on a static IP with unlimited traffic anyway, which takes them out of the GB calculation entirely.

Monitoring and alerts

Your estimate is a starting point. Usage drifts as sites change, so watch it:

  • Use the provider dashboard. Webshare shows a projected monthly usage based on your current pace. It runs higher than actual usage, which makes it a useful early warning.
  • Keep your own ledger. Log requests, successes and response sizes per day in your scraper. Compare against the dashboard weekly. Your numbers are a sanity check; the provider's meter is what you're billed on.
  • Set thresholds. Alert yourself at 70% and 90% of the plan. On monthly subscriptions, note the renewal date so an auto-renewal doesn't catch you off guard.
  • Re-measure page weight quarterly. A site redesign can double the bytes per page overnight.

Quick checklist

  1. Measure transferred MB per page in DevTools, for the approach you'll actually use.
  2. Run a one-day pilot to get your retry factor.
  3. Apply the formula and add 10–20%.
  4. Apply the seven cuts and re-measure.
  5. Pick a plan whose expiry rules fit your usage pattern, starting small.

Not sure residential is the right type at all? Read Residential vs ISP vs Mobile vs Datacenter Proxies. Building the rest of the pipeline? See A Beginner's Web Scraping Stack.

Some links are affiliate links. We may earn a commission if you buy through them, at no extra cost to you and without affecting our ratings.