- 1 Export JSON from CookieMan on the top-level site
Open the publisher origin (the top-level site), export JSON Array. Partitioned third-party cookies include
partitionKey. - 2 Keep JSON — do not convert to Netscape
Paste here only to inspect. If you must convert, stay on JSON Array. Switching to Netscape is a guaranteed key loss.
- 3 Import on the same top-level site
Chrome scopes partitioned cookies by top-level site. Import while that site is the active tab or the cookie lands in a different partition and is not sent.
Where partitionKey survives
| Format | partitionKey? | Notes |
|---|---|---|
| JSON Array | Yes, if topLevelSite is present | The only lossless CHIPS export |
| JSON Map | No | Name/value only |
| Netscape cookies.txt | No | Seven columns, no CHIPS |
| Header String | No | Values only |
| Set-Cookie | Token Partitioned may appear on some writers; this writer does not emit it, and parse ignores it | No top-level site in the header |
| Base64 | Yes, because it wraps JSON Array | Inner JSON still required |
A Set-Cookie line with
Partitioned is parsed, but the attribute handler hits break without storing a key — there is none in the header. Re-importing that JSON yields an unpartitioned cookie. What the format and the web page cannot do
- This page cannot list CHIPS cookies from your browser. Origin isolation forbids it.
- Netscape cannot represent partitions. Do not use cookies.txt as a CHIPS backup.
- Partitioned cookies require
Secure. Chrome rejects the combination otherwise.
{
"name": "third_party_id",
"value": "abc123",
"domain": ".ads.example.com",
"secure": true,
"sameSite": "no_restriction",
"partitionKey": { "topLevelSite": "https://publisher.example" }
}