Chrome Memory Saver: What Published Tests Show and Which Mode to Choose

Chrome Memory Saver can materially reduce RAM use, but Maximum is not automatically the right setting. In one published 32-tab Windows test, total Chrome memory fell from about 5.8 GB with all tabs active to 4.6 GB on Balanced and 3.6 GB on Maximum after a 20-minute idle period. The publisher’s approximately 21% and 38% reductions are external measurements, not Quasa Media results or universal expectations.

For most desktop users, Google’s performance documentation identifies Balanced as the recommended mode, making it the best starting point. Choose Maximum when freeing memory matters more than avoiding reloads, or Moderate when you frequently return to background applications and want Chrome to wait longer before deactivating them.

What the published 32-tab test found

The independent review was updated June 8, 2026 and reports testing Chrome 149 on Windows 11 with 16 GB of RAM. Its workload comprised 32 tabs, including documents, news pages, two video sites, a Figma board and multiple articles.

According to the review’s measurement table, all 32 active tabs used about 5.8 GB in total. After a 20-minute idle period, the reported totals and reductions were approximately 4.6 GB on Balanced and 3.6 GB on Maximum, equivalent to decreases of about 21% and 38% from that active baseline.

The result shows that Memory Saver produced a meaningful reduction in this particular mixed workload and that Maximum reclaimed more memory than Balanced under the reported conditions. It does not demonstrate that every 32-tab session—or every computer—will produce the same percentages.

The page does not document repeated runs, error ranges or a complete per-site breakdown, and its publisher promotes a competing tab-suspension extension on the same review page. Treat the figures as a useful external observation with limited methodology, then compare the modes using your own sites, extensions and hardware.

What Moderate, Balanced and Maximum change

Memory Saver deactivates tabs you are not using so their resources can be released; accessing an inactive tab makes Chrome reload it. Chrome’s current instructions describe Moderate as using a longer period before deactivation, Balanced as using an optimal period and Maximum as using a shorter period.

Google’s October 29, 2024 announcement adds that Moderate responds to system needs, Balanced considers browsing habits and system needs, and Maximum deactivates unused tabs more quickly than the other modes. Neither Google’s setup documentation nor its mode announcement specifies exact minute thresholds, so these settings are relative levels of aggressiveness rather than predictable timers.

• Moderate: waits longer, favoring fewer interruptions over faster memory recovery.
• Balanced: mediates between memory savings and the likelihood that you will revisit a tab.
• Maximum: deactivates eligible tabs sooner, favoring memory recovery while increasing the chance that an older tab must reload.

These modes are not limits on Chrome’s total memory use. Active pages, browser services and extensions can continue consuming RAM even after eligible background tabs have been deactivated.

Which mode fits your workload?

Start with Balanced unless your workload gives you a specific reason to move. It is the recommended option in Google’s Memory Saver settings and is appropriate for a normal mixture of articles, email, documents and occasional web applications.

Try Maximum when Chrome competes for memory with demanding desktop software or when system memory pressure interferes with other work. Judge it by whether the computer behaves better overall and whether the resulting tab reloads remain acceptable—not by tab count alone.

Choose Moderate when the cost of restoring a background tab is the larger concern. This can include sessions built around dashboards, remote consoles, research databases or web applications whose state is inconvenient to reconstruct.

Turning Memory Saver off can be reasonable during a short, controlled session in which every tab must remain immediately available and the computer has sufficient memory. For one troublesome site, however, an exclusion is more targeted than disabling the feature everywhere.

How to keep important sites active

Chrome already protects some activities from deactivation. Google’s documented list includes active audio or video, calls, screen sharing, page notifications, active downloads, partially completed forms, pinned tabs and pages connected to USB or Bluetooth devices.

Do not assume that every important web application will meet one of those conditions. A dashboard that refreshes quietly or an administrative session may matter to your work without continuously performing a protected activity.

