# Proxies in anti-detect browsers: one profile, one country, one sticky session

Anti-detect browsers isolate fingerprints per profile; the proxy is what isolates the network identity. The rule that makes both work together: one profile, one sticky session, one consistent country.


## What the browser needs from you

Every anti-detect browser has a proxy form per profile with the same fields: type (HTTP or SOCKS5), host, port, username, password. Fill them with the ProxShift gateway and a sticky username, or with a dedicated ISP address for accounts that must never change IP.

| Field | Residential sticky session | Dedicated ISP address |
| --- | --- | --- |
| Type | HTTP (or SOCKS5) | HTTP (or SOCKS5) |
| Host | res.proxshift.com | the IP from your list |
| Port | 9000 (SOCKS5: 9001) | 8000 (SOCKS5: 8001) |
| Username | USER-cc-us-state-ny-sid-profile17-ttl-24h | from your list |
| Password | PASS | from your list |


## One profile, one session id

Give each profile its own `-sid-` value and never reuse it elsewhere. The profile then lands on the same household for the whole lifetime (up to 24 hours on ProxShift), and a new day brings a new exit in the same city, which is how a real user on a consumer ISP behaves. If the profile must keep the exact same address for weeks, it needs an [ISP proxy](https://proxshift.com/isp-proxies), not a session.


## Align the profile with the exit

- Time zone and language of the profile = country and city of the exit.
- Geolocation permission, if enabled, near the exit's city.
- Keep WebRTC in the "replace with proxy IP" or "disabled" mode the browser offers.
- Test the profile's IP inside the browser before touching the account.


## Which network for accounts

| Situation | Network | Why |
| --- | --- | --- |
| Many low-value accounts, daily activity | Residential sticky sessions | Cheap per account, natural daily IP change |
| Valuable accounts that must not change IP | ISP proxy, one per profile | Static, residential-registered, unlimited traffic |
| Platforms that challenge residential-grade IPs | Dedicated mobile device | Carrier IP, rotation on your command |
| Bulk checks without logins | Residential rotating | Breadth over consistency |


## Import lists at scale

Most anti-detect browsers import proxies as `host:port:user:pass` lines. Generate one line per profile with a distinct session id, or download your ISP list from the dashboard or `GET /v1/proxies?format=txt`, then map one line to one profile.

```text
res.proxshift.com:9000:USER-cc-us-sid-p001-ttl-24h:PASS
res.proxshift.com:9000:USER-cc-us-sid-p002-ttl-24h:PASS
res.proxshift.com:9000:USER-cc-gb-sid-p003-ttl-24h:PASS
```


## Questions

**HTTP or SOCKS5 in the profile?**

Either works. HTTP is the simplest and supports credentials everywhere; SOCKS5 is useful when the browser offers remote DNS through it. Never mix: pick one per profile.

**The proxy check in the browser fails but cURL works.**

Most often a stray space in a field or the wrong port for the type chosen (9001 is SOCKS5 only). Copy the four fields again from a working cURL line.

Source: https://proxshift.com/guides/anti-detect-browsers-proxy