The single most common Chrome performance complaint — that the browser consumes too much RAM, slows the whole system down, and makes everything sluggish when many tabs are open — has a built-in solution that most users have never enabled. Chrome Memory Saver is a native feature in the Performance settings that automatically reduces the memory usage of inactive tabs. Enable it once, configure an exceptions list for apps that need to stay active, and it runs silently in the background from that point on. For the bigger picture, our Chrome How-To Guides pulls everything together.
How Memory Saver works and what it actually does
Memory Saver identifies tabs that have been inactive — no user interaction, no active media playback, no ongoing network requests — and places them in a reduced-resource state. In this state, the tab’s renderer process is suspended: JavaScript execution is paused, the DOM is held in a low-memory representation, and most of the RAM the tab was consuming is released back to the operating system. The tab continues to appear in the tab bar with its title and favicon visible — from the interface perspective, it looks like any other open tab.
The visible consequence of that reduced-resource state is reloading — it is why Chrome reloads tabs when you switch back to them. That is normal Memory Saver behaviour rather than a fault, and it can be limited per site.
The key distinction from simply closing the tab: the URL, the page position, and any unsaved form input are preserved. Clicking the tab reactivates it — the page reloads from its stored state and returns to full activity within a few seconds. You don’t need to navigate back to the page or bookmark it first. The tab was there the whole time.
Memory savings vary by what was open in the tab. A simple text article might use 50–80MB of RAM when active; throttled, that drops to 5–15MB. A tab with a complex web application — a design tool, a data dashboard, a messaging platform — might use 200–400MB when active; throttled, it drops to a similar minimal footprint. Hovering over the indicator icon on any throttled tab shows the exact amount of RAM reclaimed from that specific tab. Across a session with twenty throttled tabs averaging 100MB each, Memory Saver might reclaim 1.5–1.8GB — on a machine with 8GB total system memory, that’s a substantial portion of what the operating system and other applications need to run smoothly.
Memory Saver doesn’t apply to all tabs indiscriminately. Tabs actively playing audio or video are excluded — pausing your music by throttling the tab would be an unacceptable interruption. The foreground tab (the one you’re currently viewing) is never throttled. Tabs with ongoing network activity — a file upload, a live data stream, a background sync — are excluded for the duration of that activity. And tabs from domains in the exceptions list are permanently excluded regardless of how long they sit idle.
Enabling and configuring it
Chrome Settings → Performance (left sidebar) → Memory section → toggle Memory Saver to On. Alternatively: type chrome://settings in the address bar, press Enter, then navigate to Performance.
Below the toggle, the exceptions list appears. This is where you add specific sites that should never be throttled. Click “Add” → enter the domain (for example, app.slack.com or trello.com) → Add. The domain appears in the exceptions list immediately.
Domain specificity matters in the exceptions list:
- Entering
example.comexcludes all tabs from that domain including subdomains - Entering
app.example.comexcludes only that specific subdomain, leaving other subdomains subject to normal throttling
The exceptions list should be limited to web applications whose functionality is genuinely compromised by tab throttling — communication platforms, project management tools, monitoring dashboards, anything where the tab reactivation delay of 5-10 seconds would be disruptive. Adding everything to the exceptions list effectively disables Memory Saver in practice.
Test after enabling: open several tabs, leave them idle for a few minutes, and check whether the Memory Saver indicator appears on inactive tabs. If no indicators appear after 5-10 minutes: either those tabs have active processes keeping them awake, or the feature isn’t enabled. The Shift+Esc Task Manager shows memory usage per tab and confirms which are throttled.
Reading Memory Saver indicators in the tab bar
When Memory Saver throttles a tab, a small icon appears in the tab strip — typically a leaf or memory icon positioned where the loading spinner normally appears. The indicator is deliberately subtle; the goal is for the feature to operate invisibly in the background rather than drawing attention to itself.
Hovering over the indicator reveals a tooltip showing the exact amount of RAM reclaimed, expressed in megabytes. This tooltip is the most actionable diagnostic output from Memory Saver — it confirms the feature is working, shows the scale of savings on specific tabs, and helps evaluate whether a particular site is worth adding to the exceptions list based on its actual memory consumption.
Clicking any throttled tab reactivates it. For simple text-based pages: reactivation takes 1–3 seconds. For complex web applications with heavy JavaScript: 5–10 seconds before the application is fully interactive again. This reactivation time is why frequently-used web applications belong in the exceptions list — the interruption of a 10-second reload on every return to Slack or Notion is more disruptive than the memory saving is beneficial.
Memory Saver vs other memory management approaches
The comparison to closing tabs is the most obvious one: closing a tab recovers more memory than throttling (a closed tab uses zero RAM; a throttled tab uses a small amount). But closing requires a deliberate action, and the tab must be reopened and the page re-found if needed again. Memory Saver provides most of the memory benefit with none of the friction — the tab stays available in the bar, ready to reactivate with one click, without requiring bookmarking or remembering where to find the page.
The comparison to third-party tab suspension extensions — tools like The Great Suspender and its successors — favours Memory Saver on several dimensions. As a native Chrome feature, it doesn’t require installing an extension with broad page-access permissions, doesn’t add to Chrome’s extension overhead, and doesn’t carry the security and maintenance risks that third-party tab suspension extensions have historically involved. The Great Suspender was found to contain malware after a change in maintainership — a risk that Chrome’s native implementation inherently avoids.
Energy Saver is the companion feature in the same Performance settings panel. Where Memory Saver reduces RAM by throttling inactive tabs, Energy Saver reduces battery consumption by limiting background activity, reducing visual effects, and throttling non-visible tab animation when battery level drops below a configured threshold. Both can be active simultaneously — Memory Saver for memory-constrained machines and many-tab sessions, Energy Saver for battery-powered devices during extended use away from power.
Our Chrome Task Manager guide covers reading memory usage data per tab and extension to identify which tabs would benefit most from throttling, and our guide on speeding up Chrome covers Memory Saver alongside the full range of performance optimisation approaches. For the specific memory reduction algorithm and the conditions under which Memory Saver makes throttling decisions, Google’s Chrome Performance settings documentation covers the implementation details.
Memory Saver on different hardware and use cases
The practical value of Memory Saver scales inversely with available system RAM — most impactful where Chrome’s memory consumption is a real constraint on overall system performance, less urgent where available RAM is abundant.
- 8GB laptops: Memory Saver can be the difference between a responsive and a sluggish system during a multi-tab research session alongside other applications
- 32GB desktops: provides less urgent benefit, though still contributes to keeping Chrome’s footprint lower over long sessions as tabs accumulate
- Chromebooks with 4–8GB: where Chrome is the primary computing environment, Memory Saver is one of the highest-impact configuration changes available for improving performance without hardware changes
Use case profiles where Memory Saver provides targeted value:
- Researchers and journalists maintaining many reference tabs simultaneously across multiple sources — the tabs they’re not actively reading hold their place while consuming minimal resources
- Students in online courses keeping lecture notes, research, and assignment pages open in parallel during long study sessions
- Knowledge workers who accumulate tabs throughout the day as they switch between tasks — throttling handles the background tabs automatically without requiring the discipline to close and reopen pages
| Tab state | Memory Saver effect | Reactivation time |
| Simple article / text page | 50-80MB → 5-15MB | 1-2 seconds |
| Moderate web app | 100-200MB → 10-20MB | 2-5 seconds |
| Complex web application | 200-400MB → 20-40MB | 5-10 seconds |
| Active media tab (audio/video) | Not throttled | N/A |
| Exceptions list tab | Not throttled | N/A |
Memory Saver is one of Chrome’s best-designed built-in features precisely because it requires almost no ongoing management after initial setup. Enable it, add the 4-5 web applications that genuinely need to stay active to the exceptions list, and forget about it. Chrome’s memory footprint improves automatically from that point forward, the savings are visible in the Task Manager, and the browsing experience is noticeably more responsive on machines where RAM was the limiting factor.
What Memory Saver doesn’t fix
Being specific about limitations prevents misplaced expectations. Memory Saver addresses inactive tab memory consumption — it doesn’t reduce the memory used by the currently active tab, doesn’t reduce extension overhead (extensions run separately from tabs), and doesn’t help when Chrome is slow because of network latency or server-side performance issues rather than RAM constraints.
If Chrome is slow despite Memory Saver being active: check whether the slowdown is tab-count related or extension-related. The Chrome Task Manager (Shift+Esc) shows both tabs and extensions with their memory and CPU usage. If extensions are the top memory consumers rather than tabs: the extension audit approach (disabling, testing, removing unused ones) addresses what Memory Saver doesn’t touch. The two approaches are complementary, not competing.
Memory Saver and session restore
When Chrome restores a session from a previous browser close (“Continue where you left off” startup setting), all restored tabs start as unloaded placeholders — effectively in a throttled state similar to Memory Saver. Chrome loads them fully only when clicked. This means session restore on a 40-tab session is much faster and less memory-intensive than 40 tabs all loading simultaneously, because only the active tab loads immediately.
Memory Saver effectively extends this on-demand loading behaviour throughout the browsing session rather than just at startup. The tabs that would previously stay fully loaded in memory all session are now loaded on-demand each time they’re visited and throttled again when left idle. For users who leave Chrome open for days or weeks without restarting: this means the browser doesn’t accumulate memory debt the way it used to — Memory Saver continuously reclaims memory from idle tabs rather than letting Chrome’s footprint grow monotonically over long uptime periods.
The impact of Memory Saver on real-world Chrome performance is significant enough that it should be one of the first settings checked on any machine where Chrome feels slow or memory-constrained. It’s enabled in Settings → Performance → Memory with a single toggle, takes less than a minute to configure with a basic exceptions list, and produces immediately measurable results visible in the tab bar indicators and the Task Manager memory figures. For a feature that does this much with this little setup effort: it’s genuinely worth enabling if you haven’t already.
Monitoring the savings over time
Chrome doesn’t provide a cumulative report of how much memory Memory Saver has saved over a session — it shows only the current state of each throttled tab via the tooltip. For users who want a sense of the cumulative impact: open Chrome’s Task Manager (Shift+Esc) when working with many tabs, note the total “Memory Footprint” figure shown at the bottom, then mentally compare it to what the same session would look like with all tabs fully loaded. A rough calculation: multiply the number of currently throttled tabs by the average savings per tab shown in their tooltips. For 15 tabs at 80MB average savings each: Memory Saver is currently reclaiming approximately 1.2GB from this session’s footprint.
This calculation also reveals which tabs are the most memory-intensive and therefore the best candidates for the exceptions list adjustment. A tab that saves 400MB when throttled is a significant consumer when active — whether it deserves to be in the exceptions list depends on how frequently you need to interact with it without a reactivation delay. A tab that saves only 20MB when throttled barely justifies an exceptions list entry either way. The tooltip data makes these trade-offs visible and specific rather than relying on general intuitions about which sites are “heavy.”
Memory Saver and pinned tabs
Pinned tabs are treated the same as regular tabs by Memory Saver — they can be throttled if inactive long enough. If you rely on pinned tabs as persistent, always-active references for specific tools or dashboards: add their domains to the exceptions list to prevent them from being throttled and requiring a reload each time they’re clicked. The intent of pinning a tab (it’s important and always needed) generally aligns with the intent of the exceptions list (it should never be throttled). For pinned tabs that are more “available if needed” than “needed immediately at any moment”: letting Memory Saver throttle them and accepting the brief reload delay preserves the memory benefit without meaningfully disrupting the workflow.
Chrome’s Memory Saver represents a practical, thoughtful solution to one of the browser’s most persistent criticisms — RAM consumption from many open tabs — without requiring any compromise on tab management workflows. The ability to keep 30 tabs open without paying the full memory cost for all 30 simultaneously changes the equation for users who use open tabs as a working memory for their current research, projects, and reference material. Enable it, configure the exceptions intelligently, and the browser’s memory footprint becomes a manageable quantity rather than something that grows without bound as work sessions continue. Our guide on Fix Chrome High Memory Usage covers an adjacent issue.
