Back up profiles to a file and import them again
Export profile settings and their proxies to one JSON file, and import that file on any computer running LoginDeck.
On this page
An export is a plain JSON file holding your profiles' settings and the saved proxies they use. It's the way to keep an off-app backup, move profiles to a computer that isn't signed in to your account, or hand a set of profiles to someone else.
An export does not contain logins
Cookies, sessions, open tabs and history are not in the file. An imported profile opens signed out. To move logins too, export the cookies as well (Import and export cookies), or let sync do it on a paid plan (Cookie and session sync).
📤 Export profiles#
One profile: on its row, click ⋯ → Export.
Several profiles: tick the rows, then click Export in the bar at the bottom.
Choose where to save. The file is named antiorbit-profiles-2026-09-27.json by default. You'll see "Exported 24 to C:\Users\…".
The file holds proxy passwords in clear text
It also holds each profile's 2FA secret and any passwords you saved under Linked accounts. Treat the file like a password list: keep it off shared drives, and delete old copies.
Profiles locked by your plan are left out, and the message says how many ("3 locked profiles were left out").
What's in the file#
- Every profile's settings: name, engine, browser version, operating system, language, fingerprint, folder, tags, notes, masking settings, extensions assignments, 2FA secret and linked accounts.
- The saved proxies those profiles point at, so they still work after an import.
📥 Import the file again#
- Click the small arrow on the right of the New Profile button (More ways to add profiles).
- Click Import profiles.
- Pick your
.jsonfile. You can select several files at once.
You'll see "Imported 24 profiles, 3 proxies". The proxies go into your proxy list first (ones you already have are skipped), then the profiles arrive with their folders and tags.
Imported profiles keep their fingerprints, so they're the same machines they were before.
Importing never overwrites
If a profile in the file already exists here, the import adds a second copy named "{name} (imported)" instead of replacing what you have. Your live profile is never touched.
The whole file is checked against your plan's profile limit before anything is written. If it doesn't fit, the "… is full" dialog opens and nothing is imported.
🔁 Moving profiles to another computer#
You have two ways:
| Export file | Sync | |
|---|---|---|
| Needs the same account | No | Yes |
| Moves settings and fingerprints | Yes | Yes |
| Moves logged-in cookies | No | Yes, on paid plans |
| Works offline | Yes | No |
If both computers are your own, sync is easier: sign in on the second computer and the profiles arrive. See Use LoginDeck on another computer.
❓ Common questions#
It said "Imported 0 profiles". What happened?
The file wasn't recognised. Check it's the .json LoginDeck wrote, or a supported export from GoLogin, AdsPower or Dolphin. Files from other tools aren't read. See Move your profiles from GoLogin, AdsPower, Dolphin and others.
Why is the file called "antiorbit-profiles"?
That's the old name of the app, still in the export file name. It's the right file, and LoginDeck recognises it on import.
Can I edit the file by hand?
You can, but nothing checks your edits, so a mistake means a profile that won't open. If you want to bulk-create profiles from a spreadsheet, see Move your profiles from another browser.
Do the exported profiles' last-opened times come across?
No. Imported profiles show as never launched.
Can I export a locked profile?
No. Move up a plan first, or delete profiles until it unlocks. See "Free is full", locked profiles and other plan messages.
ℹ️ Good to know#
- Import profiles is the only import in the app, and it takes LoginDeck files and competitor files, in any mix.
- Extensions themselves aren't in the file. Add them to the library on the other computer and the assignments line up again. See Add extensions to profiles.