# How to export profiles from Multilogin

> When you export profiles from Multilogin you get encrypted .zip files only Multilogin can open. Cookies export as plain JSON, and that part travels.

Source: https://mosaicbrowser.com/guides/export-profiles-from-multilogin

## How to export profiles from Multilogin

In Multilogin, open Profiles, choose Browser, select up to 10 profiles and click Export profile; the result is an encrypted .zip only Multilogin can import. To take accounts to another browser, export each profile's cookies as JSON from the right-click menu under Cookies.

![What leaves Multilogin, and what stays behind, beside a screenshot: bulk-importing proxies into Mosaic: every line read, new and duplicate ones told apart](https://mosaicbrowser.com/covers/export-profiles-from-multilogin.webp)

You can export profiles from Multilogin in full, but for Multilogin's eyes only. Its profile export is an encrypted archive that opens in another Multilogin workspace and nowhere else. The cookie export is ordinary JSON, and when you are leaving Multilogin it is the export that matters.

## Export profiles from Multilogin

Multilogin's help article on [exporting browser profiles](https://multilogin.com/help/en_US/browser-profile-tools/how-to-export-profiles) (updated 18 September 2026, read 2 November 2026) gives these steps:

1. Open the **Profiles** tab in the top menu.
2. Pick **Browser** from the selector on the left.
3. Right-click a profile, or tick several and use the top menu.
4. Click **Export profile** and confirm with **Export**.

The limits are in the same article. Only the account owner can export, the feature is listed on Pro 50 and higher, and you can export up to 10 profiles at a time. Each profile becomes an encrypted `.zip` in an `mlx/exports` folder in your home directory, named after its export ID. Do not rename it, and do not unzip it: Multilogin will refuse a renamed file. The archive carries the fingerprint, its settings, browser data such as cookies, extensions and saved logins, and cached files.

On using the file anywhere else, Multilogin's FAQ answers in one line: exported files "are encrypted and can only be imported back into Multilogin." That makes this export a move between Multilogin workspaces or a backup, which is useful in its own right. Keep your originals until the import on the other side has worked, as Multilogin advises.

Mosaic is a desktop app

Email yourself the link and open it on your computer.

[How it works: Provider minting](https://mosaicbrowser.com/features/proxy-providers)

## Export cookies from Multilogin as JSON

The [cookie export](https://multilogin.com/help/en_US/cookies/cookie-export) is listed on all plans, for owners, managers and operators:

1. Go to **Profiles** and select **Browser**.
2. Stop any profile you want to export from.
3. Tick the profiles, right-click and choose **Cookies › Export cookies**.
4. Click **Export**.

You get one JSON file per profile. Multilogin's own warning is worth repeating: a cookie file can hold live sign-ins, so keep it somewhere private.

## Export profile settings with the Multilogin API

The settings, meaning names, notes and fingerprint options, come out through the Multilogin X API ([Postman documentation](https://documenter.getpostman.com/view/28533318/2s946h9Cv9)). `POST https://api.multilogin.com/profile/search` pages through your profiles, and `POST /profile/metas` with `{"ids": [...]}` returns their metadata inside `{"status": ..., "data": {"profiles": [...]}}`. Each profile there has a `name`, `notes`, `browser_type`, `os_type` and a `parameters` object holding the fingerprint, flags and storage settings.

We fed that documented reply to Mosaic's importer on 2 November 2026, and this is the honest part of the page. Saved as it comes, the envelope is read as a file with no profiles in it. With `jq '.data.profiles'` applied it is read as an unrecognised format, and only the names and notes come across. Mosaic's Multilogin signature looks for fields named `browserType` with `navigator` or `network`, and Multilogin X's API spells the browser `browser_type` and keeps the rest under `parameters`. That is a gap in our importer, and until it is closed, plan on names and notes only.

## Move Multilogin accounts into Mosaic

What carries an account across is its cookies and its proxy. The rest is better drawn fresh for the computer it will run on. GoLogin is the opposite case, where Mosaic reads the API record as it comes ([exporting from GoLogin](https://mosaicbrowser.com/guides/export-profiles-from-gologin) shows the difference).

1. In Mosaic, put your proxies in first: **Proxies › Bulk import** reads lists in the common formats, one per line or as a table with a header row. If you buy from a proxy seller, you can paste its gateway line as a [provider](https://mosaicbrowser.com/features/proxy-providers) instead, and every profile mints its own session.
2. Make the profiles. Either import the `jq`-filtered metas file through **Import** on the profiles screen, which brings the names and notes, or create them in a batch.
3. Give each profile its proxy, then open its editor at **Cookies**, paste the profile's JSON file into **Paste an export**, press **Load cookies** and save.

![Mosaic's Proxies bulk import: eight pasted lines in mixed formats previewed as New 6, Already there 1, Unread 1, with Import 6](https://mosaicbrowser.com/shots/proxy-import.png)
*Proxies › Bulk import reads mixed formats and says what it skipped*

A profile made this way has a fingerprint drawn from [real hardware records](https://mosaicbrowser.com/features/real-fingerprints) for the computer it runs on: macOS on a Mac. Multilogin's fingerprint options would not have helped here anyway, since they describe Multilogin's engines, Mimic and Stealthfox, and not the machine Mosaic runs on. Saved passwords stay inside Multilogin's encrypted archive, so re-enter them under **Credentials** in each profile.

Before you cancel Multilogin, open a handful of moved profiles and check that the sites you care about still know you. If the reason you are leaving is price, Mosaic Pro does not charge per profile; it is on the [pricing page](https://mosaicbrowser.com/pricing).

## Sources

1. [Multilogin Help Center: How to export browser profiles](https://multilogin.com/help/en_US/browser-profile-tools/how-to-export-profiles), read November 2, 2026
2. [Multilogin Help Center: Cookie export](https://multilogin.com/help/en_US/cookies/cookie-export), read November 2, 2026
3. [Multilogin X API documentation (Postman)](https://documenter.getpostman.com/view/28533318/2s946h9Cv9), read November 2, 2026

## Questions

### Can I open a Multilogin profile export outside Multilogin?

No. Multilogin's help centre says exported browser profile files are encrypted and can only be imported back into Multilogin. The export moves profiles between Multilogin workspaces and devices.

### Which Multilogin plans can export profiles?

Multilogin's help article, updated 18 September 2026, lists profile export on Pro 50 and higher, for the account owner only, up to 10 profiles at a time. Cookie export is listed on all plans.

### Can I rename an exported Multilogin .zip file?

No. Multilogin says exported files need their original names, which carry the export ID, and a renamed file will not import.

### What does Mosaic read from a Multilogin API reply?

Measured on 2 November 2026: the profile list Multilogin X's API returns is read as an unrecognised format, so the names and notes come across and nothing else. Cookies exported as JSON load into Mosaic profiles in full.

## Related

[Multilogin alternatives: six anti-detect browsers compared](https://mosaicbrowser.com/compare/multilogin-alternatives): Six Multilogin alternatives with prices checked on their own pages: Mosaic, GoLogin, AdsPower, Dolphin{anty}, Octo Browser and Kameleo, and who each one suits.

[Mosaic vs Multilogin: local engine or cloud platform](https://mosaicbrowser.com/compare/mosaic-vs-multilogin): Mosaic keeps every profile on your computer at one flat price. Multilogin syncs to its cloud, prices by profile count and adds cloud phones and teams.

[How to export profiles from GoLogin](https://mosaicbrowser.com/guides/export-profiles-from-gologin): To export profiles from GoLogin, its button writes a CSV of settings without cookies. Its API returns each profile as JSON, and cookies export per profile.

[How to export profiles from AdsPower](https://mosaicbrowser.com/guides/export-profiles-from-adspower): To export profiles from AdsPower, use the toolbar's Excel or Text export, or the Local API for JSON with the proxy attached. Which to use, and how to move them.

[Provider accounts: one gateway line, one exit per profile](https://mosaicbrowser.com/features/proxy-providers): Paste your proxy seller's gateway line once and Mosaic mints a separate session for every profile, so each one browses from its own exit address.

[How to manage multiple accounts without getting them linked](https://mosaicbrowser.com/guides/how-to-manage-multiple-accounts-without-getting-linked): Accounts get linked by shared cookies, IPs, fingerprints and habits. Give each its own profile, exit and history, then test it before you trust it.



[How do websites detect multiple accounts?](https://mosaicbrowser.com/guides/how-do-websites-detect-multiple-accounts): Websites detect multiple accounts by what two accounts share: cookies, the IP address, the browser fingerprint, payment and phone details, and habits.

## Run this guide on your own accounts

Every Mosaic profile is a fingerprint, a proxy exit and a cookie jar that agree with each other, kept on your computer. Free holds 3 profiles. Pro is $49 a month for any number.

Mosaic is a desktop app

Email yourself the link and open it on your computer.
