Cookie Converter: How to Export, Import and Convert Cookies (Netscape ↔ JSON)
You moved a warmed-up account into an anti-detect browser, and it asks for the password again? The problem is almost always the format: the extension exported JSON, the tool expects cookies.txt, or the other way around. A cookie converter fixes this in a minute: paste the file into the cookie converter, pick the target format, import into the profile. Below are both formats, the full workflow, and the errors that kill sessions.
Cookie formats: Netscape cookies.txt vs JSON
Netscape cookies.txt is a plain-text file where each cookie takes one line of seven tab-separated fields. JSON is the export format of the Cookie-Editor and EditThisCookie extensions, and of automation frameworks like Puppeteer and Playwright.
Lou Montulli invented the HTTP cookie at Netscape in June 1994. The browser is long dead, but its file format survived as the de facto interchange standard: curl, wget, yt-dlp and virtually every anti-detect browser read it.
| Parameter | Netscape cookies.txt | JSON (Cookie-Editor) | JSON (Puppeteer / Playwright) |
|---|---|---|---|
| Layout | one line per cookie, 7 tab-separated fields | array of name, value, domain objects | same array, expires in seconds |
| Session cookies | expiry = 0 | session: true field | expires: -1 |
| HttpOnly | #HttpOnly_ line prefix | stored as a field | stored as a field |
| Used by | curl, wget, yt-dlp, anti-detect browsers | export extensions | automation scripts |
The seven Netscape fields are domain, subdomain flag, path, secure flag, expiry in Unix time, cookie name and cookie value.
How to export cookies from a browser
Cookie-Editor is the fastest way, three clicks total.
- Install Cookie-Editor from the Chrome Web Store.
- Open the site where the account is already logged in.
- Click the extension icon, then Export and Export as JSON.
- Save the output as a .json file.
Need Netscape right away, no conversion? Install Get cookies.txt LOCALLY: its Export button produces a ready cookies.txt file.
Converting Netscape to JSON
Open the Accovod cookie converter, paste your data, pick the direction, copy the result. It works like Netscape to JSON for profile imports and extensions. The converter handles all cookies problems automatically: restores the header, fixes separators, etc.
Importing cookies into an Accovod profile
The cookies are ready, now the transfer:
- Create a profile in Accovod and attach a proxy. One profile means one IP, and the proxy country must match the country the cookies were issued in.
- Open the profile settings, find cookie import and paste the JSON content.
- Launch the profile and open the site. A live session opens the account without a login prompt.
Cookies alone do not save an account
The common belief is that imported cookies hold the account by themselves. In reality the server validates the session against the environment: IP, fingerprint, timezone. Typical scenario: cookies pulled from a European IP, pasted into a profile with an Asian proxy. The site sees a familiar token on an unfamiliar device and resets the session or pushes the account into re-verification. For an affiliate team that is a warmed-up account lost: weeks of warming and hundreds of dollars in spend budget.
So move cookies together with the environment: same IP country, same timezone, same language, a close fingerprint across canvas, WebGL and fonts. Cookies lower the chance of accounts getting linked; they do not guarantee anonymity.
Bottom line
A cookie converter fixes the format, not the environment: the converter takes a minute, the environment you configure before the import. The converter at accovod.com/cookieConverter/ is free and needs no sign-up.
FAQ
Can I transfer cookies between browsers?
Yes, this is standard practice. Export cookies from Chrome or Firefox with Cookie-Editor (JSON) or Get cookies.txt LOCALLY (Netscape), then import the file into the target browser or anti-detect profile. The environment must match: same IP region and a similar fingerprint. Otherwise the site can reset the session as suspicious.
Do cookies work with curl, wget and Puppeteer?
Netscape cookies.txt works natively with curl (-b cookies.txt), wget (--load-cookies) and yt-dlp (--cookies). Puppeteer and Playwright take JSON via the setCookie method, with expires in Unix seconds. Convert between the two depending on the tool: command-line utilities want Netscape, automation frameworks want JSON.
What is the difference between persistent and session cookies?
A persistent cookie carries an expiration date and survives browser restarts on disk. A session cookie has no expiration date, lives in memory and dies when the browser closes. In a Netscape file, persistent cookies show a Unix timestamp in the expiry field while session cookies show 0. In Cookie-Editor JSON, the session field is true or false.
Are online cookie converters safe?
Cookies are full access to your account, so process them only in tools you trust.
