Moving from another antidetect browser: profiles, proxies and cookies
Switching tools is the part everyone dreads: a hundred profiles, each with a proxy, a login and a note someone wrote two years ago. Retyping them is not an option. This guide shows how to bring them over from the export files your current antidetect browser already gives you — no account linking, no passwords shared with us.
What moves, and what deliberately doesn't
Moves: profile names, notes, tags, groups, statuses, the operating system, proxies (with their logins), the account's platform, username, password and 2FA secret, and cookies — so you stay logged in.
Doesn't move: the fingerprint. Every imported profile gets a new, consistent fingerprint from this app. That is on purpose. A fingerprint describes the browser underneath it; one copied from another engine no longer matches the browser it now runs on, and that mismatch is exactly what fingerprint checkers flag. A fresh fingerprint that fits the engine is the safer choice.
Step 1: export from your current tool
Most antidetect browsers can export profiles in one of these forms. All of them work:
- A spreadsheet (Excel or CSV) with one profile per row.
- A JSON list of profiles, as their API or "export" button returns it.
- A text file with one profile per block:
key=valuelines, blocks separated by a line of*****.
If the export is a ZIP file, unpack it first and load the file inside. Cookie exports in JSON, Netscape cookies.txt or plain name=value form are understood too.
Step 2: load it
In the app, open Profiles → Bulk import and choose the file (or paste its contents). Column names are flexible: name, remark or notes; proxy, or separate proxy type, host, port, login and password columns; 2fa or fakey; cookies. Rows that are instructions in a template ("Required", "Optional") are skipped by themselves.
Before anything is created you see a preview: how many profiles are ready, which rows can't be imported and why (a line number and a reason, such as "SOCKS4 isn't supported" or "not a proxy address"), and the columns that were recognised. Fix the file and load it again, or import what's ready and deal with the rest later.
Step 3: check the result
- Proxies that didn't exist yet are saved once and shared by the profiles that use them. Open Proxies → Check all to see which ones still work.
- Groups and statuses are created with the names from the file.
- Passwords and 2FA secrets are stored encrypted on this computer only, never uploaded.
- Cookies are imported into each profile; open a few profiles to confirm you're still logged in.
Then run the leak check (profile menu → Leak check) on one profile per proxy provider. It confirms that sites see only the proxy — not your own IP through WebRTC, DNS or forwarding headers.
Moving a team, not just profiles
If your team moves with you, invite them first (Team → Members), then import into the shared workspace. Groups become the unit of access: give a teammate open access to the Client A group, and they see exactly those profiles. Cloud sync is end-to-end encrypted, so each teammate opens a profile already logged in on their own computer.
A short checklist
- Export profiles (and cookies, if your tool keeps them separately).
- Profiles → Bulk import, read the preview, fix what it reports.
- Proxies → Check all; replace the dead ones.
- Open a few profiles: logged in? Run the leak check.
- Invite the team and give access per group.
Only import accounts you own or are allowed to manage. Our Acceptable Use Policy has the details.