How to Enable Cookies in Chrome, Safari and Firefox

To enable cookies, check the settings in the browser you actually use—not just your phone or computer settings. If a website cannot remember your sign-in or says cookies are disabled, first check whether ordinary site storage is blocked. Third-party cookie restrictions are a separate issue and do not always need to be changed.

Start with your browser and device below. Menu names can change between releases, and a school or work policy may prevent changes.

Choose the setting that matches the problem

Clicking “Accept” on a cookie banner is not the same as enabling storage in browser settings. A website can record a consent choice while a browser still restricts some storage.

How to enable cookies in Chrome on a computer

Desktop Chrome separates on-device site storage from third-party cookie controls.

1. Open Chrome Settings.

2. Go to Privacy and security, then Site settings.

3. Open Additional content settings and On-device site data.

4. Allow sites to save data if you previously blocked that behaviour.

5. Reload the affected page and try again.

Do not assume allowing site data also requires allowing every third-party cookie. For Google's current explanation, see on-device site data in Chrome.

What about Chrome on Android or iPhone?

Do not use the desktop menu path as mobile instructions. On Android, Chrome exposes third-party cookie controls under its site settings; that is a different setting from ordinary first-party storage. If an embedded service is the problem, consult Google's Android cookie controls and prefer a narrow exception for a trusted site.

On iPhone, identify whether the page is actually open in Chrome, Safari or an in-app browser before changing anything. Safari settings should not be presented as Chrome controls. Use the current browser help when the mobile interface has no matching option.

How to enable cookies in Safari on iPhone or iPad

For Safari on iPhone, check Settings → Apps → Safari → Advanced. If Block All Cookies is enabled, turn it off, return to Safari and test the page again. On versions with a different Settings layout, find Safari's settings directly. On iPad, locate the equivalent Safari control rather than assuming every label is identical.

Apple explains the effects of this setting in its Safari cookie guidance.

Prevent Cross-Site Tracking is separate from Block All Cookies. Do not turn off every privacy option simply to restore ordinary site storage.

How to check cookie restrictions in Firefox on a computer

Firefox's cookie behaviour is connected to Enhanced Tracking Protection and site exceptions. Check Settings → Privacy & Security, then inspect cookie/site-data exceptions for the affected website. Remove an accidental block rather than changing protection for every site.

If the problem appears tied to tracking protection, use the website's shield control for a limited comparison test and restore protection if it does not help. Follow Mozilla's cookies-blocked troubleshooting instructions for the current desktop interface. Mobile Firefox has a different interface.

Do you need to allow third-party cookies too?

Not necessarily. A site's own cookies can keep a cart or signed-in session working while cross-site storage remains restricted. A separate identity provider, embedded tool or other cross-domain service may need additional access.

For a trusted site in Chrome, use its third-party cookie controls or exception list when a specific function requires it. Google's cookie management guide documents those options. A browser exception does not solve every login problem.

Safari uses different cross-site protections. Turning off Block All Cookies is not a guarantee that every third-party service will receive unrestricted storage access. Check the site's supported sign-in method before relaxing broader privacy settings.

For the Android privacy trade-off and narrow exceptions, read how to block third-party cookies on Android.

If the website still says cookies are disabled

Check the setting in the same browser where the error appears. Reload the page, try a regular tab and test another trusted site. If only one website fails, inspect its own stored data and relevant extensions before resetting the whole browser.

Deleting cookies can sign you out; deleting passwords or clearing full app storage is a different and broader action. Avoid either unless necessary and understood.

If a targeted cookie change makes no difference, investigate the account, scripts, extensions or server. Our guide to website problems that cache or DNS changes will not fix explains the next diagnostic steps.

Keep the setting as narrow as the task allows

Restore stricter settings after a temporary test when practical. A cookie setting is one part of privacy, alongside accounts, permissions and tracking controls; it does not make browsing anonymous.

If you already use Quetta and want to understand its available controls, explore Quetta Privacy Guard. Changing browsers is optional, not a prerequisite for repairing cookie settings in your current browser.

Frequently asked questions

Is “allow cookies” the same as accepting a cookie banner?

No. A banner records a website consent choice. Browser settings determine which storage operations are permitted. One does not necessarily override the other.

Why do websites still ask me to sign in?

Session expiry, deliberate sign-out, private browsing, deleted storage, account policies, or website changes can require authentication again even when cookies are allowed.

Should I enable all cookies everywhere?

Start with the storage needed for the specific site and task. Use exceptions where available instead of making a global change unnecessarily.