Home → Learn → Multiple browser profiles
Running multiple browser profiles
Managing several accounts on one platform is ordinary work — agencies with many clients, sellers with several storefronts, teams testing as many users. The hard part is that browsers were built to represent one person, and everything they remember quietly ties those accounts together.
On this page
What actually links accounts
Correlation happens on more channels than most people expect. Roughly in order of how often it catches people out:
| Channel | What it ties together |
|---|---|
| Cookies & local storage | The obvious one, and the only one most people address |
| Device fingerprint | Canvas, WebGL, fonts, audio, screen — identical across every tab of one browser |
| IP address | Shared address across accounts is a direct link |
| Timezone / locale | Mismatched against the IP, or identical across accounts that claim different countries |
| Login patterns | Same times, same sequence, same device rhythm |
| Recovery details | Shared phone or email joins accounts at the account layer, whatever the browser does |
Isolation only works if it covers all of them. Solving cookies while leaving one fingerprint and one IP in place is not partial protection — the accounts are still linked.
What is not isolation
Incognito windows
Incognito forgets history and cookies when it closes. It does not change your fingerprint or your IP. Two incognito windows have the same canvas hash, the same GPU, the same fonts and the same address as each other and as your normal browser.
Chrome profiles
Separate Chrome profiles do separate cookies and storage properly, which is genuinely useful. But they share the installation, the fonts, the GPU, the screen and the connection — so the device fingerprint is identical across all of them.
A VPN on its own
Changing IP without changing the fingerprint gives you accounts that share one distinctive device across several addresses. That is a pattern in itself, and often a worse one.
The useful test
Open your setup's "separate" environments and compare their fingerprints. If the canvas hash matches, they are one identity wearing different hats. Run the fingerprint test in each and see.
What a real profile contains
Proper isolation means each profile owns its own copy of everything a site can read:
- Storage — cookies, localStorage, IndexedDB, cache, service workers, on separate disk
- Fingerprint — its own canvas, WebGL, audio, fonts, screen, hardware values
- Network — its own proxy, so the exit IP differs
- Locale — timezone and language consistent with that proxy
And critically, those values must agree with each other. A profile with a Berlin proxy, a New York timezone and a macOS user agent over Windows graphics is more conspicuous than no disguise at all. Browser fingerprinting covers why.
One proxy per profile
The rule is one profile, one address, held steady. Rotating a profile's IP every session looks like an account that teleports; sharing one address across fifty profiles rebuilds the link you were trying to break.
| Type | Best for | Trade-off |
|---|---|---|
| Residential | Consumer platforms that scrutinise IP reputation | Costs more; speed varies |
| Mobile | Mobile-first platforms | Most expensive; shared carrier addresses |
| Datacenter | Bulk work where IP reputation matters less | Easy to identify as datacenter |
| ISP / static residential | Long-lived accounts needing a stable address | Limited pools |
Whatever you choose, set the profile's timezone and language to match where that proxy exits. That one habit removes the most common mismatch there is.
Operating hygiene
- Never sign into two accounts in one profile, even briefly — the platform links them at the account layer and no browser setting undoes it.
- Keep recovery details separate. A shared phone number joins accounts regardless of isolation.
- Warm new accounts up. An account that does nothing but the one high-value action is a pattern.
- Don't paste between profiles carelessly. Tracking parameters in a copied URL carry context across.
- Keep the profile alive. Deleting and recreating loses the history that makes an account look established.
Keeping order at scale
Past about twenty profiles the problem stops being technical and becomes organisational: knowing which profile is which, which proxy it holds, when it was last used. What helps:
- Naming that encodes purpose — platform, client, account number, in a fixed order
- Groups per client or platform, so bulk actions apply to the right set
- Bulk operations — assigning a proxy to forty profiles individually is where mistakes happen
- Session import/export, so an account can be handed over or backed up without sharing a password
Working across machines
Profiles that live on one laptop are one disk failure from gone, and impossible to hand to a colleague. Syncing the definitions — name, group, proxy binding, fingerprint seed — lets the same set open on another machine. Note that a logged-in session is different from a profile definition: moving live sessions means exporting cookies deliberately, not just signing in elsewhere.
Profiles that are actually separate
Each Parallel profile gets its own storage, its own coherent fingerprint and its own proxy — with groups, bulk actions and cloud sync once there are more than a handful. Three free.
Download for Windows