Chrome Keeps Logging You Out? 10 Fixes That Actually Work (2026)

If Chrome keeps logging you out of Google, Gmail, YouTube, or your favorite sites every time you close the browser, the cause is almost always a cookie setting — Chrome is deleting your session cookies on exit, so the next launch treats you as a new visitor. Reopening Chrome should keep you signed in. When it doesn’t, the fix is usually under one of four settings: “Clear cookies and site data when you close all windows,” third-party cookie blocking, a broken sync profile, or a privacy-focused extension wiping data in the background.

This guide walks through the fixes in order of how often they actually solve the problem, based on current Chrome behavior as of 2026 on Windows, macOS, Android, and iOS. Start at the top and stop as soon as sessions stick.

Why Chrome Keeps Signing You Out

Chrome stores your session as a cookie. If anything deletes or blocks that cookie — a privacy setting, an extension, a corrupted profile, or a sync failure — Chrome loads a fresh state on the next launch and forces you to sign in again. The fastest way to diagnose it is to check whether the issue happens on every site, only Google sites, or only when you close and reopen Chrome. Each pattern points to a different fix below.

Fix 1: Turn Off “Clear Cookies on Exit”

This single setting causes the majority of “Chrome keeps logging me out” reports. When it’s on, Chrome wipes every site cookie the moment you close the last window, so logins, cart contents, and preferences all reset. The option is buried two levels deep and is sometimes enabled by a Chrome update, an imported profile, or a well-meaning “speed up Chrome” tutorial.

Desktop (Windows, macOS, Linux):

Open Chrome and click the three-dot menu in the top right, then choose Settings. In the left sidebar, click Privacy and security, then Third-party cookies (labeled Cookies and other site data in older builds). Scroll to the bottom and toggle off Clear cookies and site data when you close all windows. Close Chrome completely, reopen it, sign in once, then close and reopen again to confirm the session sticks.

Android:

Tap the three-dot menu, then Settings → Site settings → Cookies, and make sure Clear cookies when you close Chrome is off.

iOS / iPadOS:

Chrome on iOS doesn’t expose this toggle directly, but iOS’s own Limit IP Address Tracking and Private Relay can produce the same symptom. Open the iOS Settings app → Apps → Chrome and check that Allow Cross-Website Tracking is not restricted more than you intend.

Fix 2: Allow Third-Party Cookies for Google Sites

Chrome’s third-party cookie blocking is stricter in 2026 than it was a few years ago, and some Google login flows still rely on cross-site cookies to keep you signed in across Gmail, YouTube, Drive, and Docs. Blocking them globally can cause Chrome to log you out of one Google property when you switch to another.

Go to Settings → Privacy and security → Third-party cookies. Set it to Allow third-party cookies temporarily to confirm this is the cause. If it fixes the issue, switch back to Block third-party cookies in Incognito (the recommended balance) and add site-specific exceptions under Sites allowed to use third-party cookies. Useful entries:

[*.]google.com
[*.]youtube.com
[*.]googleusercontent.com
[*.]googleapis.com

Add any other site that keeps logging you out using the same [*.]domain.com format.

Fix 3: Re-Sign Into Chrome Sync

A broken sync token can cause Chrome to log you out constantly because the browser keeps trying — and failing — to refresh your credentials. Signing out of sync and back in regenerates the token and fixes the loop.

Click your profile picture in the top right of Chrome, then the gear icon, then Turn off sync. Confirm, then click the profile picture again and choose Turn on sync, sign in with your Google account, and accept the sync prompt. If Chrome asks whether to keep or delete existing data, choose Keep unless you suspect the local profile is corrupt (see Fix 7).

Fix 4: Allow Chrome Sign-In

Chrome has a separate setting that controls whether signing into any Google site also signs you into the browser. When it’s off, Chrome can bounce you out of Gmail or YouTube every time a sync handshake fails.

Go to Settings → You and Google → Sync and Google services. Turn on Allow Chrome sign-in. Restart Chrome and sign back into Google.

Fix 5: Disable Extensions That Clear Data

Privacy-focused extensions are the most common hidden cause. Any of the following can wipe your session cookies silently, especially on a schedule or on tab close:

Click&Clean
Cookie AutoDelete
Privacy Badger (aggressive settings)
uBlock Origin (when configured to block first-party cookies)
Ghostery (with “auto-delete cookies” enabled)
Most password managers in “auto-clear form data” mode

