Home > Format > Cookie Converter - JSON, Netscape, Header & Set-Cookie

Other Tools

URL ParserJSON to YAMLJSON ⇄ TOON ConverterGenerate TypeScript Types and JSON Schema from JSONINI to JSON ConverterSQL FormatterNumber to ChineseCookie Converter – Netscape to JSON & JSON to NetscapeYAML (YML) Formatter and ValidatorXML Formatter

Cookie Converter - JSON, Netscape, Header & Set-Cookie

Convert cookies between JSON, Netscape, Cookie request headers and Set-Cookie response headers locally in your browser.

Private by design:cookie data is processed only in this browser and is never uploaded.

Cookie request headers do not contain a domain. Add one when creating JSON or Netscape files for a specific site; Netscape output requires it.

Supported cookie formats
JSON cookies
Browser or extension exports represented as cookie objects.
[{"domain":"example.com","name":"session","value":"abc"}]
Netscape cookie file
Tab-separated cookies.txt format used by curl, wget and automation tools.
.example.com  TRUE  /  TRUE  0  session  abc
Cookie Header
The Cookie request header sent from a browser to a server.
Cookie: session=abc; theme=dark
Set-Cookie headers
One or more Set-Cookie response headers with cookie attributes.
Set-Cookie: session=abc; Path=/; Secure; HttpOnly
Only need JSON and Netscape conversion?Open the dedicated Netscape Cookie Converter
Convert Cookie Formats Online


Cookie data appears in several incompatible formats. Browser extensions often export JSON, command-line tools use Netscape cookies.txt, HTTP requests send a Cookie header, and servers return one or more Set-Cookie headers. This converter handles all four formats locally in your browser.


Supported Conversions


    

  • JSON cookie objects
    • 

  • Netscape HTTP Cookie File
    • 

  • Cookie request headers
    • 

  • Set-Cookie response headers
    • 



Choose a source and target format, or let the tool detect the input automatically. You can paste text or upload a .json, .txt or .cookies file, then copy or download the result.


Domain and Attribute Handling


A Cookie request header contains only names and values. It does not contain domain, path, expiry, Secure, HttpOnly or SameSite attributes. Enter a default domain when converting this format to a browser JSON export or Netscape file. Netscape output requires a domain.


Converting to Cookie Header intentionally removes attributes that cannot be represented by that format. JSON, Netscape and Set-Cookie outputs preserve supported attributes whenever the source provides them.


Examples


Cookie: session=abc123; theme=dark



Set-Cookie: session=abc123; Domain=.example.com; Path=/; Secure; HttpOnly; SameSite=Lax



[
  {
    "domain": ".example.com",
    "name": "session",
    "value": "abc123",
    "path": "/",
    "secure": true,
    "httpOnly": true
  }
]



Privacy


Cookie content is parsed and converted in the current browser. It is not uploaded to ToolMi. Even so, avoid sharing live authentication cookies with other people and revoke exposed sessions immediately.


Frequently Asked Questions


Why is a domain required for Netscape output?


Every Netscape cookie row includes a domain field, while a Cookie request header does not. Supply the website domain before converting.


Why are attributes missing from Cookie Header output?


The HTTP Cookie request header supports only name=value pairs. Attributes such as HttpOnly and SameSite belong to Set-Cookie responses.