Anti-Detect Browser Proxy Setup Guide 2026 (Complete)

Anti-detect browser proxy setup comes down to one question per profile: which IP address, country and network should a website see when this profile opens? The browser keeps each profile's cookies, logins and fingerprint apart. The proxy decides where that profile appears to connect from. Get the pairing wrong and a GEO check shows you the wrong lander, or a shared team login shows up from a different country every time someone else opens it.

This guide covers the proxy side of legitimate setups: agencies working in client accounts, brands running separate accounts where the platform allows it, media buyers checking landers in each GEO, and QA teams testing their own product. It covers proxy types and prices, sticky sessions, protocol settings, binding a proxy to a profile, and leak checks. It doesn't cover getting around a platform's restrictions, because no proxy makes that allowed.

Choosing the browser itself? See anti-detect browsers for multi-accounting teams.

Platform Rules Come First

A proxy changes the IP a site sees. It doesn't change who owns an account or what the platform allows. These are the rules to check before you build anything, as they read in September 2026:

• Meta. The Terms of Service say to "create only one account (your own)" and not to give others access to it without Meta's permission. After Meta disables an account for a violation, "you agree not to create another account without our permission." Under the Account Integrity standard, Meta may restrict or disable accounts and ad accounts owned by the same person as a disabled account, or "otherwise used to evade our enforcement actions or review processes."
• Google Ads. The circumventing systems policy prohibits "creating new accounts to re-enter the system" after a suspension and using multiple accounts to get around its policies. Google's advice to advertisers is to avoid "creating a lot of accounts in a short period of time" and to connect each account to a real business. Violations mean suspension "upon detection and without prior warning."
• TikTok. The Community Guidelines allow more than one account, for example for fan content or creative expression, "but not to deceive others or break the rules." They add: "We strictly prohibit automation tools, scripts, or other tricks designed to bypass our systems." And if an account is restricted or banned, you "may not create or use another account to get around it."
• Amazon. A staff post in Amazon's Seller Forums says you "may only maintain one seller account for each region unless you have a legitimate business need" and that issues with one account may affect all linked accounts. The Seller Code of Conduct is the policy page to check before a second store gets its own account.

Agencies don't need a proxy for most platform access anyway. A client's Meta business portfolio can give an agency partner access with full control or partial access, and a Google Ads manager account gives one sign-in to every linked client account. Use proxies on accounts you're authorized to operate, and never to replace or disguise a restricted one.

How Proxies and Browser Profiles Fit Together

A site sees two halves of every profile. The profile holds the browser side: cookies, saved logins and a stored fingerprint (user agent, screen, fonts, canvas and WebGL values, timezone, language). The proxy holds the network side: the IP address, its country and city, and the ISP or carrier behind it. The two have to agree. A profile on a Saudi IP that reports a New York timezone and English as its only language won't show you what a visitor in Riyadh sees.

Most tools line them up for you. GoLogin's profile settings fill timezone and geolocation from the proxy's IP by default, and without a proxy, GoLogin notes, the IP visible to websites "will be your actual IP." Multilogin checks each proxy you add and reads the IP-dependent data from it (Multilogin custom proxies).

Your own connection is fine for plenty of work, including an agency using partner access from its office. You need a proxy when:

• You're checking a GEO: the lander, offer, currency or consent banner a visitor in that country sees.
• A team shares a login: a static IP gives the profile the same location no matter which teammate opens it, from wherever they work. Check the tool's terms first; some ban shared logins.
• A client allowlists IPs: some tools only accept logins from approved addresses, so the profile needs a fixed one.
• You're testing your own product: sign-up or checkout flows from several countries, with test accounts.

Bind one proxy to each profile that needs one and keep it there. A GEO profile needs its country every time, a team login needs the same IP every session, and a separate IP per client keeps each client's allowlist and login history easy to read.

Proxy Types Compared, With September 2026 Prices

Here's the thing: proxy sellers write much of the proxy advice you'll find, so this guide uses their pages only for facts they own, like prices, session limits and formats. The prices below come from Decodo's pricing pages (Decodo was called Smartproxy until April 2025), as of September 2026, before VAT.

Watch the units. Residential and mobile are billed per GB of traffic, while ISP and datacenter plans come per IP or per GB. Compare at the volume and billing period you'll actually use, not the lowest price in a headline.

Datacenter Proxies

Datacenter IPs belong to hosting companies. They're fast and cheap, and Decodo's own datacenter pricing page says they share subnets, which makes them easier to block than residential IPs, so they're a weak stand-in for a real visitor in a GEO check. They fit uptime and redirect checks and work on your own sites. For an IP allowlist, use a dedicated datacenter IP: a shared one would let other customers through the allowlist too.

Residential Proxies: Rotating vs Sticky

Residential IPs come from people's devices that joined a provider's peer-to-peer network. Decodo and Bright Data both describe theirs as opt-in; pick a provider that documents its sourcing.

Rotating sessions give you a new IP on every request or connection, which suits one-off page checks. Sticky sessions keep one IP for a set time, and Decodo's session docs call them "great for logins or multi-step tasks." Its sticky IPs last 1, 10, 30 or 60 minutes, or a custom time up to 24 hours. The catch: a session ends early if the IP stops responding or sits idle for 60 seconds, and you get a new IP. For a login that stays open all day, look at ISP proxies instead.

ISP (Static Residential) Proxies

ISP proxies are IPs registered to internet service providers but hosted on data center servers, and each one stays yours for the length of the subscription (Decodo static residential). That makes them the steady option for a profile a team logs in to every day, and for any client that allowlists your IP. The trade-off is coverage. As of September 2026, Decodo's ISP locations are in the Americas, Europe and Asia-Pacific, with none in the Gulf, so a Saudi or UAE profile points you to a residential or mobile pool, or to another provider's ISP list.

