How to Enable Cookies in Any Browser

Exact steps for Chrome, Safari, Edge, Firefox, Opera and Brave — on desktop and on your phone — plus what you are actually switching on.

When a site keeps telling you to enable cookies, it is not usually asking you to allow tracking. It is asking for permission to store a small piece of text that remembers you are logged in. Without it, every page load looks like a brand new visitor, so carts empty themselves and sign-in forms bounce you straight back to the sign-in screen. This guide walks through the setting in each major browser, on desktop and mobile, and explains which parts are worth leaving off.

The short version: allow first-party cookies, keep third-party cookies blocked, and add per-site exceptions when something breaks. That combination fixes almost every "cookies are disabled" message without handing your browsing history to ad networks. If you want the background on what these files actually contain first, start with our explainer on what cookies are.

What Enabling Cookies Actually Does

A cookie is a short piece of text a website asks your browser to store and hand back on the next request. Enabling cookies simply means allowing that storage. What matters is who gets to store one, because browsers treat two very different cases under the same word.

Blocking cookies outright breaks the first category along with the second, which is why sites start complaining. The useful setting is the one that separates them — and every browser below offers it, just under a different name.

Check Whether Cookies Are Already Enabled

Before changing a global setting, confirm the problem is actually cookies. A thirty-second check:

1. Open the site that is failing in a normal window — not a private one.
2. Click the icon just left of the address (a padlock, a slider, or a shield, depending on the browser) and look for "Cookies and site data".
3. If it shows cookies in use, the block is elsewhere — usually an extension. If it shows cookies blocked for this site, you have a per-site exception overriding your global setting.
4. Try the same site in a different browser. If it works there, the problem is a setting in this browser rather than the site.

Enable Cookies in Google Chrome

Chrome on Windows and macOS

1. Click the three-dot menu at the top right and choose Settings.
2. Select Privacy and security, then Third-party cookies. You can also paste chrome://settings/cookies straight into the address bar.
3. Choose Block third-party cookies in Incognito mode for the balanced setting, or Allow third-party cookies if a specific site needs them.
4. Scroll down to Sites allowed to use third-party cookies and add the one site that needs an exception, rather than loosening the rule for everything.
5. Reload the page.

Chrome no longer offers a single global switch that blocks all cookies, so if first-party cookies are failing on one site, the cause is nearly always an entry under Sites that can never use third-party cookies or a per-site permission set from the address bar icon. Google's own Chrome cookie settings page documents the current menu layout, which shifts between releases.

Chrome on Android and iPhone

1. Open Chrome and tap the three-dot menu.
2. Tap Settings, then Site settings.
3. Tap Third-party cookies and pick your preferred level.
4. On iPhone the equivalent sits under Settings › Privacy inside the Chrome app. Chrome on iOS uses Apple's rendering engine, so some cookie behaviour follows Safari's rules rather than Chrome's.

Enable Cookies in Safari

Safari on macOS

1. Open Safari and choose Safari › Settings from the menu bar (called Preferences on older macOS versions).
2. Click the Privacy tab.
3. Untick Block all cookies. This is the switch behind most "please enable cookies" messages on a Mac.
4. Leave Prevent cross-site tracking ticked. It blocks third-party tracking cookies while still letting the site you are on sign you in.

Apple's Safari privacy settings guide covers the same panel. Note that Safari's Intelligent Tracking Prevention is more aggressive than most browsers even with cookies allowed — it caps how long some script-written cookies survive, so a site may forget you after a week without you having changed anything.

Safari on iPhone and iPad

1. Open the system Settings app — not Safari itself.
2. Scroll to Apps and tap Safari. On iOS 17 and earlier, Safari sits directly in the main Settings list.
3. Scroll down to Privacy & Security.
4. Turn Block All Cookies off.
5. Leave Prevent Cross-Site Tracking on unless a specific site has broken because of it.

Enable Cookies in Microsoft Edge

1. Click the three-dot menu and choose Settings.
2. Select Cookies and site permissions, then Manage and delete cookies and site data.
3. Turn on Allow sites to save and read cookie data (recommended).
4. Leave Block third-party cookies on, and use the Allow list below it for any site that genuinely needs them.

Edge has a second setting that blocks cookies independently of the one above: Tracking prevention, under Settings › Privacy, search, and services. If it is set to Strict, sites can break even with cookies allowed. Dropping it to Balanced resolves most of those cases, and Microsoft's Edge cookie settings page lists what each level blocks.

Enable Cookies in Mozilla Firefox

1. Open the hamburger menu and choose Settings.
2. Select Privacy & Security.
3. Under Enhanced Tracking Protection, choose Standard. This allows first-party cookies and isolates third-party ones.
4. If you are on Custom, untick Cookies, or set its dropdown to Cross-site tracking cookies rather than All cookies.
5. To fix one site only, scroll to Cookies and Site Data and use Manage Exceptions.

