Anti-detect browser proxy setup: guides and comparison

What an anti-detect browser does with a proxy

An anti-detect browser keeps many browser profiles on one computer. Each profile has its own cookies, storage and browser settings, and each one can have its own proxy. Teams use them to keep client workspaces apart, to check how sites look from other countries, and to hand profiles between colleagues.

The proxy is what gives a profile its network identity. When you open a profile, the browser usually checks the proxy first, looks up where its exit IP is, and can set the profile's timezone, language and geolocation from that answer. Every request the profile makes then goes through that proxy.

That is why one proxy per profile matters. If two profiles share an exit IP, websites see the same connection behind both of them, which undoes the point of separating them. A sticky session per profile lets you manage each profile independently. The requested lifetime is best effort: an exit can change sooner, and separate sessions can receive the same IP.

Anti-detect browser proxy support compared

Checked 1 October 2026 against each vendor's own docs. "Not stated" means the docs don't say. Prices for built-in proxies change often; each guide dates its figures.

A note on "HTTPS". No vendor's docs say whether its HTTPS type opens TLS to the proxy, which is what TrueProxies port 8443 expects. Our tests so far: AdsPower 8.7.23 passed 10 of 10 checks on 8443 with TLS to the proxy. Dolphin Anty offered no HTTPS type. GoLogin HTTPS was not tested.. Until you've checked your browser, use HTTP on 8080 or SOCKS5 on 1080.

Which TrueProxies proxy to use in an anti-detect browser

To try a residential IP in any browser, start the one-hour free trial. The trial supports country targeting and sticky sessions, without lifetime; city, region, ASN and session lifetimes need a Traffic pack.

The username pattern that works in every browser

Every anti-detect browser asks for the same four things, either as separate fields or as one string: host, port, username and password. Copy the host from your dashboard. TrueProxies targeting lives in the username, so the password never changes.

Three profiles, three sessions:

YOUR_USERNAME-country-us-city-chicago-session-shopus01-lifetime-86400
YOUR_USERNAME-country-gb-city-london-session-shopuk01-lifetime-86400
YOUR_USERNAME-country-de-session-qade01-lifetime-3600

Two rules prevent most problems. Never put hyphens or underscores in a session ID, because the hyphen separates options. And treat sticky sessions as best effort: if a residential exit goes offline, the session gets a new IP. Keeping the same session ID after a restart asks for the same IP again. Always set lifetime: without it, a session holds its IP only briefly. Misspelled options are refused, not ignored: country-usa fails with the gateway's targeting reason instead of connecting from the wrong place. More background: sticky vs rotating proxies.

Pick the port that matches the proxy type

A type and port mismatch is the most common first-day failure: SOCKS5 pointed at 8080, or HTTP pointed at 1080. If a check fails right after setup, look there first. More detail: HTTP vs SOCKS5.

Keep each profile consistent with its proxy

Most anti-detect browsers can fill a profile's timezone, language and geolocation from the exit IP. The setting names differ ("Based on IP" in AdsPower and GoLogin, "Match IP" in MoreLogin), and each guide lists the exact labels. Leave them on unless you have a reason to set values by hand.

WebRTC is the other setting to look at. Browsers offer modes that replace or hide your local addresses; each guide explains which mode its browser uses by default.

Then verify from inside the profile:

1. Open the IP leak test and confirm the exit IP, country and city.
2. Open the WebRTC leak test and the DNS leak test.
3. Compare the profile's timezone and language with the exit's location.

If the browser places the IP in a different city than our test does, the cause is usually the browser's IP lookup service, since lookup databases disagree. Switch the browser's lookup service if it offers one (AdsPower, MoreLogin, Incogniton and DICloak do), or set the values by hand.

When the browser says the proxy failed

