JavaScript Navigator cookieEnabled Property

What You’ll Learn

navigator.cookieEnabled is a read-only Boolean that tells you whether cookies are enabled. Learn the MDN check pattern, UI messaging, limits of the flag, five examples, and try-it labs.

Introduction

Many sites use cookies for sessions, preferences, and consent. If the user (or browser) blocks cookies, features that depend on them can fail in confusing ways.

navigator.cookieEnabled gives you a simple Boolean answer: are cookies enabled right now? MDN: when it is false, the browser does not support cookies or is blocking them from being set.

Understanding the cookieEnabled Property

Think of cookieEnabled as a traffic light for cookie storage at the browser level. You read it once (or when you need to warn the user) — you never assign to it.

• true — cookies appear enabled for normal use.
• false — cookies unsupported or blocked — show a clear message.
• Read-only — part of the HTML Navigator interface.
• Baseline — Newly available across modern browsers (MDN, since Sept 2024).

📝 Syntax

General form of the property:

navigator.cookieEnabled

Value

• A Boolean indicating whether cookies are enabled.

Common patterns

// MDN pattern:
if (!navigator.cookieEnabled) {
  // The browser does not support or is blocking cookies.
}

// Positive branch:
if (navigator.cookieEnabled) {
  console.log("Cookies look enabled");
}

Examples Gallery

Examples follow MDN navigator.cookieEnabled patterns. Prefer Try It Yourself to inspect your browser. Use View Output for expected messaging.

console.log(navigator.cookieEnabled);

true
(or false if cookies are blocked)

if (!navigator.cookieEnabled) {
  console.log("Cookies unsupported or blocked");
} else {
  console.log("Cookies look enabled");
}

Cookies look enabled

const msg = navigator.cookieEnabled
  ? "Cookies are enabled — preferences can be saved."
  : "Cookies are blocked — some features may not work.";
console.log(msg);

Cookies are enabled — preferences can be saved.

const lines = [
  "value: " + navigator.cookieEnabled,
  "typeof: " + typeof navigator.cookieEnabled
];
console.log(lines.join("\n"));

value: true
typeof: boolean

function cookieStatus() {
  if (!navigator.cookieEnabled) {
    return { ok: false, reason: "cookieEnabled-false" };
  }
  const key = "ctf_cookie_test";
  document.cookie = key + "=1; path=/; max-age=60";
  const stored = document.cookie.split("; ").some((c) => c.indexOf(key + "=") === 0);
  // cleanup
  document.cookie = key + "=; path=/; max-age=0";
  return stored
    ? { ok: true, reason: "enabled-and-writable" }
    : { ok: false, reason: "write-failed" };
}

console.log(JSON.stringify(cookieStatus()));

{"ok":true,"reason":"enabled-and-writable"}
(or a failure reason if cookies are blocked)

🚀 Common Use Cases

• Login / session warnings — tell users cookies are required before they submit.
• Preference storage — fall back to localStorage or in-memory state when cookies are off.
• Consent / cookie banners — adjust messaging when the browser already blocks cookies.
• Checkout / cart — surface a clear error instead of a silent empty cart.
• Diagnostics — include cookieEnabled in support debug panels.

📝 Notes

• Baseline Newly available (MDN, since September 2024).
• Not Deprecated, Experimental, or Non-standard — no status banner required.
• Read-only Boolean on Navigator.
• true does not guarantee every cookie attribute (for example SameSite=None) will succeed.
• Related: credentials, Window, JavaScript hub.

💡 Best Practices