Multilogin Proxy Setup: Step by Step

1. In Multilogin, select Create profile, or open an existing profile's settings.

2. Pick the browser core (Mimic, based on Chromium, or Stealthfox, based on Firefox) and the operating system the profile should show.
3. Open the Proxy section and switch from the built-in proxy to your own proxy.

4. Set the type to HTTP. Enter host gate.proxyfield.io, port 7000, your username (for example <login>-country-us-city-new_york) and your password. If Multilogin offers a field for a whole line, paste the line in the format it shows there.

5. Select Check proxy. Multilogin shows the exit IP and its location; it should not be your own IP.

6. Leave timezone, geolocation and WebRTC on the settings that follow the proxy, save the profile and start it. Visit https://api.ipify.org in the profile to confirm the IP.

A Multilogin profile looks most consistent when its IP, timezone and language all point to the same place, every time it opens. The location lives in the username, so each profile keeps the one you give it:

Targeting goes down to country, region (state) and city, with all 50 US states covered. Region, session and session time go in the same username: -region-<region>, -session-<id> and -ttl-<seconds> (30 to 129,600 seconds, 20 minutes by default), as in <login>-country-us-region-new_york-city-new_york-session-he9f2qga-ttl-600; every part after the login is optional. Residential is the default; add -mobile after the login for mobile IPs: <login>-mobile-country-us. After you change a profile's location, run Check proxy again so Multilogin recalculates the timezone and geolocation before the profile opens.

Each profile should look like one person on one connection. Pick the session type by how long the profile stays logged in:

• Sticky session (30 s to 36 h): the usual choice for Multilogin profiles. One sticky session per profile keeps one IP while you work. Region, session and session time go in the same username: -region-<region>, -session-<id> and -ttl-<seconds> (30 to 129,600 seconds, 20 minutes by default), as in <login>-country-us-region-new_york-city-new_york-session-he9f2qga-ttl-600; every part after the login is optional. Residential is the default; add -mobile after the login for mobile IPs: <login>-mobile-country-us.
• Rotating (a new IP on every request): only for profiles that read public pages, such as checking ads or prices in a region. A logged-in account on a rotating IP shows a new address on every page load.
• Static IP for days: a sticky session ends after 36 h at most. For an account that should sign in from the same address every day, use a dedicated ISP proxy: from $2.29 per IP per 30 days (static residential (ISP) proxies).

The number of proxies you need equals the number of profiles that run separate accounts. Fifty profiles, fifty sessions: they all draw on one ProxyField balance, so you pay for the gigabytes used, not for each proxy. How sticky and rotating sessions differ is explained in Sticky vs Rotating Proxy Sessions.

1. Generate one proxy line per profile in your ProxyField account with the configurator. Each line has the form host:port:username:password, as in gate.proxyfield.io:7000:<login>-country-us-city-new_york:<password>.
2. In Multilogin, create the profiles in bulk or import them from a file, with one proxy per profile, in a format Multilogin lists, such as host:port:username:password.
3. Run Check proxy on a few profiles before you start work.

One line per profile keeps the profiles apart. The common formats are explained in Proxy Format.

Multilogin X has an API that creates, updates and starts profiles, and the proxy is part of the profile. A profile created that way carries the same values as the form:

{
  "parameters": {
    "flags": { "proxy_masking": "custom" },
    "proxy": {
      "type": "http",
      "host": "gate.proxyfield.io",
      "port": 7000,
      "username": "<login>-country-us-city-new_york",
      "password": "<password>"
    }
  }
}

Field names follow Multilogin's API reference; check it for your version before you script against it. A started profile can be driven with Selenium, Playwright or Puppeteer, and its traffic keeps going through the profile's proxy.

Multilogin takes HTTP and SOCKS5 proxies, and ProxyField's gateway speaks HTTP, HTTPS and SOCKS5. Choose HTTP: it works with a username and password and covers everything the browser in a profile does. SOCKS5 works too, on port 7000 with the same username and password. SOCKS5 runs on the same gate.proxyfield.io:7000. SOCKS5 takes the same username and password. The difference is covered on SOCKS5 proxies.

You may use ProxyField to manage your own or your clients' social media and marketplace accounts, one IP per account. Creating fake accounts or fake engagement is not allowed. Comparing Multilogin with other antidetect browsers? See antidetect browsers compared, or the setups for AdsPower and GoLogin.

Gateway error messages: 407 Proxy Authentication Required for a wrong login or password, an IP not on the allowlist or a malformed location, 402 Payment Required when no traffic is left and 502 Bad Gateway when no exit could be connected; a restricted site gets no separate response, and a 403 comes from the site itself. Status codes are explained in proxy errors. To test a list of proxies outside Multilogin, use the proxy checker. Our 24/7 live chat helps with setup and integration.

A proxy gives a profile its own IP, location and reputation; Multilogin gives it its own fingerprint. Neither solves CAPTCHAs or overrides a platform's rules.

Start with the Easy Trial: 1 GB for $2.95, with no minimum purchase and no subscription. The traffic never expires and all purchases are final. See pricing per GB.