Cookie manager for the Afina antidetect browser

Import cookies into any profile, export decrypted cookies in Chrome / Netscape / JSON formats and keep storage isolated between accounts. Built for multi-account workflows where every account needs its own session.

Import • Export • Isolate

Sessions where you want them, nothing where you don't

Cookies are the easiest way to leak account identity. Afina isolates cookies per-profile alongside the matching fingerprint and proxy — and gives you tools to inject, dump, and migrate them between accounts on demand.

Import and export in any format

Drop cookies in Chrome JSON, Netscape, EditThisCookie or raw key/value. Export decrypted cookies as JSON files, into a folder for bulk profiles, or directly to the response.

Full per-profile isolation

Every profile has its own Chromium cookie database — no shared state across accounts. Combined with multi-accounting primitives, this is what platforms can't link.

Cookie Robot — automated warm-up

Drop a profile into the Cookie Robot and it visits a curated list of sites — search engines, news, social, ad networks — letting each one set its real cookies. New accounts arrive with a believable cookie trail without you typing a URL. Plug it into RPA scripts for fully automated warm-up batches.

Bulk operations on hundreds of accounts

Inject the same cookie set into 50 profiles at once, export decrypted cookies into one folder, or roll cookies via the local API. Everything works at scale.

FAQs

Have questions? We're here to help.

Online Support Available

Telegram Discord

Chrome JSON (the modern format used by extensions like EditThisCookie), Netscape tab-separated and raw key/value lists. Standard fields parsed: domain, name, value, path, expirationDate, secure, httpOnly, sameSite, storeId. Unknown fields are preserved.

Drop the cookies into a profile (UI or POST /api/profiles/cookies/set). Afina stores them on disk under {data_dir}/cookies/{uuid}/cookies_*.json. On the next browser start, they're injected into Chromium via CDP Network.setCookies.

Export decrypted cookies from a single profile or bulk. Source order: open profile folder → .zip archive → .afbk encrypted archive. Output formats: in-response JSON, single .json file, or per-profile files in a folder. Requires the master password to decrypt.

Yes — each profile has its own Chromium user-data-dir and therefore its own cookie SQLite, IndexedDB, localStorage and service workers. There is no shared cookie pool at the OS level.

Yes, via CDP. While the profile is running, use POST /api/profiles/eval to call Network.setCookies, or attach Puppeteer/Playwright through the wsEndpoint and use the standard cookie APIs there.

Wherever you tell the export endpoint to put them. With a path ending in .json — that exact file. With a folder path — one cookie_{accountName}_{ts}.json per profile. No path — cookies come back in the API response.

Move cookies where you need them — safely

Import, export, isolate and roll cookies across hundreds of profiles from one place.

The Afina cookie manager handles cookies per profile: import from any browser or anti-fraud tool, isolate by design, edit and export in bulk. Combined with the fingerprint engine and per-profile proxies, cookies become the third leg of the isolation stool — no shared session leaks between accounts.

Anti-fraud cross-checks cookie domains, expiry timing and unique tracking IDs. Two accounts that share a single Facebook _fbp cookie or a Google NID identifier are linked. Plain Chrome user-profiles bleed cookies through the same disk layout; extensions live in a shared cookie jar. Afina keeps every profile's cookie store in its own SQLite DB on disk — physical separation, not "we promise".

What's inside the cookie manager

1. Import / export in every common format

JSON, Netscape, EditThisCookie, header strings, browser exports. The same parser feeds both bulk import on profile creation and the per-profile editor — drop a 200-cookie blob and it just works.

2. Per-profile isolation

Each profile gets its own cookies jar, IndexedDB, localStorage, service worker registrations and cache. There is no "default" pool to bleed into. The same isolation that powers multi-accounting at scale.

3. Supported formats

Standard Set-Cookie attributes (Domain, Path, Expires, HttpOnly, Secure, SameSite), partitioned cookies (CHIPS), Storage Access API state. Cookies imported from any source map cleanly into the profile's jar.

4. Bulk operations

Apply the same cookie set across N selected profiles, expire-and-replace by domain, delete by pattern. Drives warm-up flows and credential rotation across portfolios without manual clicking.

5. Sealed in the encrypted vault

Cookies marked sensitive are sealed with your local zero-knowledge key before they touch disk. Storage sees a sealedBox blob, not the cleartext value — even a stolen profile dump is unusable without the master password.

Where teams use the cookie manager

Affiliate teams reuse warm cookie sets to skip account-warmup runs. Discord and social automation teams keep per-account session state across browser restarts. Airdrop farms import pre-warmed cookie packs from suppliers. QA engineers replay flaky e2e flows with a known-good cookie state. The cookie manager is the bridge between "fresh profile" and "established account".