Move your profiles from GoLogin, AdsPower, Dolphin and others
Export a file from your old antidetect browser and import it into LoginDeck. Names, proxies, cookies and folders come across.
On this page
You don't have to rebuild your deck by hand. Export your profiles from your current tool, then import that file into LoginDeck. Cookies come with them where the export includes them, so accounts arrive already signed in.
📤 Step 1: export from your old tool#
Use the old app's own export or backup button:
| Tool | What to export | File |
|---|---|---|
| GoLogin | "Export profiles" | .csv |
| AdsPower | The Export button on the profile list | .xlsx (or the same sheet saved as .csv) |
| Dolphin Anty | Profile export | .json |
| AdsPower local API | A dump from its local API | .json |
| LoginDeck | Export from a row's ⋯ menu or the selection dock | .json |
Export cookies as part of the file if the tool offers it. That's what carries your logins.
Other vendors
Only the files above are read. Exports from Multilogin, Incogniton, Octo Browser, Kameleo, MoreLogin, Undetectable and VMLogin aren't supported. If your tool can write an AdsPower-style spreadsheet, see the tip at the end of this page.
📥 Step 2: import into LoginDeck#
- At the top of the sidebar, click the caret beside New Profile ("More ways to add profiles").
- Choose Import profiles.
- The file picker opens, titled Import from GoLogin / Dolphin / AdsPower. You can select several files at once, and you can mix a LoginDeck export with a competitor's file in the same pick.
- Click Open.
A toast reports what arrived, for example "Imported 24 profiles, 18 logged in" — and, from a LoginDeck export, how many saved proxies came with them.
Can't see your .xlsx file?
The picker starts on the Profile export filter, which only lists .csv and .json. Switch the file-type dropdown to All files and your AdsPower .xlsx appears.
✅ What comes across#
| Carried over | Notes |
|---|---|
| Profile name | A profile with no name becomes "Imported profile" or "AdsPower profile". |
| Notes | HTML formatting is stripped. |
| Operating system | Read from the source's OS or user-agent. An Android profile lands as Windows 11. |
| Language | From the source's language, locale or country code. |
| Timezone | A fixed timezone comes across as a manual one; otherwise the profile matches its proxy's exit. |
| Screen size | Kept when the file records it. |
| Proxy | Type, host, port, username and password. |
| Cookies | Inserted into each profile after it's created, so the account arrives signed in. |
| Folder | From AdsPower's group. |
| Tags | From Dolphin's tags. |
♻️ What is rebuilt, and why#
The source's user agent, graphics card, fonts and other fingerprint traits are not copied. LoginDeck generates a fresh machine for its own browser engine from the profile's operating system and language, keeping the screen size when it could read it.
That's deliberate. A fingerprint copied from another tool's browser would name a browser version LoginDeck isn't running, and traits that don't agree with each other are easier for a site to spot than a clean, consistent machine. Imported profiles always use the Chromium engine.
🍪 If the logins didn't come across#
- Your export had no cookies. Export cookies from the old tool, then import them per profile: row ⋯ → Import cookies…. LoginDeck reads Cookie-Editor and EditThisCookie JSON, GoLogin and AdsPower exports, Playwright storage state and Netscape
cookies.txt. See Import and export cookies. - The toast said "with cookies pending". The profile was created and the cookie file was read, but the cookies weren't written in. Import them again for those profiles from the row menu.
🧯 If nothing arrived#
A toast reading "Imported 0 profiles" means no file in your pick was recognised. Check:
- the file is one of the kinds in the table above;
- a CSV from AdsPower still has its
proxytypeandcookiecolumns — a trimmed sheet isn't recognised as AdsPower; - you didn't re-save a
.jsonexport as something else.
Still stuck? Email support@logindeck.com and say which tool and which export button you used. Don't attach the file itself — an export holds your proxy passwords and cookies.
Plan limits
An import is checked against your plan's profile limit before anything is written. If the file holds more profiles than your plan covers, a dialog says so and nothing is imported. See Plans and what each one includes.
ℹ️ Good to know#
- Nothing is overwritten. If an imported profile has the same internal id as one you already have, the newcomer is added with "(imported)" after its name.
- Saved proxies come first. From a LoginDeck export, proxies already in your library are skipped rather than duplicated.
- Browser version. Imported profiles keep the default engine version rather than jumping to the newest one. You can change it per profile: Chrome or Firefox, and which browser version.
- Bulk-create from a spreadsheet. LoginDeck reads the first worksheet of an
.xlsxwith AdsPower's column names —name,remark,group,ua,countrycode,proxytype,proxy,cookie— so you can build your own sheet to create many profiles with their proxies in one go.