Loading page
About this tool
View, manage, add, edit, and delete browser cookies in real-time.
Cookie Viewer reads `document.cookie` for the current domain and lists every name and URL-decoded value it can see, then lets you add a cookie with a chosen expiry in days, overwrite an existing value, or delete one by re-setting it with an expiry of 1 January 1970. New cookies are written with `path=/` and the value URL-encoded. It is for developers and QA testers who want to flip a feature flag or clear a session marker without opening the browser's devtools panel.
Open Cookie Viewer on AltFTool — it loads instantly in your browser.
The page reads the cookies your browser exposes for this domain the moment it loads and lists each one as a Name / Value row, or shows 'No cookies found for this domain.' Press Refresh to re-read them after something else changes a cookie.
Press Add Cookie to open the Add New Cookie form, fill in Name, Expires (Days) and Value, then press Save — a 'Cookie added!' toast confirms and the row appears in the table.
On any row, the pencil button reopens the cookie as Edit Cookie with its Name locked, and the trash button deletes it after you confirm 'Delete the cookie ... This cannot be undone.'; Clear All removes every listed cookie in one go.
The list runs `decodeURIComponent` on each value, so a JSON or path-bearing cookie reads as itself instead of a wall of %7B and %2F escapes.
You enter a number of days and the correct `expires` header string is generated, avoiding the malformed date that silently turns a cookie into a session cookie.
Removal re-sets the cookie with a 1970 expiry on `path=/`, which is the only way a script can delete a cookie — there is no delete API.
No. `document.cookie` is scoped to the current origin, so this page can only list cookies belonging to this domain. Cookies for other sites are inaccessible by design — that isolation is the same-origin policy, and no page-level tool can work around it.
Cookies marked HttpOnly are deliberately hidden from JavaScript, so session and auth cookies usually will not appear. Cookies scoped to a different path or subdomain than the current page are also excluded. Use the browser's own Application panel to see those.
Around 4 KB per cookie in practice — RFC 6265 asks browsers to support at least 4096 bytes for the name, value and attributes combined, and most cap it there. Browsers also limit how many cookies one domain may hold, so store an identifier and keep the data server-side.
Set it again with the same name and a past expiry: `document.cookie = "name=; expires=Thu, 01 Jan 1970 00:00:00 UTC; path=/"`. The path must match the one the cookie was created with, which is why a cookie set on a narrower path can appear undeletable from the site root.