Free planning tool
Proxy bandwidth calculator
Turn requests and transferred data into a GB estimate. Allow for retries, add headroom and review the traffic amount before you buy.
No account needed. Use it for an API job, a browser workflow or an authorised monitoring task.
Your bandwidth estimate
Estimated traffic: 9.9 GB. Whole-GB planning amount: 10 GB.
For 30 days, including your extra attempts and headroom.
- Initial requests
- 7.5 GB
- Extra attempts
- 0.75 GB
- Headroom
- 1.65 GB
Rounded up to whole GB
10 GB
EUR 39.00
Current rate: EUR 3.90 per GB. Final terms and price are shown in the shop.
You review the amount before adding anything to your cart.
A planning estimate, not a usage measurement or billing guarantee. Compression, cached assets, uploads and partial failures can change the result. See what counts as traffic.
The calculation
Make the inputs match your job.
Start with the number of requests you intend to make and the mean transferred bytes per attempt. Include upload and download. For a browser visit, count the resources loaded through the proxy, not just the first HTML document.
Extra attempts are additional requests divided by initial requests. Ten extra attempts for every hundred initial requests means 10%. A request retried more than once can make this figure exceed 100%.
Headroom is your chosen allowance on top of that total. It is not a measured error bound. If your sample already includes retries, leave extra attempts at zero to avoid counting them twice.
From requests to GB
requests/day × days × kB/attempt × (1 + extra attempts ÷ 100) × (1 + headroom ÷ 100) ÷ 1,000,000
Illustration: 1,000 requests/day × 30 days × 250 kB is 7.5 GB. Add 10% extra attempts and 20% headroom: 9.9 GB, or a 10 GB whole-number planning amount. These inputs are examples, not typical page sizes.
Measure before scaling
A small representative run beats a guess.
Measure a sample
Use the same client, resources and cache settings as the real job. Record initial requests, extra attempts and upload/download totals separately.
Check what the counter includes
Browser resource transfer sizes and client counters may omit protocol traffic or show cached responses. They are inputs to an estimate, not an exact proxy bill.
Compare with actual usage
Run a bounded job through your account, allow for its usage refresh, then compare the metered change. Adjust the next estimate using that result.
For measurement references, see Chrome’s Network panel and the scope of resource transferSize.
Continue