Do not compare unit prices first: what rhythm are you buying?
Rotating residential buys traffic: exits can rotate; the bill mostly follows GB. Static residential buys a fixed exit for the term: the bill mostly follows IP × month—not “how many GB you pushed this month.” Different task rhythms cannot be ranked by “whose unit price looks lower.”
If you have not picked the product class yet, read Rotating vs static residential first. If you already need static and are choosing shared vs dedicated, read Shared vs dedicated static. This page assumes you roughly know rotating vs static and focuses on how you pay and how to estimate real cost, using an “effective-result total cost” frame against on-site tiers. Lawful, authorized commercial and technical use only. Not supported for use in mainland China.
What per-GB billing is (rotating residential)
Rotating residential settles on traffic usage: fit for public-page batch sampling, multi-region checks, and independent short tasks. On-site published list about $0.40/GB—console wins. Country/region selection and HTTP or SOCKS5 follow what the console returns—protocol does not change the bill unit; it stays traffic-based.
Large-traffic side has a full 100 TB bundle: about $0.20/GB effective; published full-bundle total about $20,000. You must buy the complete 100 TB package for that tier; not split; on-site rule 1 TB = 1,000 GB (100 TB = 100,000 GB). Whether a bundle is worth it: see “Should you buy the 100 TB bundle?” below. Plans and estimators: Pricing.
What per-IP billing is (static residential)
Static residential gives a fixed exit for the term, billed mainly per IP × month (or resource cycle)—not by how many GB you used that month as the primary bill.
- Shared static about $1.50/IP/month (console wins)
- Dedicated static about $5/IP/month (console wins)
Fit when you lawfully operate stores that need long login and a consistent network identity. Isolation and multi-store planning: Shared vs dedicated static. This page only contrasts “monthly-rent logic vs traffic logic.”
Side-by-side billing
| Dimension | Rotating (per GB) | Rotating · 100 TB bundle | Shared static | Dedicated static |
|---|---|---|---|---|
| Bill unit | ~$0.40/GB (console wins) | ~$0.20/GB effective; full package ~$20,000; not split | ~$1.50/IP/month (console wins) | ~$5/IP/month (console wins) |
| What you buy | Traffic usage; rotatable exits | Fixed large traffic quota (rotating side) | Fixed exit for the term (shared-pool orientation) | Fixed, dedicated-orientation exit for the term |
| Main bill driver | Total traffic (retries / payload / failures per console metering) | Whether you can consume the full package; sunk cost | IP count × months | IP count × months |
| Typical use | Public sampling, multi-region checks, short tasks | Sustained high-traffic rotating workloads | Authorized store fixed-identity start / routine | Higher isolation long fixed identity |
| Bad cross-compare | “Per IP” vs static unit price | Forcing a full package on small traffic | Monthly rent for large rotate sampling | Many dedicated IPs for occasional page checks |
Prices above are marketing-page published figures—always console. This table is not a success-rate or competitor-delta claim.
Choose by budget question
| Your question | Prefer | Why | ZTProxy |
|---|---|---|---|
| Public page spot-checks / assorting; traffic not huge | Rotating · start per GB | Pay for usage; no monthly fixed IP | Rotating ~$0.40/GB; Rotating + Pricing |
| Monthly traffic may hit TB scale and tasks are rotating-type | Estimate effective traffic, then list tier vs 100 TB full package | Bundle unit lower but not split; has a floor | 100 TB: ~$0.20/GB, total ~$20,000; console wins |
| Authorized store needs the same exit long-term | Static · per IP/month | You buy fixed identity, not GB | Shared ~$1.50 or dedicated ~$5; detail Shared vs dedicated |
| “Static uses lots of traffic—cheaper than rotating?” | Ask whether you need fixed identity first | No fixed identity → rotating; need fixed identity → compare IP×month | Rotating vs static / Shared vs dedicated; sampling back to rotating |
| Same project has both sampling and stores | Split queues and bills | Mixing two rhythms in one bill unit mis-costs fastest | Manage rotating traffic + static monthly rent separately |
| Still undecided rotating vs static | Selection guide first, then return here for cost | Wrong class → any unit-price compare is wrong | Rotating vs static |
Effective-result total cost
Do not stare only at list price. More useful is a rough “what does it cost to get a usable result”—illustrative frame, not a promise, not a clone of the on-site calculator; metering details follow the console.
- Rotating (per GB): roughly ≈ (total traffic needed for successful target results, including retries, redirects, image/script weight, failed requests) × tier (~$0.40/GB or full-bundle effective)
- Static (per IP/month): roughly ≈ (fixed exits needed) × (shared ~$1.50 or dedicated ~$5) × months
List $0.40/GB is not “you only pay net HTML of successful pages”; failures and retries usually enter usage (exact rules: console—this page invents no fixed uplift %).
Qualitative rough scenes (illustrative, not promises)
Weekly spot-checks of a few public product pages. Traffic usually small → start rotating per GB; skip monthly fixed IPs; skip the 100 TB package for now.
Sustained large public sampling; monthly traffic may hit TB scale. Estimate traffic for effective results (retries + page weight), then compare ~$0.40/GB vs a full 100 TB package (~$0.20/GB, not split). Forcing a full package on small traffic raises sunk cost.
Authorized single- or multi-store long backend login. You need fixed identity → static per IP/month; shared ~$1.50, dedicated ~$5—detail Shared vs dedicated. Do not force rotating traffic to carry whole-month login identity.
Same project has public sampling and authorized stores. Split bills: rotating watches traffic; static watches IP×month. Do not mash both into one “who is cheaper” compare.
“When static monthly traffic is huge, is it cheaper than rotating?” If the task does not need fixed identity, static does not replace sampling traffic logic—return to rotating. If it needs fixed identity, compare IP count × months, not GB. Class frame: Rotating vs static.
Should you buy the 100 TB bundle?
Only when you reasonably expect to consume package-scale volume and the workload is truly rotating/traffic-type does the ~$0.20/GB compare matter. Remember on-site rules:
- Full package purchase, not split
- 1 TB = 1,000 GB (100 TB = 100,000 GB)
- Published total about $20,000—pricing card + console win
Do not write or assume “buying the package always saves money”: small traffic forced into a full package raises sunk cost. Use the estimator on Pricing; do not clone the full calculator here.
How to compare with other vendors fairly
Align questions before unit prices:
- Same bill unit (per GB vs per IP/month)?
- Do failures / retries enter usage?
- Minimum spend or full-package floor?
- Is static per IP/month, with region/stock separate?
This page does not publish unverified competitor price tables or “X% cheaper than brand Y.” After you re-read on-site tiers with effective-result cost, confirm on Pricing.
Pre-order checklist
- Task rhythm: rotate sampling / multi-region checks → watch GB; fixed identity / authorized stores → watch IP×month. Class undecided → Rotating vs static.
- Scale estimate: monthly traffic (GB / TB) or fixed IP count?
- Rotating tier: start ~$0.40/GB, or evaluate 100 TB full package (not split)?
- Static tier: shared ~$1.50 or dedicated ~$5? Detail Shared vs dedicated.
- Region: confirm stock in Locations + console before bulk.
- Smoke test: run a real task small, then re-read “effective results” against the console bill.
- Connect: Docs EN quickstart; sticky boundary: Sticky vs static.
FAQ
How are residential proxies usually billed—per GB or per IP?
Two common logics: rotating residential by traffic (GB); static residential by IP / month. ZTProxy rotating published about $0.40/GB; large traffic has a 100 TB full package about $0.20/GB effective; shared static about $1.50/IP/month; dedicated about $5/IP/month. Currency USD; console + Pricing win.
Why can the bill be higher than “$0.40/GB looks cheap”?
You often pay for total traffic needed for usable results, not only successful-page net HTML. Retries, redirects, image/script weight, and failed requests usually enter usage (console metering). Effective-result total cost is closer to the real bill than list price alone.
Should high traffic buy a fixed 100 TB-style package?
If the workload is rotating-type and you reasonably expect package-scale volume, compare ~$0.20/GB. Must buy full package, not split; 1 TB = 1,000 GB; total about $20,000—console wins. Small traffic need not force it. Estimate on Pricing first.
When static monthly traffic is huge, is it cheaper than rotating?
Ask whether you need fixed identity. No fixed identity—public sampling only → still rotating per GB. Need fixed identity → compare IP count × months; do not use static to “absorb sampling.” Shared vs dedicated: Shared vs dedicated.
Where is the shared vs dedicated static price gap?
Shared about $1.50/IP/month; dedicated about $5/IP/month (console wins). Both are fixed exits for the term; the gap is isolation orientation and multi-store planning—long form: Shared vs dedicated.
How to compare vendors fairly?
Unify bill unit (GB vs IP/month), ask whether failures/retries meter, check package floors and minimums, then rough effective-result cost. Do not compare ad $/GB alone. This page has no unverified competitor ranking.
Does sticky session change the billing unit?
Usually no. Sticky is a short session option on rotating: consecutive requests try the same exit; it is not monthly static, and usually does not change the per-GB unit. Detail: Sticky vs static; class boundary: Rotating vs static.
Who wins on price? Mainland China?
Prices and plans follow Pricing and the console; payment methods follow what registration/console currently offers (USDT/USDC available; Visa/Mastercard applying / pending). All proxy services on this site are not supported for use in mainland China.
Next steps
- Use the two tables: traffic bill (per GB) or IP monthly-rent bill.
- Open Pricing; rotating → Rotating; static → Static.
- Class undecided → Rotating vs static; static chosen, shared/dedicated → Shared vs dedicated.
- Connect via Docs EN quickstart; smoke-test a real task, then scale from console usage.
Separate per GB vs per IP → rough-estimate on Pricing →
Unsure? On-site support or [email protected]. Align task rhythm and bill unit before unit price.