Firefox accepts cookies by default, so if a site tells you cookies are disabled, the fix is almost always in Settings → Privacy & Security, where either the "Strict" tracking protection level or a stray per-site block is doing the work. The steps differ by version: Firefox 103 and later, released July 2022, shipped the desktop cookie settings in their current form, with Total Cookie Protection switched on for every user in version 103 and above. Everything below assumes that menu layout.
Manage cookies from the Privacy & Security panel, not from a toolbar button. Firefox keeps two separate lists that look similar: one blocks cookies for named sites, the other blocks them for all sites except named ones. Choosing the wrong list produces the opposite of what you intended.
On desktop, open the menu button (three horizontal lines, top right), choose Settings, then Privacy & Security in the left column. Scroll to the Cookies and Site Data block. The default radio button reads "Allow pages to store cookies and site data," and if it is already selected, cookies are on and the website's warning is wrong or refers to a third-party cookie it cannot reach.
On Android, tap the three-dot menu, choose Settings, then Advanced, then Cookies; the toggle at the top is the master switch, and it sits at the same level as the tracker-blocking control. On iOS, the path is Settings, then Data Management, because Firefox for iPhone stores cookie handling under site data rather than privacy.
Check the "Manage Exceptions" list before you change any global setting. A site added to the Block list there overrides the Allow default, and clearing that one entry fixes the site without loosening protection everywhere else. The same panel's "Clear Data" button also wipes site data for every site, so leave it alone until you have the exception list sorted.
How to Enable Cookies in Firefox Desktop in Seven Steps
The desktop sequence takes about forty seconds on a fresh profile and roughly two minutes when you are also auditing the exception lists. Work through it in this order, because each step closes off a cause the next one would otherwise mask.
1: Open the menu button at the top right, then choose Settings. On macOS the same item sits under the Firefox menu as Settings, and the keyboard shortcut Ctrl+, (Cmd+, on Mac) opens it directly. 2: Select Privacy & Security in the left sidebar. The page loads three blocks: Enhanced Tracking Protection, Cookies and Site Data, and Passwords. 3: Under Cookies and Site Data, confirm the "Allow pages to store cookies and site data" radio button is selected. Firefox ships with it selected, so a wrong choice here means someone changed it or a policy file did. 4: Click "Manage Exceptions" and read the Block column line by line. Remove the site you are trying to fix with the Remove button, then click Save Changes. 5: Return to the site and reload with Ctrl+F5 (Cmd+Shift+R on Mac) to bypass the cached page that may still show the old cookie warning. 6: If the site still fails, set Enhanced Tracking Protection to Standard for that site using the shield icon in the address bar, then reload again. 7: As a last resort, scroll up and change the global Enhanced Tracking Protection level from Strict to Standard. Strict is the level most often responsible for third-party cookie failures on embedded checkout and login frames.
Failure handling matters more than the happy path here. If the radio button snaps back to a blocking option after you save, an enterprise policy is enforcing it: type about:policies in the address bar and check the Active tab for a Cookies entry, which only a system administrator can remove. If the settings page itself refuses to load, start Firefox in Troubleshoot Mode via Help → Troubleshoot Mode to rule out an extension rewriting privacy preferences.
One timing detail from Mozilla's own documentation catches people out. Firefox writes preference changes to prefs.js when the browser closes cleanly, so force-quitting Firefox right after you flip the radio button can discard the change. Wait a few seconds before closing, or verify the setting persists after a restart before telling anyone the fix is done.
What the "Strict" Tracking Protection Level Actually Blocks
Strict mode applies Mozilla's full tracker list and also strips known tracking parameters from URLs, but the cookie consequence is narrower than most guides admit. Firefox does not delete first-party cookies in Strict mode; it blocks cookies and storage set by domains on its Disconnect-based tracker list, which covers most advertising and analytics networks. A site that sets its own session cookie keeps working.
The failure case that generates most "enable cookies" messages is an embedded login or payment frame from a third-party domain that happens to sit on the tracker list. Retail checkout pages built on separate payment domains, single sign-on widgets, and comment systems are the classic examples. The page's own JavaScript asks for a cookie, gets nothing, and displays the generic error even though your cookie setting is fine.
Standard mode blocks only cross-site tracking cookies and leaves everything else alone. That is the right working level for most people who need a site to function, and Mozilla's own support pages describe Standard as the default for new installs. Custom mode lets you keep all third-party cookies while still blocking trackers, which is a reasonable middle option for a shared machine.
The cost of loosening the level is measurable in page weight and privacy, not just principle. Switching from Strict to Standard lets cross-site cookies from trackers outside the strict list through, which on news sites typically means more advertising requests per page; the exact count varies by site and cannot be pinned to a single figure, so check the shield icon's report on the site you care about rather than trusting a generic number.
Total Cookie Protection and Its Exception for Embedded Content
Total Cookie Protection is the feature most likely to be blamed for cookie errors it did not cause. Since Firefox 103, it stores every site's cookies in a separate cookie jar keyed to the top-level site, so a tracker loaded on two different sites gets two unrelated cookies and cannot link them. It is not a switch you turn on anymore, and the old preference name for it no longer controls anything.
The jar model has one real edge case: a third-party embedded service that needs to recognise you across different top-level sites. A support chat widget, a federated login button, or a cross-domain payment flow may legitimately need that continuity, and under Total Cookie Protection it gets a fresh jar per site. Firefox ships a built-in exception list for known breakage, and Mozilla updates it with browser releases rather than through a setting.
You cannot exempt a single site from Total Cookie Protection in current Firefox versions. The Privacy & Security panel no longer offers that control, and documentation that tells you to untick a Total Cookie Protection checkbox is describing a version that stopped existing when the feature became unconditional. If an embedded service breaks, the working levers are the per-site tracking protection toggle and the cookie exception list, not a jar-level switch.
Watch for the misleading symptom where clearing cookies fixes a site for one visit only. That pattern points to Total Cookie Protection separating the embedded frame's storage from the top-level page each time, not to a disabled cookie setting, and no amount of re-enabling cookies will change it. Report the breakage through the shield icon's panel if the built-in exception list has not caught up.
Firefox Cookie Settings on Android and iPhone Versus Desktop
Mobile Firefox hides the same controls in different places and uses different labels, which is why desktop instructions fail on phones. Both mobile versions default to accepting cookies, and both let you clear them, but only Android exposes a full exception list comparable to the desktop one.
| Control | Desktop (Settings → Privacy & Security) | Android (Settings → Advanced → Cookies) | iPhone (Settings → Data Management) |
|---|---|---|---|
| Master cookie switch | "Allow pages to store cookies and site data" radio | Cookies toggle at top of screen | Site data stored by default, no master cookie radio |
| Per-site block list | Manage Exceptions, two columns | Exceptions list for sites | Exceptions list for sites |
| Tracking protection levels | Standard, Strict, Custom with per-site shield toggle | Standard and Strict, toggled in Enhanced Tracking Protection | Standard and Strict in Tracking Protection |
| Total Cookie Protection control | None since version 103 | None | None |
| Clear all site data | Clear Data button in Cookies and Site Data | Settings → Delete browsing data | Settings → Data Management → Clear data |
The table's most useful row is the first. iPhone Firefox has no master cookie radio because iOS hands cookie handling to WebKit, so the "enable cookies" instruction for that platform is really "stop blocking site data for this site in the exceptions list." Anyone following a desktop tutorial on an iPhone will hunt for a button that was never there.
Android carries a genuine advantage: its exceptions list accepts wildcard-free per-domain entries and survives browser updates, so a site you have fixed stays fixed. Desktop exceptions can be cleared en masse through the "Clear Data" dialog if you tick "Cookies and Site Data" along with site data, so untick that box when you only mean to free disk space.
Version drift explains the rest. The frequency of tracking protection updates is set by the browser release channel, and Android Firefox follows the same release numbering as desktop from version 103 onward. Confirm your exact version in Settings → About Firefox before following any menu path, because pre-103 layouts put cookie options under a single Privacy panel.
Why an Extension, Not Your Settings, Keeps Blocking Cookies
Before you touch a single radio button, rule out the add-ons. Content blockers such as uBlock Origin maintain their own blocklists and can drop cookies for specific domains regardless of what Firefox's settings say; their badge counter in the toolbar is the fastest tell. Disable the extension for the site through its own popup, not through Firefox's add-on manager.
Container tabs produce the same illusion. A site opened in a work container and then in a personal container holds two separate cookie stores, so a login performed in one looks forgotten in the other. If the site works in a normal tab and fails in a container, you found the cause and no cookie setting needs changing.
Profile-specific preferences trip up people who maintain two Firefox profiles for privacy reasons. Each profile carries its own prefs.js, so enabling cookies in one leaves the other untouched. Type about:profiles in the address bar to see which profile is active and launch the one that holds your bookmarks if the settings page looks unfamiliar.
Antivirus browser shields and parental-control suites sit outside Firefox entirely and can block cookie headers at the network layer. Test in a private window with extensions disabled: if cookies work there, the culprit is an add-on; if they still fail, the block is above the browser and the fix belongs in the security software's web-shield settings, not in Firefox.
Reading the Site Info Panel When Cookies Fail Anyway
The address bar's site info panel is the fastest diagnostic and almost never appears in cookie tutorials. Click the padlock (or the shield beside it), then "Clear cookies and site data" to see whether Firefox holds any data for the domain at all. A zero-entry list after a page load means cookies were refused at the network level, while a populated list means the site received them and chose to reject them.
Cross-reference that with the shield icon's report, which names the specific trackers blocked on the current page. If the site's own domain appears in that blocked list, a per-site toggle from the shield immediately restores function. If only third-party domains appear, the problem is the site's detection script being overzealous about a tracker it cannot reach, and the fault is not yours to fix.
The Permissions panel inside the same site info dialog sometimes carries an explicit cookie permission row on sites with policies attached; where present, set it to Allow. This row exists only in newer builds and only for sites whose response headers request it, so its absence is normal and not a sign of a broken installation.
Use Reader View as a cross-check on whether a page's cookie wall is cosmetic. If the article text loads in Reader View, the content exists and the cookie banner is blocking presentation, which means the site's script needs permission the browser is withholding rather than the site being unreachable. That distinction decides whether you keep troubleshooting or write the site off.
When Allowing Cookies Still Leaves You Logged Out
Cookies enabled plus a login that never sticks usually means the site wants a third-party cookie for its identity provider. Single sign-on flows from a different domain, social login buttons, and hosted checkout all fall in this group, and the fix is a per-site tracking protection exception on the identity domain, added after the initial page loads.
A stale cookie can also outlive a password change and hold the site in a half-logged-in state. Clear cookies for that site only through the padlock panel, reload, and sign in once; never reach for the global Clear Data button for this. Global clearing logs you out of everything and buries the real diagnosis under a pile of re-authentication.
Time-zone and system-clock errors mimic cookie failures because session cookies carry expiry stamps. If your operating system clock is more than a few minutes off, servers reject freshly minted cookies as expired, and every fix above appears to fail. Check the clock before the browser, then re-test.
On sites that demand a cookie consent choice before any cookie is set, enabling cookies in Firefox changes nothing until you click the banner. The consent record lives in the site's own storage, and Firefox's Settings panel cannot pre-answer it for you; some builds honour a Global Privacy Control signal you can enable under Privacy & Security, but whether the site respects that signal is the site's decision.
FAQ
Do I need to re-enable cookies after every Firefox update?
No. Cookie preferences live in your profile and survive updates, but a version jump can reset individual privacy toggles and re-apply default tracking protection levels. Mozilla's release notes list user-facing privacy changes per version, and the Enterprise release notes flag policy changes that can force settings. Re-check the radio button after a major update if a site suddenly fails.
Firefox says cookies are enabled but a website still says they are disabled. What now?
The site is almost certainly detecting a blocked third-party cookie rather than your first-party setting. Test in a private window with extensions off; if the site works there, an extension was blocking it. If it fails in both, set a per-site tracking protection exception using the shield icon. The site's own detection script, not your setting, is the usual culprit.
Does clearing cookies delete password manager entries too?
No. Firefox's Clear Data dialog wipes cookies and site storage without touching saved logins, which live in the Passwords block of the same panel. You will be signed out of sites, because sign-in tokens are cookies, but the stored credentials remain available. Tick the box labelled "Site settings" only if you also want to reset permissions like camera access.
Is there a keyboard shortcut to the cookie settings?
Yes, Ctrl+, opens Settings on Windows and Linux, and Cmd+, does the same on macOS. From there, Privacy & Security is one click down the sidebar. No single shortcut jumps directly to the Cookies and Site Data block, so the two-step path is the fastest route. The about:preferences#privacy URL reaches the panel directly.
Why did my exception list clear itself?
The Clear Data dialog clears saved exceptions if you tick "Cookies and Site Data" while clearing, so exceptions are not permanent unless you avoid that combination. Profile refreshes also discard them, and enterprise policy resets wipe them silently. Back up anything you care about by noting the domains you have allowed.
Can I turn off Total Cookie Protection to fix a site?
Not through a setting, because the feature has been applied on top of the jar store for every user since version 103 and the old preference no longer controls it. Mozilla maintains a shipped exception list for known breakage, updated with browser releases rather than user toggles. Report the site through the shield panel so it can be considered for that list.
Do cookies work the same way in Firefox Focus and private windows?
No. Firefox Focus discards cookies when you end the session, and private windows isolate them from your regular profile, so a site that works in private but not normal means something in your normal profile's extension or exception list is blocking it. Use the private-window test as a diagnostic, not as a permanent fix. Focus aims at deliberate cookie use, not persistent sign-in.
What happens to cookies if I synchronise Firefox across devices?
Firefox Sync does not transfer cookies. It moves bookmarks, history, passwords, tabs, and preferences, but a login on your laptop sets a cookie only on that machine, so sites will ask you to sign in again on a second device. Cookie exceptions set in the settings panel travel with synced preferences only where Mozilla includes that preference in the sync set, which site exceptions generally are not.