How To Allow Cookies On Chrome | Fix Sign-Ins And Saves

If a website won’t let you sign in, keeps forgetting your settings, or loops you back to a login page, cookies are often the reason. Chrome can block cookies in a few different ways: a global block, a block for third-party cookies, or a site-by-site rule you set once and forgot about.

This walkthrough shows where cookie settings live in Chrome, how to allow cookies in a safe, controlled way, and what to check when the switch looks right but the problem keeps happening.

What Cookies Do In Chrome

Cookies are small text files a site stores in your browser. They help sites remember that you’re signed in, what language you picked, what’s in your shopping cart, or whether you’ve already accepted a banner. Without cookies, many sites still load, but anything that needs “memory” can break.

Two cookie types matter most in Chrome settings:

• First-party cookies come from the site you’re visiting (the address in the bar).
• Third-party cookies come from other domains used by the site (like embedded services).

Lots of login issues come from blocking cookies broadly. Some checkout, video, or classroom tools can also fail if third-party cookies are blocked for that site’s embedded services.

Before You Change Anything, Spot The Real Block

Chrome can block cookies at different layers. This quick check keeps you from flipping the wrong switch.

1. Is the issue on one site or many? One site points to a site rule. Many sites points to a global setting.
2. Does the problem happen only in an embedded window? That leans toward third-party cookie blocking.
3. Did it start after you used “Clear browsing data”? Clearing cookies signs you out and wipes saved choices, which can feel like cookies got blocked.

If you only need cookies for one site, a site exception is usually the cleanest fix. If lots of sites are failing, turn cookies on globally first, then tighten rules again once things work.

Allow Cookies In Chrome On Any Device

Chrome’s menus differ slightly by device, but the controls map to the same idea: cookie rules for all sites, then exceptions for specific sites. Start with the device you’re using right now.

Desktop Chrome (Windows, Mac, Linux, Chromebook)

Use this path for Chrome on a computer:

1. Open Chrome.
2. Click ⋮ (top right) → Settings.
3. Click Privacy and security.
4. Click Third-party cookies (or Cookies and other site data, depending on version).
5. Choose a setting that allows cookies:

• Allow third-party cookies if the site needs embedded sign-in tools or external widgets.
• Block third-party cookies if you prefer a tighter default, then add a site exception for the site that’s failing.

To confirm cookies are allowed for a specific site without changing your whole browser, use a site exception (steps below).

Chrome On Android

1. Open Chrome.
2. Tap ⋮ → Settings.
3. Tap Site settings.
4. Tap Cookies.
5. Select Allow cookies (or keep a stricter option and add a site exception).

On some Android builds, the “third-party” control sits in the same Cookies screen. If a login inside an embedded window fails, try allowing third-party cookies for that site.

Chrome On iPhone And iPad

On iOS, Chrome uses Apple’s web engine, and some cookie behavior is influenced by iOS settings. Chrome still offers site settings, but if a site keeps logging you out, check these two places:

1. In Chrome: Open Chrome → ⋯ → Settings → Content Settings or Site settings (menu names vary) → review cookie controls if present.
2. In iOS Settings: Check any settings tied to site tracking or content restrictions that could limit cookies across browsers.

If you can’t find a cookie toggle in Chrome on iPhone/iPad, use the site-specific method next (it often solves the real issue), then restart Chrome.

How To Allow Cookies On Chrome For Sites You Trust

If one site is broken, don’t loosen your whole browser. Add an exception for that site. This is also the best move when a school platform, payment page, or work portal needs cookies to stay signed in.

Add A Site Exception On Desktop

1. Open Chrome and go to the site that’s failing.
2. Click the padlock (or site controls icon) in the address bar.
3. Open Site settings.
4. Find Cookies and set it to Allow for that site.
5. Reload the page and try signing in again.

If you don’t see a cookie option there, use Chrome Settings:

1. Go to Settings → Privacy and security → Third-party cookies (or Cookies and other site data).
2. Under site rules, add the site under an Allowed list.
3. Use the site’s exact domain (like example.com) and save.

Add A Site Exception On Android

1. Open the site in Chrome.
2. Tap the address bar controls (padlock or settings icon).
3. Tap Permissions or Site settings.
4. Set Cookies to Allow if available.
5. Return to the site and refresh.

If you can’t set it from the site page, use Chrome Settings → Site settings → Cookies, then allow cookies and retry.

When You Should Allow Third-Party Cookies For One Site

Some pages rely on services that run on a different domain, even though you never notice. A few common cases:

• Single sign-on buttons tied to an external identity service
• Embedded checkout or payment frames
• Video classroom tools embedded inside a course page
• Chat widgets or scheduling tools tied to a different domain

If the site works only after you allow third-party cookies, keep that permission limited to the site that needs it, not your whole browser.

Cookie Settings Map

Chrome’s labels shift across versions, so it helps to know the common places where cookie rules show up. Use this as a “where do I tap next?” reference.

Device And Chrome Build	Menu Path To Cookie Controls	Best First Move
Windows / Mac / Linux	Settings → Privacy and security → Third-party cookies	Keep default, add a site allow rule if only one site fails
Chromebook	Settings → Privacy and security → Third-party cookies	Turn cookies on, then narrow with site rules
Android Phone	⋮ → Settings → Site settings → Cookies	Allow cookies, then test sign-in again
Android Tablet	⋮ → Settings → Site settings → Cookies	Add a site exception if you want a tighter default
Any Desktop (Site-Level)	Address bar icon → Site settings → Cookies	Allow cookies for that domain and reload
Any Desktop (Exceptions List)	Settings → Privacy and security → Cookies area → Site rules	Add domain to “Allowed” list
iPhone / iPad (Chrome + iOS)	Chrome Settings (varies) + iOS Settings controls	Try site-level fix, restart Chrome, then retest
School Or Work Managed Browser	Settings may show “Managed” notice	Check if a policy is forcing a cookie block

