Cookie Fields Explained: Name, Value, Domain, Path, Expiry and Flags
Name, value, domain, path, expiry, Secure, HttpOnly, SameSite, what each field in Cookie Editor means and what changing it does.
Expand any cookie in Cookie Editor and you will see the same set of fields. Each one answers a specific question: what is stored (name and value), where it applies (domain and path), how long it lasts (expiry and session), and how the browser may handle it (Secure, HttpOnly, SameSite). Once these click, the whole panel, and most cookie behaviour, stops being mysterious.
The identity fields: name and value
The name is the key the site chose, such as theme, lang or session_id. The value is the stored state: dark, en, or a long random string for a session. Two cookies can share a name if their domain or path differ, so the name alone never identifies a cookie, the combination of name + domain + path does.
The scope fields: domain and path
The domain says which host the cookie belongs to. A cookie set for example.com may also be sent to subdomains if it is a domain cookie (shown with a leading dot in some tools); a host-only cookie goes only to the exact host that set it. The path limits which section of the site receives it: / means everywhere, while /account means only pages under that path. Wrong scope is the number-one reason an edit seems to be ignored, the page is reading a different cookie with the same name.
The lifetime fields: expiry and session
A cookie with an expiration date is persistent: the browser keeps it until that date, across restarts. A cookie with no expiry is a session cookie, discarded when the browser closes. If a preference keeps “forgetting” you, compare the expiry before and after the site rewrites it, the full picture is in Session vs Persistent Cookies.
The safety flags
| Flag | Meaning | Can you change it in Cookie Editor? |
|---|---|---|
| Secure | The cookie is only sent over HTTPS connections | Yes, but clearing it weakens protection, leave it as the site set it |
| HttpOnly | JavaScript on the page cannot read the cookie; only the browser sends it | It can be viewed/deleted, but the flag exists to stop scripts rewriting it, change the setting on the site instead |
| SameSite | Controls whether the cookie travels on cross-site requests (Strict, Lax or None) | Yes; changing it can break embedded or sign-in flows, so test carefully |
| Host-only | The cookie belongs to one exact host, not subdomains | Determined by how the cookie was set; recreating the cookie changes it |
Which fields should a beginner touch?
Start with value only. It changes what the site reads without changing where or how long the cookie applies. Touch expiry when you are deliberately testing persistence. Leave domain, path and flags alone until you are testing scope on purpose, and export a backup first, as described in the import and export guide.
Reading a cookie like a sentence
Take a typical preference entry and read it field by field as one sentence: 'For the site at this domain, on all paths, remember that theme is dark, until this date next year, send it over secure connections only, and do not let page scripts read it directly.' Every field you struggled to memorise is in that sentence doing one plain job. When a cookie behaves unexpectedly, translate it back into the sentence and the odd one out usually announces itself: an expiry in the past, a path that does not cover the page you are on, a domain one level off from where you expected.
The fields that cause the most confusion
Three fields generate most support questions. The domain field confuses because a leading dot and a parent domain mean the cookie travels to subdomains too, so one preference can appear on several related sites. The path field confuses because a cookie set for a shop section may simply not exist, as far as the blog section is concerned. And SameSite confuses because its effects appear on other sites, in embeds and cross-site requests, rather than on the site that set it. If you master those three, the rest of the table is bookkeeping.
| Field | Controls | Change it when |
|---|---|---|
| Name and value | What is remembered | Testing a preference state |
| Domain | Which hosts receive it | Almost never; scope errors are usually the site's |
| Path | Which folders receive it | Diagnosing a cookie that 'vanishes' between sections |
| Expiry | How long it lives | Testing what happens when a state ages out |
| Secure | HTTPS-only travel | Leave as the site set it |
| HttpOnly | Hidden from page scripts | Cannot be changed in the panel, by design |
| SameSite | Cross-site sending | Testing embeds and sign-in flows |
Frequently Asked Questions
Why is a value a long random string?
That is usually a session ID or a token: the real data lives on the site's server, and the random value is just the key that looks it up. Never share these, see the sign-in safety guide in the Privacy category.
What does a leading dot in the domain mean?
It marks a domain cookie shared with subdomains, as opposed to a host-only cookie for one exact host.
Can I make a session cookie permanent by setting an expiry?
You can edit the expiry, and the browser will keep the cookie longer, but the server may still expire the session on its side, so the sign-in may not actually last.


