This guide explains how to verify which cookies are actually stored in your browser while visiting your website. This is one of the most reliable ways to confirm whether a cookie is really being set on the page, instead of only relying on scan results or plugin settings.
Before you start
Before checking cookies in your browser, make sure that:
- your website is open in the browser
- you are testing the correct page
- you know whether you have already accepted or rejected consent in the cookie banner
- you use a clean session when possible, such as a private or incognito window
Testing in a clean session is important because old cookies may still be stored from previous visits.
Step 1: Open your website
Go to the page you want to test on your site.
Use the exact page where you expect cookies or tracking tools to load. For example, if you want to test analytics, embedded videos, maps, chat tools, or marketing scripts, open the page where those elements are actually present.
Step 2: Open your browser developer tools
In most browsers, you can open developer tools by right-clicking anywhere on the page and selecting Inspect.
You can also use these shortcuts:
- Chrome / Edge / Brave:
F12orCtrl + Shift + I - Mac:
Cmd + Option + I
This opens the browser inspection panel.
Step 3: Go to the Storage or Application area
Inside developer tools, look for the section that shows browser storage.
Depending on the browser, the name may be different:
- in Chrome-based browsers, open the Application tab
- in Firefox, open the Storage tab
This is the area where the browser shows cookies saved by the website.
Step 4: Open the Cookies section
In the left-side panel, find Cookies and expand it.
You will usually see one or more domains listed under it. Click the domain of the website you are testing.
The browser will now display the cookies currently stored for that domain.
Step 5: Read the cookie list carefully
You should now see a table with information such as:
- cookie name
- value
- domain
- path
- expiration date
- size
- security flags
Focus first on the cookie names, because this is the fastest way to understand what is really active in the browser.
If a cookie appears in this list, it means it has actually been stored in the browser for that domain.
Step 6: Check the website before giving consent
To understand what happens before consent, reload the page in a clean session before clicking any banner button.
Then inspect the cookie list again.
At this stage, you should verify whether only essential cookies are present, or whether optional cookies are already being set too early.
This helps you understand whether the site is behaving correctly before consent is collected.
Step 7: Accept consent and check again
Now interact with the cookie banner and accept the categories you want to test.
For example, you may accept all cookies, or only specific categories such as analytics or marketing.
After doing that, reload the page if needed and check the cookie list again.
Compare the new result with the previous one. If additional cookies appear only after consent, that usually means those scripts are being loaded after user approval.
Step 8: Reject consent and test again
To verify the opposite scenario, clear the cookies and run another test.
Open a fresh session, visit the page again, reject optional cookies from the banner, and inspect the cookie list once more.
This lets you confirm whether optional cookies remain blocked when consent is denied.
Step 9: Clear old cookies when needed
If the results seem confusing, remove stored cookies and repeat the test.
You can do this directly from the browser storage panel, or by clearing site data in your browser settings.
This is important because previously stored cookies can remain visible even if they are not being created again during the current visit.
Step 10: Compare browser cookies with your scan results
Once you have reviewed the browser cookies, compare them with the cookies detected by Cookiedad.
This helps you understand the difference between:
- cookies detected by a scan
- cookies known in your configuration
- cookies that are actually written in the browser during a real visit
A cookie may appear in a scan because it is potentially used on the site, but not appear in the browser during a specific session if the related script did not load or no consent was given.
How to understand the results
Here is the practical rule:
- if a cookie appears in the browser storage, it is really present in that session
- if a cookie does not appear there, it is not currently stored in the browser for that page and session
- if a cookie only appears after consent, it is likely tied to optional functionality
- if a cookie appears before consent and is not essential, it may need further review
Common mistakes
Checking the wrong page
Some cookies are only loaded on specific pages. Always test the page where the service actually runs.
Testing with old cookies still stored
A previous visit may leave cookies in the browser and make the result look inaccurate. Use a clean session whenever possible.
Confusing scripts with cookies
A script can load without immediately writing a cookie. The cookie list only shows what has actually been stored.
Forgetting to reload after changing consent
Some scripts only set cookies after the page reloads. If needed, reload the page and check again.
Final result
You have successfully checked which cookies are really present in the browser.
This method gives you a direct, real-world view of what your visitors’ browsers are storing and is one of the best ways to verify whether your cookie setup is working as expected.