Per GB Pricing
Per GB pricing means paying for the volume of data transferred through a proxy service. At a rate of 3 USD per gigabyte, 20 GB costs 60 USD before any additional charges. The useful question is how much traffic your task produces: opening a product page in a browser, uploading a video, and retrieving a small data response can consume very different amounts.
This is one of the proxy pricing models used for residential, mobile, datacenter, and ISP services. Gigabytes can be sold in prepaid packages, monthly subscriptions, or through a balance charged as you work. Per GB defines the unit being purchased; it does not, by itself, tell you when to pay or when unused traffic expires.
What the price of one gigabyte pays for
Your payment covers access to an exit IP and the network that carries your requests through it. Behind that access are addresses or participating devices, internet connectivity, gateway servers, routing and session software, maintenance, support, and handling misuse complaints. A commercial rate must cover those costs and leave room for the provider's profit. The provider's own internet bill is only one part of the service you are buying.
At an illustrative price of 3 USD/GB, these services are normally bundled into the rate rather than itemized on your bill. A higher price may buy access to a different network, more precise targeting, or a better-supported service. It does not establish that the same volume of data will complete more work. That depends on the target websites and your setup.
The share spent on addresses, connectivity, support, and profit differs between services. The customer pays the quoted rate for the bundle; its value depends on whether that bundle supplies the access and capacity the task needs.
Why datacenter, residential, and mobile gigabytes cost differently
The amount of data can be identical while the cost of providing the route differs.
| Network | What affects the price | What the buyer should establish |
|---|---|---|
| Datacenter | Server capacity, hosting connectivity, and owned or leased address space can be shared across substantial traffic volumes | Whether the target accepts these exits and whether the plan permits the intended load |
| ISP | ISP-associated addresses, supplier agreements, and usually continuously running server infrastructure | Whether the rate includes shared pool access, dedicated addresses, or a separate address fee |
| Residential | Recruiting and retaining participating devices, partner payments, and routing around devices that become unavailable | Whether the required locations have usable capacity and sessions last long enough |
| Mobile | Cellular connectivity, device or modem access, carrier plans, and managing a distributed or physical device network | Whether the service supplies a traffic pool or exclusive access to a modem, and what restrictions apply |
For a concrete price reference, one published product family offers basic packages of 100 GB of datacenter traffic for 50 USD, 50 GB of residential traffic for 50 USD, and 25 GB of mobile traffic for 50 USD. The respective rates are 0.50, 1, and 2 USD/GB. Elsewhere, a residential entry package offers 5 GB for 30 USD, or 6 USD/GB. These are examples of public offers, not market averages or a quality ranking.
Residential supply can involve payments to app partners or participants who permit their connections to be used. Mobile supply can involve participating phones or managed modems and SIM plans. Those arrangements have different costs. A residential device disappearing can require another exit; it does not guarantee that an existing session will survive unchanged.
Datacenter traffic can be the economical choice when it works on the intended sites. Residential or mobile access may improve results for some tasks, but neither label guarantees acceptance or immunity from blocks. Buying the most expensive network without testing it can be just as wasteful as repeatedly retrying an unsuitable cheap one.
Renting a dedicated mobile modem for a week or a month is a different purchase from buying gigabytes from a mobile pool. The fixed fee, carrier limits, available speed, and sharing arrangement all need to be included in that comparison.
What the traffic counter measures
A common published calculation adds request headers + request body + response headers + response body. Both upload and download count. Cookies are part of the headers; they should not be added again if those headers are already included in a measurement.
Sending 2 MB to a site and receiving 1 MB back therefore involves approximately 3 MB of application data, plus any other traffic included by the billing system. A tool reporting only downloaded response bodies will show a smaller total.
The same downloaded byte passes from the website through the proxy to the customer. That does not automatically mean it is billed twice. “Upload plus download” describes the two directions of communication; the service's metering rules determine the charge.
HTTPS can add handshake and encryption-related traffic to the tunnel. Some services explicitly count those bytes. Their share matters more for repeated tiny requests using new connections than for a large download. Measuring encrypted traffic volume does not require reading its contents. Keep HTTPS protection and measure the actual cost of your connection pattern.
For browser work, the HTML is only part of the load. Images, scripts, stylesheets, fonts, background data calls, and media can all use the proxy. Extracting a few prices into a small CSV file may require downloading far more data than the final file contains.
Compression adds another distinction: transferred bytes and the size after decompression can differ. Browser network tools show both. A locally saved, decompressed response is not a substitute for the provider's traffic counter.
GB, GiB, and rounding
1 GB is 1,000,000,000 bytes. One GiB is 1,073,741,824 bytes. The same transfer has a numerical value about 7.37% larger in GB than in GiB. Commercial documentation includes an explicit change from GiB to decimal GB, so the distinction can affect real dashboard comparisons.
Check the billing unit and any minimum or rounding rule. A display rounded to two decimal places does not establish that every small request is rounded up for billing. Conversely, a headline rate per GB does not promise byte-by-byte charging under every plan.
GB also measures volume, not speed. A 10 GB package says nothing about how quickly it can be used. Connection limits and transfer rates remain separate service conditions.
Failed requests, CAPTCHAs, and paid retries
A request that fails your business task can still transfer billable data. A CAPTCHA or access-denied page has a response body even though it contains none of the information you wanted.
One published metering policy counts target-site responses such as 403, 404, and 503, plus bytes received before a transfer times out. It excludes errors generated by the proxy service itself. If the target sends nothing, the outgoing request can still count. Other products must be checked against their own rules.
A retry makes another attempt and can add more traffic. Repeatedly rotating the IP and reloading the same blocked page can consume the budget while producing no usable results. Stop and diagnose a persistent failure instead of treating every error as a reason for unlimited retries.
Error pages and successful pages may have different sizes, so a failure rate alone cannot tell you the wasted gigabytes. Measure the traffic from both. An HTTP 200 response also needs validation: a login screen, empty result, or challenge page may still be unusable.
How many pages fit into one gigabyte?
Use the average billed traffic per completed operation, including its required resources and repeat attempts. An operation might be one product record, a location-specific search, or a complete browser action. Define it consistently before comparing costs.
The following examples use decimal units and assumed total consumption:
| Average traffic per operation | Approximate operations per 1 GB |
|---|---|
| 50 KB | 20,000 |
| 200 KB | 5,000 |
| 1 MB | 1,000 |
| 3 MB | 333 |
| 10 MB | 100 |
These are calculations, not typical page sizes. A browser session with media and background requests can be much heavier than a simple data request.
Consider 100,000 operations at an illustrative rate of 3 USD/GB. At 200 KB each, they consume 20 GB and cost 60 USD. At 3 MB each, they consume 300 GB and cost 900 USD. The fifteenfold difference comes from the assumed data volume, not a change in the proxy price.
Estimate a project by measuring a representative sample: record the starting counter, run the real workflow, wait for usage statistics to update, and divide the additional billed GB by the number of completed operations. Include different page types, first logins, returning sessions, and the actual location filters. A single request to an IP-checking page is a poor substitute for that test.
Compare the cost of usable results
The most useful comparison is total proxy spending divided by the number of usable results. A cheaper gigabyte can cost more per completed task if the network requires many attempts.
Here is a hypothetical comparison. Each service handles 100,000 attempts, averaging 1 MB of billed traffic per attempt, for 100 GB in total:
| Service | Rate | Traffic cost | Usable results | Cost per 1,000 usable results |
|---|---|---|---|---|
| A | 2 USD/GB | 200 USD | 50,000 | 4 USD |
| B | 3 USD/GB | 300 USD | 90,000 | about 3.33 USD |
Service B costs more per GB but less per useful result in this example. In your test, use measured traffic rather than assuming every success and failure is equally large. Include expired allowance or minimum commitments when they form part of the money actually spent.
Scraping APIs can use another unit, such as successful requests or returned records, with the provider handling attempts internally. That cannot be compared with a raw proxy's price per GB until both are converted to the cost of the same completed task. An API's promise not to charge for failed requests does not automatically apply to that company's ordinary proxy network.
The advertised rate and the price of your configuration
A quoted rate needs its conditions attached. “From 0.80 USD/GB” may require buying a terabyte for 800 USD. A small 5 GB purchase can have a much higher unit price while still requiring far less cash. Check the minimum payment, purchase volume, included features, and whether the advertised price is a temporary promotion.
Volume discounts are useful when the extra traffic will be used. Compare the complete order on both sides of a discount threshold, and establish whether the reduced rate applies to the whole purchase or only to additional usage. A quoted monthly equivalent can also require a larger advance payment.
Location filters deserve their own price check. A documented standard-pool offer includes country selection but charges twice the normal rate for state, city, ZIP, or ASN selection. Other offers include such filters. A broad worldwide price therefore does not establish the cost of your exact location settings.
The twofold charge applies to the traffic routed with those paid filters under that offer. It does not mean the page itself became twice as large. Keep physical transfer volume and the amount deducted or charged by the tariff distinct.
Check premium pools, dedicated allocations, optional service features, taxes, and currency conversion at checkout. The rate for extra traffic can also differ from the package's average rate. Comparing providers is meaningful only with the network, required filters, billing unit, and tax basis aligned.
When unused gigabytes expire
An allowance can expire at the end of a billing cycle, last for a specified period after purchase, or remain available without a fixed expiry. These conditions affect the amount of useful traffic the payment buys.
Published arrangements include monthly GB that do not roll over, transfers of unused traffic when upgrading, and separately purchased traffic with a different expiry from the main allowance. One auto-top-up arrangement carries additional GB into the following billing cycle, then expires any remainder at the end of that cycle.
“Non-expiring” also needs its account conditions read. A published residential policy says that maintaining an available balance may depend on regular top-ups or an active subscription. Check the exact rule for your account rather than assuming the wording promises access indefinitely without conditions.
Suppose a 100 GB monthly package costs 200 USD. You use 20 GB and lose the remaining 80 GB at expiry. The advertised rate was 2 USD/GB, but the payment per used gigabyte was 10 USD. A smaller package with a higher unit price could have been cheaper overall.
If the remaining GB stay valid and will be used later, they are not already wasted. You have paid in advance for future capacity. Also distinguish canceling the next renewal from losing access immediately: some subscriptions allow the remaining traffic to be used until the paid period ends.
What happens when the balance runs out
Depending on the product, traffic can stop, require a manual top-up, trigger an enabled automatic purchase, or continue at an agreed overage rate. Do not assume the service will stop simply because the original package is exhausted.
One published auto-top-up example purchases another 5 GB when the balance drops below 1 GB, charging a saved card or internal balance. Another subscription feature triggers a selected top-up at 90% of the current allowance. These settings can keep a task running, but they can also keep funding a faulty loop.
Establish the refill quantity, refill price, spending limits, and how to disable further purchases. Additional GB can have their own expiry. Buying them shortly before a cycle ends is expensive if they expire before the work is done.
An exhausted allowance may appear as an authentication-style error. For example, a documented proxy response uses 407 TRAFFIC_EXHAUSTED. Read the provider's error text and check the dashboard before replacing working credentials or retrying indefinitely.
Why a spending limit may not stop the bill immediately
A budget alert, a hard usage limit, and auto-top-up perform different jobs. An alert informs you; a limit can stop access; auto-top-up buys more service. Check which behavior is enabled.
One documented zone limit is calculated every 15 minutes, allowing spending to exceed the threshold before it takes effect. At an assumed 2 GB per minute, another 15 minutes means up to 30 GB. At 3 USD/GB, that is 90 USD beyond the intended stopping point. This illustrates the possible cost of delayed enforcement, not a universal delay for proxy services.
For large jobs, combine provider-side limits with task-side controls: bounded retries, a maximum number of operations, monitoring, and a way to stop the process. Leave headroom for delayed statistics and requests already in progress.
Where unexpected traffic goes
Start with the scope and timing of the measurement before deciding that the counter is wrong.
| What you see | What to check |
|---|---|
| Provider usage exceeds the scraper's download total | Uploads, headers, TLS or other counted overhead, compression, and additional resources |
| Traffic grows while the main job seems idle | Open browser profiles, media, background polling, updates, sync tools, and other scripts using the same access |
| The main account balance falls without matching requests | Traffic reserved or transferred to sub-users, as distinct from traffic consumed |
| A large monthly figure appears after one busy day | Whether the dashboard is showing actual use or a projected total |
| The counter updates after the script stops | Reporting delay and in-flight requests |
| Usage appears on unfamiliar domains | Shared credentials, old contractor access, compromised passwords, or an overly broad IP allowlist |
A published dashboard example projects 300 GB for a month after 10 GB on the first day. The projected 300 GB has not already been consumed. Another documented system deducts GB from the main balance when assigning them to a sub-user; that allocation is not proof of completed network transfers.
Separate credentials and budgets for each project make these checks easier. A 100 GB shared account allowance does not become 100 GB for every generated endpoint or browser profile.
If the discrepancy remains, run an isolated test and compare matching time ranges and units. Ask for a usage breakdown by user, domain, and direction where available. Record the transfer sample, counter readings, timestamps, and applicable billing rules. A mismatch caused by counting only response bodies differs from unexplained additional charges; do not accept an unexplained discrepancy just because some overhead is normal.
Reduce traffic without breaking the task
Load only what the task needs. A simple HTTP request may be sufficient for a page whose required data is already in the response. A browser is appropriate when the workflow depends on rendering or interaction. Test that distinction rather than automatically loading every page in a full browser.
Stop unnecessary resources before they download. Browser automation can block images, media, fonts, or selected third-party requests. Check that the changes preserve the required content and do not trigger extra reloads or failed attempts. Disabling JavaScript blindly can remove the data you came to collect.
Reuse work where freshness allows. Cache reusable resources, avoid duplicate jobs, and keep suitable connections or sessions alive. Repeatedly starting a fresh browser can discard reusable state and require another full load. A sticky IP may help a session, but it does not make subsequent traffic free.
Control retries and background activity. Limit attempts, pause appropriately after rate limits, and stop on persistent access or account errors. Close unused profiles and ensure system-wide proxy settings are not carrying unrelated software downloads. Keep compression enabled where supported and compare transferred sizes rather than decompressed output.
Measure the result after each change: the aim is fewer paid bytes per completed task. A large reduction in downloaded data is not a saving if the task starts failing and needs to run again.
When per GB pricing is a good fit
Traffic-based pricing can suit small or uneven workloads that need access to a broad pool, multiple locations, or rotating exits. It can avoid paying for a large fixed address list that receives little use. The expiry and minimum purchase still need to fit the schedule.
Sustained large transfers, media-heavy browsing, or a workload using only a few stable addresses deserve comparison with suitable fixed-price plans. As a simple example, a 60 USD monthly package and an equivalent service at 3 USD/GB cost the same at 20 GB. Above that volume, the fixed package has the lower direct price only if it permits the required usage without extra charges and delivers comparable results.
Compare like-for-like access. A cheap datacenter plan is not an alternative if the required sites reject it. A mobile modem is not a replacement for a geographically diverse mobile pool. A traffic allowance does not itself promise unlimited simultaneous connections, exclusive IPs, or unrestricted destinations.
What to establish before buying
The purchase should answer five practical questions:
- What will one usable result cost? Measure your workflow with the required network and filters, including errors and retries.
- What is included in the meter? Confirm upload, download, overhead, units, rounding, and treatment of failures.
- How much must be paid upfront? Check minimum purchases, discounts, optional features, and the price of extra GB.
- How long can the traffic be used? Read expiry, rollover, cancellation, and account-activity conditions for each allowance.
- What stops further spending? Confirm the behavior at zero balance, automatic purchases, sub-user limits, and any delay in enforcement.
With those answers, the price per GB becomes a usable budget figure: you know what is counted, what the rate covers, and how much work the purchase is likely to complete.