3 min read Updated August 17, 2026

Fix SameSite=None cookies rejected without Secure

Chrome rejects a cookie with SameSite=None without Secure. CookieMan JSON stores None as sameSite: "no_restriction". Paste the broken object below, set secure to true in the output, and import on an HTTPS origin — the converter will not silently flip the flag for you.

Netscape cannot record SameSite at all. If the only copy you have is cookies.txt, you must add None+Secure in JSON after conversion.

SameSite=None without SecureSameSite None rejectedSameSite=None Secure requiredcookie SameSite None
  1. 1
    Confirm the rejection

    CookieMan’s popup surfaces the browser error when save fails. DevTools Application panel simply does not show the cookie.

  2. 2
    Fix the JSON here

    Paste the object. In the output, set "secure": true and keep "sameSite": "no_restriction". Do not import on plain HTTP except localhost experiments.

  3. 3
    Apply on HTTPS

    Open the https origin, Import → Apply. Cross-site iframes still need CHIPS if the cookie is third-party — partitioned export.

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

Symptom → cause → fix

SymptomCauseFix
Cookie disappears on saveSameSite=None without SecureSet secure: true in JSON
Cross-site iframe has no cookieNone+Secure but not partitioned when CHIPS is requiredAdd partitionKey via the extension export
Works in curl, fails in Chromecurl ignores SameSiteExpected — fix JSON for the browser
sameSite: "none" in a dumpAccepted on parse as no_restrictionStill needs Secure
This web page cannot set cookies on example.com. It rewrites files. The extension applies them through chrome.cookies.set, which still obeys Chrome.

Accepted sameSite strings

            parseSameSite: "strict" | "lax" | "none" | "no_restriction"
# anything else → unspecified

Set-Cookie serialisation:
  no_restriction → SameSite=None
          

Questions people ask

Is localhost allowed without HTTPS?
Chrome treats localhost as a secure context for many cookie purposes, but SameSite=None still wants the Secure attribute set. Prefer https://localhost or https://127.0.0.1 when testing None.
Will the converter set Secure automatically?
No. Auto-flipping flags would hide illegal exports. You change secure, then import.
Does cookies.txt preserve None+Secure?
Secure is column 4. None is not stored. Re-importing Netscape will not restore None — SameSite lost in cookies.txt.
3 min read

SameSite Lost in cookies.txt Exports

Netscape cookies.txt has no SameSite column. JSON → Netscape → JSON always yields unspecified. Keep JSON Array when Lax, Strict or None must survive Chrome import.

SameSite cookies.txtSameSite Netscape Open the guide
3 min read

Fix __Host- Cookie Rejected by Chrome

__Host- cookies must be Secure, Path=/, and host-only (no Domain). Paste broken JSON, correct the fields, then import on that host over HTTPS.

__Host- cookie rejected__Host- prefix Open the guide
3 min read

Export Partitioned CHIPS Cookies

Partitioned cookies need JSON Array with partitionKey.topLevelSite. Netscape, headers and Set-Cookie drop the key, so Chrome stores the wrong partition.

CHIPS cookiespartitioned cookie export 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