Chrome Memory Saver: check tab activity and site exceptions before assuming a fault
If a tab still uses memory after you enable Chrome Memory Saver, check its activity and exceptions before assuming the setting is broken. This guide covers desktop Chrome's Performance controls and sites that should remain active.

Based on the sources linked below. The photograph is for illustration.
Before you start
STEP BY STEP
Here’s how
1. An old tab is not automatically a faulty tab
A Quasarzone question from August 18, 2024 describes a page still using about 200MB after three hours with Memory Saver enabled following a PC reset. That is one person's observation, not a universal memory target or deactivation deadline. Google explains that Chrome frees memory by deactivating unused tabs and reloads them when you return. Instead of judging one currently viewed tab's number, first identify which tabs were unused and what activity they still contained.
2. Check desktop Chrome's Performance controls
Go to the top-right More menu → Settings → Performance and check Memory Saver. Google's guide lists Moderate, Balanced and Maximum levels: Moderate waits longer, while Maximum deactivates tabs sooner. Record the current level and compare changes one at a time. This guide does not set a universal delay or savings percentage. These performance customization controls do not apply to Chrome on Android or iOS.
3. Look for work that is still happening inside a tab
Google lists audio or video playback and calls, screen sharing, downloads, partially completed forms and pinned tabs among activities that can prevent deactivation. A tab may still have work to do even when you have not clicked it. As a comparison example, leave an ordinary reading page without important input open while working in another tab. Do not interrupt a necessary call or download merely to test the feature; check after the activity finishes. Save any document you are editing first.
4. Keep the always-active list focused
Review Always keep these sites active under Settings → Performance. Use Add to select an available site from your current tabs or enter a web address manually. For example, select a work site where reloading on return is inconvenient. Conversely, if the site you are using to check savings is already listed, reconsider whether that exception matches your goal. Excluding every site leaves fewer tabs available for deactivation, so keep the list limited to what you need.
5. Separate a settings check from a performance result
Confirming the setting and exceptions does not prove a memory problem is fixed. Compare similar sites and workloads before and after a change, and also consider how inconvenient reloading a returning tab becomes. If trouble persists, restore the previous setting and consult Chrome Help for further diagnosis. You need not apply every forum comment as though it were a verified fix. This explains the official feature's scope, not a measured improvement on a particular PC.
Sources & further reading
Quasarzone — Memory Saver is enabled but appears inactive (August 18, 2024) ↗Google Chrome Help — Personalize Chrome performance ↗Some sources are in Korean. Check the original guidance for current product, store or software conditions.
Read this article in Korean →
