Antidetect browsers exist to make each profile look like a separate person on a separate computer. The proxy is the part that makes it a separate place, and it's the part people most often get subtly wrong in a way that undoes everything else.
The setup itself takes about a minute in every one of these tools. The decisions around it are what matter.
The three rules before you touch a settings screen
One profile, one IP, permanently. The address is the single strongest link between two accounts. Two profiles behind the same IP are connectable no matter how carefully you've varied their fingerprints, screen sizes and user agents. Platforms record this at the time, so sharing early and separating later doesn't unwind it.
Sticky, not rotating. This one catches experienced people. A rotating gateway hands you a new IP on every request, which is exactly right for scraping and exactly wrong here. One page load pulls a hundred resources, so a single page can reach a site from three countries in four seconds while your fingerprint stays identical throughout. Nothing about a real person looks like that.
Residential or mobile, not datacenter. Datacenter ranges are published and easy to identify. Using one behind an antidetect browser is a contradiction: you've spent effort making the browser look like a home computer and then announced you're in a data centre.
The sticky session is not optional
If your provider gives you a rotating gateway by default, find the sticky option before you create a single profile. On our residential plans a session lives in the username, and the dashboard writes it for you when you pick a session length. The format guide explains what those extra words in the username mean.
What you'll be typing
Every one of these tools wants the same four values in separate boxes, plus a protocol:
The same four values, in whatever order the tool asks for them
198.51.100.7Host:8080Port:hp_ir4k2-session-a41f9c-time-1800Username:9fa2c1Password198.51.100.7:8080:hp_ir4k2-session-a41f9c-time-1800:9fa2c1hp_ir4k2-session-a41f9c-time-1800:9fa2c1@198.51.100.7:8080http://hp_ir4k2-session-a41f9c-time-1800:9fa2c1@198.51.100.7:8080
A sticky residential line. The session and time modifiers keep this profile on one exit IP.
Note the username. On a sticky residential plan it carries the session id, which is what pins the profile to a single IP. Copy it exactly, including everything after the first hyphen, because trimming it back to the bare username silently turns rotation back on.
AdsPower
Proxy settings live in the profile itself, in the Proxy Info section when you create or edit one.
AdsPower
- 1
Open New Profile, or edit an existing one
Proxy is per profile. There's no global setting, and that's deliberate.
- 2
In Proxy Info, set Proxy Type
HTTP, HTTPS or SOCKS5. Match what your provider gave you, and remember each protocol has its own port.
- 3
Fill in Proxy Host and Proxy Port separately
The host on its own with no
http://in front of it, and the port in its own box. - 4
Fill in Proxy Account and Proxy Password
These are the proxy's own credentials, not your AdsPower login and not your provider's dashboard login.
- 5
Press Check Proxy before saving
It reports the exit IP and location it sees. Confirm the country is the one you asked for; a mismatch here means your targeting didn't take.
Dolphin Anty
Dolphin keeps proxies in their own list and assigns them to profiles, which is the better model once you have more than a handful.
Dolphin Anty
- 1
Open the Proxies section and add a new proxy
Saving it once and reusing it beats retyping it into every profile.
- 2
Paste your line, or fill the fields in
Dolphin parses pasted
host:port:user:passlines well. Glance at what it filled in before saving, because a password containing a colon can land in the wrong box. - 3
Name it after the profile it belongs to
Not after the country. You'll have twenty US proxies and no way to tell which profile owns which, and reusing one by accident is the mistake that links accounts.
- 4
Assign it when you create the profile
In the profile's proxy field, pick the saved entry.
GoLogin
Open the profile, go to the Proxy tab, and choose a custom proxy rather than the built-in traffic. Fill in the connection type, the host, the port and the credentials. GoLogin will offer to set the profile's timezone from the proxy's location, which is worth accepting: a US exit IP paired with a European timezone is a mismatch that gets noticed.
Multilogin, Octo, Incogniton
All follow the same pattern: a proxy section inside the profile, a protocol dropdown, four fields, and a test button. If you can do one you can do all of them. Multilogin is the strictest about matching timezone and locale to the proxy, and it's right to be.
Check it from inside the browser
The built-in test buttons only prove the proxy answered them. Once the profile is open, load a page that reports what the site actually sees and check three things:
What to verify in the profile, not in the settings dialog
| Check | What wrong looks like |
|---|---|
| The exit IP | Your own address, meaning the profile isn't using the proxy at all. |
| The country and city | A location you didn't ask for, meaning your targeting didn't apply. |
| WebRTC | Your real local address showing alongside the proxy's. The browser should be masking this; if it isn't, the setting is off. |
| Timezone | A timezone that doesn't match the exit country. This one is a strong signal on its own. |
| The IP again, five minutes later | A different address, meaning your session isn't sticky and rotation is still on. |
The last row is the one people skip, and it's the one that quietly costs profiles.
That final check is worth doing deliberately. Open the profile, note the IP, do some ordinary browsing for a few minutes, and look again. If it changed, your session modifier isn't being applied and every profile you've created so far has been hopping addresses mid-session.
Common problems
Pages load slowly but do load. Residential proxies are slower than your own connection by nature, because traffic goes through somebody's home line. A second or two of extra latency is normal. Ten is not, and usually means an overloaded exit rather than a broken setup.
One site works, another shows an error page. The proxy is fine and that site has flagged the IP. No setting will fix it; you need a different address. This is why one profile per IP matters, since a burned IP then costs you one profile instead of all of them.
The proxy tests fine but the profile shows your real IP. Almost always a profile that was open before the proxy was saved. Close it fully and reopen.
Everything worked yesterday and nothing works today. Check whether your plan still has traffic left. A residential plan that's run out of data stops passing traffic while every setting still looks perfectly correct, which is a genuinely confusing failure.