How to Reduce Chrome Memory Usage: 10 Fixes for High RAM

How to reduce Chrome memory usage fast

If Chrome is using too much memory, start here: open Chrome Task Manager, sort by Memory Footprint, close or save inactive tabs, enable Memory Saver, remove heavy extensions, review Preload Pages, then restart and update Chrome. That cuts the active tab and extension load behind most high Chrome RAM sessions.

Fix	Speed	RAM impact	Best when
Open Chrome Task Manager	Immediate	High	You need to find the worst tab or extension
Close or save inactive tabs	Immediate	High	You have 20+ tabs open
Enable Chrome Memory Saver	Minutes	Medium-high	Tabs sit inactive for long stretches
Add Memory Saver exceptions	2 minutes	Protective	Calls, dashboards, or music must stay active
Trim extensions	10 minutes	Medium	Chrome has many background processes
Review Preload Pages	2 minutes	Low-medium	Chrome feels busy before you open pages
Restart and update Chrome	5 minutes	Low-medium	You have not restarted Chrome recently

Why Chrome uses so much memory

Open your system's activity monitor and you may see several Chrome processes using a lot of RAM. That does not always mean Chrome is broken. Chrome runs tabs, extensions, renderers, media, background pages, and service workers in separate processes so one bad tab is less likely to take down the browser.

The tradeoff is memory. Every active tab needs RAM for rendering, JavaScript, media playback, and page state. Heavy web apps such as Google Sheets, Figma, Slack, Notion, or large dashboards can use far more memory than a simple article. Extensions add their own background work. Chrome can also preload pages so they open faster.

The pattern is simple: the more open tabs, extensions, and background tasks you keep alive, the more memory Chrome uses. The fix is to find the tab or extension doing the damage, then make Chrome keep less loaded.

You do not have to guess. Start with the fast checks, then move down the list.

Fix 1: Use Chrome's built-in Task Manager

Before changing settings, see what is eating your memory. Press Shift + Esc on Windows or Linux, or go to Menu > More Tools > Task Manager on any platform. Chrome's internal Task Manager shows memory usage per tab, extension, and background process.

Sort by the Memory Footprint column to find the worst offenders. A single heavy web app can use more memory than a stack of simple tabs. Select any process and click End Process if you are ready to close that tab or extension process.

You can also turn on tab memory usage on hover in Chrome's Performance settings. That makes it easier to spot a heavy tab before opening Task Manager.

Fix 2: Close tabs you are not actively using

This is obvious, and it works. Every tab you close frees its active page state. If you have 50 tabs open but are using 5, the other 45 tabs are still asking Chrome to remember them.

People keep tabs open for a reason. They are reference material, tasks in progress, or articles to read later. Closing them can mean losing context. That is where the next fix helps.

Fix 3: Save tab groups with TabGroup Vault, then close them

If you want to cut Chrome's memory without losing your work, save your tab groups before closing them. TabGroup Vault takes a snapshot of your tab groups: every tab URL, the group name, the group color, and the tab order. Then you can close those tabs, reclaim the memory, and restore the group later with a single click.

This works especially well for project-based browsing. Save your Research group on Monday, close it, work on something else, and restore it on Wednesday exactly as it was. Chrome stays lighter in between, and the project stays intact. For the full workflow, use the guide to reducing Chrome memory usage without losing your tabs.

Fix 4: Enable Chrome's Memory Saver mode

Chrome includes a built-in Memory Saver setting under Settings > Performance. When Memory Saver deactivates an inactive tab, the tab stays visible in your tab strip, but its contents reload when you open it again.

Chrome desktop gives you three Memory Saver levels: Moderate, Balanced, and Maximum. Moderate deactivates tabs less often, Balanced sits in the middle, and Maximum frees memory more aggressively. If a site must stay live, add it to "Always keep these sites active" in the same Performance settings area.

Memory Saver is useful for passive tab buildup, but it is not the same as saving your work. Chrome's tab discarding predates Memory Saver, and Memory Saver arrived in Chrome 108 to make proactive deactivation more common for inactive background tabs. When a deactivated tab reloads, page state can change. For tabs you need to preserve as a project, saving the tab group with TabGroup Vault before closing it is still the more predictable approach.

Why Memory Saver may not seem to work

