Drıftstack docs
Docs

Import or export cookies for a profile

You might be here because: “how do I import cookies” · “export my cookies” · “Couldn’t find any cookies in that file” · “Couldn’t read any cookies” · “Import button is greyed out” · “what cookie file formats work” · “Cookie header has no domain” · “load my cookies” · “transfer a login into a profile”

Short answer

Cookies are imported and exported from the session window’s cookies pane while a session on the profile is running: Export saves the jar as JSON; Import reads a cookies.txt or JSON cookie file whose cookies name their site, and writes them into the running session. Because the profile saves its cookies when the session closes, the import becomes part of the profile. To transfer a login into a profile, export the cookies from a session where you are signed in and import them into a session on that profile.

Check first

  • Is a session running? Import is disabled without one, and Export needs at least one cookie present.
  • Signed in and online.

Likely causes and fixes

  1. How to export. In the cookies pane press Export (“Export the cookie jar as JSON”).

  2. How to import. Press Import and choose a file. Accepted, auto-detected: a Netscape cookies.txt; a JSON array of cookie objects (as common browser extensions export); a {cookies:[…]} wrapper or browser storage-state file; or a WebDriver BiDi cookie export (the JSON that browser-automation tools save). Each cookie must carry its site (domain). A bare Cookie: header or name=value pairs carry no site and are not imported. A cookie whose value is not readable text is skipped; the app reports it as unreadable, or names it if no cookie in the file could be read. The app reports “Imported N cookies (read as [format], M entries unreadable)”, where [format] is JSON or Netscape. When the session could not import some of them, the note adds “Skipped M cookies that could not be imported.”.

  3. “Couldn’t find any cookies in that file (tried JSON, cookies.txt, Cookie header + name=value).” The file was not recognised. Re-export from the source in one of the formats above.

  4. “Couldn’t read any cookies — Cookie header has no domain and no default domain was provided — nothing imported” or “Couldn’t read any cookies — name=value pairs have no domain and no default domain was provided — nothing imported”. A bare header or name=value list carries no site; use a JSON or cookies.txt export that includes domains.

  5. “input looked like JSON but failed to parse” / “JSON did not contain a cookie array or object”. The JSON is malformed or not a cookie list.

  6. Too large / too many. See Cookie jar too large (limit about 3.9 MiB and 2000 cookies).

  7. From code. GET …/cookies reads the jar and POST …/cookies/set writes it.

If it still fails

Press Talk to a person in this chat (or open Help) and include the format you used, the file size and the exact note under Import. Never send the cookie file itself — it contains your logins.