Getting logged out of websites every time you close Chrome, or repeatedly signed out even while browsing — this is one of the most common Chrome complaints and it’s almost always caused by how Chrome handles cookies rather than anything the website is doing wrong. The fix is usually in settings, not in the site itself. If you want the full context, see our Chrome How-To Guides.
The most common cause by far: Chrome is configured to clear cookies when the browser closes. Check this first. chrome://settings/clearBrowserData → “On exit” tab — if “Cookies and other site data” is checked here, Chrome is deleting your login sessions every time it closes. Uncheck it → save. Problem solved for most people.
The cookie deletion culprit
Websites keep you logged in by storing a session cookie — a small token that says “this browser is authenticated as user X.” When that cookie is deleted, the website has no way to recognise you and treats you as a new visitor, sending you back to the login page.
There are three common places where cookie deletion gets configured in Chrome:
- Clear on exit (settings): chrome://settings/clearBrowserData → On exit tab → check if Cookies is selected. Most common cause.
- Third-party cookies blocked: If you’ve blocked all third-party cookies, sites that use third-party authentication (sign in with Google, social login) may keep logging you out because the authentication token is treated as a third-party cookie. chrome://settings/cookies → check the cookie blocking level.
- Extension doing it: Privacy Cleaner, Cookie AutoDelete, or similar extensions automatically delete cookies on a schedule or on tab close. If you have any such extension: check its settings, or disable all extensions temporarily and test whether the logout problem persists.
Site-specific cookie exceptions
Even with “clear cookies on exit” turned off: some sites may still log you out. This usually means the site’s own session has an expiry that’s shorter than your browsing session — the authentication token on the server side expired, not Chrome’s cookie. This is a website-side issue and not configurable from Chrome.
For sites that continuously log you out even mid-session: add them to Chrome’s cookie exception list to ensure their cookies are never cleared. chrome://settings/cookies → “Sites that can always use cookies” → Add → enter the site’s domain. This tells Chrome to keep that site’s cookies regardless of any other deletion settings.
Chrome Sync and the logout problem
A separate but easily confused issue: Chrome itself (not websites) logging you out of your Google account. This is a different problem — your Chrome profile becomes disconnected from your Google account, which can affect Sync, Google services accessed in Chrome, and features like password sync.
Chrome signing out of your Google account typically happens when: the Google account password was changed on another device, the authentication token expired (happens more with long browser uptimes), or a browser update required re-authentication. The fix: click “Sign in to Chrome” in the top right → re-enter Google credentials → Chrome reconnects to your account.
This is distinct from websites logging you out. When Chrome disconnects from Google, your website sessions (Gmail, YouTube, banking) are usually unaffected — cookies for those sites are separate from Chrome’s own authentication.
Partitioned cookies and what they mean for logins
Chrome’s cookie changes as part of the Privacy Sandbox project affect how some authentication flows work. As third-party cookies are phased out: sites that use third-party authentication (embed a login widget from another domain) need to adapt. If a site recently started logging you out repeatedly that didn’t before: this may be the cause — the site hasn’t updated its authentication flow for Chrome’s stricter cookie policies.
Temporary workaround: chrome://settings/cookies → “Allow related sites to access your cookies when you’re browsing.” This enables the Privacy Sandbox’s related website sets feature, which allows certain cross-site cookie access patterns that are considered acceptable under the new model.
Our guide on managing Chrome cookies covers the cookie architecture and clearing options in detail, and our Chrome privacy settings covers how third-party cookie blocking affects browsing. For troubleshooting persistent logout issues across specific websites, Google’s Chrome Help has documentation on cookie settings and exception management.
Checking for corrupted cookie storage
Occasionally the Chrome cookie database itself becomes corrupted, causing inconsistent behaviour — some sites stay logged in, others repeatedly log out with no apparent pattern. If the settings-based fixes haven’t helped and the problem affects multiple unrelated sites: cookie database corruption may be the cause.
Fix: close Chrome completely → navigate to %localappdata%GoogleChromeUser DataDefault → find the file named “Cookies” → rename it to “Cookies.bak” → reopen Chrome. Chrome creates a fresh cookie database. You’ll need to log in to everything again, but the corrupt database is no longer causing issues. If the problem resolves: the renamed file was corrupted. If it returns: the issue is in Chrome settings or elsewhere.
When specific sites keep logging you out
Some sites have aggressive session management that doesn’t rely on Chrome’s cookie behaviour at all. Banking sites, for example, often timeout after 10-15 minutes of inactivity for security reasons. Government and healthcare portals often have mandatory session limits. These timeouts happen server-side — Chrome has no control over when the website decides to invalidate your session, regardless of cookie settings.
Other sites log out when they detect a change in IP address or browser fingerprint mid-session — a security feature to detect session hijacking. If your IP address changes during a browsing session (dynamic IP reallocation from your ISP, or VPN switching servers), some sites treat this as suspicious and invalidate the session. This presents as “Chrome kept logging me out” but is actually the site protecting against what looks like session theft.
| Symptom | Most likely cause | Fix |
| Logged out of everything when Chrome closes | Clear cookies on exit enabled | Uncheck in Settings → On exit |
| Logged out of everything mid-session | Extension clearing cookies | Disable Cookie AutoDelete or similar |
| One specific site keeps logging out | Server-side session timeout or cookie exception | Add site to “Always keep cookies” list |
| Logout after closing and reopening a tab | Third-party cookie blocking affecting auth | Adjust cookie settings or add site exception |
| Chrome itself (not websites) signed out | Google account token expired | Re-sign into Chrome profile |
| All sites fine, one keeps logging out | Site-side session limit (banking, gov) | Normal behaviour — not Chrome’s fault |
The pattern to remember: if all sites are logging you out, it’s a Chrome setting (clear on exit, or a cookie-clearing extension). If one specific site is the problem, it’s either that site’s session management, a cookie exception needed for that domain, or a cookie partitioning issue affecting how that site’s authentication token is stored. The cookie “On exit” setting is the most frequently missed configuration, and it’s the first thing worth checking before going further.
Incognito and private browsing
Incognito mode is designed to delete all session data when the window closes — cookies, session tokens, form data. So if you’re using Incognito and you get logged out when you close it: that’s intentional behaviour, not a bug. If you want persistent logins: use a regular Chrome window. Incognito is for sessions where you don’t want anything stored afterward, and it delivers on that exactly.
VPN-related logout issues
Using a VPN that routes through multiple servers or that changes your IP address during a session can trigger “suspicious activity” logouts on security-sensitive sites. Banking sites, payment platforms, and some corporate tools monitor for IP changes mid-session and terminate the session if the IP changes (as it might if your VPN server changes).
If you’re logged out of sensitive sites regularly and use a VPN: test without the VPN active. If the logouts stop: the VPN’s IP changes are triggering the site’s security logic. The fix: use a VPN server that stays stable during your session, or whitelist sensitive sites from VPN routing using your VPN’s split tunnelling feature.
Multiple Google accounts causing confusion
If you have multiple Google accounts signed in to Chrome (a work account and a personal account, for example): cookie conflicts between the accounts can sometimes cause unexpected logouts on Google services. When both accounts are active in Chrome, the browser has to manage separate cookie contexts for services that appear identical (both might be Gmail, but for different accounts).
For Chrome accounts: use separate Chrome profiles rather than multiple accounts in the same profile. Each profile maintains its own completely separate cookie store, eliminating the cross-account interference. Managing multiple accounts through the profile switcher (click your profile picture → Switch) avoids the cookie conflicts that arise from having multiple accounts active in the same browser context.
Remember me and “stay signed in” checkboxes
Many sites offer a “Remember me” or “Stay signed in” checkbox at login. When you check this: the site sets a longer-lived persistent cookie rather than a session cookie that expires when the browser closes. If you didn’t check “Remember me” and Chrome closes (even with cookies-on-exit disabled): the session cookie expires naturally because it was only ever intended for that browser session.
The practical fix: check “Remember me” on sites you want to stay logged into. This creates a persistent cookie that survives browser restarts regardless of Chrome’s cookie handling settings. The cookie eventually expires (usually 30-90 days depending on the site), at which point you log in again and check the box again. This is the intended authentication flow for most consumer websites — the persistent “stay logged in” state depends on the cookie the site creates when you opt into it, not on Chrome never deleting session cookies.
Cookie management in Chrome has become more complex as privacy changes have been introduced, but the fundamental issue behind most “keeps logging me out” reports is still simple: a setting is configured to delete cookies, or an extension is doing it, and the fix is to find and change that configuration. The On exit clearing setting remains the most common single cause and it’s worth checking that first before going deeper into cookie partitioning, VPN interactions, or server-side session logic.
Chrome’s “Continue where you left off” and session restoration
chrome://settings → “On startup” section → “Continue where you left off” setting opens all your previously-open tabs when Chrome restarts. This is separate from cookies and doesn’t keep you logged in — it reopens the pages, but if your session tokens have been cleared, you’ll be on the login page of those sites rather than your previous session state.
If you combine “Continue where you left off” with “Keep cookies on exit”: you’ll reopen to your previous tabs already logged in — the closest Chrome gets to a seamless session across browser restarts. This is the configuration for users who want to close and reopen Chrome without losing their context or their sessions.
Checking what Chrome cleared during the last session
Chrome doesn’t maintain a detailed log of what data it deleted, but you can infer it from patterns. If you were logged in before closing Chrome and not logged in when you reopened: something deleted the session cookie. The On exit settings, Cookie AutoDelete or similar extensions, or a profile reset are the sources. Checking each in sequence resolves it: visit chrome://settings/clearBrowserData → On exit → see what’s checked. Then check your extensions list for anything related to privacy cleaning. Then check whether Chrome was updated and reset settings as part of the update. Related: Fix Chrome High Memory Usage.
One sometimes-overlooked cause: if you cleared browsing data manually (Ctrl+Shift+Delete) and checked “Cookies” in the dialog, that clears all cookies including active sessions. This is a manual action you may not remember doing, especially if it was days ago and you noticed the logouts only when revisiting sites. Chrome’s download history (Ctrl+J) can serve as a rough timeline reference — if you cleared data the same day cookies disappeared, it was the manual clear. If this sounds familiar, Fix Chrome Tabs Crashing is worth a look.
One last scenario worth mentioning: if you’re on a work computer and Chrome is resetting cookies on a schedule you didn’t configure, the policy may be set by IT. Managed Chrome installations sometimes include policies that clear browser data periodically. chrome://policy → look for “ClearBrowsingDataOnExitList” or similar. If it’s there: IT configured it and local changes won’t persist. For work computers: use your corporate SSO (single sign-on) for work tools rather than relying on Chrome’s cookie persistence — SSO is designed to handle the authentication properly regardless of cookie state. Our guide on Disable Chrome Auto Sign covers an adjacent issue.
