What Is a Cookies Enabled Test?
This tool goes further than simply checking the navigator.cookieEnabled flag your browser
reports - it actually writes a real, temporary test cookie to your browser, immediately reads it back, and
confirms whether that round trip genuinely succeeded. This matters because the basic flag can occasionally
report "enabled" even in edge cases where cookies are actually being blocked by a specific privacy setting,
extension, or third-party context - a functional test catches what a simple flag check can miss.
How to Use the Cookies Enabled Test
- Load this page - the test runs automatically the moment it loads.
- Check both readouts: the basic browser flag, and the actual functional test result.
- Click "Run Test Again" to repeat the check, useful after changing a browser cookie setting.
How It Works
This tool first reads navigator.cookieEnabled for a quick baseline. It then attempts to
genuinely write a uniquely-named test cookie using document.cookie, immediately checks whether
that exact cookie now appears when reading document.cookie back, and reports success only if
the round trip actually worked. The test cookie is deleted immediately afterward regardless of the result,
so nothing persists on your device beyond this page load.
Understanding Your Results
- Both the flag and the actual test show cookies working - cookies are fully functional in your current browser context, the expected result for most standard browsing.
- Flag says "enabled" but the actual test fails - this is exactly the scenario this tool is built to catch; some privacy extensions, strict cookie settings, or specific browsing contexts can block actual cookie writes while the basic flag still reports enabled.
- Both show cookies disabled or failing - cookies are genuinely blocked in your current browser, likely due to a privacy setting, private/incognito mode restriction, or extension.
- "Total Cookies Found" seems low - this only counts cookies visible to the current page's domain and path; it won't include cookies set by other websites, which browsers correctly keep separate.
Browser Limitations
This test can only check cookie behavior within the current page's own context - it can't test third-party cookie behavior across different sites, which many modern browsers restrict by default as a privacy protection regardless of your first-party cookie settings. A cookie working correctly here confirms first-party cookies function normally, but doesn't guarantee identical behavior for every cross-site scenario a specific website might rely on.
Common Mistakes to Avoid
- Testing in private/incognito mode and expecting persistent results - cookies often still work temporarily in private browsing, but are cleared when that session ends, which is expected behavior rather than a fault.
- Assuming a failed test means all websites will break - some sites function fine without cookies for basic browsing, though many interactive features like login and shopping carts do require them.
- Not retesting after changing a browser setting - click "Run Test Again" after adjusting any cookie-related setting to see the updated result immediately.
Frequently Asked Questions
Why test this instead of just checking navigator.cookieEnabled?
The basic flag can occasionally report "enabled" even when actual cookie writes are being blocked by a specific extension or privacy setting; an actual set-and-read test catches that gap directly.
Does the test cookie stay on my device after the test?
No, it's deleted immediately after being read back, regardless of whether the test succeeds or fails, so nothing persists beyond confirming the result.
Is the test cookie sent to any server?
No, this test only reads and writes the cookie locally within your browser using
document.cookie - nothing is transmitted anywhere.
Why does my test fail in private/incognito mode?
Some browsers restrict certain cookie behavior more strictly in private browsing modes, which can cause this test to report a failure even though standard browsing would work normally.
What should I do if cookies are actually disabled?
Check your browser's privacy or cookie settings, and consider whether any installed extensions might be blocking cookies; many websites, especially ones requiring login, need cookies enabled to function correctly.
Conclusion
A real functional test gives you more confidence than a flag alone, since it confirms cookies are actually working end to end rather than just being reported as available. For a check of your browser's other storage mechanisms, see the Web Storage Test.