Mobile Proxies

Mobile proxies route through 3G, 4G and 5G carrier connections. They earn their price when the carrier matters: a mobile-only lander, an offer targeted at one carrier's subscribers, or a flow that changes on mobile networks. Decodo lets you target mobile IPs by carrier ASN as well as city. For plain logins they add cost without adding much, since a static ISP IP is steadier. At list price, Decodo's mobile traffic costs twice its residential rate. The 50% discount on its mobile pricing page as of September 2026 makes the per-GB rates equal, so check which price applies when you buy.

Picking a Proxy by Job

The real question isn't which proxy type is best. It's what the profile is for.

• GEO checks of landers and offers. Residential in the target country, city-targeted when the offer differs by city. Rotating is fine for a quick look; use a sticky session for anything multi-step, like a form or checkout. Set the profile's language to the market too, since some sites pick the language from the browser rather than the IP. The profile side of GEO QA is covered in antidetect browsers for affiliate marketing.
• Carrier-dependent checks. Mobile, targeted by carrier.
• A shared team login to a client tool. One static ISP IP per client, in the country your team works from. The login history then shows where the work actually happens, and the client has one IP to approve.
• IP-allowlisted dashboards. A static IP: ISP, or a dedicated datacenter IP if the site doesn't care about IP type.
• QA of your own product. Residential or ISP per test country, sticky sessions, test accounts only.
• Public page checks such as uptime, redirects and ad destinations. Datacenter or rotating residential, within the target site's terms.

Setting Up a Proxy in Your Anti-Detect Browser

The fields are much the same in Multilogin, GoLogin, AdsPower, Dolphin Anty and similar tools; the menus differ.

Step 1: Map Every Profile to Its Proxy

Before touching the browser, start a sheet with one row per profile: client, account, platform, profile name, owner, proxy type, host, port, session setting or static IP, and country. Keep proxy passwords in your password manager, not the sheet. The map stops two profiles from sharing a sticky session by accident, and it gives you a recovery path when a proxy dies or someone leaves.

Step 2: Set the Session

Providers set session behavior in the username or the port. Decodo's user:pass docs show the pattern for residential proxies: rotating sessions use port 7000 on gate.decodo.com, while sticky sessions are kept apart by port (10001, 10002 and so on), with the country and session length in the username:

Host:     gate.decodo.com
Port:     10001 (next profile: 10002)
Username: user-USERNAME-country-us-sessionduration-60
Password: your proxy password

sessionduration takes any whole number of minutes from 1 to 1440 (custom sticky sessions). Other providers use their own parameter names and limits; IPRoyal's residential proxy pricing page, for example, advertises sticky sessions of up to 7 days. ISP proxies skip this step, since the IP is fixed.

Step 3: Add the Proxy to the Profile

Open the profile's proxy settings and fill in four things:

1. Protocol. HTTP, HTTPS or SOCKS5. Decodo supports HTTP(S) and SOCKS5 on all four proxy types, and Multilogin accepts all three. For browsing, any of them works, as long as it matches what your provider set up for that endpoint.
2. Host and port. From the provider dashboard. Multilogin takes host, port and credentials as IP:port:login:password in one line.
3. Authentication. Username and password, or an allowlisted IP. IP authentication only works if the provider has approved the address you connect from, so for a team spread across locations, username and password is simpler.
4. Location settings. Let the profile take its timezone and geolocation from the proxy IP, then set its language to the market.

Then run the proxy check (Multilogin runs it automatically). Don't log in to anything until it passes and the IP, country and ISP are the ones you expect.

Step 4: Check for Leaks

Open a leak-test page inside the profile before the first login, and again whenever the proxy changes:

• IP and location. The IP, country, city and ISP should match the proxy.
• WebRTC. Browsers use WebRTC for calls and live features, and it can expose a different IP from the one the page loaded through. BrowserLeaks' WebRTC test compares the two and flags a local IP leak.
• DNS. A misconfigured proxy setup can send DNS lookups straight to your ISP's servers. BrowserLeaks' DNS leak test shows which servers resolve your lookups.
• Timezone and language. They should match the proxy's country, or the market you're testing.

If anything shows your own connection, fix the proxy before touching an account.

Step 5: Keep Each Binding Stable

• One account per profile, and one proxy per profile.
• Don't swap a live profile's proxy type or country mid-project. Its timezone, geolocation and any client allowlist depend on it; if you must change it, run the checks again.
• Re-test after the provider replaces an IP or you renew a plan.
• When a client leaves, delete their profiles and release or reassign their static IPs. When a teammate leaves, remove their access and change any proxy credentials they could see.

Common Setup Mistakes

• Logging in before the proxy check passes. The first login happens on your own connection, which defeats the point of a GEO or allowlisted profile.
• Rotating IPs under a logged-in session. Rotation suits one-off page checks. For anything logged in, use a sticky session or a static IP.
• A timezone or language that doesn't match the proxy. Your GEO check then shows a version real visitors never see.
• Skipping the WebRTC and DNS tests. They take a minute and catch leaks the proxy check doesn't.
• Comparing prices across different units. Per GB against per IP, pay as you go against monthly, and discounted rates against list prices.
• Treating a proxy as permission. If a platform restricted an account, a new IP doesn't change that. The route back is the platform's appeal process.

Frequently Asked Questions

Final Thoughts

Anti-detect browser proxy setup is simpler than the vendor guides make it look. Match the proxy type to the job, bind one proxy to each profile that needs one, check for leaks before the first login, and compare prices on the same unit and billing period. And keep the platform rules in view: a proxy changes the IP a site sees, not what the platform allows.

← Back to the blog