Logo
Inscription

Ouvrir le menu

Logo

Switch to Undetectable in an evening, not a week

Move profiles from Dolphin Anty, AdsPower, GoLogin, Multilogin, Octo, and regular Chrome or Firefox. Their cookies and real browser details come across too. One extension does it from inside any browser, including another antidetect's profile.

Any Chromium or Firefox
No source API needed
Local by default

Works even after your old subscription ends, as long as the profile still opens.

Move from almost anywhere

Dolphin Anty
AdsPower
GoLogin
Multilogin
Octo Browser
Incogniton
MoreLogin
Chrome
Firefox
Brave
Edge
Dolphin Anty
AdsPower
GoLogin
Multilogin
Octo Browser
Incogniton
MoreLogin
Chrome
Firefox
Brave
Edge
Edge
Brave
Firefox
Chrome
MoreLogin
Incogniton
Octo Browser
Multilogin
GoLogin
AdsPower
Dolphin Anty
Edge
Brave
Firefox
Chrome
MoreLogin
Incogniton
Octo Browser
Multilogin
GoLogin
AdsPower
Dolphin Anty

Don't see yours? The Converter runs inside any Chromium or Firefox browser, including another antidetect's profile.

Three ways to move in

Pick one, or combine them.

Undetectable Converter

Best for any browser, even a closed API

Install the extension in the browser you are leaving, even inside another antidetect's profile. Open a profile, click once, and it lands in your local Undetectable with its cookies and real browser details. It moves one profile at a time. No source API, no active subscription.

Manual import with Cookies Converter

Best for cookie files you already have

Already have cookie files? Create a profile in Profile Manager and add your cookies and proxy. The free Cookies Converter puts any cookie file into the right format first.

Local API and automation

Best for teams and anyone who scripts

The Local API creates a profile with cookies, proxy, folder, tags, and notes in one call. Bring the data from your old tool and script the import yourself.

How the Converter works

Token migrations break at the worst time: the subscription ended, the service changed its API, the account got blocked. The Converter does not rely on any of that. It reads the profile from inside the running browser, so it needs no source API and no active subscription. It reads the real User-Agent, resolution, and hardware the profile reports, not a value from a config file. It moves one profile at a time.

Old profile
Undetectable
1

Install the Converter in the browser you are leaving.

2

Open the profile you want to move.

3

Click the Converter icon, then Send to Undetectable.

4

The profile appears in Profile Manager with its cookies and browser details.

What the Converter captures

Cookies
User-Agent
Screen resolution
CPU cores
RAM
Local by default

The extension sends everything straight to the Undetectable app on your computer. It stays there unless you pick a cloud profile.

We do not copy your old fingerprint on purpose

A copied fingerprint is often the reason people leave in the first place. Spoofing built on random noise is what gets accounts linked. When you move in, we keep what platforms actually use to recognize an account: OS family, resolution, timezone, languages, hardware class, and cookies. The fingerprint itself comes from a real device configuration, not from noise.

You move the account and its logins. The fingerprint is built fresh from a real device, not copied from the old one.

What moves and what doesn't

Every antidetect loses the last group too. We just list it up front.

Moves

  • Cookies
  • User-Agent, resolution, CPU, RAM
  • Proxy (you re-attach it)
  • Profile name, notes, tags, and folders (via Local API or manual import)

Approximated by design

  • Canvas, WebGL, and Audio hashes
  • Font list

Rebuilt from a real device configuration instead of the old noise.

Doesn't move yet

  • Session data kept outside cookies: localStorage, sessionStorage, IndexedDB
  • Installed extensions and their data
  • Bookmarks and open tabs
  • Licenses tied to the old app

Local by default, private by design

Local by default

New profiles are created on your machine. What the Converter reads stays there and does not reach our servers.

Cloud is opt-in

Only if you choose to make a profile a cloud profile is its data stored on our servers, and then only encrypted.

Open Local API

Documented, so you can read it before you run it.

Token only for the import

If you use one, revoke it right after.

Moving a team? Talk to us

Tell us what you use now and how many profiles you have. We will help you plan the move.

Migration FAQ

Cookie-based sessions move across, so most stay signed in. Sites that keep their session outside cookies, in localStorage or IndexedDB, may ask you to log in once, because we do not move that data yet. Device-bound services like Google may ask you to confirm the login.
No. The Converter reads the profile from inside the running browser, so it works even after the old plan ends, as long as the profile still opens.
Yes. Install the Converter inside the other browser's profile and send it over, one profile at a time. For large volumes, script the import against the Local API.
The Converter moves one profile per run. For bulk, script against the Local API, which has no built-in limit.
No, and that is on purpose. We keep what links accounts, like OS, resolution, timezone, languages, hardware class, and cookies, and build the fingerprint from a real device configuration instead of copied noise.
Only the profile-management calls, like create, launch, and edit, move to the Local API. Your in-profile scripts in Puppeteer, Playwright, or Selenium connect over CDP the same way.
By default, no. Profiles are created locally on your machine, so what the Converter reads stays there. It only reaches our servers if you choose to make a profile a cloud profile, and then it is stored encrypted.