Chrome Using Too Much Memory? Fix One PC, Then the Fleet

Updated: October 2026

The ticket says the laptop is slow, and Task Manager says Chrome is holding more memory than everything else combined. Sometimes that's a problem and sometimes it's Chrome doing what it was built to do. Here's how to tell which, fix the one machine in front of you, and push the same settings to every PC so the ticket doesn't come back.

Why Chrome Uses So Much Memory

Chrome splits itself into many processes on purpose. Each site you open generally gets its own renderer process, and extensions, the GPU and the network stack run separately too. That's Site Isolation, and it's a security feature: a malicious page in one process can't easily read what another site is doing.

The trade is memory. Every process carries its own overhead, so twenty tabs cost more than twenty pages' worth of content. Windows Task Manager then shows a long list of "Google Chrome" entries, and the total looks alarming.

A big number isn't automatically a problem, either. Windows hands spare RAM to whatever is most likely to need it and takes it back when something else asks. Unused memory does nothing for the user. The question is whether the machine is running out, not whether Chrome's line is the biggest.

Is It Chrome, a Tab or an Extension?

Start inside Chrome, not in Windows Task Manager. Press Shift+Esc (or open the menu, then More tools, then Task manager) and sort by Memory footprint. Chrome's own Task Manager names every tab, extension and helper process, so you can see exactly what's heavy.

Three patterns come up again and again. One web app, such as a big spreadsheet, a CRM or a video call, is taking a large share on its own. An extension is sitting high even though the user barely uses it. Or no single line stands out and the user simply has dozens of tabs open.

For the first, the fix is usually the app or the workflow, not Chrome. For the second, remove the extension. For the third, Memory Saver is built for exactly this.

If you'd rather check from a script, Get-Process chrome in PowerShell totals the working set across every Chrome process. Our list of PowerShell commands has the one-liners for sorting processes by memory.

Fixes That Work on One PC

Turn on Memory Saver. In Chrome, go to Settings, then Performance, and switch on Memory Saver. Chrome discards tabs that have sat in the background and reloads them when the user clicks back. There are three levels: Moderate waits longest before a tab goes inactive, Balanced sits in the middle, and Maximum discards soonest.

Trim the extensions. Open chrome://extensions and remove anything nobody can explain. Every extension that runs in the background holds memory whether its icon is clicked or not.

Stop Chrome running after it's closed. Under Settings, then System, switch off "Continue running background apps when Google Chrome is closed." Otherwise extensions and apps keep their processes alive after the last window shuts.

Clearing the cache comes up in every guide. It frees disk space, not RAM, so it rarely changes the number in Task Manager. The same goes for switching hardware acceleration on and off: it moves work between the CPU and GPU, and it's worth trying when a page stutters, not when memory is the complaint.

This walkthrough covers the same settings in about four minutes, if you'd rather watch a technician click through them.

Push the Fix to Every PC

Fixing Chrome by hand on one laptop helps one user. Chrome's enterprise policies set the same thing everywhere, and the user can't quietly switch it back. You can deploy them through Group Policy with Google's ADMX templates, through Intune, or as registry values under HKLM\Software\Policies\Google\Chrome.

The exceptions list matters more than the level. Some web apps break when they're discarded: a call-queue monitor, a softphone, a dashboard that has to keep polling. In this r/sysadmin thread from August 2026, an admin weighing Memory Saver for 16 GB machines gets advice from people who already rolled out tab sleeping in Edge. They added their call-queue monitor and ERP to an exceptions policy first, let the default roll out, and heard nothing from users.

Roll it out in rings. Start with Balanced on a pilot group, collect the web apps that complain, add them to the exceptions list, then widen. Move to Maximum only on machines that are short on RAM.

For devices outside Intune or a domain, the same registry values can go out from your RMM as a script. OpenFrame runs scripts as bulk operations across devices, with an approval gate before anything changes. Our RMM explainer covers how that kind of fleet-wide change works in general.

Shared Machines and RDS Hosts

On a Remote Desktop Session Host, every user runs their own copy of Chrome. Whatever one session costs, multiply it by the number of people logged in. That makes Memory Saver and the extension allowlist more valuable on a terminal server than on any laptop.

Chrome's footprint isn't only RAM, either. Recent versions download an on-device AI model for local features, and on shared hosts it lands in every user's profile. This r/sysadmin thread from December 2025 found it taking around 4 GB of disk per user on RDS servers. One reply adds that hundreds of PCs pulling the model after the same update saturated their internet connection.

The policy for that one is GenAILocalFoundationalModelSettings. Set it to 1 and Chrome won't download the model. If you're already stripping built-in extras from the Windows image, our guide to debloating Windows 11 covers the operating system side.

When It's Not Chrome's Fault

Sometimes the machine is just too small for the job. A laptop with 8 GB of RAM running Teams, Outlook and a dozen browser tabs will page to disk no matter how Chrome is tuned. Memory Saver buys headroom. It doesn't add RAM.

And sometimes "Chrome is slow" isn't about memory at all. Check CPU and network before blaming RAM. Chrome's DevTools have a Performance monitor that shows CPU, memory and layout work per tab, and a slow connection feels exactly like a slow browser to the user.

The order that works: find the heavy line in Chrome's Task Manager, fix that one thing, set Memory Saver and an extension allowlist by policy, and keep an exceptions list for the web apps that must stay live. Do it once in policy and the same ticket stops arriving from every desk.

For the scripting side of fleet fixes, the PowerShell commands guide is the next read.