Importing profiles
Bring profiles from AdsPower, Kameleo, Multilogin, Dolphin Anty, GoLogin or a Clout export.
On this page
Choose Import profiles from the register toolbar or the Create menu. The dialog discovers installed sources and lists profiles you can choose. Listing and importing are separate operations.
Before you move a Creator account
Close the source profile so its most recent browser data has been saved. Keep the vendor installation available until you have checked the imported profile’s fingerprint, proxy and signed-in state.
Do a small first import. Conversion can change engine-specific noise, and a copied cookie jar can still contain an expired session. Read Browser engines before moving aged accounts.
Choose a source
| Source | What you need | How Clout obtains profiles |
|---|---|---|
| AdsPower | The local installation and its signed-in account session | Account pull using the existing session |
| Kameleo | Its local workspace | Files from the workspace; no account token for discovery |
| Multilogin | The local installation and usable signed-in session | Detected local session and vendor profile data |
| Dolphin Anty | The running app signed in, or a pasted API token | Running-session bridge and cloud API, with local cookie recovery when available |
| GoLogin | A pasted GoLogin API token | Cloud list and profile requests |
| Clout profile file | A profile JSON exported by Clout | File preview and explicit import |
GoLogin’s current dialog says needs your API token. It does not depend on recovering the app’s local sign-in token. Paste the token, then use List profiles if the list has not appeared automatically.
Use the discovery list
- Open Import profiles and wait for detection.
- Follow the source’s sign-in or token instructions.
- Use Check again after opening a vendor app or changing its signed-in account.
- Expand the source’s groups and select profiles.
- Press Import and read the results.
The list starts with nothing selected. Profiles already present are marked Already here and cannot be selected in the normal discovery import. This path adds profiles instead of silently replacing an existing working row.
Counts come from the source data and the current Clout store. A missing count means the source did not supply it, not that the account contains no profiles.
AdsPower
The account pull uses the session already on the machine. You do not need to create an AdsPower API key for that flow. If the dialog asks you to open AdsPower and sign in, do that and choose Check again.
Discovery, acquisition and saving have separate progress. A large account can take time to list before the first profile is saved. Wait for the existing pull to finish before starting another.
The imported launch format stays AdsPower-compatible and uses SunBrowser. Clout can obtain that engine without AdsPower installed, but keep the vendor available while validating the import.
Kameleo
Clout reads a workspace from disk and copies the imported data into its own store. The source workspace is not edited. Imported profiles retain the Kameleo launch format and open with Chroma.
Kameleo’s engine must be available on the launch computer. Importing the records does not redistribute that engine. Use the ordinary Start action for a Kameleo profile; you do not need a separate Kameleo launch command.
Dolphin Anty
Keep Dolphin open and signed in. The normal path obtains a temporary import credential through its running local bridge; it does not ask for your Dolphin password. The import credential remains in the desktop’s main process.
If that path is unavailable, expand Use an API token instead and paste a revocable token. A pasted token belongs to the dialog. Revoke it at the vendor when you finish if you no longer need it.
The optional Read saved token fallback is a separate action and warns before a possible macOS Keychain prompt. Opening discovery does not run that fallback.
Cookies may come from the cloud export or recoverable locally saved data. If neither path yields a session, the profile will need site sign-in after import. Do not assume every imported profile carries cookies.
Multilogin and GoLogin
Both are converted to the SunBrowser launch format. Multilogin uses the session and data the importer can discover on this machine. GoLogin uses the API token you paste.
The importer maps identity, proxy, names and organisation from the vendor payload. Session and stored credential availability differs by source. Check the per-profile outcome and then open one representative profile before scaling up.
macOS permission prompts
The initial detection pass reads local files and processes without a Keychain prompt. Cloud listing can make authenticated requests to the vendor. Reading a saved encrypted token is a distinct, announced step.
If you refuse that step, use the supported running-session path or a pasted token. Do not grant unrelated system permissions to make an unavailable vendor session appear.
Import a Clout export
The file preview distinguishes a new ID from an ID already in this store. An existing ID means replacement, which requires a separate acknowledgement. A normal profile export excludes cookies and credentials; import the session separately if that is your intention.
Profiles explains the export formats. Command line lists the corresponding import verbs for a server or script.