Open chrome://extensions in the address bar. Toggle every extension off, restart Chrome, and sign in. If the problem disappears, re-enable extensions one at a time — closing and reopening Chrome after each — until you find the culprit. Once identified, either remove it or dig into its settings and disable the “clear on exit” or “auto-delete” feature.

Fix 6: Clear the Cache (But Not Cookies)

A corrupted cache entry can confuse Chrome’s auth flow even when cookies are intact. The trick is to clear the cache without clearing cookies, so you don’t sign yourself out on purpose while trying to fix being signed out.

Press Ctrl+Shift+Delete (Windows/Linux) or Cmd+Shift+Delete (macOS). Set the time range to All time. Check Cached images and files. Uncheck Cookies and other site data and Browsing history. Click Clear data. Restart Chrome.

Fix 7: Create a Fresh Chrome Profile

If none of the above works, the user profile itself is likely corrupted. Rather than reinstalling Chrome, creating a new profile is faster and preserves your installation.

Click your profile avatar in the top-right of Chrome, then Add at the bottom of the menu. Create a new profile and sign in with Google. Use this profile for a day. If logins stick in the new profile but not the old one, the old profile’s files are damaged. Move any bookmarks or extensions you need to the new profile, then delete the old one from the profile menu.

Advanced users can also manually delete the broken profile folder after closing Chrome completely:

Windows: %LOCALAPPDATA%\Google\Chrome\User Data\Default
macOS: ~/Library/Application Support/Google/Chrome/Default
Linux: ~/.config/google-chrome/Default

Rename Default to Default.old before Chrome starts — Chrome will rebuild a clean profile on next launch. Keep the backup for a few days in case you need to copy bookmarks out.

Fix 8: Reset Chrome Settings

Chrome has a built-in reset that reverts startup pages, new-tab page, search engine, pinned tabs, content settings, and extensions to defaults without deleting your bookmarks, history, or saved passwords. It’s lighter than a profile wipe and fixes most misconfigurations left over from old extensions or tweaks.

Go to Settings → Reset settings → Restore settings to their original defaults, then click Reset settings. Restart Chrome and test.

Fix 9: Check Your Date and Time

Cookies and OAuth tokens are time-sensitive. If your device clock is wrong by more than a few minutes, Google’s auth servers will reject tokens as expired or future-dated, and Chrome will silently log you out. This is especially common after a motherboard battery (CMOS) failure on an older PC, or after changing time zones on a laptop with auto-sync disabled.

Windows: Settings → Time & language → Date & time → turn on Set time automatically and Set time zone automatically, then click Sync now.

macOS: System Settings → General → Date & Time → turn on Set time and date automatically.

Android: Settings → System → Date & time → turn on Use network-provided time.

Fix 10: Reinstall Chrome

If you’ve worked through every fix above and sessions still reset, a full reinstall clears any deep-seated corruption in Chrome’s binaries. Before uninstalling, sign into Chrome sync on another device (or at myaccount.google.com) so your bookmarks and passwords are safe on Google’s servers.

Windows: Go to Settings → Apps → Installed apps, find Google Chrome, click the three-dot menu, and choose Uninstall. Check the box to also delete browsing data. Restart, then download the latest installer from google.com/chrome.

macOS: Drag Google Chrome from Applications to the Trash. Also delete ~/Library/Application Support/Google/Chrome and ~/Library/Caches/Google/Chrome. Then reinstall.

Android: Chrome is a system app on most Android phones and can’t be fully uninstalled. Instead, open Settings → Apps → Chrome → Storage and tap Clear storage and Clear cache. Then open Play Store and tap Update if available, or uninstall updates and let it reinstall fresh.

When to Suspect the Google Account Itself

If Chrome logs you out across multiple devices at the same time — phone, laptop, and desktop all at once — the problem isn’t Chrome, it’s your Google account. Google automatically signs every session out when it detects a suspicious login, a password change, or a session token revocation. Check myaccount.google.com → Security → Your devices for unfamiliar entries, change your password if anything looks off, and turn on 2-Step Verification if it isn’t already. After securing the account, sign back into Chrome and the logouts should stop.

Quick Checklist

If you’re in a hurry, these four fixes solve the issue for the vast majority of users — in this exact order:

Turn off Clear cookies and site data when you close all windows.
Allow third-party cookies for [*.]google.com.
Turn off every privacy extension one at a time.
Sign out of Chrome sync, then sign back in.

If none of those work, the problem is almost certainly a corrupted Chrome profile (Fix 7) or a wrong system clock (Fix 9). Work through those next before reinstalling Chrome.