How is proxy bandwidth billed?
The most common misunderstanding about residential proxies is that you pay "per proxy" or "per IP". With modern residential networks you actually pay for bandwidth — the total volume of data that passes through the proxy, measured in gigabytes. One username/password credential can route through millions of rotating IPs; what you are charged for is the traffic, not the number of addresses.
This matters because your cost is driven entirely by how much data your task moves, not by how many endpoints you touch. A lightweight text-scraping job that visits thousands of pages may use very little data, while a handful of media-heavy pages can burn through far more.
Why big proxy plans can waste money
Large plans look cheaper per gigabyte, and sometimes they are. But the effective price is only lower if you actually use the whole allocation. Two things routinely go wrong:
- Overbuying. You estimate 50GB, use 8GB, and the rest sits idle. If it expires, the "discount" was an illusion.
- Expiry. Many providers reset monthly. Unused bandwidth simply vanishes at the end of the cycle, so a big block pressures you to consume fast or lose it.
Small plans flip this. You buy 1–5GB, run your real workload, measure actual consumption, and only then decide whether a larger tier makes sense.
Test a proxy provider before you scale
Before you commit budget, answer concrete questions. Does this provider reach the cities you target? Are success rates high on your specific sites? Is latency acceptable for your tooling? A 5 GB starter is plenty to run a representative sample of your workflow and get real numbers instead of marketing claims.
Testing small also lowers integration risk. You confirm that HTTP(S) and SOCKS5 work with your stack, that rotating and sticky sessions behave as documented, and that your code handles retries correctly, all before spending at scale. The integration guides include working code.
How much proxy bandwidth do I need?
A rough estimate is easy to build:
- Run your task against a small sample (say, 100 requests).
- Check the bandwidth consumed for that sample.
- Multiply up to your target volume, then add ~20% headroom for retries and overhead.
Because consumption depends on what you load, use this qualitative guide as a starting point:
| Example task | Rough bandwidth need | Why |
|---|---|---|
| Scraping plain HTML / prices | Low | Mostly small text responses |
| SEO rank & SERP monitoring | Low–Medium | Text plus some page assets |
| Ad verification (loading full pages) | Medium | Images, scripts, trackers load |
| Market research on media-rich sites | Medium–High | Photos and galleries add up |
| Downloading images or video | High | Media is the bulk of the payload |
These are directional, not exact — your real numbers come from the sample test above.
Small plans at Nefo
Nefo is built around this flexibility. The smallest residential proxy package is 5 GB for $4.50, and bandwidth never expires, so a quiet month never wastes what you paid for. You also get country, state, city and ISP targeting, HTTP, HTTPS and SOCKS5, and rotating or sticky sessions. When volume grows, top up or move to a larger package without losing your remaining balance: 100 GB is $73 ($0.73/GB). See current options on the pricing page or create an account to run a small test first.
Use proxies only for lawful purposes such as market research, price monitoring, ad verification, SEO tracking and collecting publicly available web data in line with applicable terms and laws.
Key takeaways
- You pay per gigabyte of traffic, not per IP or credential.
- Big commitments only save money if you consume them; otherwise they waste budget, especially when bandwidth expires.
- Small pay-as-you-go plans let you test before scaling and budget predictably.
- Estimate usage from a small sample, then add headroom for retries.
- Nefo starts at 5 GB for $4.50 and bandwidth never expires.
Frequently asked questions
It depends on the task. Text-only scraping uses little, loading full pages with images and scripts uses more, and downloading media uses the most. Run a sample of about 100 requests, measure it, scale up and add around 20% headroom.
With Nefo, no. Bandwidth stays in your balance until you use it. Always check any provider's terms, since many providers reset unused bandwidth monthly.
Yes. Add more bandwidth whenever you need it. Because the balance does not expire, top-ups stack onto what you already have. See the pricing page.
For most workflows, yes. 5 GB is enough to run a representative sample and check success rates, targeting, latency and integration before you decide on a larger package.
It depends on the job. Per-GB billing suits variable work and many rotating IPs. If you need one fixed address, a static ISP IP or 24-hour IP may fit better.