The Security Sandbox Overhead
Google Chrome is built with security as a primary focus. One of its most robust defenses against malicious websites is a feature called “Site Isolation.” When enabled, Chrome forces every single website you visit to run in its own dedicated, isolated operating system process. This ensures that if you have your bank open in one tab and a compromised blog in another, the malicious site cannot read the memory of the bank tab (protecting against vulnerabilities like Spectre).
While this is a critical security feature, it comes at a massive cost to system resources. Running every single domain (including iframes for ads on those domains) in a separate process consumes an enormous amount of RAM. On older computers, laptops with limited memory (like 4GB or 8GB), or when trying to run Chrome alongside heavy software like video editors, Site Isolation can cause the entire system to thrash, freeze, or crash. If you desperately need to reclaim RAM and are willing to accept the security trade-off, you can disable this strict isolation.
How to Turn Off Site Isolation
You can disable process isolation via the experimental flags menu.
Warning: Disabling this feature significantly reduces your browser’s security against cross-site scripting and speculative execution attacks. Do this only on trusted networks with ad-blockers enabled.
- Open Google Chrome.
- Click inside the main address bar at the top of the browser.
- Type
chrome://flagsand press Enter. - A page titled “Experiments” will load.
- In the search bar at the top, type Site Isolation (specifically looking for “Disable site isolation” or “Strict site isolation”).
- Depending on your Chrome version, you may need to find the flag that says Disable site isolation and set it to Enabled, or find Strict site isolation and set it to Disabled.
- Click the blue Relaunch button at the bottom of the screen.
Upon restarting, Chrome will consolidate processes, significantly reducing its overall RAM footprint at the cost of strict inter-tab security.