Using proxies in multi-profile browser tools

Most browser-profile tools that isolate fingerprints per profile (separate cookies, canvas/WebGL noise, timezone, and so on) configure their proxy the same way: a per-profile form with host, port, username and password fields, or an equivalent proxy URL field. OneForProxy works with any of them — there is nothing product-specific to install.

The four fields

Every credential from Proxies maps to the same four values:

If the tool takes a single proxy URL instead of separate fields, the equivalent is:

http://ofp_0123abcd:PASSWORD@proxy.oneforproxy.com:8080

or, for SOCKS5:

socks5://ofp_0123abcd:PASSWORD@proxy.oneforproxy.com:1080

One profile, one sticky session

The point of a multi-profile tool is that each profile looks like a consistent, separate visitor over time — which means each profile should also keep a consistent exit IP rather than rotating on every request. Give each profile its own sticky session id in the username:

ofp_0123abcd-session-profile01-life-60
ofp_0123abcd-session-profile02-life-60

-life-<minutes> (1–1440) controls how long that IP is pinned; renew it by reusing the same session id before it expires, or let it lapse and get a fresh IP on the next connection. Different session ids run in parallel and never share an IP — see Sticky sessions for the full behavior.

Matching geography to the profile

If a profile is meant to represent a visitor in a specific country (or state/city), add that to the username too, before the session suffix:

ofp_0123abcd-country-us-state-california-session-profile01-life-60

Key order and allowed characters are documented in Targeting and the Docs.

Verifying a profile's IP

Before running real traffic through a profile, open https://api.ipify.org inside it and confirm the printed IP matches the country you targeted and stays the same across a reload — that's proof the sticky session is holding. A different IP on every reload usually means the -session- suffix is missing, or was typed differently between requests; session ids must match exactly, including case.

If the profile can't connect

Check the credential is active under Proxies, and that the username has no typos in its -key-value suffixes — an unrecognized key or malformed value returns 407 before the connection is even attempted. The full error table is in Errors.