Google Chrome has been the dominant web browser for over a decade, and in most enterprise environments it’s effectively the standard. But with that dominance comes a long-standing complaint: Chrome uses a lot of memory and spawns an alarming number of processes.
If you’ve ever opened Task Manager on a user’s laptop and seen 15–30 Chrome processes consuming gigabytes of RAM, you’re not alone. As an IT professional, you’ve probably had to explain—more than once—that Chrome isn’t “broken,” it’s working exactly as designed.
That design, however, isn’t always ideal for:
- Older hardware
- Virtual desktops (Citrix / AVD / RDS)
- Shared workstations
- Low-memory laptops
- Power users with dozens of tabs and extensions
This article explains why Chrome behaves this way, what you can safely tune, what you should not disable, and how to strike the right balance between performance, stability, and security.
Why Google Chrome Uses Multiple Processes
Chrome’s architecture is fundamentally different from older browsers like Internet Explorer or even early versions of Firefox.
Instead of running as a single monolithic process, Chrome uses a multi-process sandboxed model, where different components are isolated from one another.
Typically, Chrome creates separate processes for:
- Each browser tab (or group of tabs)
- Each extension
- GPU rendering
- Network services
- Crash handlers
- Utility services
The Benefits (Why Google Did This)
From a design and security perspective, this approach is excellent:
- Stability – One tab crashing doesn’t kill the entire browser
- Security – Malicious websites are sandboxed away from the OS
- Performance isolation – Heavy tabs don’t freeze the whole browser
- Better exploit mitigation – Process isolation limits attack scope
In enterprise security terms, Chrome’s architecture significantly reduces blast radius when something goes wrong.
The Downside: Memory and CPU Overhead
The trade-off is resource consumption.
Each Chrome process:
- Has its own memory overhead
- Allocates CPU scheduling time
- Maintains sandbox boundaries
- Loads shared libraries independently
On modern systems with 16–32 GB of RAM, this is usually acceptable. But in real-world IT environments—especially VDI—this model can become a serious performance bottleneck.
Important Reality Check Before Tweaking Chrome
Before we go any further, this needs to be said clearly:
Completely disabling Chrome’s multi-process model is not recommended for most users or enterprises.
Some tweaks reduce memory usage, but they also:
- Reduce browser security
- Increase crash impact
- Break enterprise compatibility
- Violate Chrome security best practices
The goal is optimization, not destruction.
Changing Configuration
You can limit the Chrome processes to one by changing the configuration with a few simple steps.
- Right-click on the “Chrome.exe” shortcut on the desktop and select “Properties“.Clicking on Properties Note: If you don’t have a shortcut, create one.
- Click on the “Shortcut” tab on the top and select the “Target” option.
- Add the following command line at the end of the listed target location.–process-per-site
- After adding the command line, the full entry in the target panel should look like the following.”C:\Program Files (x86)\Google\Chrome\Application\chrome.exe” –process-per-site
- Click on “Apply” and then select “Save“.
- Now Chrome should be running a single process for all the tabs.
Option 1: Manually close the processes
Use the built in Chrome Task Manager
You may be familiar with the Windows Task Manager, but did you know that the Google Chrome Web browser has its own built-in task manager window that lists each process currently running. Using Google Chrome’s built-in task manager will allow you to view exactly which page is freezing, and you can then end the process behind that page only. If you need to see each process Google Chrome is using, access the Chrome task manager by clicking the wrench icon in the upper-right corner of the screen, selecting “More Tools” and then clicking “Task Manager.” Or you can press Shift + Esc, and this will also open the Chrome Task Manager
Press Shift + Esc inside Chrome to open the Chrome Task Manager.
Here you can see:
- Individual tabs
- Extensions
- Memory usage per process
- CPU spikes
- Network usage
Use the Windows Task Manager
Because all the Google Chrome tabs currently open have their own separate process, each of the processes will appear in your operating system’s task manager window. Press the “Ctrl,” “Alt” and “Delete” keys together and click the “Task Manager” button to access a window that will show all programs and processes running on your machine. Select the “More Details” button and scroll down to “Google Chrome” to find the multiple active Chrome processes. Click the process you want to close and choose “End Process.
Before changing any configuration, understand what is actually consuming resources.
Real-World Tip
In many environments, extensions—not tabs—are the real problem. I’ve seen a single poorly written extension consume more RAM than 20 tabs combined.
Ending a single extension process often resolves complaints instantly.
Option 2: Reduce Processes with --process-per-site (Advanced, Use Carefully)
Chrome supports a command-line switch that changes how processes are allocated.
How It Works
By default, Chrome uses process-per-tab (with site isolation rules layered on top).
The --process-per-site switch forces Chrome to use one process per site, not per tab.
How to Configure It
- Right-click your Chrome shortcut
- Select Properties
- In the Target field, append:
--process-per-site
Example:
"C:\Program Files\Google\Chrome\Application\chrome.exe" --process-per-site
- Click Apply and OK
- Launch Chrome using this shortcut
What This Actually Changes
- Multiple tabs from the same site share a process
- Total process count drops noticeably
- Memory usage often decreases
The Trade-Off
- Reduced isolation
- A single site crash can close multiple tabs
- Not recommended for high-risk browsing
In managed environments, this is best limited to:
- Kiosk devices
- Lab systems
- Non-privileged users
- Resource-constrained VDI
Option 3: Control Extensions (The Biggest Win)
From real-world experience, extensions are the #1 Chrome performance killer.
Best Practices for IT Teams
- Audit extensions regularly
- Remove anything not business-critical
- Prefer Microsoft Edge + Chrome extension parity where possible
- Block consumer extensions via GPO or Intune
How to Review Extensions
Navigate to:
chrome://extensions/
Disable or remove:
- Unused extensions
- Duplicate functionality
- Legacy or unsupported plugins
Security Bonus
Fewer extensions = smaller attack surface.
Option 4: Stop Chrome Running in the Background
By default, Chrome continues running background processes even after users close it.
To disable this:
- Open Chrome Settings
- Go to System
- Disable Continue running background apps when Google Chrome is closed
This is especially useful on:
- Laptops
- Shared devices
- VDI environments
Option 5: Chrome Flags (Use with Extreme Caution)
Chrome Flags (chrome://flags) expose experimental features.
One commonly discussed option is Site Isolation.
About Site Isolation
Site Isolation dramatically improves security by ensuring each site runs in its own process—even across tabs.
Disabling it can reduce process count, but:
It significantly weakens Chrome’s security posture.
Professional Recommendation
In 2026, disabling Site Isolation is almost never justified in enterprise environments. Any performance gains are outweighed by security risk.
Monitor Background Processes
Chrome may continue running in the background even after all windows are closed. This can be disabled:
- Click the three-dot menu in Chrome.
- Go to Settings > System.
- Toggle off Continue running background apps when Google Chrome is closed.
Final Thoughts
While Google Chrome’s multi-process design offers performance and security benefits, it’s not ideal for everyone—especially those on lower-end systems. By learning how to disable multiple processes in Google Chrome, you can reduce memory usage and enjoy a faster, more responsive computer.
Make sure to strike a balance between performance and stability. Completely disabling Chrome’s multi-process feature is not recommended, but tweaking it for efficiency can make a big difference.
From my early days on the helpdesk through roles as a service desk manager, systems administrator, and network engineer, I’ve spent more than 25 years in the IT world. As I transition into cyber security, my goal is to make tech a little less confusing by sharing what I’ve learned and helping others wherever I can.