Profiles & fingerprints
A profile is a completely separate browser environment: its own cookies, local storage, cache, extensions, proxy and device fingerprint.
Templates, not random values
Sites compare many signals with each other: the operating system in the user agent, the installed fonts, the GPU reported by WebGL, the screen size, the number of CPU cores, client hints and more. A random mix (say, a macOS user agent with Windows fonts) is easy to spot.
Profiles are therefore generated from device templates — real-world combinations where every value agrees:
| Signal | Example (Windows 11 · Chrome template) |
|---|---|
| User agent & client hints | Chrome on Windows NT 10.0, platform "Windows" |
| Screen | Common resolutions for that class of device |
| Hardware | 4–16 cores, 8–32 GB memory |
| GPU | Vendor/renderer pairs seen on Windows |
| Fonts | The default Windows font set |
Settings you can change
- Proxy: none, HTTP, HTTPS or SOCKS5.
- Geo auto-match: timezone, locale, language and geolocation from the proxy IP (toggle, with manual override).
- WebRTC: disabled, replaced with the proxy IP, or real.
- Screen, CPU cores, memory within the template's realistic range.
- Canvas, WebGL and audio noise on/off.
- Media devices and Do Not Track.
- Start URLs and extensions to load.
Status
| Status | Meaning |
|---|---|
| Running | Open on this device |
| Stopped | Ready to start |
| Locked | Over your plan limit (read-only) or open on another device |
Profiles over your plan's limit are locked, never deleted. Upgrading unlocks them.