How Chrome’s Site Isolation Keeps Your Tabs Separate and What It Costs

Why tab isolation matters

Modern browsers face attacks that try to read data from one website while another is open in a different tab. Techniques such as Spectre exploit speculative execution to leak information across process boundaries. If a malicious page could access the memory of another site’s renderer, it could steal passwords, session tokens, or other sensitive data.

What Site Isolation actually does

Site Isolation assigns a dedicated renderer process to each distinct origin (site). Each renderer runs inside its own sandbox, so even if a compromised page gains arbitrary code execution, it cannot directly read or write the memory belonging to another site’s process. This dramatically reduces the success rate of side‑channel attacks that rely on cross‑process memory reads.

Seeing Site Isolation in action

1. Open Chrome and navigate to any website, for example https://example.com.
2. Press Shift+Esc to open Chrome’s Task Manager.
3. In the list of processes, locate the entries labeled “Renderer”. Each entry shows the site’s origin next to it (e.g., “Renderer – example.com”).
4. Open a second tab with a different site, such as https://news.ycombinator.com, and notice a new Renderer entry appears for that origin.
5. For a deeper view, visit chrome://processes. The “Site Isolation” column will show a separate PID for each site’s renderer.

These steps let you verify that Chrome is treating each origin as an isolated process without needing any special tools.

Trade‑offs and practical limits

• Memory usage. Because each site gets its own renderer, Chrome’s RAM consumption rises roughly 10‑20 % compared with a non‑isolated mode. On devices with limited memory, many open tabs can lead to increased swapping or noticeable slowdown.
• Extension compatibility. Extensions that rely on direct DOM access across origins or shared memory buffers may break. Most popular extensions have been updated, but internal or legacy tools might need adjustment.
• Policy overrides. Enterprise administrators can disable Site Isolation via the SiteIsolationEnabled policy. Doing so reduces protection against side‑channel attacks and is discouraged for security‑sensitive environments.

Keeping the protection on

For most users, the default setting (enabled) provides the best balance of security and performance. Periodically check Chrome’s Task Manager or chrome://processes to confirm that each site still appears as a separate Renderer. If you observe severe slowdowns on a low‑RAM device, consider closing unused tabs rather than disabling the feature, as the security benefit outweighs the modest memory cost for typical workloads.