What Counts Toward Proxy Data Usage?
Proxy traffic can include request and response bodies, headers, cookies, authentication data, redirects, bytes transferred before a failure, and retries. Images, media, large HTML, and repeated static assets can make each request much larger than a small JSON response.
Use the average transferred data reported by the billing system when possible. If only the response-body size is known, increase the safety margin to account for protocol overhead, failed transfers, and workload variation.
How Many Proxy Requests per GB?
Using decimal units and no safety margin, 1 GB supports about 100,000 requests at 10 KB each, 50,000 at 20 KB, 20,000 at 50 KB, 10,000 at 100 KB, 2,000 at 500 KB, 1,000 at 1 MB, or 500 at 2 MB.
Choose the unit used by the provider: 1 decimal GB is 1,000,000,000 bytes, while 1 binary GiB is 1,073,741,824 bytes. Mixing those units produces a different capacity estimate.
Build a Reviewable Proxy Bandwidth Estimate in Three Steps
First measure average transfer size from proxy logs or a browser network panel; use a workload preset only as a starting point. Second choose whether the request count is a total, a daily campaign, or a per-thread workload so activity days and concurrency are applied correctly.
Third add a practical reserve for response variation and retries, commonly 10% to 30%, and confirm whether billing uses GB or GiB. The calculator can work from traffic to request capacity or from request demand to required traffic.
Reduce Proxy Data Usage Before Buying More Traffic
When the target supports it, enable gzip or Brotli, block images, fonts, CSS, or JavaScript that the task does not need, reuse stable resources with ETag or If-Modified-Since, and cap retry attempts.
Measure again after optimization and return the new average transfer size to the calculator. The result and suggested tier are planning references, not live pricing, inventory, provider measurement, or a final bill.
How many proxy requests can 1 GB support?
It depends on transferred data per request. In decimal units, 1 GB supports about 10,000 requests at 100 KB each or about 2,000 requests at 500 KB each before applying a safety margin.
Should I enter only the response body or all transferred data?
Use the average transferred data reported by the billing system when possible. If you know only the response-body size, increase the safety margin for request and response headers, redirects, and data transferred before failures.
Will failed requests consume traffic?
They can. Data sent or received before a failure, plus any retries, may still count toward metered usage.
GB vs. GiB: what is the difference?
A decimal GB is 1,000,000,000 bytes, while a binary GiB is 1,073,741,824 bytes. Use the unit defined in your provider's billing documentation.
Is the recommended tier my final bill?
No. The tier is a planning reference based on the estimate. It does not represent live pricing, inventory, provider measurements, or a final bill.
