Are Cookies Enabled?
This page sets a real test cookie, reads it back and deletes it, then does the same with localStorage, sessionStorage and IndexedDB. You get a clear yes or no for each, a hint about how your browser treats third-party cookies, and steps to turn cookies on.
Last updated:
Details
- Status
- Waiting for test…
Third-party cookies hint
Detecting your browser…
A single website cannot fully measure third-party cookies without loading another domain, which this site never does. This is your browser's documented default behaviour.
How to enable cookies
- Open the three-dot menu (⋮) > Settings > Privacy and security.
- Click Site settings > Additional content settings > On-device site data (older versions: Cookies and site data).
- Choose Allow sites to save data on your device and remove the site from Not allowed to save data.
- For embedded logins or widgets, open Third-party cookies and either allow them or add the site under Allowed to use third-party cookies.
- Reload the page.
Shortcuts: chrome://settings/content/siteData and chrome://settings/cookies. Incognito windows block third-party cookies by default.
- Menu (⋯) > Settings > Cookies and site permissions (newer: Privacy, search, and services > Site permissions).
- Click Manage and delete cookies and site data (or Cookies and site data).
- Turn on Allow sites to save and read cookie data.
- Check the Block list for the site, and turn off Block third-party cookies only if an embedded service needs it.
- Reload the page.
Shortcut: edge://settings/content/cookies. Tracking prevention set to Strict can also break embedded logins.
- Menu (☰) > Settings > Privacy & Security.
- Under Enhanced Tracking Protection, choose Standard. If you use Custom, make sure Cookies is not set to All cookies.
- Under Cookies and Site Data, click Manage Exceptions and remove any block for the site (or add it as Allow).
- Reload the page. For a single site you can also click the shield icon and turn protection off.
Standard mode uses Total Cookie Protection: third-party cookies work but are kept in a separate jar for each site.
- Choose Safari > Settings > Privacy.
- Untick Block all cookies.
- Leave Prevent cross-site tracking on unless an embedded login keeps failing.
- Reload the page.
Safari always blocks third-party cookies; sites can ask for access with the Storage Access API.
- Open the Settings app > Apps > Safari (older iOS: Safari).
- Find Block All Cookies (in Privacy & Security, or under Advanced on newer versions) and turn it off.
- Optionally turn off Prevent Cross-Site Tracking for a stubborn embedded login, then turn it back on later.
- Return to Safari and reload.
Safari's switch only affects Safari. Chrome, Firefox and Edge on iPhone have their own privacy settings inside each app.
- In Chrome, tap ⋮ > Settings > Site settings.
- Tap On-device site data (or Cookies) and turn it on.
- Tap Third-party cookies and pick the option you need, or add an exception for the site.
- Reload the page.
- Tap the menu (☰) > Settings > Browsing privacy (or Privacy and security).
- Turn on Allow cookies / Accept cookies; allow third-party cookies only if needed.
- Check that Smart anti-tracking is not blocking the site.
- Reload the page.
Labels vary by version; search Settings for "cookies" if you can't find them.
- Brave: click the lion icon (Shields). Under Cookies, choose Block cross-site cookies or Allow all, not Block all.
- Brave defaults:
brave://settings/shields> Block cookies. - Opera:
opera://settings/cookiesandopera://settings/content/siteData. - Reload the page.
How to use the Are Cookies Enabled?
- Open the page: the tests run automatically and finish in under a second.
- Read the big result: green means first-party cookies work; red means they are blocked for this site.
- Check the storage cards to see whether localStorage, sessionStorage and IndexedDB are available.
- Read the third-party cookie hint if an embedded login, chat or video is failing on another site.
- Follow the steps for your browser, reload, and press Run test again to confirm the fix.
What this cookie test checks
Many browsers expose a navigator.cookieEnabled flag, but it only reflects the main setting. Privacy extensions, per-site blocks and strict modes can leave the flag at true while quietly throwing cookies away. So this page does what a real website does: it writes a short-lived cookie named ftc_cookie_test with SameSite=Lax, checks that document.cookie returns it, and then deletes it with max-age=0. It repeats the idea for the other storage types sites rely on.
| Storage | Lifetime | Sent to the server? | Typical size limit | Used for |
|---|---|---|---|---|
| Cookies | Until the expiry date, or the browser session | Yes, with every request to that site | About 4 KB per cookie (RFC 6265 asks browsers to support at least 4,096 bytes) | Logins, carts, consent choices, security tokens |
| localStorage | Until cleared by the user or site | No | About 5 MB per site in most browsers | Settings, drafts, offline data |
| sessionStorage | Until the tab is closed | No | About 5 MB per site | Multi-step forms, one-tab state |
| IndexedDB | Until cleared (may be evicted when disk is low) | No | A share of free disk space | Web apps, offline mail and documents |
First-party vs third-party cookies by browser
| Browser | First-party cookies | Third-party cookies by default |
|---|---|---|
| Chrome | Allowed | Allowed in normal windows (as of 2025); blocked in Incognito |
| Edge | Allowed | Allowed, except known trackers blocked by Tracking prevention |
| Firefox | Allowed | Partitioned per site (Total Cookie Protection) |
| Safari, all iPhone/iPad browsers | Allowed (script-set cookies may expire after 7 days) | Blocked (Intelligent Tracking Prevention) |
| Brave | Allowed | Blocked by Shields |
Browser vendors change these defaults from time to time; the table reflects their documented behaviour as of 2025.
Fixing "cookies are disabled" errors
- Check per-site lists first. Chrome, Edge and Firefox can block one site even when cookies are on globally.
- Try a private window without extensions. If the test passes there, an extension is the cause.
- Login loops on embedded sign-ins (a payment or single sign-on window inside another site) usually mean third-party cookies are blocked. Allow them for that one site rather than everywhere.
- Clearing cookies fixes corrupted sessions but logs you out of sites; it does not disable cookies.
- Managed devices at work or school can enforce cookie policies that you cannot change.
Frequently asked questions
How does this test check if cookies are enabled?
It sets a cookie named ftc_cookie_test on this site with JavaScript, reads document.cookie to see whether it was stored, then deletes it. It also reports the navigator.cookieEnabled flag, but the real write-and-read result is what counts, because some blockers leave the flag true while silently dropping cookies.
What is the difference between first-party and third-party cookies?
A first-party cookie belongs to the site in your address bar. A third-party cookie belongs to a different domain loaded inside the page, such as an embedded widget, ad or sign-in frame. Most browsers now block or partition third-party cookies by default while keeping first-party cookies on.
Can this page test third-party cookies exactly?
Not fully. A true test needs a second domain that sets a cookie inside a frame, and this site does not load other domains for privacy reasons. Instead it shows what your browser does by default (for example Safari blocks them, Firefox partitions them) and which settings to check.
Why do websites need cookies?
Cookies keep you logged in, remember your cart, language and consent choices, and protect forms against forgery. Without first-party cookies, most logins and checkouts fail or loop back to the sign-in page.
How do I enable cookies on an iPhone?
Open Settings, tap Apps then Safari (or Safari directly on older iOS), and make sure Block All Cookies is turned off. It sits in the Privacy & Security section or, on newer iOS versions, under Advanced. Prevent Cross-Site Tracking can stay on; it only limits third-party cookies.
What are localStorage and sessionStorage?
They are simple key-value stores that sites use to save settings in your browser. localStorage stays until it is cleared; sessionStorage is wiped when you close the tab. Blocking cookies in most browsers blocks these too.
Does this test read or upload my cookies?
No. It only counts how many cookies this site can see, never shows their values, removes its own test cookie and test keys immediately, and sends nothing to any server.
Are all the tools on FreeToolCabin tested for quality and accuracy?
Yes! Every tool on our site undergoes automated Q/A testing in real browser environments to ensure high precision, correct output, and zero errors. If you happen to spot a bug or have a suggestion, please contact us at [email protected] and our team will review it right away.