Edge keeps signing you out of YouTube because the browser is deleting or failing to persist the cookie session that YouTube uses to recognize you. In Edge, that usually traces to one of four causes: tracking prevention blocking or partitioning YouTube's cookies, a stale or conflicting Microsoft account sign-in at the browser level, an intermittent "third-party cookie" or "site data" clearing policy, or a corrupted profile store. The sign-out is the visible symptom; the cookie or token lifecycle is the actual failure.

The sign-out mechanism, one layer deeper than "clear your cookies"

YouTube does not authenticate you with a password on every page load. It authenticates you once, then hands your browser a small set of session artifacts. That's the core of the answer, and it explains everything downstream.

The primary artifact is a set of first-party cookies set on .youtube.com and .google.com. The most important is a session identifier tied to your Google Account login. Alongside it, Google sets cookies that carry a rotating authentication token, a "consent" cookie for cookie preferences, and a set of preference cookies (theme, volume, playback settings). YouTube's front end also stores state in browser storage and in a service worker cache.

Three things keep you "signed in" between visits:

The session cookie must survive browser restart. If it's a session-only cookie, closing Edge signs you out. Most Google cookies are persistent, but a policy that clears "cookies and site data on close" converts them to session-only in effect. The authentication token must not be rejected or rotated out. If the token is invalidated server-side (password change, security event, sign-out everywhere), the cookie can persist while still being useless. The cookie must actually reach YouTube. Tracking prevention can block a third-party cookie read or a cross-site request, and partitioned storage can isolate the cookie so the YouTube page can't see the token your Google account page set.

Here's the plain-language version: signing in leaves a key under the doormat, and Edge is either sweeping the key away on exit, locking the door the key opens, or handing you a key to a different door.

The professional caveat most thin explainers miss: Google and Microsoft run two separate identity systems that both touch Edge. Your Windows or Microsoft account sign-in and your Google Account sign-in are unrelated. A Microsoft-account sign-in prompt appearing on YouTube does not mean YouTube is signed in. Confusing these two layers is the single most common reason people misdiagnose the problem.

How much data is actually at stake, and how often it breaks

A signed-in YouTube session is not one cookie. A typical signed-in .google.com and .youtube.com cookie set runs into the dozens of individual cookies, plus local storage entries for player state and a service-worker cache. Clearing "cookies and site data" wipes all of it at once, which is why a single clear can sign you out of YouTube, Gmail, Google Drive, and Search personalization simultaneously.

The frequency matters more than the count. Tracking-prevention and cookie policies apply continuously, not once. If Edge's setting blocks a cookie category that YouTube depends on, the sign-out can recur every time the token tries to refresh — which Google does on a rolling basis rather than only at login. That means the failure can look intermittent: signed in today, signed out tomorrow, with no obvious trigger.

Storage partitioning compounds this. Modern browsers, including Edge, can isolate storage by top-level site so that a cookie set in one site context is not readable in another. When partitioning interacts with a YouTube embed or a cross-site sign-in flow, the token can be written to a partition the main YouTube page never reads. The result is a silent mismatch: cookie present on disk, session absent in the page.

Compare the alternatives to understand the blast radius:

Approach What it protects Sign-out risk for YouTube Typical trade-off
Edge tracking prevention (Balanced) Cross-site tracking Moderate; can block or partition auth cookies Some sites behave inconsistently
Edge tracking prevention (Strict) Aggressive cross-site blocking High; sign-in flows often break Many embedded logins fail
Edge tracking prevention (Basic) Minimal blocking Low Weaker cross-site privacy
"Clear cookies on close" enabled Local privacy on shared devices Very high; session cookies die on exit You re-authenticate constantly
Third-party cookie block Cross-site cookies generally High for embeds and SSO flows Federated sign-in can fail
Allow-list YouTube/Google Those specific sites Low You loosen protection for those domains

There is no universal "correct" row here. The right setting depends on whether the device is shared, whether you use Google as a federated identity for other services, and how much re-authentication friction you tolerate. The table exists to make the trade-off explicit, not to prescribe one.

Edge cases that mimic a sign-out but are not one

Some failures look identical to "Edge keeps signing me out" but have different causes, and treating them as cookie problems wastes time.

The multi-profile case is the big one. Edge supports multiple profiles, each with its own cookie jar. If YouTube is signed in under Profile A and you open it under Profile B, you are genuinely signed out in B — but nothing is broken. The same applies to a work or school profile managed by an organization: management policies can force clear-on-exit or block certain cookies, and you cannot override them locally. A work profile that signs you out is often doing exactly what its administrator configured.

