Why Twitch pauses when you switch tabs

# The thirty-second triage

Open chrome://settings/help — or edge://settings/help, brave://settings/help, opera://about — and read the whole build string, all four numbers, not just the major version. Then match it below.

1. Desktop Chrome 147.0.7727.47 or newer. The feature is off in your build. Whatever is pausing your tab, it is not this. Jump to section 4.^[6]
2. Desktop Chrome 145 or 146. This is your cause, and the fix is an update rather than a setting. Chrome 145 went stable on 10 February 2026 and 146 on 10 March 2026; both predate the revert.^[3]
3. Chrome on Android. Still enabled by default, deliberately. The flag declaration in Chromium's media_switches.cc reads FEATURE_ENABLED_BY_DEFAULT under an Android build guard and FEATURE_DISABLED_BY_DEFAULT in the #else branch.^[7] Nothing you toggle in the app changes it.
4. Edge, Brave, Opera, Vivaldi. These carry their own version number and a separate Chromium version. The one that matters is the Chromium one. Brave, for instance, prints both: a user reporting this exact symptom quoted their build as "Brave Version 1.76.74 Chromium: 134.0.6998.89".^[12] Read the number after the word Chromium and compare it against 147.0.7727.47.
5. Firefox or Safari. Different engines. This flag lives in Chromium's media code and has no counterpart in either, so a pausing tab in Firefox or Safari is a different problem with a different fix.

# What Chrome changed, and when it stopped

Chromium development happens in the open, so a behaviour change like this leaves a paper trail: a code review with a commit message, a bug with a milestone, and a release that carries it. All three are readable without an account. Here is the trail for this one, read from Chromium Gerrit and the Chromium release dashboard on 14 September 2026.

That is the entire rationale, stated by the engineer who wrote it, with a credible interval attached. It is not a conspiracy about ad-blocking and it is not something Twitch did. It is a battery-life change, measured, shipped behind a flag, and later judged not worth the complaints on machines that are plugged into a wall.

The last row deserves a second look, because it shows the feature is still being tuned rather than abandoned. On 6 August 2026 a further change altered the rule "to explicitly exclude video via a !HasVideo() check", with the commit noting that "Out of the 16384 possible flag combos, 4 now return false when they used to return true, all involve muted video".^[9] In plain terms: on the platforms where the feature is still live, it now targets muted audio-only playback and leaves muted video alone. A Twitch stream has video, so it is outside the narrowed rule.

# The exact rule Chromium applies

The decision is made in one function, WebMediaPlayerImpl::ShouldPausePlaybackWhenHidden, in Chromium's Blink media layer. It is worth reading because the conditions explain why every workaround that circulates either works or does not, and nothing in the function is about Twitch specifically.^[8]

Three things have to be true at once before the muted-background rule fires. The feature must be enabled — which, after April 2026, means Android. The media must have no video, unless the platform also has background suspend switched on, which desktop does not. And the player volume must be exactly zero: the source condition is literally volume_ == 0., not "muted-ish", not "quiet".^[8]

Two exemptions in the same function are worth knowing because they are genuine escape hatches. Picture-in-Picture is explicitly carved out — the code comment reads "Video PiP is the only exception when background video playback is disabled", and the function returns early for a video player in PiP.^[8] And a tab whose audio is being captured, for instance by a recorder or a virtual cable, is treated as audible and preserved.

There is a second, quieter background optimisation that people sometimes confuse with this one. Chromium can disable the video track of a hidden tab while keeping the audio running, which saves decode work without a visible pause. It is deliberately skipped for live content: the source comment says "Disabling tracks causes seeks which can cause problematic network delays on streaming resources", and the function bails out when the resource is streaming.^[8] A live Twitch channel is streaming, so this optimisation is not what stopped your player either.

# Current browser, still pausing

This is the case the rest of the internet does not cover, because the rest of the internet is still on the February story. If you are on a Chromium newer than 147.0.7727.47 and a hidden Twitch tab still stops, work down these in order. They are ordered by how often they turn out to be the answer, not by how interesting they are.

1. An extension or userscript. This is the single most likely answer on a current browser, and the evidence is in the archive of the most popular ad-blocking script for Twitch. One reporter wrote: "It only happens with the script active for me (chrome). With the script deactivated, the stream pauses but automatically unpauses when switching back on the tab."^[12] The maintainer, testing the opposite configuration, wrote: "With the audio set to muted (default) and the player playing; I switch to a new tab and switch back, the player is now paused (user interaction is required to unpause the stream). This occurs with or without the script active."^[12] Two people, two machines, two different answers — which is exactly what an extension conflict looks like. Test in a clean profile with no extensions before you test anything else.
2. Edge's sleeping tabs, if the tab has been idle a long time. Microsoft documents that sleeping tabs "puts background tabs to sleep after two hours of inactivity", and publishes the list of activities that prevent it. That list includes "The page is currently playing audio".^[11] It does not mention silent video. A muted Twitch tab left running for hours is therefore a plausible candidate on Edge in a way it is not on Chrome, whose published exemption list covers video as well. Treat this as a lead to test rather than a settled fact: the published wording is what we are reading, not the implementation.
3. Chrome's per-site Sound permission. The script maintainer noted in the same thread that as a prerequisite for reproducing anything he had, in his words, changed Twitch's site settings under Chrome to set "Sound" from "Automatic (default)" to "Allow".^[12] Automatic is a heuristic, and heuristics on a site you have deliberately muted can land somewhere you did not intend. Set it explicitly for twitch.tv and re-test.
4. Brave Shields. Brave's blocker and Twitch's ad detection interact badly in ways that have their own history, and it can leave the player stalled rather than pausing it as such. We cover the browser-by-browser picture, including which Brave settings break Twitch playback and login, in our guide to Twitch supported browsers.
5. A stall that looks like a pause. If the player shows a spinner, dumps to a lower rendition, or drops the quality menu entirely, that is a delivery problem and not a background-tab problem. Start from why the Twitch quality options are missing instead, and check the player's own stats before touching browser settings.

