- 1 Export from Cookie Quick Manager
In Firefox, export the site’s cookies as Netscape
cookies.txtor as JSON. Avoid CSV unless you are ready to rebuild seven Netscape fields by hand. - 2 Convert to JSON Array
Paste the file below. Netscape becomes JSON with
httpOnlytaken from#HttpOnly_. If you already exported JSON objects, detection keeps them. - 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.
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 Manager | Paste here as | Then |
|---|---|---|
| Netscape / cookies.txt | Tab-separated file | JSON Array for Chrome Import |
| JSON list of cookies | JSON array or map | Leave as JSON Array, import |
| HTTP headers | Cookie: or Set-Cookie | JSON, then fix domains if needed |
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.