Choose rotating, sticky session, or static residential by how long the same exit must stay—then confirm pricing in the console.
Start with one question: how long must the same exit stay?
Most “rotating vs static” debates start in the wrong place. Pool size and protocol labels matter less than one fact: how long does this job need the same residential exit IP?
Some work needs a long-lived fixed identity—authorized store backends and brand accounts you may operate. Other work only needs many independent exits—batch public pages, assortment sampling, multi-country spot checks. Between those poles: a multi-step checkout, post-login form, or ad-preview path where the same exit should hold for minutes, not a monthly lease.
Selection follows task rhythm. Use the decision table below to mark rotating (per-request), rotating with sticky, shared static, or dedicated static—then open the matching product and pricing. Smoke-test one real connection before you scale. Use these services only for lawful, authorized business and technical work.
What rotating residential proxies are
Rotating residential (dynamic residential on ZTProxy) routes traffic through a gateway into a residential pool. The exit can change per request or stay briefly under a sticky session parameter from the console.
Rotating fits jobs that do not need one identity for the whole project: batch public-page fetches, multi-region sampling, price or assortment checks, and short verification tasks. Pick country or region where inventory allows; bill primarily by traffic (GB). Marketing framing: about $0.40/GB, and a 100 TB full-bundle rate around $0.20/GB (full bundle only, not split; 1 TB = 1,000 GB). Confirm in console. Protocols are typically HTTP or SOCKS5—use the host, port, and auth the console returns.
See the products overview and Locations for multi-region sampling.
What static residential proxies are
Static residential assigns a fixed exit for the subscription term. Identity stays consistent while the order is active—useful when long login state, an allowlist-style source, or a stable environment matters more than many exits.
Static fits authorized store and brand-account operations you may run, and workloads that break when the exit jumps mid-day. Billing is typically per IP per month (shared vs dedicated). Marketing figures: about $1.50 / IP / month shared and about $5 / IP / month dedicated; confirm in console. Manage region, term, and renewals in the dashboard. Check Locations before large commitments—inventory can change.
If you only need continuity for a short multi-step flow, read the next section before buying a month of static.
Sticky session ≠ static IP
A sticky session on rotating residential asks the provider to try to keep the same exit for a defined window. When the window ends, the node changes, or the session cannot be held, your exit can still move. Sticky is a session parameter—not a leased fixed address.
A static IP is an order-assigned fixed residential address for the term you buy. You watch renewals and region, not session timers.
Rule of thumb: minutes to tens of minutes → rotating + sticky (console params). Same address for the whole term → static (shared first if isolation needs are modest; dedicated for exclusive fixed identity). Buying sticky when you needed a term-long fixed exit—or static for one-off sampling—wastes budget.
Side-by-side comparison
| Rotating (per-request) | Rotating + sticky | Shared static | Dedicated static | |
|---|---|---|---|---|
| Exit behavior | New exit often each request | Same exit for a session window (best-effort) | Fixed exit for the term | Exclusive fixed exit for the term |
| Billing unit | Traffic (GB) | Traffic (GB) | Per IP / month | Per IP / month |
| Geo flexibility | Strong for multi-region sampling | Strong; sticky holds one geo briefly | Tied to assigned region | Tied to assigned region |
| Login / long sessions | Poor fit for long logins | OK for short post-login flows | Built for long stable identity | Long stable identity + isolation |
| Typical jobs | Batch public pages, multi-region checks | Checkout/forms, one ad-preview path | Authorized store / brand long login | Higher isolation, long-term dedicated identity |
| Weak spots | Exit changes break long state | Window ends / node change can still move you | Shared pool; confirm isolation fit | Higher monthly cost; confirm inventory & term |
Numbers and protocols only from the live site and console—this table is not a success-rate or inventory guarantee.
Choose by task
| Task type | Prefer | Why | ZTProxy mapping |
|---|---|---|---|
| Batch public pages; many independent multi-region requests | Rotating (per-request) | No need for same identity across requests | Rotating residential · traffic billing |
| Short post-login flow, multi-step checkout/form, one ad-preview path | Rotating + sticky session | Same exit briefly; not a month-long lease | Rotating · session params per console |
| Authorized store / brand account long login; stable environment | Static · start with shared if fit | Fixed exit for the term | Shared static · about $1.50 / IP / month (confirm in console) |
| Higher isolation or long-term dedicated identity | Static · dedicated | Exclusive fixed IP | Dedicated static · about $5 / IP / month (confirm in console) |
| Same project mixes collection and store ops | Split queues: rotating + static | Mixing rhythms raises cost and failure modes | Order both; manage separately |
| Spot-check one country’s language/currency UI | Rotating + geo; sticky if flow is long | Sampling doesn’t need monthly fixed IP | Rotating + Locations |
Short cases
Authorized store backend. For an authorized store or brand account with long admin sessions, prefer static; start shared if isolation needs are modest, dedicated for exclusive fixed identity. Confirm region and term in console.
Competitor or assortment checks. Public listings across many SKUs or regions with no need for yesterday’s exit to equal today’s → rotating per-request. Retries and page weight raise GB cost.
Multi-country ad or landing checks. Verify language and layout from several countries with rotating + geo; add sticky only if one multi-step preview must share an exit.
Checkout or localization UI tests. Brief continuity for forms or currency/language paths → rotating + sticky first. Reserve static when one address must last the whole billing term.
Regional public content checks. Independent samples do not need a monthly fixed IP—use rotating and Locations, lawfully and within site terms.
Mixed workload. Split queues: rotating for public sampling, static for authorized long-login work. Order both and manage separately. See Solutions.
Align billing with budget
Match the bill to how work consumes capacity:
- Rotating: pay for GB. Retries, heavy pages, and parallel workers raise traffic even when results look flat. About $0.40/GB; 100 TB full bundle about $0.20/GB (full bundle only; 1 TB = 1,000 GB). Confirm in console. USD.
- Static: pay for IP × months. Shared about $1.50 / IP / month, dedicated about $5 / IP / month. Confirm in console.
Match the unit to task rhythm. Open Pricing, estimate against a small real job, then scale.
Pre-order checklist
- Region: Confirm options on Locations and in console (inventory can change).
- Product type: Rotating, rotating + sticky, shared static, or dedicated static—from the tables above.
- Protocol: HTTP or SOCKS5 as returned for that product—copy host, port, and auth from the console.
- Client stack: Browser, script, or automation configured against console credentials.
- Smoke test: One real task at small volume; only then raise concurrency or IP count.
- Docs: Follow Docs EN quickstart for first connection patterns.
FAQ
What’s the difference between rotating and static residential—which should I buy?
Rotating changes exits (per request or via sticky) and bills mainly by traffic. Static keeps a fixed exit for the term and bills per IP. Buy rotating for independent or multi-region jobs; buy static when authorized long-login work needs the same address for the term. Use the decision table, then open rotating or static.
Can a sticky session replace a static IP?
No. Sticky is best-effort continuity on rotating for a session window; the exit can still change when the window ends or the node moves. Static is a term-assigned fixed address. Sticky for short flows; static when you need the same IP for the whole term.
Cross-border store / long backend login—which type?
For authorized store or brand backends with long login state, prefer static. Start shared if isolation fits; dedicated for exclusive fixed identity. Confirm region and term in console. Do not use proxies for unauthorized account activity.
I only check assortment or competitor pages—do I need static?
Usually no. Independent public-page checks fit rotating with geo selection. Static adds monthly IP cost if you never need the same exit tomorrow. Smoke-test rotating on a small sample first.
How does billing work—per GB or per IP?
Rotating is primarily per GB; static is primarily per IP / month. Marketing figures (about $0.40/GB, 100 TB ~$0.20/GB full bundle, shared ~$1.50, dedicated ~$5) must be confirmed in console. See Pricing.
Are HTTP and SOCKS5 supported?
Depends on the product. Use the protocol, port, and auth returned in the console for your order—do not guess from generic examples.
What do I need for a first connection?
An account, region, product type, and a client with console-returned credentials. Smoke-test once before scaling. See Docs EN quickstart.
How do I check country/city availability?
Use Locations plus the console (or sales if inventory is unclear). Availability can change—confirm before a large static order or multi-region plan.
Can this be used in mainland China?
All proxy services on this website are not supported for use in mainland China.
Next steps
- Mark your row: rotating, sticky, shared static, or dedicated static.
- Open Pricing and confirm the plan in console.
- Order rotating and/or static; manage mixed queues separately.
- Connect via Docs EN quickstart, then scale after a successful smoke test.
Still unsure? Contact on-site support or [email protected]. Choose by how long the same exit must stay, then test one live connection.