Table of Contents
For high Chrome memory use, start with Settings > Performance > Memory Saver and check which tabs or extensions consume resources. Experimental flags are version-dependent, and the four settings discussed below do not all act as straightforward RAM-saving switches.
The screenshots show flags from particular Chrome builds. A flag can be renamed, removed, or restricted to a platform. Leave an experiment at Default unless you have a specific reason to test it and a way to compare the result.
Partial swap is a rendering control

chrome://flags/#ui-disable-partial-swap relates to partial screen updates in the graphics pipeline. It does not prioritize active tabs or automatically unload inactive ones.
The identifier contains “disable,” so do not infer its effect from a shortened article label. Chromium’s switch definition describes disabling partial swap for certain graphics drivers or emulators. Treat this as a rendering or compatibility setting rather than a general memory fix.
Infinite Tabs Freezing pauses eligible background work

chrome://flags/#infinite-tabs-freezing has been used to freeze eligible tabs outside a protected set of recently used tabs. Tabs with important background activity, such as audio or a video call, can be excluded. The protected-tab count and behavior are implementation details that may change.
Freezing pauses page tasks. Discarding unloads the page from memory and reloads it when you return. Chrome’s freezing explanation makes this distinction clear. Freezing a tab should not be described as automatically removing all of its memory.
Memory Purge on Freeze Limit controls repeated cleanup

chrome://flags/#memory-purge-on-freeze-limit is a lower-level experiment concerning memory purges in renderers with frozen pages. Its description limits purging to once per backgrounded interval to reduce overhead when pages are periodically unfrozen.
That does not establish a predictable RAM saving on your PC. The result depends on Chrome’s other tab-management behavior and the pages you keep open. Avoid enabling it simply because its name includes “memory.”
Disable Subframe Process Reuse can create more processes
chrome://flags/#disable-process-reuse controls whether out-of-process subframes can reuse compatible processes from unrelated tabs. Chromium’s flag description says enabling this experimental mode results in more processes being created.
Leave process-management settings at Default for ordinary browsing. Chrome’s process model is more complex than “one tab equals one process”: frames, sites, extensions, and other components can affect the process count.
Use supported memory controls first
- Save unfinished work and update Chrome.
- Open Settings > Performance and turn on Memory Saver.
- Choose the available deactivation level that suits your workflow.
- Add important sites to the keep-active list if they must remain ready in the background.
- Close unneeded tabs and disable unnecessary extensions one at a time.
Memory Saver can reload an inactive page when you return to it, so check how important web apps handle that behavior. Google’s performance-settings guide describes the supported options.
Use the Chrome and Edge Task Manager guide to identify a particular tab or extension. For system-wide pressure, see how to inspect Windows resource use.
If you test a flag, record its original setting, change one item, relaunch, and compare the same workload. Restore Default when the change offers no clear benefit or causes problems. Keep sandbox and site-isolation protections enabled.
Reader Comments 0
Sign in with email or Google to join the discussion.