Blocking third-party cookies in Chrome is one of the most effective ways to reduce cross-site tracking, but it can also affect sign-ins, embedded content, and shopping carts.
This guide explains exactly where the setting is, what it does, and what to expect as Chrome’s privacy model changes in 2026.
What third-party cookies are
Cookies are small files that websites store in your browser to remember preferences, sessions, and activity.
First-party cookies are set by the site you visit directly, while third-party cookies come from another domain, often an advertiser, analytics provider, or embedded service.
Third-party cookies are widely used for ad measurement, cross-site personalization, and tracking users across multiple websites.
They are also the reason many privacy-focused browser settings and regulations target cross-site data collection.
How to block third-party cookies in Chrome
Chrome makes it possible to block third-party cookies through its privacy settings.
The exact menu labels can vary slightly by desktop and mobile version, but the core path is consistent.
On desktop Chrome
- Open Chrome.
- Select the three-dot menu in the top-right corner.
- Choose Settings.
- Click Privacy and security.
- Select Third-party cookies.
- Choose Block third-party cookies or the closest equivalent option shown in your version.
On Android Chrome
- Open the Chrome app.
- Tap the three-dot menu.
- Go to Settings.
- Tap Site settings or Privacy and security, depending on your version.
- Tap Third-party cookies.
- Enable the block setting.
On iPhone and iPad Chrome
- Open Chrome.
- Tap the three-dot menu if available, or use the app settings flow shown on your device.
- Go to Settings.
- Find Privacy and security.
- Open Third-party cookies and block them.
If you do not see the exact option, update Chrome first.
Google has been rolling out changes to cookie controls and privacy defaults, so newer versions may present the setting differently.
What happens when you block third-party cookies?
When third-party cookies are blocked, sites can no longer rely on cross-site cookies to recognize you across domains.
That reduces common tracking methods used by advertising networks and analytics platforms.
In practical terms, you may notice:
- Fewer personalized ads based on browsing across multiple sites.
- Some embedded videos, maps, or chat widgets behaving differently.
- Occasional sign-in problems on services that depend on third-party identity or session tools.
- Shopping cart or checkout issues on some older ecommerce setups.
Most modern websites should continue to work normally, but any site built around third-party authentication, payment flows, or embedded tools may need extra permissions.
Which sites still need cookie access?
Chrome typically allows you to create exceptions for specific sites.
This is useful when blocking third-party cookies breaks a feature you need, such as a work portal, banking tool, or video platform.
Common examples include:
- Single sign-on systems used by employers and schools.
- Payment processors embedded in checkout pages.
- Helpdesk chat widgets and customer support modules.
- Content embeds from YouTube, Google Maps, or social platforms.
If a trusted site stops working, open the site settings for that domain and allow cookies only where needed.
This keeps your default privacy posture strong without disabling functionality everywhere.
How Chrome’s Privacy Sandbox changes the picture
Google has been replacing third-party cookies with Privacy Sandbox technologies, which aim to support advertising and measurement with less direct cross-site tracking.
These include proposals and APIs such as Topics, Attribution Reporting, and Protected Audience.
For users, this means the browser is moving toward a model where ad systems may still function, but with fewer traditional third-party cookies.
For site owners and marketers, it means analytics and campaign measurement may need to rely more on first-party data, server-side tools, and consent-based strategies.
In 2026, understanding how to block third-party cookies in Chrome remains useful because not every website has fully adapted.
Even as privacy controls evolve, manual blocking still gives users an immediate way to reduce tracking exposure.
Should you block third-party cookies?
For most people, the answer is yes, unless a specific website breaks and you need an exception.
Blocking them improves privacy with limited downside on well-maintained sites.
You should strongly consider blocking third-party cookies if you:
- Want to reduce ad tracking across websites.
- Share a device and want fewer stored identifiers.
- Use public or work computers.
- Prefer a tighter privacy setup without installing extra extensions.
You may want to leave them enabled temporarily if you regularly use legacy business apps, specialized healthcare portals, or older ecommerce sites that still depend on third-party services for login or checkout.
How to check whether blocking is working
After changing the setting, you can verify the result in Chrome’s privacy controls and site information panels.
Visit a website that normally uses embedded third-party services, then look for blocked content or cookie notices in the browser interface.
You can also inspect site permissions by clicking the lock icon next to the address bar and reviewing cookie-related settings.
If a site is allowed to use cookies only when you need it, you should see the permission reflected there.
Other privacy steps that help alongside cookie blocking
Blocking third-party cookies is only one part of a broader privacy strategy.
To reduce tracking further, combine it with other Chrome settings and good browsing habits.
- Turn on Do Not Track alternatives only where supported by the site; browser signals are not universally honored.
- Review and limit ad personalization in your Google account.
- Use site-specific permissions for location, camera, and notifications.
- Clear browsing data regularly if you share a device.
- Keep Chrome updated to get the latest privacy controls and security fixes.
For advanced users, privacy-focused extensions can help, but Chrome’s built-in third-party cookie controls already address one of the biggest cross-site tracking mechanisms.
Common problems after blocking third-party cookies
If a site stops working, the issue is usually not the block itself but a dependency on a third-party service for authentication, embedded resources, or checkout flow.
The easiest fix is to allow cookies only for that site rather than turning the feature off globally.
Typical symptoms include repeated logins, blank embedded frames, broken forms, or a checkout page that does not advance.
In most cases, refreshing the page after adding a site exception resolves the issue.