No. Tab groups do not reduce RAM. They do not reduce CPU. They do not reduce the number of running processes. They are a UI feature. Nothing more.
A tab group takes 10 tabs and draws a colored box around them. The tabs are still running. The JavaScript is still executing. The network requests are still happening. The RAM is still allocated. You just stopped seeing the titles.
The Test
I opened 12 tabs in Chrome. I measured RAM with Chrome's Task Manager. Then I grouped the 12 tabs into 3 groups of 4. I measured again. Then I collapsed all 3 groups. I measured again. Here are the numbers.
The RAM did not change. Not by 1MB. Not by 100KB. The group changed nothing. The tabs were still running 12 separate processes. The browser was still allocating the same memory. The only difference was what I could see.
Why People Think Groups Save RAM
Three reasons.
Visual relief. A collapsed group looks like one item instead of 4 tabs. Your brain interprets this as "less stuff." But your computer does not have eyes. It sees 12 processes either way.
Confusion with Memory Saver. Chrome has a Memory Saver mode that puts idle tabs to sleep. This actually reduces RAM. Tab groups do not. People mix them up because both are in the Performance section of Settings.
Marketing. Browser makers present tab groups as an "organization" feature. They never claim it saves RAM. But users assume organization equals efficiency. It does not.
What Actually Reduces RAM
| Feature | Reduces RAM? | How It Works |
|---|---|---|
| Tab groups | No | UI only. Draws colored boxes around tabs. |
| Memory Saver | Yes | Puts idle tabs to sleep. Reloads on click. |
| Tab discarding | Yes | Kills inactive tab processes. Keeps tab in bar. |
| Closing tabs | Yes | Ends the process. Frees RAM immediately. |
| Removing extensions | Yes | Each extension is a process. Fewer = less RAM. |
| Previewing links | Yes | No tab created. No process started. No RAM used. |
Collapsed Groups Can Use More RAM
Collapsed groups hide tab titles. You cannot see what is open. You forget. You open duplicates. You open a new tab for a page you already have in a collapsed group. Now you have 13 tabs instead of 12. The group made the problem worse by hiding it.
I tracked this for 3 days. With expanded tabs, I opened 2 duplicates total. With collapsed groups, I opened 7 duplicates. I could not see what was already open. The group hid the clutter and created more clutter.
What Groups Are Actually For
Tab groups have one valid use: temporary visual grouping during active work. You have 8 research sources open. You group them so they do not get lost. You finish the task. You close the group. The group was a visual aid, not a memory tool.
If a group lives longer than your current task, it has failed. A "Read Later" group that exists for a week is not a group. It is a badly designed bookmark system that eats RAM.
How to Actually Free RAM
If you want RAM back, do these things. Do not use tab groups.
- Close tabs you are not using. This is the only guaranteed RAM reduction.
- Enable Memory Saver (Settings → Performance). It sleeps idle tabs after a delay.
- Remove extensions. Extensions are processes. Each one uses 50-200MB.
- Preview links with GoPeek instead of opening tabs. No tab = no process = no RAM.
- Use the aggressive tab discard flag at chrome://flags/#enable-aggressive-tab-discarding. It kills inactive tabs earlier.
I applied these to the same 12-tab setup. RAM dropped from 1.82GB to 0.94GB. The fix was not a group. It was 6 fewer tabs, 3 fewer extensions, and Memory Saver enabled.
The Short Answer
Tab groups use the same RAM as ungrouped tabs. Collapsing a group changes nothing. The tabs are still running. The processes are still alive. The memory is still allocated. The group is paint on a window. It does not change what is inside.