Firefox's Standard mode has shipped Total Cookie Protection since 2022, which keeps each site's cookies in a separate jar so a tracker embedded on two different sites cannot connect the two visits. Mozilla's Enhanced Tracking Protection documentation explains what each level blocks. On Firefox for Android the same control sits under Settings › Enhanced Tracking Protection.

Enable Cookies in Opera

1. Open Settings from the Opera menu, or paste opera://settings/cookies into the address bar.
2. Under Privacy & security, open the cookies section.
3. Make sure sites are allowed to save cookie data, then choose whether to block third-party cookies.
4. Check Opera's built-in ad blocker separately — it can block the script that sets a cookie before the cookie setting ever applies. Its exception list is under Settings › Basic › Block ads.

Opera is built on Chromium, so its menus closely mirror Chrome's with Opera's own additions layered on top. The Opera site settings documentation covers the per-site permission panel.

Enable Cookies in Brave

1. Open Settings from the menu, then Privacy and security.
2. Find the cookie controls and set them to allow cookies, blocking only cross-site ones.
3. For a single site, click the Shields lion icon in the address bar and lower the shield level for that site.
4. Reload the page.

Brave blocks cross-site cookies by default and layers its own tracker blocking on top through Brave Shields. When a site misbehaves in Brave but works everywhere else, the Shields panel is almost always the cause rather than the cookie setting itself.

Allow Cookies for One Site Only

This is the setting worth learning, because it fixes the broken site without changing how the other several hundred you visit behave. Every browser keeps a per-site exception list:

Browser	Where the exception list lives
Chrome	Settings › Privacy and security › Third-party cookies › Sites allowed to use third-party cookies
Safari (macOS)	Address bar padlock › Settings for This Website
Edge	Settings › Cookies and site permissions › Manage and delete cookies › Allow
Firefox	Settings › Privacy & Security › Cookies and Site Data › Manage Exceptions
Opera	Settings › Privacy & security › Site settings › Cookies and site data
Brave	Shields icon in the address bar, per site

Add the exception, reload, and leave your global setting alone. A single allowed domain is a far smaller privacy cost than switching third-party cookies on everywhere to satisfy one checkout page.

Cookies Still Blocked? What Else to Check

If the setting looks right and the site still complains, one of these is usually responsible:

• A content blocker or privacy extension. uBlock Origin, Privacy Badger, Ghostery and most ad blockers can stop the request that sets a cookie. Disable them for that one site rather than globally.
• Private or incognito mode. Cookies work inside the session but vanish when the last private window closes, which is why "remember me" never sticks there — and why incognito is not private in the way most people assume.
• Antivirus or security suite web shields. Several suites proxy your traffic and strip cookies as part of their own tracking protection.
• A wrong system clock. Cookies carry an expiry timestamp. If your device clock is days out, the browser can treat a freshly issued cookie as already expired.
• Corporate or school device policy. Managed browsers can lock the cookie setting entirely — Chrome shows "Managed by your organisation" when this is the case.
• An old or corrupt cookie for that domain. Clear cookies for that single site, then sign in again. It is a far more targeted fix than clearing everything.

The Privacy Trade-Off You Are Making

Allowing cookies is not a neutral act, and it is worth being precise about the cost. First-party cookies mostly tell a site things it already knows: that you are you, and that you were here before. Third-party cookies are the ones that build a profile of your browsing across unrelated sites, which is the mechanism behind targeted advertising.

There is a security dimension too. A session cookie is the token that proves you are logged in, which makes it a target — stealing one is the entire point of session hijacking. That is a reason to sign out of sensitive accounts on shared machines, not a reason to disable cookies.

The Flags That Make a Cookie Safer

You do not set these — the site does — but knowing they exist explains why some cookies are riskier than others. A cookie marked Secure is only ever sent over HTTPS. One marked HttpOnly cannot be read by JavaScript, which closes off the most common theft route. The SameSite attribute controls whether a cookie travels on requests originating from other sites, which is what makes modern third-party cookie blocking possible in the first place.

What Cookie Settings Do Not Protect You From

Turning cookies off is not the privacy win it looks like, because several tracking methods never touch the cookie store at all. Browser fingerprinting identifies you from your screen size, fonts, graphics hardware and timezone — a combination stable enough to recognise you with every cookie cleared.

Then there are the storage tricks built specifically to survive a cookie clear: supercookies live outside normal cookie storage, zombie cookies rebuild themselves after deletion, and an evercookie copies one identifier into a dozen storage mechanisms at once so removing it from one restores it from the others. Our guide to how websites remember you covers the full set, and browser telemetry covers what your browser itself reports independently of any site you visit.

For a concrete picture of what your current setup exposes, run the privacy score check before and after changing your cookie settings — the difference is usually smaller than people expect, which is rather the point. Choosing a browser that defaults to sensible protection does more than any single toggle, which our best privacy browsers comparison goes into.

Frequently Asked Questions