Get started

Import your browser profiles.

Donut turns existing Chromium-family profiles into Wayfern profiles. Bookmarks, history, local storage, cookies and saved passwords come with them, and each imported profile gets its own new fingerprint. Import is free on every plan.

Supported sources: Chrome, Chromium, Chrome Beta, Dev and Canary; Microsoft Edge, Edge Beta and Dev; Brave, Brave Beta and Nightly; Opera and Opera GX; Vivaldi; Arc; Yandex Browser; and Wayfern. Firefox-based browsers cannot become a Chromium profile; move their cookies instead.

In the app

Open More → Import profile (Cmd/Ctrl+O). The page has three tabs:

In the same pass you can rename each profile, put all of them in a group (or make a new one), give them one proxy or spread your stored proxies across them in turn, and choose what happens when a name is taken: rename (Name (2)) or skip. One broken profile never stops the batch. The last screen lists what was imported, skipped or failed.

Cookies and passwords

Chromium encrypts cookies, passwords and payment data with a key that the operating system keeps for that browser: the macOS Keychain, Windows DPAPI, or the Linux secret service. Donut asks the system for that key, opens the data and seals it again with Wayfern’s key. On macOS, the system can ask you to allow access to the Keychain item.

The import report says what came across. Some data can stay behind:

• If the key cannot be opened (you declined the prompt, or the keyring is locked), everything except cookies and passwords comes across, and you sign in again.
• Chrome 127 and later on Windows bind cookies to Chrome itself. No other app can move those cookies.
• Close the source browser first. If it runs, site data can be incomplete.
• Protected settings, such as the homepage and the search engine, go back to their defaults. Extensions that belong to the source browser are not carried over.
• In the Snap package, connect the keyring first: sudo snap connect donutbrowser:password-manager-service.

From another anti-detect browser

Other anti-detect browsers do not export a Chromium profile folder, so there is nothing for the folder or ZIP import to read. Export the cookies from the old tool, create profiles in Donut, and import the cookies. The fingerprint never moves between tools: each engine makes its own.

Over the REST API

Three endpoints cover a migration (full shapes in the API reference):

• GET /v1/profiles/import/detect lists importable profiles, optionally from a ?folder=.
• POST /v1/profiles/import imports in bulk, with group_id, a proxy_id per item and duplicate_strategy (rename or skip).
• POST /v1/proxies/import adds proxies from a text list or a Donut JSON export.

# 1. See what is on this computer
curl -sS http://127.0.0.1:10108/v1/profiles/import/detect \
  -H "Authorization: Bearer $DONUT_API_KEY" | jq '.profiles[].path'

# 2. Import one profile into a group
curl -sS -X POST http://127.0.0.1:10108/v1/profiles/import \
  -H "Authorization: Bearer $DONUT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "items": [
      { "source_path": "/Users/me/Library/Application Support/Google/Chrome/Default", "new_profile_name": "Old Chrome" }
    ],
    "group_id": "e2074e8e-2a9e-46dd-a91e-c34c88ee1e35",
    "duplicate_strategy": "rename"
  }'

Remote MCP refuses detect_browser_profiles and import_browser_profiles with TOOL_IS_LOCAL_ONLY, because they read folders on your disk. Run them in the app or over the REST API.

Good to know

• The import never downloads a browser. Download Wayfern first.
• Fingerprints are made per imported profile. A fingerprint for another operating system needs Pro, Team or Enterprise.

Checked against the app on October 14, 2026.