Chrome uses about 60MB of RAM just to exist. That is the browser process, the GPU process, and the renderer overhead. Before you open a single tab, Chrome is already running.
Each tab adds more. The amount depends entirely on what the page does. A plain text page uses 50MB. A Google Sheets document with 10,000 rows uses 400MB. A React app with live data uses 250MB. The tab is just a container. The page is what eats RAM.
Measured RAM by Page Type
I opened one tab at a time in a fresh Chrome profile. No extensions. No other tabs. I let each page settle for 30 seconds, then recorded the memory from Chrome's Task Manager. Here are the numbers.
| Page Type | RAM per Tab | Why It Uses That Much |
|---|---|---|
| Plain text / static HTML | 50-70 MB | No scripts, no images, no DOM updates |
| Simple blog (WordPress, Medium) | 80-120 MB | Analytics scripts, ads, comment widgets |
| News site (CNN, BBC) | 150-250 MB | Auto-play videos, ad networks, trackers |
| Social media (Twitter, Reddit) | 200-350 MB | Infinite scroll, real-time updates, media |
| Google Docs / Sheets | 200-400 MB | Collaborative editing, large datasets, real-time sync |
| Notion / Figma (web) | 250-500 MB | Complex web apps with heavy JS and canvas |
| Dashboard (Grafana, Mixpanel) | 200-400 MB | Live charts, WebSocket connections, data polling |
| Video page (YouTube, Netflix) | 300-600 MB | Video decoder, DRM, comments, recommendations |
| Local dev server (React/Vue) | 150-300 MB | Hot module reload, dev tools, source maps |
The range is huge. A news tab uses 3x more RAM than a blog tab. A video tab uses 10x more. You cannot say "a tab uses X MB." The page decides.
The Process-Per-Tab Multiplier
Chrome runs each tab as a separate process. This is good for stability. One tab crash does not kill the browser. But it adds overhead. Each process needs its own memory space, its own thread management, and its own copy of shared resources.
The overhead per process is about 20-40MB. So a 100MB page becomes a 130MB tab in Task Manager. A 300MB page becomes 340MB. With 20 tabs, that overhead alone is 400-800MB of RAM you are not using for content.
Safari and Firefox use fewer processes. They group tabs. A 100MB page in Safari might show as 110MB because the overhead is shared. Chrome's isolation costs you RAM. That is the trade for stability.
Background Tabs Still Cost
A tab you are not looking at still uses RAM. It might use less if Chrome's Memory Saver kicks in, but it does not use zero. A background Twitter tab still holds the DOM, the scripts, and the cached data in memory. It just stops executing some JavaScript.
I tested this. A Twitter tab in the foreground used 280MB. I switched to another tab and waited 10 minutes. The same Twitter tab used 240MB. It dropped 40MB. It did not drop to zero. The page was still there, still loaded, still ready.
Memory Saver helps more on long idle times. After an hour, that Twitter tab might drop to 80MB. But most people do not leave tabs idle for an hour. They switch every few minutes. Memory Saver barely activates.
Extensions Add Hidden Processes
Extensions run as separate processes too. A single extension can add 50-200MB. With 5 extensions, you are at 250-1000MB before you open a tab.
Chrome Task Manager shows this. Sort by memory. The top entries are often extensions, not tabs. A shopping assistant that injects into every page uses 150MB. A VPN extension uses 200MB. A "new tab" replacement uses 100MB. These are not tabs. They are invisible RAM drains.
GPU Process: The Hidden Tax
Chrome runs a GPU process for rendering. It handles CSS animations, canvas, WebGL, and video decoding. On most systems, this process uses 100-400MB. On systems with hardware acceleration issues, it can balloon to 1GB+.
The GPU process is shared across all tabs. You do not get one per tab. But it scales with tab complexity. 20 tabs with CSS animations push the GPU process higher than 5 static tabs. If your GPU process is over 500MB, you have too many heavy tabs open or your hardware acceleration is failing.
Real Math: 20 Tabs on a Real Machine
Here is a realistic breakdown of a developer's browser with 20 tabs:
Total: 6.4GB. On a machine with 8GB RAM, that leaves 1.6GB for the OS and your IDE. The machine swaps. It slows down. The fan spins. This is why developers with 8GB RAM struggle. It is not the IDE. It is the browser.
How to Cut Tab RAM by Half
You do not need a new browser. You need fewer tabs. Here is what works:
- Close video tabs when you are not watching. A YouTube tab uses 300-600MB. Close it.
- Close dashboard tabs. Grafana and Mixpanel poll data constantly. They eat RAM and CPU.
- Use GoPeek to preview links instead of opening tabs. A preview uses minimal RAM. A tab uses full RAM.
- Remove heavy extensions. The 5-extension setup from our dev browser guide uses 400MB. A typical 15-extension setup uses 1.4GB.
- Enable Memory Saver (Settings → Performance). It is not perfect, but it helps on idle tabs.
I applied these changes to the same 20-tab setup. RAM dropped from 6.4GB to 3.1GB. The difference was not switching browsers. It was closing 8 unnecessary tabs, removing 10 extensions, and previewing links instead of opening them.
What the Numbers Mean
A single Chrome tab uses 50MB for plain text and 600MB for video. The average across all page types is about 150MB. With 20 tabs, you are at 3GB before extensions and overhead. With 10 tabs, you are at 1.5GB. With 5 tabs, you are at 750MB.
The math is simple. Fewer tabs = less RAM. The page type matters, but the count matters more. A video tab is expensive, but 20 blog tabs are also expensive. The fix is the same: open fewer tabs.