Home → Learn

Learn

How browsers identify visitors, how to keep accounts genuinely separate, and how to stop doing the repetitive parts by hand.

The one idea underneath all of it

Almost everything on this page follows from a single point, and the guides make more sense in its light: detection is not looking for a fingerprint it recognises — it is looking for one that disagrees with itself.

That inverts the obvious strategy. Randomising values feels like hiding, and it is the fastest way to get flagged, because random values contradict each other: a Windows user agent reporting a Mac GPU, a device claiming eight CPU cores and a phone screen, a browser set to Portuguese connecting from a German datacenter. Real machines are boringly consistent. A profile is convincing when it is boring in the same way.

So "unique fingerprint" is the wrong goal and "coherent fingerprint" is the right one — which is why proxies, timezones and locales are part of the same subject rather than a separate one.

Where to start

If you are new to this, read in this order. Each one assumes the one before it.

1. Antidetect vs VPN vs incognito — start here if you are not yet sure the category is what you need.
2. Browser fingerprinting explained — what the signals actually are, and which ones matter.
3. Behavioral bot detection — the other half of the same problem, and the one most setups never touch.
4. Headless browser detection — why a browser with no window is served less of the internet than one with a window.
5. Language and locale mismatch — the same kind of contradiction, produced by any page that prints a date.
6. Proxy timezone mismatch — the single contradiction that is cheapest for a site to check.
7. Fingerprint drift — the signal that costs established accounts is not an unusual device, it is a changed one.
8. How accounts get linked — the signals outside the browser, and where this kind of software stops helping.
9. Why you keep getting logged out — what actually holds a session, and why copying a profile folder loses it.
10. WebRTC leaks — the leak that survives a working proxy, and why the usual fix makes you more identifiable.
11. Running multiple browser profiles — what links accounts together, and what isolation does and does not cover.
12. Residential vs datacenter proxies — the address half of the same problem.
13. Browser automation, then Puppeteer and Playwright — only once the profiles themselves are right.

Seeing it applied is often faster than reading about it: the use cases work through agencies, e-commerce and QA testing.

Reference

The guides above cover the concepts. For the product itself — every profile field, every automation command, the local API — see the documentation.