Static vs Rotating Residential Proxies: What You Actually Pay For

These two get confused constantly because both are called “residential”. They behave differently, but the decisive difference is usually how you are billed.

What each one is

Rotating residential routes through a pool of real consumer connections. You get a different IP per request, or per session window. The addresses genuinely belong to households, so they carry high trust.

Static residential, usually sold as ISP proxies, is a single IP registered to a consumer ISP but hosted in a datacenter. You get ISP-level trust with datacenter speed and stability, and the address is yours for the term.

The billing difference matters more

Rotating residential is billed per gigabyte. You pay for traffic, not addresses. Access to thousands of IPs is included; bandwidth is the meter.

ISP proxies are billed per IP per month. Unlimited traffic through a fixed number of addresses.

That inverts the sizing question. With rotating you ask “how much data will I move?”. With ISP you ask “how many addresses do I need at once?”.

When per-GB wins

You need many different IPs and little data each. Checking search rankings from 500 locations, verifying ads across regions, sampling prices in different countries. Thousands of IPs, a few KB each — trivial bandwidth, and buying 500 static IPs would be absurd.

Geographic breadth. Rotating pools cover far more countries and cities than any static inventory.

Short bursts. Occasional work where a monthly per-IP fee would sit idle.

When per-IP wins

High volume through few addresses. Downloading large pages, media, or anything measured in gigabytes. On a per-GB plan the bill scales with your traffic; on ISP it does not move.

Anything logged in. Accounts want a consistent IP. A static address you keep for months looks like a person with a home connection — see rotating vs sticky sessions.

Speed and consistency. ISP proxies sit in datacenters on good connections. Rotating residential routes through consumer links with consumer latency and variable reliability.

Predictable cost. A fixed monthly figure, whatever your usage. Per-GB bills can surprise you — an unnoticed retry loop on a media-heavy site can burn a plan in hours.

A worked comparison

Scraping 100,000 product pages at roughly 100 KB each, so about 10 GB.

• Rotating residential at $1.81/GB ≈ $18 — plus you get thousands of IPs and effortless rate-limit spreading.
• ISP proxies: you would need several to spread the load, at $2.44/proxy/month, so maybe 5 IPs ≈ $12/month with unlimited traffic.

At this volume they are close. Move 100 GB and the picture changes completely: rotating costs ~$180, the ISP proxies still cost $12.

The crossover is roughly where your bandwidth cost exceeds your IP cost. Estimate your GB before choosing — how many proxies you need has the arithmetic.

Cut bandwidth before you buy more

If you land on per-GB, blocking images, fonts and media typically cuts usage by 70–80%. That single change often matters more than which provider you pick — there are code examples in Puppeteer and Playwright.

Quick guidance

You need	Choose
Many IPs, little data each	Rotating residential
Few IPs, lots of data	ISP (static)
Logged-in accounts	ISP (static)
Wide geographic coverage	Rotating residential
Predictable monthly cost	ISP (static)
Occasional short bursts	Rotating residential

Plenty of setups use both: ISP proxies for the accounts, rotating residential for discovery. They are not competing purchases so much as different tools.

Current pricing for both is on the pricing page, and ISP proxies and residential proxies have the detail on each.