AdsPower alternative for antidetect browser migration

Prepare the profile spreadsheet

Keep an unchanged copy of the file exported from AdsPower. If you have an Excel workbook, save the relevant sheet as UTF-8 CSV before importing. Put the column names in the first row and one browser profile in each following row. Keep explanatory notes and merged cells outside the data you intend to import.

A supported flat JSON table is an array of objects with direct field values, processed through column mapping. It differs from a full profile configuration JSON file. Check the file structure before choosing an import route; a nested configuration from another application does not become a table simply because its extension is JSON.

Preserve the relationship between the profile name, platform account and proxy. For a seller, that may be one store per profile; for an agency, it may be a client's social account. If the export has no cookies or other required login data, plan to sign in again. The cloud sync and backup guide explains the data types involved.

Match account and cookie columns

Open Profiles → Import and choose your file. The importer recognizes common English and Chinese headers. English examples include name and profileName for the profile name, username and account for the platform account, and remark for notes. Other supported fields include groups, tags, login URLs, startup URLs, language, time zone and a 2FA secret.

Review the column assignments and the First rows preview. Set unneeded columns to Don’t import and select the correct source for unmatched fields. Keep Account and Password separate from Proxy user and Proxy password: website credentials and proxy credentials authenticate to different services. Also check Login URL separately from Startup URLs when the source contains several web addresses.

A Cookies column is parsed from its contents. A familiar header does not establish that its values are valid or belong to the expected account. Continue with Next: check rows and inspect any validation messages. Return to the original export to resolve missing or ambiguous values instead of borrowing data from a different profile.

Import separate proxy fields

CSV proxy details can occupy separate columns. Map them to Proxy type, Proxy host, Proxy port, Proxy user and Proxy password. Corresponding English headers include proxyType, proxyHost, proxyPort, proxyUsername and proxyPassword. Supported proxy types are HTTP, HTTPS and SOCKS5. Check that the host and port describe the connection supplied by your proxy provider.

If you also map a complete Proxy column, that column takes priority and the importer does not assemble a connection from the separate fields. This applies even when the complete Proxy cell is empty. Choose one representation and inspect the preview, especially when a file contains both an old proxy string and newer connection fields.

Import validation cannot establish that a proxy subscription is active or that its current exit IP is in the intended region. After creating the profiles, test the connection and check the actual exit IP. Use the proxy setup guide to verify credentials, connection type and location before signing in to the target account.

Check templates, duplicates and available capacity

A spreadsheet without a full fingerprint gets fingerprint settings from a device template. Choose Windows 10, Windows 11 or an Apple silicon Mac template as appropriate, and check language and time zone. This generates settings for the imported profile; it does not restore every fingerprint value from the previous browser.

Review valid rows, rows with problems, duplicate names and the remaining profile allowance before submitting. The Duplicate names choices are Rename (add a number), Skip duplicates and Keep the name. A separate migration group can make the new profiles easier to match against the original export while you verify them.

1. Set Default group for rows without a group and confirm the device template used for rows without a fingerprint.
2. Fix invalid rows and choose how duplicate names should be handled. Check how many profiles your plan and member allowance still permit you to create.
3. Run the import and compare the created count with the source rows. Review skipped rows and cookie failures before retrying only the records that still need attention.

Update scripts and verify the migrated profiles

WGBrowser does not implement the AdsPower Local API. Adapt endpoint paths, request bodies, authentication and response handling using its Local API documentation. Open Settings → Local API and enable the Turn on Local API setting. The default local port is 54345, and the service generates a key when first enabled. Use the new profile IDs in your script.

Open one imported profile through the API and connect Puppeteer or Playwright to the CDP address returned for that run. Verify that you can select the intended page, perform a small operation and close the profile normally. If you intend to move the task into a plugin, review the automation options and validate the plugin's inputs and results separately.

For each test profile, compare the platform account, proxy exit IP, language, time zone, device template and actual login state. Ordinary spreadsheets do not restore complete local storage, and imported cookies may no longer represent an active session. Resume larger multi-account tasks only after the imported data and a complete run have been checked.

FAQ