TechnSols
Advertisement

Cookie Inventory Manager

Manage your cookie inventory online for free. See this site's cookies and scan pasted code for cookie-setting calls, with no install and no sign-up.

Be the first to rate this tool

Read the current site cookies, or scan pasted code, then categorise and export.

What Is Cookie Inventory Manager?

Cookie Inventory Manager is a free online tool by TechnSols that lists the cookies a site sets, so you can see them, name them, and sort them into categories. It reads the cookies of the site you open it on, and it scans pasted code for cookie-setting calls, then builds one inventory table you can filter and export.

Advertisement

A cookie is a small piece of data a site stores in the visitor browser, and a site that does not know its own cookies cannot write an honest cookie policy or a honest banner. The inventory is the first step of every cookie job: list them, name the purpose of each one, and sort them into necessary, preferences, analytics, and marketing. The MDN cookie guide explains how cookies work, including the flags that control who can read them.

One honest limit matters most. This tool can only read the cookies of the current site, and only the ones JavaScript is allowed to see. Cookies marked HttpOnly are hidden from JavaScript by design, and cookies from other sites are hidden by the browser itself, so no tool on a web page can read them. If you open this tool on your own site, you see your own site cookies. If the site needs a banner for those cookies, the Cookie Consent Banner builds it from a form.

People use it to audit a site before writing its cookie policy, to check what a new plugin added, to compare the cookies before and after a redesign, or to build the inventory a GDPR checklist asks for. It suits a first audit, a yearly review, or a handover where nobody remembers which cookies the site sets. The export it writes is a CSV file, so you can keep it with the project.

How To Use Cookie Inventory Manager?

Here is how to manage a cookie inventory online in three quick steps. Using Cookie Inventory Manager is simple. There is no software to install and no account to make. Read the current cookies, scan pasted code, and export the list. If the cookies come from external scripts, the Script Inspector lists those scripts and their domains.

Step 1: Read The Current Site Cookies

Press Read My Cookies to list the cookies this page can see, with each name, its value length, its domain, its path, and its expiry where the browser shows it. The list holds only the cookies JavaScript can read: HttpOnly cookies are hidden by design, and the tool says so plainly instead of pretending the list is complete. Count the rows, and note the names you do not recognise.

Step 2: Scan Pasted Code For Cookies

Paste the page HTML or a JavaScript file into the code box and press Scan Code. The tool lists every cookie-setting call it finds: document.cookie assignments, Set-Cookie headers in sample responses, and known analytics and advertising calls, each with the line it came from. A cookie the code sets but the live list misses is usually HttpOnly, or set on a path this page never visits.

Step 3: Categorise And Export

Set a category for each cookie, necessary, preferences, analytics, or marketing, and add a short purpose note, such as keeps the visitor signed in or measures page visits. Filter the table by category to check the balance, then press Export CSV to download the inventory. If the inventory feeds a compliance check, the GDPR Compliance Checklist starts with the same inventory step.

The whole job takes a few minutes. A file built from a form is ready to use, and the steps above are the same every time.

Why Cookie Inventory Manager?

A cookie policy that guesses its cookies is a policy that lies to visitors and to regulators. The inventory fixes that: it lists the real cookies, with their real names and purposes, so the policy and the banner describe the site as it is. A site that adds a chat widget or an analytics tag without updating the inventory will publish a policy that misses the new cookies, and the first audit will find them. If the policy needs writing, the Privacy Policy Template writes it from the inventory.

The rules it follows come from how browsers work. The All About Cookies explains cookies in plain words, including why some are needed for the site to work and why others need consent first. This tool applies that split to the inventory: necessary cookies are always on, and the rest need a choice before they are set.

Real Names, Not Guesses

An inventory built from memory misses the cookies a plugin sets quietly. This manager reads the live cookies and the pasted code, so the names in the table are the names the browser really sees. The Consent Log Viewer reads the consent records for the cookies listed here.

Categories Visitors Understand

A cookie named _ga means nothing to a visitor, but analytics that measures visits does. The category and purpose note turn each row into a sentence a visitor can read, and the policy and the banner can then use the same words, so the site speaks with one voice.

Honest About What It Cannot See

A tool that claims to list every cookie is lying, because HttpOnly cookies are hidden from JavaScript. This manager says which cookies it cannot see and why, and suggests the server log or a browser scan for the rest. An honest inventory with a known gap beats a complete looking list that is wrong.

What Can You Do With Cookie Inventory Manager?

A cookie inventory fits any site that sets cookies. These are the jobs this manager handles best.

Audit A Site Before A Policy

Read the cookies, scan the code, and categorise the rows before writing the cookie policy. The policy then names the real cookies, and the banner then offers the real categories. If the notice needs a preview, the Privacy Notice Previewer shows how it reads to a visitor.