Our checks showed "Connection test failed!" in AdsPower and a bare "ERROR" badge in Dolphin Anty. Vendor documentation also lists "Failed to establish a proxy connection" in Dolphin Anty, "Proxy check failed" in Multilogin, "Detection Failed" in MoreLogin, "Failed to get proxy data" in Octo Browser. None of them shows the reason the proxy gateway gave.

Paste the same proxy into the TrueProxies proxy checker, or run it with curl over HTTP on port 8080. The reason comes back in the 407 body and the X-Proxy-Reason header:

curl -v -x "http://YOUR_HOST:8080" \
  -U "YOUR_USERNAME-country-us-session-shopus01:YOUR_PASSWORD" \
  https://example.com -o /dev/null

The usual reasons are a wrong password, a misspelled targeting option, a used-up Traffic pack, or a closed trial. A bare 407 with no reason means too many failed attempts in a row; wait 60 seconds. The anti-detect browser proxy errors guide maps every browser message to its fix.

Built-in proxies vs your own

Most of the tools above offer proxies inside the app. GoLogin charges $1 per GB after the traffic its plans include. Octo Browser's Proxy Shop lists €7/GB for 1 GB in its docs. Multilogin charges $3.50/GB as a top-up and from $2.275/GB in bulk. MoreLogin sells static IPs, Incogniton runs a Proxy Shop next to a free shared proxy, DICloak added partner IPs in September 2026, and ixBrowser sells proxies in the app without public prices. AdsPower and Dolphin Anty don't sell their own. Prices were checked 1 October 2026.

Built-in proxies make sense when you want one bill and a quick start, or when you need something TrueProxies doesn't sell, like a static IP for weeks or mobile IPs. Your own proxies make sense when you run more than one browser and want one provider across all of them, when you need region, city or ASN targeting, when you want to set each session's lifetime yourself, or when per-GB tiers matter at volume.

Setup guides by browser

• AdsPower proxy setup. Formats for Add Proxy and Bulk Create, the Local API call, and fixes for "Connection test failed", "Proxy failure" and "Abnormal" in Network Diagnostics.
• Dolphin Anty proxy format. All six documented proxy layouts with TrueProxies examples, bulk add, the Remote API, and what "Failed to establish a proxy connection" usually means.
• GoLogin proxy setup. The paste formats, Import proxies and bulk Update proxy, the API call, and each GoLogin proxy error with its fix.

Other browsers and cloud phones

Kameleo. Kameleo sets a proxy per profile over HTTP, SOCKS5 or SSH, and its Local API can create, update and test that proxy in code. Paste a Traffic pack sticky session as username:password@hostname:port on the profile's Connection tab, then run Test Proxy before you launch. Its docs treat HTTP and HTTPS as one type, so use HTTP on 8080 or SOCKS5 on 1080.

DICloak. DICloak keeps proxies in a saved list, parses host:port:user:pass from Quick Input, and imports them in batches on paid plans. Its Local API v2 can create, check and update proxies, with an IPv4 or IPv6 setting on each. Save your Traffic pack sessions once, then give each profile its own.

BitBrowser. BitBrowser takes HTTP, HTTPS, SOCKS5 and SSH proxies and adds them in bulk as Host:Port:Username:Password lines or through an Excel profile template. Its Local API sets a proxy per profile and can update proxies across many profiles in one call. Confirm each exit with Proxy Detection.

ixBrowser. ixBrowser adds up to 200 proxies per batch, one proxyip:port:username:password line each, and its Local API sets a proxy when it creates or updates a profile. Batch lines default to HTTP, so point them at port 8080, and give each line its own session ID.

GeeLark. GeeLark runs cloud phones rather than a desktop browser, and each cloud phone can take its own HTTP, HTTPS or SOCKS5 proxy, from a spreadsheet or through its API. Pair each phone with its own Traffic pack sticky session, targeted to the country the phone is set up for.

Anti-detect browser proxy FAQ

Related guides

• Anti-detect browser proxy errors
• TrueProxies proxy checker
• Traffic packs
• Datacenter IPv6