Drıftstack docs
Docs

Export and import profiles (with or without their proxy)

You might be here because: “export my profile” · “import a profile file” · “give a profile to a teammate” · “move a profile to another account” · “The file names its proxy (label and address, no password)” · “no proxy chosen yet: choose one in Edit before launching” · “the imported profile has no cookies” · “does the export include my proxy password” · “400 ValidationFailed on import”

Short answer

Export writes a profile to a JSON file that holds its name, device, description and notes — not its cookies or logins — and Import reads that file and creates a fresh profile, in the same account or another. That is how you hand a profile to a teammate or move it between accounts. In the desktop app the file also names the profile’s proxy — label and address, never the password — so an import on a computer that has that proxy keeps the choice.

Check first

  • Expecting logins to travel with it? Browser state is not in the file. Cookies move separately (see the cookies page).
  • Sharing the file? After an export the app says so: “The file names its proxy (label and address, no password), which anyone you share it with can see.”.
  • Room for one more profile? An import is a new profile and counts against the plan’s number (429 when you are at it).

Likely causes and fixes

  1. What the app says after Export and Import. Export: “Exported … as a JSON file.”, plus the proxy note whenever the file carries one. Import: “Imported N profiles.” and, for each one whose proxy is not on this computer, “… no proxy chosen yet: choose one in Edit before launching.”.

  2. The imported profile has no proxy. The file names a proxy only by label and address; if this computer or account does not have it, the profile arrives without one and will not launch until you pick one. Fix: Edit the profile and choose a proxy.

  3. The name already exists (409). Import uses the name in the file unless you give another; from code, name_override renames without editing the file. Fix: rename, or delete the profile holding that name.

  4. The device is no longer offered (400). The device in the file must be in the current catalog: an older retained profile still exports, but its file cannot be imported. Fix: create a new profile on a device your plan offers.

  5. From code. Export needs a key with read scope; import needs write:profiles (a broad write key also works), and a team admin can import into the owner’s workspace. Notes travel; a file exported before notes existed imports with none.

If it still fails

Press Talk to a person in this chat (or open Help) and include the exact note shown after Import, the device named in the file, and whether the file came from another account. Attach the file only if you are comfortable with the proxy label and address it names being seen.