Check What A New Plugin Added

Install the plugin, open the tool, and compare the new cookie list with the old export. A plugin that adds three marketing cookies without telling you shows up at once, and the inventory tells you what to add to the policy and the banner.

Compare Before And After A Redesign

Export the inventory before the redesign, then read it again after. Cookies that vanished were tied to the old design, and cookies that appeared belong to the new one. The two exports are the record of what changed, and the policy update follows from them.

Advertisement

Quality And Settings

The tool reads document.cookie on the current page and parses each name and value, then scans the pasted code with patterns for document.cookie assignments, Set-Cookie headers, and known tracker calls. Each row holds the name, the value length, the domain, the path, the expiry where known, the source, live or code, and the category you set. The table filters by category and by search text, and the export writes a CSV file with one row per cookie. If a value needs encoding for a link, the File Hash Generator hashes an export file to prove it has not changed.

  • Reads the current site cookies through document.cookie, live in the browser.
  • Scans pasted HTML or JavaScript for cookie-setting calls, with line numbers.
  • Says plainly which cookies it cannot see, and why HttpOnly hides them.
  • Categories and purpose notes on every row, in plain words.
  • CSV export with names, categories, and purposes, but never secret values.

There are no other settings to learn, because the inventory is a table with a filter and an export. Read the cookies, scan the code, set the categories, and export the file. If a cookie you expect is missing, check whether it is HttpOnly or set on another path, and read the server log for it.

How Cookie Inventory Manager Works

The manager reads the cookies by splitting document.cookie on semicolons and parsing each name and value pair, then it scans the pasted code line by line for cookie-setting patterns and records the line number of each match. The two lists are merged by cookie name, so a cookie found in both places shows both sources, and a cookie found only in code is marked as code only. The category and purpose you set are kept in the table, and the export writes the rows as CSV. When the export needs a format check, the JSON Validator checks the JSON form of an export.

Two limits are worth knowing. The tool can only read the cookies of the current site, and only the ones JavaScript is allowed to see, so HttpOnly cookies and other site cookies are never listed. It also scans only the code you paste: a cookie set by a script that loads at runtime, such as a tag manager, will not appear unless that script code is pasted too. For the full picture, pair this inventory with a browser scan and a server log.

Privacy

Everything you check stays in your browser. The cookies are read on your own computer, and nothing you enter is uploaded to a server, stored, or shared with anyone. Closing the tab clears the list, so the cookie names never leave your device.

Because no account is needed, there is no name, email, or history tied to what you inventory. 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 Inventory Manager work smoother, whether this is your first file or your fiftieth.

  • Read the cookies on several pages, because different pages set different cookies.
  • Paste the full page HTML, not a snippet, so the code scan sees every call.
  • Set a purpose note on every row, in words a visitor can understand.
  • Export after each audit, and keep the old exports to compare later.
  • Re-run the inventory after adding a plugin, a widget, or an analytics tag.

When the inventory is complete, compare it with the cookie policy line by line. If a link in the policy needs encoding first, the URL Encoder Decoder encodes it without mistakes.

More Tools For The Same Job

These tools handle the same kinds of jobs: cookies, consent, and privacy pages.

FAQ

Common questions about managing a cookie inventory, answered plainly.

Is Cookie Inventory Manager by TechnSols Free?

Yes, Cookie Inventory Manager by TechnSols is completely free to use, with no account, no sign-up, and no usage limit. You can inventory as many cookies as you like, and everything you check stays in your browser, so nothing is uploaded or stored anywhere.

Can It Read Another Site Cookies?

No, a browser page can only read the cookies of the site it runs on, and only the ones JavaScript is allowed to see. This tool reads the cookies of the site you open it on, and it scans pasted code for cookie-setting calls. It cannot read any other site cookies, and no browser tool can.

Why Are Some Cookies Missing?

Cookies marked HttpOnly are hidden from JavaScript by design, so document.cookie never shows them, and neither does this tool. Cookies set by the server before the page loads, and cookies from other paths or subdomains, may also be missing. A server log or a browser scan sees more than any page can.

What Does The Code Scan Find?

The code scan reads pasted HTML or JavaScript and lists every cookie-setting call it finds, such as document.cookie assignments, Set-Cookie headers in sample responses, and known analytics and advertising calls. It finds what the code says, not what the site does at runtime.

Can I Export The Inventory?

Yes, the inventory exports as a CSV file with one row per cookie: name, value length, domain, path, expiry, and category. The export holds the cookie names and the categories you set, not the secret values, so the file is safe to share with your team or an auditor.

Read the cookies, scan the code, and export the list. An inventory you can trust is the start of every cookie job, and that is the whole point of listing them first.

Follow TechnSols on Google
Add TechnSols as a preferred source to see more of our tools in Google Search.
Add to Preferred Sources
Advertisement