Reduce Chrome Memory While Watching Video: 3 Steps (2026)

You’re three chapters into a tutorial, the fan spins up, and the cursor stutters. Say you keep tabs open and one is a 1080p video holding 300-530 MB. Chrome’s Memory Saver reclaims idle tabs but skips any tab producing audio. A timer-based suspender handles the gap. Three steps below.

Key takeaways

• A 1080p video tab holds 300-530 MB. A static article tab holds about 80 MB. The video tab is the one thing that must stay loaded.
• Chrome Memory Saver (reactive, ML-timed) never discards a tab playing audio. It reclaims idle tabs under system RAM pressure.
• A timer-based suspender like SuperchargePerformance frees idle tabs on your own clock, 90-95% of each tab’s RAM, without touching the video.

Why Your Video Tab Stays Resident

Chrome runs each tab in its own renderer process. When you discard a tab, the renderer terminates and the browser process keeps only the tab entry (favicon, title, URL), freeing 90-95% of that tab’s RAM. Memory Saver, built into Chrome since v108, calls that discard automatically under system pressure.

The safety gate, however, skips several categories: the active tab, pinned tabs, any tab producing audio, tabs with unsubmitted form input, and sites on your exclusion list. A video tab with sound sits in the “producing audio” bucket, so it keeps running at full cost no matter how much RAM pressure the system is under.

The GPU process adds a second layer. After opening and closing multiple video tabs in one session, the GPU process accumulates texture memory and can hold 1-2 GB on Windows 11. Ending the GPU process reclaims the accumulated memory, and Chrome restarts the process within seconds.

Step 1: Enable Memory Saver and Pick a Mode

Open chrome://settings/performance in the address bar. Toggle Memory Saver on. You get three modes:

Below the mode selector, the “Always keep these sites active” exclusion list (added in Chrome 124) lets you pin specific domains that should never be discarded. Add your video platform if you want an extra layer of protection beyond the audio gate.

Three steps total: open the settings page, flip the toggle, pick a mode. The change is immediate.

Step 2: Suspend Idle Tabs on a Timer

Memory Saver is reactive. It waits for system RAM pressure or the ML revisit prediction before discarding anything.

A timer-based suspender closes that gap. SuperchargePerformance (Chrome Web Store version 1.5.1) runs a chrome.alarms check every 30 seconds. When a tab has been inactive past the timer, the extension calls chrome.tabs.discard(), which terminates the renderer and frees 90-95% of that tab’s RAM. The tab stays in your strip. It just no longer burns memory.

The suspension safety gate mirrors Memory Saver’s: a tab is not suspended if it is active, pinned, or producing audio. The extension also skips chrome://, chrome-extension://, and file:// URLs, tabs created within the last 30 seconds, 34 auto-protected web-app domains (Figma, Notion, Slack, Discord, Google Docs, …), any site on your personal whitelist, and tabs holding unsaved form data.

The free tier gives you three timer settings: Off, Low (15 minutes), and Med (5 minutes, the default on install). PRO lets you set the interval in seconds.

The extension also ships 195,123 DNR blocklist rules that stop ad and tracker requests.

Step 3: Reclaim GPU Process Memory

Open Chrome’s Task Manager (Shift+Esc). Look for the GPU Process row. If it shows 1 GB or more after you have opened several video tabs in a session, that is accumulated texture memory.

Select the GPU Process row and end that process. Chrome restarts the GPU process within seconds. Your current video tab resumes decoding. Any closed video tab’s textures are gone.

You can also open chrome://discards for a per-tab view of memory and discard state, including an “Urgent Discard” control for forcing a specific tab to release its renderer immediately.

Memory Saver vs a Timer-Based Suspender

What we measured

Measured on 2026-10-20 using Chrome for Testing 148.0.7778.96 (headless, fresh profile) with SuperchargePerformance 1.4.9, on a Linux machine (AMD Ryzen 7 9800X3D, 33 GB RAM) with 8 tabs from page set fixture-heavy-v1.

Method:

1. Launch Chrome for Testing 148.0.7778.96 headless with a fresh, empty profile, Chrome’s default feature settings and audio muted. Load a tabs-only helper extension plus SuperchargePerformance 1.4.9.
2. Open 8 background tabs from page set fixture-heavy-v1, one after another. Each must return HTTP 200 and finish its page script.
3. Keep one blank tab in the foreground and close any other tab Chrome or an extension opened on its own.
4. Measure memory as PSS (proportional set size) summed over every Chrome process, read from Linux /proc//smaps_rollup. Shared pages are split across the processes that share them, so nothing is counted twice. This is not the same number as Chrome Task Manager’s “Memory footprint”.
5. Wait 10 s, then until three samples 2 s apart are within 2 % of each other. Take the middle one (“before”).
6. Discard all 8 background tabs with SuperchargePerformance’s own “suspend all inactive tabs” action (force mode). Confirm through chrome.tabs that exactly 8 are discarded.
7. Wait 30 s (Chrome releases a discarded tab’s memory gradually, 10 to 20 s after the discard), then settle the same way and measure “after”.
8. Run the whole procedure twice from scratch. Each reported number is the mean of the two runs, which agreed within 10 %.

Two independent runs, fresh browser each time, checked metrics agreed within 10% (largest gap 1.16%).

When the Built-In Saver Is Enough

If you keep under ten tabs and run Memory Saver on Maximum, you do not need an extra extension. Memory Saver discards idle tabs under RAM pressure, and the audio gate keeps your video live. You are done.

A timer-based suspender frees each tab’s RAM on your own clock, 90-95% of it, without touching the video tab or stopping playback. That is the missing lever.