InPrivate and Guest windows are a second case. InPrivate discards session data when the window closes, by design. If you only notice sign-outs after using InPrivate, the cause is the mode, not a bug. Guest mode is stricter still.

A third case is the "signed in but looks signed out" state. YouTube can show a signed-out interface when the page fails to load the account chip — for example, if a script is blocked or the network request to the account endpoint fails. You are still authenticated; the UI just can't prove it. Hard-refreshing usually restores the chip.

Two more edge cases worth naming. First, a password change or "sign out of all devices" security action invalidates tokens server-side, and the browser cookie becomes a dead key — Edge isn't deleting anything, Google already revoked it. Second, clock skew: authentication tokens carry time-based validity, and a system clock that is substantially wrong can cause token validation to fail in ways that look random. That's rare but real, and it explains sign-outs that correlate with sleep/resume cycles rather than browsing.

Misconceptions that send people down the wrong path

The most persistent misconception is that "Edge keeps signing me out of YouTube" is a Microsoft-versus-Google fight. It usually isn't. YouTube runs in Edge the same way it runs in Chrome; the difference is Edge's default tracking-prevention posture and its own cookie-clearing policies. The browser vendor and the identity provider are separate layers, and the failure is almost always at the cookie-policy layer, not a deliberate inter-company block.

A second misconception: that clearing your cache and cookies is the fix. It's the diagnostic reset, not the cure. If a policy keeps deleting the cookie, clearing it just reproduces the problem on the next refresh. The cure is changing the policy or allow-listing the domain, not clearing more aggressively.

A third: that "remember me" guarantees persistence. It doesn't if the underlying cookie is being cleared on exit. Persistent login depends on both the site setting a persistent cookie and the browser retaining it.

A counterintuitive detail worth sitting with: sometimes the sign-out is the privacy feature working as intended, and the "fix" is to accept more tracking for those two domains. If you have enabled clear-on-close for privacy on a shared machine, signing you out of YouTube is exactly the behavior you asked for. The only honest remedies are to disable that policy, allow-list the domains, or use a separate profile for the shared-use case. There is no setting that gives you both aggressive local clearing and persistent sign-in.

A practical sequence with concrete thresholds

Work through this in order. Stop as soon as the sign-out stops recurring for a defined observation window — a practical threshold is seven days of normal use with no unexpected sign-out.

Confirm the layer. Sign in, close Edge, reopen it, and check whether you are still signed in before touching any URL. If you're out immediately on reopen, the problem is exit-time clearing, not tracking prevention. Check the tracking-prevention level at edge://settings/privacy. Balanced is the default; Strict is the usual culprit for broken sign-in. Add youtube.com and google.com to the exceptions list rather than dropping the whole browser to Basic. Check clear-on-close at the same settings page. Turn off "cookies and site data" clearing on exit if it is enabled, or exclude the two domains if partial clearing is available. Verify you're in the intended profile. Open edge://version and confirm the profile path matches the one where YouTube is signed in. Rule out server-side revocation. If other devices are also signed out, Google invalidated the token; sign in again and confirm the issue stops. Repair the profile only after the above fails. A corrupted profile store produces failures that settings changes cannot fix. Creating a fresh profile and re-signing in is the last diagnostic step, not the first.

Red-flag warnings before you start:

If a work or school profile is forcing the behavior, local settings may be locked by management policy and cannot be changed — contact your administrator rather than fighting the policy. Do not disable tracking prevention globally to fix one site; use per-site exceptions instead. Do not assume "clear everything" is safe — it signs you out of every Google service at once. Do not treat repeated security sign-outs (password changes, "new sign-in" alerts you didn't initiate) as a browser bug; investigate the account.

Limits of what this diagnosis can establish

Everything above describes stable browser and identity mechanisms. What it cannot do is pinpoint your specific failure without seeing your settings and account state. The four causes produce the same visible symptom, and only the practical sequence separates them. If the sequence exhausts without resolution, the remaining possibilities — a managed device policy, an account-side security action, or a corrupted profile store — require evidence this article cannot supply.

Current Edge menu labels, exact default settings, and specific policy names change between versions. Treat the settings paths as directional and confirm them in your installed build rather than as fixed facts. If a step doesn't match what you see, the version has moved on; the underlying mechanism has not.