Convert Cookies Between Any Format

Convert Cookies Between Formats Instantly

A cookie converter turns exported browser cookies into the exact format another tool needs — Netscape (cookies.txt), JSON, an HTTP Cookie header, CSV, TSV, SQLite, or a cURL cookie jar. Paste or upload your file, pick the output format, and download the result in seconds. Everything runs locally in your browser — free, no sign-up, and your cookie data is never uploaded to a server.

How It Works

1. Upload your cookie file (supports .cookies, .http-request, .set-cookie, .keyvalue, .tsv, .txt, .json, .csv, .db)
2. Select the format you want (for example: Netscape to JSON, CSV to Set-Cookie)
3. Click Convert and download your new file instantly

Supported Conversions

This tool handles conversion in either direction between every format it supports, including:

• Netscape (cookies.txt) to JSON
• JSON to Netscape (cookies.txt)
• Cookie header (Name=Value) to JSON
• JSON to Cookie header
• Netscape (cookies.txt) to a one-line Cookie header
• CSV to JSON, and JSON to CSV
• cURL cookie jar to JSON
• SQLite (Cookies.db) to JSON

Cookie Format Comparison

Not sure which format you need? Use this table to match the format to the tool you’re using.

Features

• Convert cookies 100% free
• Run the tool without installation or signup
• Use it in Chrome, Firefox, Edge, and other browsers
• Convert cookies in seconds
• Everything runs locally in your browser — your cookie file is never uploaded to a server
• No account or email required

Why Use This Tool?

Browsers, APIs, and extensions require cookies in specific formats.
Save time and avoid errors by using this cookie conversion tool. Convert Netscape cookies to JSON, Set-Cookie headers to CSV, or export cookies from Chrome and Firefox into the format you need with one click.

How to Export Cookies From Your Browser

Chrome and Edge

Open DevTools (F12), go to the Application tab, expand Cookies in the sidebar, and select the site. You can copy individual values from there, or use a cookie-export browser extension to save the whole set as a Netscape (.txt) or JSON file. Paste the result into the converter above to switch it to the format you need.

Firefox

Open DevTools (F12) and go to the Storage tab, then expand Cookies and select the site. As with Chrome, a cookie-export extension is the fastest way to get a full Netscape or JSON file you can drop straight into the converter.

Cookie Format Guide

Netscape Cookies (.txt)

The Netscape format stores cookies in plain text with tab-separated fields such as domain, path, expiry, and value. Many browsers, cURL, and extensions still use this format. A valid file starts with a comment line and lists seven tab-separated fields per cookie: domain, include-subdomains flag, path, secure flag, expiration timestamp, name, and value.

# Netscape HTTP Cookie File
.example.com	TRUE	/	TRUE	1893456000	session_id	a1b2c3d4e5

JSON Cookies (.json)

JSON cookies store data in key-value pairs inside an array. Chrome and Firefox export cookies in this format, and developers use it because it is easy to read and process.

[
  {
    "name": "session_id",
    "value": "a1b2c3d4e5",
    "domain": ".example.com",
    "path": "/",
    "expires": 1893456000,
    "secure": true,
    "httpOnly": true
  }
]

HTTP Request (Cookie)

HTTP requests send cookies in the format:
key=value; key2=value2;
Use this format in API clients like Postman or when you run curl commands with headers.

Cookie: session_id=a1b2c3d4e5; theme=dark

HTTP Response (Set-Cookie)

Servers send cookies in HTTP responses with the Set-Cookie header. Each cookie includes details like expiry date, Secure, and HttpOnly flags. Developers parse this format when they debug server responses.

Set-Cookie: session_id=a1b2c3d4e5; Domain=.example.com; Path=/; Secure; HttpOnly

Key=Value

This format saves cookies one per line:
name=value
You can copy and paste these cookies quickly into scripts or tools.

session_id=a1b2c3d4e5
theme=dark

CSV Cookies (.csv)

CSV cookies store data in comma-separated rows. Open them in Excel or Google Sheets to view columns like name, value, domain, path, and expiry.

name,value,domain,path,expires,secure
session_id,a1b2c3d4e5,.example.com,/,1893456000,TRUE

TSV Cookies (.tsv)

TSV cookies use the same fields as CSV but separated by tabs instead of commas. This format works better with Unix tools and text editors because it avoids issues with commas inside cookie values.

SQLite Cookies (.db)

Browsers like Chrome, Edge, and Opera save cookies in SQLite databases (Cookies.db). This format supports structured queries and fast lookups but requires a database reader. The relevant columns are typically host_key, name, value, path, expires_utc, and is_secure.

cURL Jar

The cURL cookie jar stores cookies in the Netscape format. Use it to persist cookies across multiple requests in API automation or web scraping, typically with curl -c cookies.txt to save and curl -b cookies.txt to send.

Custom Cookies (.cookies)

Some extensions and apps save cookies in .cookies files. These files may contain JSON, text, or other structures. This tool converts them into standard formats automatically.

Frequently Asked Questions

Why does my cookies.txt file not look like a Netscape format cookies file?

A valid Netscape cookies.txt file starts with the comment line # Netscape HTTP Cookie File, and every cookie sits on its own line with exactly seven tab-separated fields: domain, include-subdomains flag, path, secure flag, expiration timestamp, name, and value. This error usually shows up when the file uses spaces instead of tabs, a field is missing, the file was saved as .csv or .json instead of .txt, or the header comment line was removed. Paste the file into the converter above — it detects and fixes most of these issues automatically.

What does “# Netscape HTTP Cookie File” mean at the top of the file?

It’s a comment line that marks the file as using the Netscape cookie format. Parsers ignore it, and it exists mainly so humans and older tools can identify the file type at a glance. You can leave it in place — the converter skips it automatically when reading your file.

How do I convert a cookies.txt file into a one-line Cookie header?

Paste your Netscape-format file into the converter, choose Header (Name=Value) as the output format, and click Convert. The tool strips the domain, path, and expiry fields and joins the remaining name/value pairs with semicolons into a single line ready to paste into a request header.

Is this cookie converter free, and do I need to sign up?

Yes — it’s completely free, with no sign-up, no email, and nothing to install. Everything runs in your browser, and no cookie data is uploaded to a server.

Does the converted JSON work with Puppeteer, Playwright, or Selenium?

Yes. The JSON output uses the same name, value, domain, path, expires, secure, and httpOnly fields that Puppeteer’s setCookie(), Playwright’s addCookies(), and Selenium’s add_cookie() expect, so you can usually paste it in directly.

Is it safe to convert cookies here? Where does my data go?

Conversion happens locally in your browser using JavaScript — your cookie file is never uploaded to a server or stored anywhere. That said, treat exported cookies like passwords: they can grant access to your accounts, so only convert cookies you trust and never share the output with anyone else.