Move from Multilogin
Cookies as files, proxies as a list, the fingerprint from our catalog. Nothing is deleted in Multilogin: work in both until you are sure.
What moves from Multilogin today
- Cookies as JSON files (an array or an object with a cookies field) or Netscape cookies.txt
- Proxies as a list, one per line: host:port:user:pass, user:pass@host:port or socks5://…
- The fingerprint: a new one for every profile, from our catalog
How to move
-
Export cookies from Multilogin In Multilogin: Profiles → Browser, stop the profiles, tick them, right-click → Cookies → Export cookies. Each profile gets its own JSON file.
-
Add proxies as a list In «Proxies» → «Add your own», one per line.
-
Create the profiles We pick each profile's fingerprint from the catalog; choose its proxy when you create it.
-
Load cookies into the profiles «Import» → «Cookies into profiles»: paste the text or upload files named after the profiles.
Other sources
Every browser you can move from is on the move page. From Dolphin Anty profiles move automatically: move from Dolphin Anty.
An anti-detect browser removes the technical traces of the browser. It does not guarantee an account won’t be banned: platforms also look at behaviour, creatives and payments.
Questions about moving from Multilogin
Does the fingerprint move from Multilogin?
No. We pick each profile's fingerprint from our catalog. Cookies and proxies move from Multilogin.
Do I need to delete my profiles in Multilogin?
No. We don't touch anything in Multilogin: work in both browsers until you are sure.
What cookie format do you need?
Multilogin saves cookies as one JSON file per profile. We take JSON — an array of cookies or an object with a cookies field — and Netscape cookies.txt. Name the files after the profiles and the cookies land in the right ones.