If you have arrived here because something you were trying to do online got blocked, or because a tutorial told you that you need residential proxies without explaining why, this is the starting point. No prior knowledge assumed, no jargon that is not explained as it appears.
What a proxy actually does
Normally your computer connects directly to a website, and the website sees your IP address, the number your internet provider assigned to your connection. A proxy sits in the middle: you send your request to the proxy, the proxy forwards it to the website, and the website sees the proxy’s address instead of yours.
That is the whole mechanism. Everything else is about whose address you borrow.
Why the type of address matters
Websites treat addresses differently depending on where they come from, and this is the part that surprises newcomers.
A datacenter address belongs to a hosting company, the sort of place servers live. These are cheap and fast, but they are also obviously not people. The ranges are publicly registered, so a website can tell instantly that a request came from a server, and many sites treat that as a reason to block, challenge, or serve different content.
A residential address belongs to a real home internet connection, assigned by a consumer provider to a household. To a website it looks like an ordinary person browsing from home, which is why it works on sites where datacenter addresses do not. These come from people who agreed to share their connection, which is why they cost more: the supply is finite in a way datacenter addresses are not.
There are other types, and the full vocabulary is in the glossary, but that distinction covers most of what a beginner needs.
When you actually need one
Residential proxies are worth their cost when your work depends on either of two things.
Seeing what people elsewhere see. Prices, search results, product availability, and advertising vary by country and often by city. If you need to know what a customer in Germany sees, you have to ask from Germany, and a residential address in Germany is how you do that. This covers price monitoring, checking how your site or ads appear in other markets, and collecting research data that varies by region.
Collecting public data at a scale one connection cannot manage. Any site will notice thousands of requests from a single address and start refusing them. Spreading that volume across many addresses is how large collection jobs keep working.
If neither applies, you may not need residential proxies at all. Undefended targets and your own infrastructure are fine over cheaper datacenter addresses, and using residential where it is not needed is simply more expensive. The honest comparison is in residential versus datacenter.
The two ways they behave
This is the concept that confuses people most, and it is simple once stated.
Rotating means each request goes out through a different address. This is the default and the right choice for collecting data, because spreading requests across many addresses is exactly what keeps any single one from drawing attention.
Sticky means you keep the same address for a while. You need this whenever a site remembers you between requests: logging in, stepping through a multi-page search, or anything where changing address mid-way would look like a different person appeared halfway through. You get it by adding a session identifier to your username, and it lasts for a set time before rotating.
Most projects use both: rotating for bulk collection, sticky for the parts that involve a sequence. More in sticky versus rotating.
How you pay for them
Residential proxies are billed by the data you move, measured in gigabytes, rather than by how many addresses you use. That catches people out, because it means the number of IPs is not something you buy, and the thing to estimate is bandwidth.
The practical consequence is that what you fetch matters more than how many requests you make. Fetching a page’s underlying data is a few kilobytes; loading that page fully in a browser with all its images, fonts and scripts can be several megabytes. The same job built the second way can cost a hundred times more. That trade-off is covered in estimating bandwidth and cutting bandwidth costs.
Your first request
Four things: a host, a port, a username, and a password. The host and port never change. Your targeting goes in the username.
# simplest possible: rotating, no location preference
curl -x customer-USERNAME:PASSWORD@p.shifter.io:443 https://ipinfo.io/json
# same request, but exiting through Germany
curl -x customer-USERNAME-country-de:PASSWORD@p.shifter.io:443 https://ipinfo.io/jsonRun the first one twice and you should see two different addresses, which confirms rotation is working. The full format, including sticky sessions and city targeting, is in how to connect to a residential proxy.
Four mistakes beginners make
Expecting a proxy to solve a blocking problem on its own. The address is one signal among several. If your requests do not otherwise look like a browser, you can still get blocked, and the next thing to fix is usually headers.
Going too fast. New users often send requests as quickly as their code allows, which is the fastest route to being blocked. Slow down deliberately; a polite pace is not just courteous but keeps your success rate high, per rate limiting and throttling.
Trusting a 200 response. A page can return “success” while containing a challenge, an empty result, or a generic version of what you wanted. Check that the content is what you expected before treating it as data, as in detecting blocked or fake content.
Loading full pages when the data is available directly. Many sites fetch their content from an underlying endpoint your browser can reveal in its network panel. Calling that directly is faster, simpler to parse, and dramatically cheaper, which is the decision in when you need a headless browser.
Staying on the right side of it
Proxies change where your request appears to come from. They do not change what you are allowed to do. Collect public data, respect each site’s terms of service and robots directives, keep your request rate polite, and be careful with personal data. Reaching content that legitimately varies by region is ordinary business work; using a proxy to get around a restriction meant to apply to you is not, and the tool does not change that. The legitimate framing is in bypassing geolocation restrictions legally.
Where to go next
Once your first request works: choosing the right plan for sizing, how many proxy IPs you actually need if someone asks you that question, and what to test before you buy if you are still evaluating. When something breaks, IP not rotating and fixing 407 errors cover the two most common first problems.
The bottom line
A proxy forwards your request so the site sees its address rather than yours, and a residential one borrows a real home connection, which is why it is treated as an ordinary visitor. You need that when your work depends on seeing what people in a specific place see, or on collecting public data at a volume one connection cannot sustain. Rotate by default, hold a sticky session when a site is tracking a sequence, and remember that you pay for data transferred, so fetching less is the main lever on cost. Start with a single bare request, confirm it rotates, then add targeting one flag at a time.
When you are ready, residential proxies give you the country and city targeting, rotation and sticky sessions described here through one connection, with per-GB pricing so a small first project costs a small amount.