Enabling third-party cookies requires adjusting privacy settings in your browser—the exact steps depend on Chrome, Safari, Firefox, or Edge.
A site tells you third-party cookies are blocked, and a feature won’t load. Enabling third-party cookies in a browser takes about thirty seconds once you know which menu your browser hides them in, and the setting lives in a different spot on every major browser. The right toggle gets the site working again without changing how everything else behaves.
Why Would You Need To Enable Third-Party Cookies?
Some websites rely on third-party cookies to let you sign in with a Google or Facebook account, load embedded checkout forms, or launch inline editors. When your browser blocks them, those features silently break instead of working. You’ll notice it when:
- A sign-in button redirects in a loop without logging you in
- An embedded payment or support widget stays blank or spins endlessly
- An online document editor or image tool shows an error at launch
- A corporate single sign-on portal rejects each attempt
Enabling third-party cookies for just the site you’re on often fixes the problem without changing how your browser handles every other page.
How Browsers Handle Third-Party Cookies
Every major browser places the toggle in a different menu, but the goal is the same—letting one site use cookies set by another site when a feature requires it. The table below shows exactly where each browser puts the setting and what to change.
| Browser | Settings Path | What To Change |
|---|---|---|
| Chrome (Desktop) | Settings → Privacy and security → Third-party cookies | Choose “Allow third-party cookies” or add a site exception |
| Chrome (iPhone / iPad) | iOS Settings → Chrome | Turn on “Allow Cross-Website Tracking” |
| Safari (Mac) | Safari → Settings → Privacy | Uncheck “Prevent cross-site tracking” |
| Safari (iPhone / iPad) | Settings → Safari → Privacy & Security | Turn off “Prevent Cross-Site Tracking” (and “Block All Cookies” if on) |
| Microsoft Edge | Settings → Cookies and site permissions → Cookies and data stored | Check “Allow sites to save and read cookie data” and uncheck “Block third-party cookies” |
| Firefox | Settings → Privacy & Security → Enhanced Tracking Protection | Choose “Standard” or add the site to “Manage Exceptions” |
| Chrome site exception | Settings → Privacy and security → Third-party cookies → Sites allowed | Add the domain; use [*.]domain.com to include subdomains |
Step-By-Step For Each Browser
Each browser uses a slightly different settings path. Below are the exact menu names and toggles for Chrome, Safari, Edge, and Firefox.
Google Chrome (Desktop)
Open Chrome and click the three-dot menu in the top-right corner. Go to Settings → Privacy and security → Third-party cookies. You have two choices:
- Allow third-party cookies enables them globally, which is the quickest route if you trust the sites you visit.
- Keep the default block and add an exception under Sites allowed to use third-party cookies → Add. Enter the domain, using the
[*.]prefix if subdomains also need access (e.g.,[*.]google.comcovers accounts.google.com and mail.google.com in one entry).
Chrome’s official documentation on third-party cookies calls this the only reliable settings path for desktop.
Google Chrome On iPhone And iPad
Chrome on iOS doesn’t have its own cookie toggle inside the app. Open the iPhone or iPad Settings app, scroll down to Chrome, and turn on Allow Cross-Website Tracking. This lets Chrome treat third-party cookies from that site as if they came from the site itself.
Safari (Mac)
Open Safari and go to Safari → Settings (or Preferences on older macOS versions) → Privacy. Uncheck Prevent cross-site tracking. If the site still doesn’t load after reloading, also uncheck Block all cookies in the same panel. Close the settings window—Safari saves changes automatically.
Safari (iPhone And iPad)
Open the Settings app and scroll to Safari. Under Privacy & Security, turn off Prevent Cross-Site Tracking. If you see Block All Cookies turned on, turn that off too. Reload the site in Safari and the missing feature should appear.
Microsoft Edge
Click the three-dot menu in Edge and open Settings → Cookies and site permissions → Cookies and data stored. Make sure Allow sites to save and read cookie data (recommended) is on. Below that, uncheck Block third-party cookies if it’s enabled. Edge shares Chrome’s underlying engine, so the behavior is identical once the setting is changed.
Mozilla Firefox
Open Firefox and click the menu button → Settings → Privacy & Security. Under Enhanced Tracking Protection, select Standard instead of Strict or Custom. If you prefer to keep Strict mode for most sites, click Manage Exceptions under Cookies and Site Data and add the site’s domain. Firefox’s official support emphasizes per-site permissions rather than a single global toggle.
What To Check If The Setting Doesn’t Work
Changing the toggle is usually enough, but sometimes a second layer of privacy protection or a stale session keeps the site from loading. The table below lists the most common hang-ups and the thing that clears each one.
| Problem | Likely Cause | What To Try |
|---|---|---|
| Site still broken after changing the setting | Old cached cookies are overriding the new rule | Clear browser cache and cookies, then reload the page |
| Setting reverted after restarting the browser | A privacy extension or OS-level override reapplied the block | Check tracking-prevention extensions and disable them for that site |
| Chrome exception doesn’t take effect | Wrong domain format in the exceptions list | Use [*.]domain.com to cover all subdomains |
| Safari keeps blocking after you uncheck one option | Both “Prevent cross-site tracking” and “Block all cookies” are still active | Verify that both settings are disabled in Safari’s Privacy panel |
| Firefox ignores the change | Enhanced Tracking Protection is set to a stricter profile | Switch to “Standard” or add the site to the exceptions list |
| Sign-in still fails after enabling cookies | The site’s session token expired while cookies were blocked | Log out, close the tab, open a new window, and log back in |
The Settings To Confirm Before You Close The Tab
When you’ve changed the toggle, reload the site and check whether the missing feature loads. If it does, you’re done. If it doesn’t, run through these three checks:
- Did the setting stick? Open the same settings panel and confirm the toggle is still in the right position. Some browsers revert after a restart if an extension or corporate policy overrides the change.
- Does the site need a fresh session? Log out, clear the tab, and log back in. A stale login token can still block access even after cookies are allowed.
- Is there a second privacy layer? Safari and Firefox both have two separate controls that affect cross-site cookies. Disabling one but not the other leaves the block in place.
Once those three boxes are checked, the site should load the feature that brought you here.
References & Sources
- Google Chrome Help. “Manage cookies in Chrome.” Official documentation covering third-party cookie settings and site exceptions for desktop Chrome.