# Three fixes that cannot work

These three appear repeatedly in the current results for this question. Each of them is contradicted by a document its own vendor publishes, which makes them unusually easy to check.

• "Turn off Memory Saver." Google's own help page lists the activities that stop Chrome deactivating a tab, and the first entry is "Active audio or video (playback or calls)".^[10] A Twitch tab with the player running is on that list. Memory Saver also reloads a tab when you return to it — the page says "When you access an inactive tab, it automatically reloads"^[10] — which is a different symptom entirely from a player sitting paused mid-stream with the frame still on screen.
• "Go to chrome://flags and search for it." There is no flags entry. We searched Chromium's about_flags.cc and flag_descriptions.cc on main on 14 September 2026 for PauseMutedBackgroundAudio and found zero occurrences; the feature is declared only in the media layer.^[7] Nothing you type into the flags search box will surface it. The only manual lever is a command-line switch, which is not a realistic fix for a viewer and is unnecessary on a current build anyway.
• "Twitch did this to save bandwidth." A reasonable guess, and a common one — a user in the most-linked thread wrote "This issue only occurs for me (sometimes) when the stream volume is set to 0%. I figured Twitch implemented this feature intentionally for bandwidth-saving purposes".^[12] The volume-zero observation was right; the attribution was not. The code is in Chromium, not on Twitch's servers, and the reports that reached Google's own support forum in 2026 were filed under the title "Muted videos/streams pause when i switch tabs (twitch, youtube, twitter specifically)".^[14] Three unrelated sites failing at once points at the browser.

# What actually holds

Ranked by how permanent they are. The first one retires the problem on desktop; the rest are for Android, for Edge, and for the extension case.

1. Update the browser, and check the full build number. On desktop Chromium, anything from 147.0.7727.47 onward has the feature switched off.^[6] On a derivative browser, compare the Chromium version in its About page rather than the vendor's own version number. This is the whole fix for the February-to-April symptom, and it needs no settings changes.
2. Do not sit at zero volume. Drag the player to 1%. It is inaudible in practice and it keeps the volume condition false, so the rule never fires — on Android as well as on an out-of-date desktop build. Chromium treats a volume change in a hidden tab as a resume, so this also un-pauses a stream that already stopped.^[8]
3. Mute the tab instead of the player. Right-click the tab and choose Mute site, with the Twitch player itself left unmuted. The tab-level mute does not touch the media element's volume, so the condition the code checks is never satisfied.
4. Use Picture-in-Picture on Android. This is the one exemption written into the function itself.^[8] On a phone, where the feature remains on by design, PiP is the reliable way to keep a muted stream alive while you do something else.
5. On Edge, exclude twitch.tv from sleeping tabs. Microsoft documents a per-site block list under Settings, System and performance.^[11] Add twitch.tv and the two-hour timer stops applying to it. Worth doing regardless, because it also removes the tab from Edge's other performance optimisations.
6. Test in a clean profile before blaming the browser. A new profile with no extensions takes thirty seconds to create and settles the extension question outright. If the pause disappears there, re-enable your extensions one at a time; the ad-blocking ones for Twitch are the usual answer.^[12]

# If it is your channel being watched

There is a version of this question that arrives from the other side of the player: does a viewer whose tab paused still count, and did anything visible happen to channels during the window when desktop Chrome was doing this?

The counting rules themselves are not this page's subject and we do not restate them here — what Twitch's Viewer Count measures, and its position that a muted player in a background tab still counts, is set out with sources in how the Twitch viewer count works. The relevant point for this page is narrower and follows from it directly: that rule is about a player that is playing. A paused player is not playing. Whatever the counting policy says about muted tabs, it stops applying at the moment playback stops.

The more useful reading is the general one. A meaningful share of a live audience is watching in a tab that is not in front of them, muted, doing something else — and every layer between your encoder and their eyes has its own opinion about what to do with a tab nobody is looking at. Browsers save battery. Extensions rewrite the player. Latency modes trade buffer for immediacy. None of that is under your control, and none of it is worth chasing.

# The bottom line

A muted Twitch tab that stops the moment you click away was, on desktop, a deliberate Chromium battery-saving feature with a name, a measured justification of roughly 11% energy, a release it shipped in and a build it was withdrawn in. The withdrawal is the part that is missing everywhere else, and it is the part that decides what you should do: if your desktop Chromium is 147.0.7727.47 or newer, stop reading advice written in February.

If you are on Android, the behaviour is the shipped configuration rather than a fault, and the two things that reliably work are a volume above zero and Picture-in-Picture. If you are on a current desktop build and it still pauses, the order to test is extensions first, Edge's sleeping tabs second, the per-site Sound permission third — and if the player is spinning rather than sitting still, you are looking at a delivery problem and should start somewhere else entirely.

Everything asserted above is checkable without an account: Chromium's commit history and source are public, the Chrome and Edge help pages are public, and the bug is public. Where this guide has inferred rather than read — the tab-mute distinction, and whether Edge's audio-worded exemption list leaves a silent video tab eligible for sleeping — it says so in the line where it does it. That is the difference between a documented answer and a confident one.