Modern web applications, development dashboards, and real-time collaboration platforms consume substantial amounts of system RAM when left active across dozens of browser tabs. Google Chrome includes a native performance optimiser known as Memory Saver (formerly High Efficiency Mode) that automatically frees memory from inactive tabs so active browsing remains responsive. However, certain mission-critical applications—such as ongoing audio calls, real-time monitoring dashboards, and active database consoles—must remain awake in the background. Configuring Memory Saver site exceptions prevents Chrome from discarding essential background workflows while preserving memory efficiency across general tabs.
How Chrome Memory Saver Manages Background Tabs
Memory Saver continuously monitors system memory pressure and individual tab idle times. When memory pressure increases or a tab has remained unviewed for an extended period, Chrome transitions the tab into a discarded state. In this mode, the tab’s Document Object Model (DOM) and rendering context are purged from physical RAM, while its URL, session history, and scroll position are retained in lightweight metadata.
When you click back onto a discarded tab, Chrome automatically reloads the page from the local cache. While this process is transparent for static content, it can terminate unsaved form inputs, interrupt long-polling WebSocket connections, or reset media playback in web applications that lack robust local state persistence.
Prerequisites and Compatibility
- Google Chrome version 108 or newer running on Windows, macOS, or Linux.
- Administrative rights if deploying exclusions across enterprise fleets via Group Policy or Chrome Enterprise Core.
How to Enable and Configure Memory Saver
Memory Saver can be adjusted directly from the built-in Chrome Performance settings interface:
- Open Google Chrome.
- Click the three vertical dots (customise and control) in the upper-right corner and select Settings.
- In the left sidebar, click Performance.
- Locate the Memory Saver toggle switch and ensure it is turned On.
- Depending on your Chrome version, you can select the discarding aggressiveness:
- Moderate: Discards tabs only under noticeable memory pressure based on system needs.
- Balanced: Balances system responsiveness with user habits, discarding tabs after reasonable idle periods.
- Maximum: Aggressively discards tabs shortly after they become inactive to maintain maximum free RAM.
Adding Site Exceptions to Keep Tabs Always Active
To guarantee that specific web services remain active in the background without being discarded, add them to the exclusion list:
- Navigate to Settings > Performance.
- Under the Memory Saver section, locate the sub-heading labelled Always keep these sites active.
- Click the Add button on the right.
- A dialogue box displays two configuration tabs:
- Currently open tabs: Select any running web applications directly from your current session (e.g., Jira, Grafana, Slack).
- Add manually: Type a specific domain, subdomain, or URL pattern.
- To exclude an entire domain including all its subdomains, format the entry using wildcard notation:
[*.example.com]. - Click Add to save the rule.
Configuring Exceptions via Enterprise Policy
For IT administrators managing Windows workstations, Memory Saver exclusions can be enforced across domain-joined machines using Group Policy (GPO) or registry settings:
Path: HKLM\SOFTWARE\Policies\Google\Chrome
Value Name: TabDiscardingExceptions
Value Type: REG_MULTI_SZ / List
Data:
https://monitoring.internal.network
[*.]slack.com
[*.]teams.microsoft.com
Alternatively, the general Memory Saver policy can be enforced using the HighEfficiencyModeEnabled integer setting (1 for enabled, 0 for disabled).
Inspecting Tab Discard States in chrome://discards
To verify that your exceptions are functioning as expected, Chrome provides an internal diagnostic dashboard:
- In the Chrome address bar, navigate to
chrome://discards. - Review the table of all open tabs across your active windows.
- Locate your excluded web application in the list.
- Inspect the Auto Discardable column: excluded domains will display a cross icon (False), confirming Chrome is prevented from purging that tab from memory.
Best Practice Tips for Tab Management
- Target Specific Subdomains: Avoid whitelisting broad generic domains such as
[*.]google.comunless necessary; instead, specifymeet.google.comordocs.google.comto keep general search tabs eligible for memory savings. - Combine with Battery Saver: On portable laptops, ensure Energy Saver mode is also activated in the Performance menu to throttle background visual frame rates when unplugged.
- Monitor Extension Overhead: Heavy browser extensions run in separate background processes that are exempt from Memory Saver; audit your installed extensions via
chrome://extensionsto reclaim additional RAM.