Use Chrome’s Official Cookie Controls As Your Source Of Truth

If Chrome’s menu names don’t match what you see, follow Google’s own steps for your current version. This is also the safest way to confirm whether you’re changing third-party rules or global cookie behavior.

Google documents cookie controls here: Google’s cookie management steps for Chrome.

After You Allow Cookies, Test The Fix The Right Way

A quick refresh isn’t always enough. Cookies can be created during sign-in flows, redirects, or embedded steps. Run a clean test:

1. Close the problem tab.
2. Open a new tab and go back to the site.
3. Sign in again and complete one action that should “stick” (save a setting, add an item, switch a preference).
4. Close the tab, reopen the site, and check if it remembered you.

If it still forgets you, you might be allowing cookies but wiping them right after with a separate setting.

Settings That Can Erase Cookies Even When They’re Allowed

These options can make it seem like cookies are blocked even when you turned them on.

Auto-Clear On Exit

Chrome can clear site data when you close the browser. If that’s on, you’ll get signed out each session. Look for options tied to clearing browsing data or “clear on exit” behavior in Chrome settings.

Incognito Mode

Incognito windows store cookies only during that session. Once you close all Incognito windows, the cookies vanish. If a site works in a regular window but not in Incognito, that’s normal behavior.

Extensions That Block Trackers Or Cookies

Some extensions block cookies, strip login redirects, or break embedded sign-in pages. For a fast check, disable extensions one by one, or test in a new Chrome profile with no extensions installed.

Multiple Chrome Profiles

Cookies are profile-specific. If you fixed cookies in one profile but the problem continues, confirm you’re using the same Chrome profile each time.

Fix Cookie Problems That Keep Coming Back

When cookies are allowed but the site still fails, it’s usually a corrupted cookie, a mismatched site exception, or a blocked third-party step inside the page.

Delete Cookies For One Site Only

Clearing all cookies can be a pain if you rely on lots of logins. A site-only clear is cleaner:

1. Open Chrome Settings.
2. Go to the cookies and site data area.
3. Search for the site domain under stored data.
4. Remove just that site’s data.
5. Restart the sign-in flow from a fresh tab.

Google’s help doc also covers clearing cookies and site data in Chrome: Chrome browsing data cleanup steps.

Check The Exact Domain You Allowed

If you allowed example.com but the login happens at accounts.example.com or a different domain, the exception might not apply. Add the domain you actually see during sign-in and test again.

Watch For Embedded Login Frames

If you sign in through an embedded box (not a full page), Chrome may treat that as third-party. A tight third-party setting can block the cookie that keeps you signed in. Add a site exception for third-party cookies on that site, then retry.

Common Symptoms And Fast Fixes

If you want a straight path from problem to fix, use the table below. It focuses on the patterns people hit most often when cookies are blocked or wiped.

What You See	What’s Usually Going On	Fix To Try First
Login loop after entering password	Cookies blocked for the sign-in domain	Allow cookies for that site, then restart the sign-in flow
Site forgets language, theme, or settings	Cookies allowed, but cleared on exit or by cleanup	Turn off auto-clear behavior or exclude that site from cleanup
Cart empties after refresh	Site cookie not being stored	Allow cookies for the store domain, then test again
Video class tool won’t load inside a course page	Third-party cookie needed for embedded service	Allow third-party cookies for that site only
Payment page fails or returns an error	Cookie blocked during redirect or embedded checkout	Allow cookies, disable blocking extension, retry
Works in one Chrome profile, not another	Cookie rules differ by profile	Copy the same site exception to the problem profile
Works on mobile data, fails on Wi-Fi	Network filter or DNS rule interfering with embedded services	Test on another network, then allow the site cookies again
Settings page shows “Managed”	Work or school policy is enforcing cookie rules	Use a personal profile or ask the admin to change the policy

Safer Defaults Once Things Work

After you get your logins and saves working again, you can keep cookies under control without breaking everyday sites.

Use Site Exceptions Instead Of A Wide-Open Rule

If you had to allow third-party cookies to fix one site, switch back to a tighter default later and keep a site exception for the one place that needs it. That way you’re not granting extra cookie access everywhere.

Review The “Allowed” List Every So Often

Over time, site exceptions pile up. Skim your allowed list and remove entries you no longer use. Fewer rules makes it easier to spot a mismatch when something breaks again.

Use A Separate Profile For School Or Shared Devices

If a laptop is shared, a separate Chrome profile can keep logins and cookie rules from colliding. It also helps when one person wants stricter blocking and another needs cookies for coursework platforms.

Quick Checklist For Stubborn Cases

If you tried the main steps and you’re still stuck, run this checklist in order. Each step is fast and tends to reveal the hidden cause.

1. Confirm cookies are allowed for the exact domain you’re using.
2. Allow third-party cookies for that site only if the login is embedded.
3. Clear cookies for that site only, then restart the sign-in flow.
4. Disable extensions that block trackers or site data, then retry.
5. Test in a new Chrome profile with default settings.
6. Check for a “Managed” note that points to a work or school policy.

Once cookies are allowed in the right place, most sites snap back to normal: sign-ins hold, settings stay saved, and pages stop looping.