3 min read

Convert Cookie Quick Manager exports to JSON

Cookie Quick Manager is a Firefox extension that exports cookies as Netscape or JSON; paste that export here to produce a JSON array you can import in Chrome with CookieMan. This is not the Cookie Quick Manager site, and a web page cannot read Firefox’s cookies.sqlite.

Prefer the extension’s Netscape or JSON export over copying a request header. Header-only copies lose Domain and HttpOnly.

Cookie Quick ManagerCookie Quick Manager exportFirefox cookies to ChromeCookie Quick Manager JSON
  1. 1
    Export from Cookie Quick Manager

    In Firefox, export the site’s cookies as Netscape cookies.txt or as JSON. Avoid CSV unless you are ready to rebuild seven Netscape fields by hand.

  2. 2
    Convert to JSON Array

    Paste the file below. Netscape becomes JSON with httpOnly taken from #HttpOnly_. If you already exported JSON objects, detection keeps them.

  3. 3
    Import in Chromium

    Install CookieMan in Chrome or Edge, open the same origin, Import → preview → Apply. Host-only versus dotted domains must match what Firefox stored.

Cookies are credentials. Conversion stays in this page — delete the file when you are done.

Firefox jar to Chrome jar — what still breaks

A transferred cookie is necessary, not sufficient. Sites that bind the session to user-agent, IP or a device token will still log you out. Partitioned CHIPS cookies from Chrome will not appear in a Firefox Netscape dump. __Host- cookies must keep Secure, Path=/ and no Domain or Chrome rejects them — fix __Host- rejected.

Export from Cookie Quick ManagerPaste here asThen
Netscape / cookies.txtTab-separated fileJSON Array for Chrome Import
JSON list of cookiesJSON array or mapLeave as JSON Array, import
HTTP headersCookie: or Set-CookieJSON, then fix domains if needed
CookieMan runs on Chromium. It will not load as a Firefox extension. The conversion is the bridge; the live editor is Chrome/Edge.

Leading dots and host-only

Netscape column 2 TRUE means “include subdomains” (not host-only). CookieMan JSON stores the inverse as hostOnly. If a session works on www.example.com but not app.example.com, you imported a host-only cookie. Compare the flag before you blame the server.

Questions people ask

Can I import cookies.sqlite into this converter?
No. Paste Netscape or JSON text. SQLite is a different schema and is not a supported format.
Will Firefox SameSite values survive a cookies.txt export?
Not through Netscape. If Cookie Quick Manager’s JSON export includes SameSite, paste JSON instead of cookies.txt.
Is this an official Cookie Quick Manager page?
No. It is a conversion guide for files that extension can emit. Use Cookie Quick Manager itself to read the Firefox jar.
3 min read

Convert Get cookies.txt LOCALLY to JSON

Turn a Netscape file from the Get cookies.txt LOCALLY extension into a JSON array that keeps HttpOnly flags, then import it in Chrome or another profile.

Get cookies.txt LOCALLYcookies.txt to JSON Open the guide
3 min read

JSON Array vs cookies.txt Field Mapping

Side-by-side mapping of CookieMan JSON Array fields to Netscape cookies.txt. SameSite, partitionKey and store metadata never survive the seven-column file.

JSON vs cookies.txtcookies.txt field mapping Open the guide
3 min read

Cookie-Editor Alternative for Chrome (MV3)

Cookie-Editor is a cookie inspector. CookieMan is a Manifest V3 editor that imports the same JSON and converts it to cookies.txt, headers or Base64.

Cookie-Editor alternativeCookie-Editor Chrome Open the guide

Apply this on live cookies

The converter rewrites files. The extension reads and writes the jar in Chrome, including HttpOnly cookies.

Free and MIT-licensed · Chrome, Edge and other Chromium browsers · Nothing leaves your machine