1. Open Chrome Settings and select Performance.
2. Turn on Memory Saver and choose a deactivation level.
3. Under Always keep these sites active, add only the domains whose background state must be preserved.
4. Leave each protected service in the background for longer than a normal interruption, then check its alerts, synchronization and unsaved state.

Exclusions can cover site patterns rather than a single page. Google’s matching example says that adding google.com also covers subdomains such as drive.google.com and calendar.google.com. Use the narrowest pattern that meets your requirement so unrelated pages are not kept active unnecessarily.

How to compare the modes on your computer

Your own controlled comparison is more relevant than copying an external percentage because it includes your real operating system, extensions and web applications. Keep the workload consistent so the Memory Saver mode remains the principal variable.

1. Create a fixed set of sites you genuinely use, including both ordinary pages and heavier web applications.
2. Restart Chrome, open those pages in the same order and interact with each one so it finishes loading.
3. After a fixed settling period, record the total memory used by all Chrome processes in your operating system’s process monitor.
4. Leave the same neutral tab in the foreground for a fixed idle interval. Avoid starting downloads, media or form editing unless they are deliberately part of the workload.
5. Record memory again, revisit the background tabs and note reloads, lost position, delayed notifications or missing state.
6. Restart Chrome and repeat the procedure with another mode. Repeat each condition if you need an average rather than a single observation.

On Windows and Linux, Google’s keyboard-shortcut reference assigns Shift+Esc to Chrome Task Manager. You can also open it from More tools, and Google’s optimization instructions say to select Memory to sort tasks by their usage.

Chrome Task Manager helps separate tabs, extensions and background tasks, while the operating system’s process monitor provides a session-wide Chrome total. Record both if possible: summing only visible page rows may omit browser, GPU, extension or worker processes.

How to interpret the measurements

Evaluate memory recovered and work interrupted together. Calculate the reduction by subtracting the idle result from the active baseline, dividing the difference by the active baseline and converting the result to a percentage. Pair that percentage with the number of unexpected reloads and any loss of useful background behavior.

A lower reading is not automatically a better outcome if a critical monitoring page stops updating. Conversely, a modest reduction may be valuable if it prevents disk swapping or leaves sufficient memory for another application.

Do not compare a fresh startup in one mode with a long-running session in another. Keep the Chrome profile, tab set, foreground tab, idle interval and other running applications consistent. Page updates, extension activity and delayed background work can otherwise obscure the mode’s effect.

Also record reload latency and state preservation. Memory Saver deliberately exchanges retained background resources for available memory, so the appropriate mode is the one that improves the complete workflow rather than merely producing the smallest isolated figure.

Why savings may be smaller than expected

First, some tabs may be ineligible for deactivation. Active media, calls, downloads, partially completed forms and pinned tabs are among the activities covered by Google’s automatic protections.

Second, active content or extensions may dominate Chrome’s footprint. Memory Saver cannot deactivate the page you are currently using, and reclaiming background tabs will not fix a demanding foreground application. Sort Chrome Task Manager by memory and inspect whether the largest tasks are expected pages, unnecessary extensions or unwanted background processes.

Third, an idle interval may be too short, or several variables may have changed together. Closing tabs, updating extensions and switching Memory Saver modes during the same run prevents a useful comparison. Change one variable at a time and preserve the raw readings.

A practical starting configuration

Set Memory Saver to Balanced, add only essential sites to the always-active list and use Chrome through several representative work sessions. If memory pressure remains disruptive, compare Balanced with Maximum using the same workload and retain Maximum only when the additional headroom is worth the reloads.

If Maximum produces little improvement, inspect Chrome Task Manager before concluding that Memory Saver has failed. Protected tabs, active pages or extensions may account for most of the remaining footprint. Let a repeatable measurement of your own workload—not the lowest number from someone else’s test—determine the mode.

Also read:

• NAB Show Expands Creator Lab for 2026 with AI and Networking Focus