Deck Help Center
Download

Import and export cookies

Paste or load a cookie export to make a profile open already logged in, and export a profile's cookies as a backup.

Updated · 5 min read

On this page

Cookies are the logged-in part of a browser. Import a cookie file into a profile and it opens already signed in, with no password typing. Export them and you have a copy of that session you can keep or move to another computer.

A cookie file is a login

Anyone who opens your export file is logged in as you. Keep these files somewhere private, and don't email or upload them.

🍪 Import cookies into a profile#

  1. Stop the profile if it's running.
  2. Open the profile's editor (row ⋯ → Edit) and click the Cookies tab.
  3. Either paste the export into Paste a cookie export and click Import into this profile, or click From a file… and choose the file.
Pasting a cookie export into the Cookies tab and importing it.

A headless browser opens for a second or two to write the cookies in, then the result appears: "Imported 48 of 50 — the jar now holds 48".

You can also import without opening the editor: on the profile's row, click ⋯ → Import cookies… and pick the file.

Formats LoginDeck accepts#

SourceNotes
Cookie-Editor and EditThisCookie JSONThe usual browser extension exports
GoLogin or AdsPower cookie exportPaste the JSON
Playwright storage stateThe cookies inside it are read
Netscape cookies.txtTab-separated, and #HttpOnly_ lines are honoured

The JSON can be a plain list, or an object with a cookies, Cookies, data or cookie key. Expiry times in seconds or milliseconds, hostOnly, and domains with or without a leading dot are all sorted out for you. The same cookie listed twice is imported once.

Reading the result#

  • "48 of 50": two were not accepted. The browser decides what it will store.
  • "12 of them are session cookies with no expiry": those live in memory only and won't be there next time the profile opens. That's how they were exported, not something LoginDeck can fix.
  • "3 refused by the browser" names the cookies it rejected, usually because the domain or flags don't make sense together.

📤 Export a profile's cookies#

  1. Stop the profile.
  2. On its row, click ⋯ → Export cookies… (or use Export… on the editor's Cookies tab).
  3. Choose where to save it. The file is named like acme-google-ads-cookies-2026-09-27.json.

The file is Cookie-Editor JSON, so it goes straight back into LoginDeck or into a browser extension.

🔢 Count or clear cookies#

On the editor's Cookies tab:

  • Count what is there opens the profile briefly and reports "312 cookies in the jar right now".
  • Clear cookies signs the profile out of everything. It asks first.

The state line at the top of the tab tells you where you stand: "312 cookies across 24 sites, as of 2 h ago. This profile launches logged in to whatever they belong to." Or "No cookies recorded. This profile launches logged out of everything."

Clearing cookies signs you out for good

The fingerprint and proxy stay, but the only way back into those accounts is another cookie import or typing the password again.

❓ Common questions#

Why does it say "stop this profile before importing or exporting its cookies"?

The profile's browser is open, and two browsers can't use one cookie store. Click Stop on the row and try again.

I imported cookies but the site still asks me to log in.

Common reasons, in order:

  1. The cookies were session cookies with no expiry. The result line says so. Ask whoever exported them for a fresh export.
  2. The cookies have expired, or the site invalidated them when it saw a new location. Imports do not refresh cookies.
  3. The proxy is in a different country from where the account usually signs in. Set a proxy that matches, then import again. See Which proxy should I use?
  4. The export was partial, missing the domain that actually holds the session (some sites use several).

If it still fails, export the cookies again from the source browser with all domains included.

Do I need cookies at all, or can I just log in?

Logging in normally is fine, and often safer for a fresh account. Cookie import is for accounts that already exist somewhere else.

Can I import cookies into a locked profile?

Yes. Importing works on locked profiles. Exporting doesn't.

Can I import cookies into a Firefox profile?

Not yet: "cookie import/export is not available for Firefox profiles yet — it works on Chromium profiles". See Chrome or Firefox.

What happens if I paste the wrong kind of file?

You get a reason, for example "that is not valid JSON", "no cookie array found in that file", or "that does not look like cookie JSON or a Netscape cookies.txt file". Nothing is changed.

Can I import cookies into a profile I haven't saved yet?

LoginDeck offers to save it first, because cookies are written into the profile's own folder on disk. Click Save and continue. If you were creating a batch with Quantity, open one of the new profiles and import there.

ℹ️ Good to know#