Memory Saver does not deactivate every inactive tab. Chrome may keep tabs active when they are doing work that should not be interrupted, including audio or video playback, screen sharing, notifications, downloads, partially filled forms, pinned tabs, and pages connected to USB or Bluetooth devices.

If Memory Saver looks like it is not doing anything, check those exclusions first. Then look for pinned tabs, active media, extensions, and heavy web apps in Chrome Task Manager. When the setting still seems quiet, the practical next step is the same: check which tabs are protected, which extensions are running, and which processes are using memory.

Fix 5: Remove unnecessary extensions

Extensions are a hidden source of memory bloat. Each extension runs as its own process, and many inject scripts into every page you visit. An ad blocker, a password manager, a grammar checker, and a screenshot tool may look small on their own. Together, they can add hundreds of megabytes of overhead.

Go to chrome://extensions and review what you have installed. Disable anything you do not use regularly. For extensions you use occasionally, consider turning them on only when needed instead of letting them run all day. Then reopen Chrome Task Manager and see whether the extension processes changed.

Fix 6: Disable hardware acceleration (if on older hardware)

Hardware acceleration moves some rendering work from the CPU to the GPU. On modern systems with dedicated graphics cards, this often improves performance. On older systems or laptops with integrated graphics, it can backfire, causing Chrome to allocate extra memory for GPU processes without much speed benefit.

To disable it, go to Settings > System and toggle off "Use hardware acceleration when available". Restart Chrome and check whether memory usage drops. If it does not help, turn it back on.

Fix 7: Review Preload Pages

Chrome can preload pages so browsing feels faster. That can help, but it also means Chrome may do background work before you open a page.

Go to Settings > Performance and review Preload Pages. If Chrome is using too much memory or feels busy in the background, try a less aggressive preload setting and compare Task Manager before and after.

Fix 8: Update Chrome

Chrome updates can include performance and stability fixes, and they only finish applying after you restart the browser. Go to Settings > About Chrome to check for updates. If Chrome has been open for days or weeks, restart it after the update and check memory again.

Fix 9: Clear browsing data and cache

Over time, Chrome accumulates cached data, cookies, and browsing history. Most of that lives on disk, but a bloated profile can still make Chrome feel heavier while it manages that data.

Go to Settings > Privacy and Security > Delete browsing data. Select cached images and files, cookies, and browsing history. Choose a time range and clear the data. This will not affect your saved passwords or bookmarks unless you select them.

Fix 10: Use Energy Saver for battery and background CPU

Energy Saver is not the same as Memory Saver, but it can still help when Chrome is doing expensive background work. From Chrome 133, eligible CPU-intensive background tabs can be frozen when Energy Saver is active.

Freezing suspends work in a tab. Discarding unloads a tab from memory. Use Memory Saver when your main problem is RAM. Use Energy Saver when your laptop is draining battery, the fans are spinning, or background tabs are doing too much CPU work.

How much memory should Chrome use?

There is no single normal number. Chrome memory usage depends on the sites you open, the number of active tabs, media playback, extensions, operating system, and available hardware. A few simple pages may feel light, while one large web app can dominate memory by itself.

Scenario	What to check	What to do first
A few simple tabs	Extensions and background pages	Use Task Manager before changing settings
Many mixed tabs	Heavy web apps and media tabs	Close or save inactive groups
Web apps open all day	Sheets, dashboards, chat, design tools	End heavy processes you are not using
Lots of extensions	Extension processes in Task Manager	Disable anything you do not use daily
Tabs used as a to-do list	Inactive projects and reference tabs	Save, close, and restore later

If Chrome is using enough memory to slow the system, do not chase a universal benchmark. Open Chrome Task Manager, sort by Memory Footprint, and start with the process at the top of the list.

The long-term solution: change how you use tabs

The fixes above help in the short term, but the root cause is usually the same: too many tabs open at once. The durable fix is changing your tab habits.

Instead of keeping 50 tabs open as a to-do list, save them. Use tab groups to organize your work, take snapshots with TabGroup Vault, and close what you are not actively using. Collapsed tab groups and Chrome's vertical tabs can make a crowded window easier to review, but they are organization features, not RAM fixes. The RAM-saving action is closing saved tabs or letting Chrome deactivate inactive ones.

For a deeper walkthrough, see our guide on reducing Chrome memory usage without losing your tabs. For why Chrome slows down with many tabs, read our explainer on why Chrome slows down with too many tabs. For practical speed tips, check our tab-focused Chrome performance guide.