An antidetect browser is a Chromium or Firefox build with a profile manager on top. Each profile gets its own cookies and storage, and its own values for the traits sites read to recognise a device: user agent, screen size, timezone, language, fonts, and canvas and WebGL output. Open two profiles side by side and, to a website, they look like two different computers. AdsPower, GoLogin, Multilogin and Dolphin Anty are common examples.
Why the proxy matters as much as the fingerprint
The browser controls what the device looks like. It does not control the IP address, and the IP has to agree with the device story. A profile set to Berlin time and German language that connects from a Dallas IP is a mismatch a risk engine notices. The usual pattern is one proxy per profile, configured in the profile itself, with the timezone and language set to match the IP's location.
For logged-in accounts, a static IP is the safer fit: the account sees the same address at every login, the way it would from a home connection. A rotating exit on a logged-in profile looks like the account hopping between cities. The AdsPower and GoLogin guides show how to give each profile one static ISP IP.
Common confusion
- It does not hide your IP. That is the proxy's job. Without one, every profile shares your real address, and a WebRTC leak can expose it even with one, so check the browser's WebRTC setting.
- It is not a headless browser. Antidetect browsers are built for people working in many profiles, though many offer a local API for automation.
- It does not change the rules. Running several accounts is fine where the platform allows it; our allowed-use policy spells out the rest.