What Is Cookie Viewer?
Cookie Viewer is a free online tool by TechnSols that shows every cookie the current site has stored in your browser, with each cookie name and value on its own line. Open the page and the list appears at once, so you can see what the site keeps, copy the list as JSON, or set a test cookie to watch it appear.
Cookies are small text files a site stores in the browser, and they carry the session, the preferences, and the tracking flags a site needs. The MDN guide to Document cookie explains the same idea: a cookie is a name and a value with an expiry, and the browser sends it back with every request to that site.
This viewer is different from the live Cookie Manager tool, which keeps a full inventory of a site cookies with their categories and purposes. That tool manages the whole inventory; this one shows the cookies that are live in your browser right now, exactly as the browser sees them.
People use it to check what a site stored after they accepted a banner, to confirm a login cookie is set, to see which cookies survive a reload, or to prove what a page really keeps. It suits a developer, a tester, a privacy minded visitor, or anyone who wants to see the cookies on the site in front of them.
How To Use Cookie Viewer?
Here is how to view cookies online in three quick steps. Using Cookie Viewer is simple. There is no software to install and no account to make. Open the page, read the list, and copy or export what you find. If the site must ask before it stores anything, the Consent Banner Generator tool builds that consent banner.
Step 1: Open The Page On The Site To Check
Open this page on the site whose cookies you want to see, because a page can only read the cookies of its own site. The list shows what this site stored in this browser, and nothing from any other site appears. Open the viewer where the cookies live, and the answer is about that site.
Step 2: Read The Cookie Names And Values
Read the list: each row shows a cookie name and its value, with a count of how many cookies the site has set. Long values are shown in full when you open them, so a session token or a preference string can be read as it is stored. Press Refresh after the site sets a new cookie, and the list updates at once.
Step 3: Copy, Export, Or Set A Test Cookie
Press Copy JSON to copy the whole list, or Download JSON to save it as a file. Press Set Test Cookie to store a cookie called technsols-test for one day, then watch it appear in the list, and press Delete Test Cookie to remove it again. If the site also answers with headers, the Script Inspector tool shows those headers.
The whole check takes less than a minute, because the list is read the moment the page loads. Cookies you can see are cookies you can question, and that is the whole point of viewing them here.
Why Cookie Viewer?
A list beats a banner because a banner only asks, while a list shows what was actually stored. The viewer reads the cookies the browser holds right now, so an accepted banner that stored five cookies shows five rows. If the site loads outside code that sets its own cookies, the Header Checker tool lists those outside scripts.
The reason cookies matter is that they travel: the browser sends them back with every request, so the server knows the session, the preferences, and the flags on each visit. The MDN page on HTTP cookies shows the same point from the other side: the value lives on the document object, and any script on the page can read it.
Every Cookie Is Named Plainly
A cookie list in developer tools hides behind panels and tabs, and a visitor who never opens them never sees what is stored. The viewer puts each name and value on its own line in plain text, so a cookie called session or tracking is visible to anyone, not only to developers who know where to look.
A Test Cookie Proves The Viewer Works
A viewer that shows nothing leaves a doubt: is the site clean, or is the viewer broken? Setting a test cookie answers it: press the button, refresh the list, and the test cookie appears. Delete it again and it disappears. The round trip proves the list is live, and an empty list after that means the site really set nothing.
The Count Shows The Scale At Once
One cookie is a session; forty cookies is a tracking stack, and the count tells you which one you are looking at before you read a single name. The viewer shows the count at the top, so the scale of the storage is clear in one glance. If the count must be checked against the page search tags, the User Agent Parser tool builds those tags.
What Can You Do With Cookie Viewer?
A cookie viewer fits any job where a site stores cookies in the browser. These are the jobs this viewer handles best.
Check What A Banner Really Stored
A consent banner promises to store only what you allowed, and the viewer checks the promise: accept the banner, open the viewer, and read the list. If a marketing cookie appears after you refused marketing, the banner is not keeping its word. If the page must be checked another way, the Meta Tags Generator tool shows the browser that loaded it.
Confirm A Login Cookie Is Set
A login that fails silently often fails because the session cookie never landed, and the viewer shows whether it did. Sign in, open the viewer, and look for the session cookie by name. If it is missing, the login never completed; if it is there, the fault lies somewhere else, and the search is narrower.
See Which Cookies Survive A Reload
A cookie that survives a reload is persistent, and one that vanishes was a session cookie that lived only while the tab was open. Reload the page and read the list again: the cookies that are still there are the persistent ones, and the ones that are gone were never meant to last. That difference matters when a setting keeps coming back.
Quality And Settings
The viewer reads document.cookie for the current site, splits it into name and value pairs, and shows each cookie with its value and a count of the whole list. The list copies and downloads as JSON, a test cookie can be set for one day and deleted again, and the list refreshes on demand. If the viewer must sit beside the site search tags, the JSON Formatter tool builds those tags for the page.
- Every cookie for this site, with its name and value.
- Live count of how many cookies the site has set.
- Copy the whole list or download it as JSON.
- Set a test cookie for one day to prove the list is live.
- Delete the test cookie again with one click.
There are no other settings to learn, because the list is the whole tool. Open the page, read the cookies, and copy or export what you find.
How Cookie Viewer Works
The viewer reads document.cookie when the page loads and splits the string on its separators into name and value pairs, then shows each pair as a row. The test cookie is written with an expiry one day ahead and the path set to the whole site, so it appears in the list until it is deleted or expires. If a cookie value must be read as structured data, the Robots File Generator tool formats that JSON so it reads clearly.
Two limits are worth knowing. The viewer sees only the cookies JavaScript can read: HttpOnly cookies are invisible on purpose, because the browser withholds them from scripts to protect sessions. It also sees this site only, because the same origin policy stops any page from reading another site cookies.
Privacy
Everything you view stays in your browser. The cookies are read on your own computer, and nothing you see is uploaded to a server, stored, or shared with anyone. The test cookie is written in your own browser too, and it is deleted when you press the button or when its one day expiry passes.
Because no account is needed, there is no name, email, or history tied to what you view. Closing the tab ends the session, and the browser clears the input from memory. That is the same protection on every tool here: your work stays yours, and nothing about it is kept, shared, or sold.
Tips
A few habits make Cookie Viewer work smoother, whether this is your first check or your fiftieth.
- Open the viewer on the site itself, not on another site.
- Set a test cookie first when the list is empty, to prove it is live.
- Press Refresh after accepting a banner, so new cookies appear.
- Export the JSON before you delete anything you may need.
- Remember that HttpOnly cookies never appear, by design.
When the list is read, you know what the site keeps. If the site also needs a crawl file for search engines, the Meta Description Checker tool builds that robots file.
More Tools For The Same Job
These tools handle the same kinds of jobs: reading cookies, headers, and pages.
- Cookie Inventory Manager: lists the cookies a site has stored.
- Cookie Consent Banner Generator: builds the banner that asks before storing.
- Third Party Script Inspector: lists the outside scripts a page loads.
- HTTP Header Checker: shows the response headers a site sends back.
- User Agent Parser: parses any user agent string you paste in.
- HTTP Status Code Checker: checks the status code a page returns.
- Meta Tags Generator: builds the meta tags a page needs for search and sharing.
- JSON Formatter: formats raw JSON so it reads clearly.
- Meta Description Length Checker: checks the length of a page description.
- IP Address Lookup: looks up the address a connection comes from.
FAQ
Common questions about viewing cookies, answered plainly.
Is Cookie Viewer by TechnSols Free?
Yes, Cookie Viewer by TechnSols is completely free to use, with no account, no sign-up, and no usage limit. You can view the cookies on any site as often as you like, and everything is read in your browser, so nothing is uploaded or stored anywhere.
Why Do Some Cookies Not Appear?
Cookies marked HttpOnly are invisible to JavaScript on purpose, because the browser withholds them from scripts to protect sessions and logins. The viewer can only show the cookies JavaScript can read, so a session cookie set with that flag will not appear here, even though the browser still holds it.
Can I See Another Site Cookies?
No, the same origin policy stops any page from reading another site cookies, so this viewer shows only the cookies of the site it runs on. That is a browser safety rule, not a limit of this tool, and no browser tool can read cookies that belong to a different origin.
What Is A Test Cookie?
A test cookie is a harmless cookie this tool writes in your browser, called technsols-test, with a one day expiry, so you can watch the viewer list update. Press Set Test Cookie to store it, press Refresh to see it, and press Delete Test Cookie to remove it again when you are done.
Do Cookies Stay After I Close The Tab?
Session cookies vanish when the tab closes, while persistent cookies stay until their expiry date passes or until they are deleted. Reload the page and read the list again to see which ones survived, because the ones still listed are the persistent ones, and the missing ones were session only.
Open the page, read the cookies, and copy or export what you find. Cookies you can see are cookies you can question, and that is the whole point of viewing them here.