What Is a Residential Proxy? How It Works
Bohdan Anpilohov
Last updated on · Jun 18, 2026 · 9 min read
Residential proxies explained: how they work, the types, rotating vs sticky, price per GB, and whether they can be detected in 2026. A practitioner's guide.
In short. A residential proxy is a home IP address — one an internet provider assigned to a real device in someone's house. Route your traffic through it and a website sees an ordinary person on a home connection, not a server. Residential proxies are billed per gigabyte, run in rotating or sticky modes, and in 2026 a residential IP alone is no longer enough to stay undetected: anti-bot systems also check your TLS fingerprint and behaviour.
Every serious website figures out, in a fraction of a second, where a request came from and whether a human or a script sent it. The main clue is your IP address. If that address belongs to a data center, many sites block the request on sight. A residential proxy fixes this by swapping the server address for an ordinary home one.
What is a residential proxy
A residential proxy is an IP address that an internet service provider (ISP) assigned to a real device in someone's home. When your requests pass through it, the target site sees an ordinary home user instead of a server in a data center.
The difference between a residential and a data-center address comes down to who owns it. Every IP belongs to an autonomous system (ASN) — a block of addresses under a single owner that tells a site whose address it is. A data-center proxy's ASN belongs to a host (Amazon, Google Cloud, OVH); those ranges are publicly known and flagged by anti-bot systems in advance. A residential proxy's ASN belongs to a consumer ISP (Comcast, Vodafone, Türk Telekom), so its address is indistinguishable from a neighbour's.
How residential proxies work
You don't connect to each home IP by hand — you talk to a gateway, and it picks an address from the pool. The gateway (also called backconnect) is a single entry point that hands you a different exit IP for each request.
A request goes through four steps:
- You send the request to the gateway — one host and port.
- The gateway picks a free residential IP that matches your parameters (country, city, ISP).
- The request reaches the site through that home address.
- The site replies to the residential IP, and the gateway returns the response to you.
On your side, only one connection string changes. The gateway handles the pool, the exit-node choice, and rotation.
Types of residential proxies
"Residential proxy" is an umbrella for five different tools:
| Type | What it is | When to use it |
|---|---|---|
| Rotating | A new IP on every request or on a timer | Large-scale scraping and data collection |
| Static (ISP) | Residential trust + data-center speed | Long sessions, account management |
| Mobile | Carrier IPs (4G/5G) | The strictest anti-bot targets |
| Dedicated | An address only you use | Sensitive tasks, clean reputation |
| Shared | A pool split between clients | Budget, high-volume jobs |
ISP proxies (static residential) are a hybrid worth knowing: the address physically sits in a data center but is registered to a consumer ISP. You get residential-level trust at data-center speed and stability, which makes them a strong pick for managing accounts.
Mobile proxies are the hardest to block because of CGNAT — thousands of real subscribers share a single mobile IP. Blocking one would cut off a thousand genuine users, so sites rarely do it.
Rotating vs sticky sessions
Rotation and sticky are two modes of the same pool, not separate products.
- Rotation changes the IP on every request. It suits large-scale collection: the load spreads across thousands of addresses.
- A sticky session holds one IP for a fixed window — usually from 10 minutes to 24 hours. You need it when the address must stay stable: log in, add to cart, check out.
The mode is set with a parameter in the connection string; there's no need to change plans.
Residential vs datacenter, ISP, mobile, and VPN
| IP source | Detection risk | Speed | Cost | Best for | |
|---|---|---|---|---|---|
| Residential | Home ISP | Low | Good | Higher (per GB) | Protected sites, geo |
| Datacenter | Hosting | High | Fastest | Low | APIs, tolerant targets |
| ISP (static) | ISP, but in a DC | Low | High | Mid-to-high | Accounts, long sessions |
| Mobile | Carrier | Lowest | Medium | Highest | Strictest targets |
| VPN | Usually a DC | High for automation | High | Low | Personal privacy |
Since "residential proxy or VPN?" is one of the most common questions, here's the short answer: they solve different problems. A VPN gives you one shared address and is built for one person's privacy. A residential proxy is a pool of thousands of home IPs with rotation, built for automation and scale. For data collection a VPN is useless — its single address hits rate limits almost immediately.
What residential proxies are used for
Residential proxies are for tasks where you need to look like a real user from a specific country and do it at volume:
- Web scraping of sites that block data-center ranges
- Ad verification — how ads actually render in a given country
- Price monitoring of competitors by region
- Rank tracking in search for a specific geo
- Managing multiple accounts without instant bans
- Sneaker and ticket drops — appearing as many different shoppers
- Accessing geo-restricted content
Can a residential proxy be detected?
A residential IP makes detection much harder, but in 2026 it no longer guarantees you're invisible. Anti-bot systems (Cloudflare, DataDome, Akamai) check four layers at once, and failing any one of them gets you blocked:
- IP. This is where a residential proxy helps: a home ASN removes the crudest "this is a server" signal.
- TLS fingerprint (JA4). JA4 is a fingerprint of the TLS handshake that tells a site which client is really connecting. Claim to be Chrome in your User-Agent while sending a Python library's handshake, and you're blocked before the page loads.
- Post-quantum TLS. Since April 2024 (version 124), Chrome uses the post-quantum key exchange X25519MLKEM768 by default. According to Cloudflare, by 2025 over a third of human web traffic was already protected this way. A client without that key looks outdated and stands out — even on a clean residential IP.
- Behaviour — cursor movement, rhythm, and request timing.
The takeaway is simple: a residential IP is necessary but not sufficient. It clears the first barrier; the rest depends on how coherent your client's fingerprint and behaviour are.
What matters more: pool size or IP reputation
A pool's headline number ("100M+ IPs") says almost nothing about quality. Three things actually matter:
- Reputation beats novelty. A residential IP with no history can score worse with a site than an aged address that carries organic traffic.
- Addresses burn per target. An IP heavily used against Amazon is flagged on Amazon but stays clean on another site. Reputation is tracked per target.
- The real metric is curation: how often addresses rotate, whether they get to rest, and the success rate the pool delivers on your target in your country.
So when you evaluate a provider, ask about coverage in the country you need and the success rate on your targets — not the total address count.
How much do residential proxies cost
Residential proxies are billed per gigabyte of traffic, not per request. A market reference for 2026:
| Segment | Price per GB (approx.) |
|---|---|
| Budget | from ~$1.75 |
| Mid-range | ~$2.2 |
| Premium | ~$3.5–10+ |
| Jetproxy (prepaid) | from $1.99, billed per GB |
Because the bill follows traffic, the biggest saving is cutting the weight of the pages you load. According to HTTP Archive, the median web page in 2025 weighs about 2.86 MB, and roughly 40% of that is images (with fonts and CSS, nearly half). For data collection you usually don't need any of it.
Blocking images and fonts cuts traffic by 2–4×. Scraping 100,000 pages in full is around 290 GB; with assets blocked it's about 70 GB. At $2/GB that's $580 versus $140 for the same job.
That's why the billing model matters: for irregular workloads, paying per gigabyte up front beats a monthly subscription — you top up only what a job needs, instead of paying for a quota that resets at month's end.
How to choose a provider
- Coverage in the country you need, not a total IP counter
- Real success rate on your targets
- Targeting granularity — country, city, ISP, ASN
- Protocols — HTTP(S) and SOCKS5
- Billing model — prepaid, per-GB, no monthly subscription
- Support — it matters most when you're getting started
How to get started
A provider gives you a connection string in the form host : port : username : password. In most tools it goes in as an ordinary HTTP proxy:
# A basic request through a residential gateway
curl -x http://user:pass@gw.jetproxy.io:8080 https://ip.jetproxy.io
# => { "ip": "...", "country": "TR", "isp": "Türk Telekom" }
# Sticky session: append a session label to the username
curl -x http://user_session-abc123:pass@gw.jetproxy.io:8080 https://ip.jetproxy.ioCountry, rotation, and session type are set with parameters in the username — no plan change required.
Are residential proxies legal?
The tool itself is legal. What makes it illegal is the use: harvesting personal data, bypassing paywalls, fraud. Use residential proxies for publicly available data, respect each site's terms, and pick a provider with a transparent source of IPs.
The bottom line
A residential proxy gives you a real home IP so your requests look like an ordinary user's traffic from the country you need. Choose the mode for the job — rotation for scale, sticky for sessions — judge a pool by its reputation rather than its size, and remember that in 2026 the IP address is only the first of four checks.
You can try it on a curated pool at Jetproxy — prepaid, from $1.99.
Frequently asked questions
- What is a residential proxy in simple terms?
- A residential proxy is the IP address of a real home device, assigned by an internet provider. Traffic routed through it looks to a website like an ordinary user's requests rather than a server's.
- How is a residential proxy different from a VPN?
- A VPN gives you one shared IP and is built for one person's privacy. A residential proxy is a pool of thousands of home addresses with rotation, built for automation and scale. For data collection a VPN doesn't work — its single address hits rate limits fast.
- Can a residential proxy be detected?
- By the IP alone, almost never — to a site it's an ordinary home address. But in 2026 anti-bot systems also check the TLS fingerprint (JA4), the browser fingerprint, and behaviour, so a residential IP doesn't guarantee invisibility on its own.
- How much do residential proxies cost?
- They're billed per gigabyte; the 2026 range is roughly $1.75 to $10+ per GB depending on provider and volume. Blocking images and fonts during data collection cuts usage 2–4×.
- How are rotating proxies different from sticky?
- They're two modes of one pool. Rotation changes the IP on every request (for large-scale scraping); sticky holds one address for 10 minutes to 24 hours (for logins, carts, and multi-step flows).
- What is an ISP proxy?
- An ISP proxy (static residential) is an address that physically sits in a data center but is registered to a consumer ISP. It combines residential trust with data-center speed and stability.