Open Task Manager while Chrome is running and the numbers are striking. A browser with a handful of tabs consuming more RAM than a video game. Dozens of individual processes listed under a single application. Memory usage that climbs steadily throughout the day and barely drops when you close tabs.
This is not Chrome being broken. It is Chrome doing exactly what it was designed to do. Modern browsers use memory deliberately, aggressively, and for good reasons. Understanding how that works explains both why the numbers look the way they do and why the obvious fixes often do not work the way you expect.
Every Tab Is Its Own Process
The single biggest driver of browser memory usage is process isolation. Chrome, Edge, and most Chromium-based browsers give every tab its own operating system process. Not a thread inside a shared process. A completely separate process with its own memory allocation.
This design exists for stability and security. When one tab crashes, the others keep running. When a webpage attempts to read memory from another page, process isolation prevents it. The architecture is genuinely better than the alternative, where all tabs share a single process and one bad webpage can bring the entire browser down.
The cost is memory. Each process carries overhead. A basic tab showing a news article might use 80 to 150MB. A tab running Google Sheets or Figma can reach 400 to 800MB. A YouTube tab with video actively playing sits somewhere in between. With thirty tabs open you are running thirty separate processes, each with its own memory footprint, and the total adds up fast.
Firefox takes a different approach, grouping tabs into a smaller number of shared processes rather than isolating each one completely. This reduces memory overhead but offers slightly less isolation between tabs. In testing with twenty tabs open, Firefox consistently uses 20 to 30 percent less RAM than Chrome under equivalent conditions. The trade-off is a design choice rather than one being simply better than the other.
JavaScript Runs Even When You Are Not Looking
Closing a tab is obvious. What is less obvious is how much work is happening in tabs you have not looked at in an hour.
Modern websites are not static documents. They are applications. A news site runs analytics scripts, tracks scroll depth, checks for new notifications, and refreshes advertising content on a timer. A web app like Notion or Google Docs maintains a persistent connection to the server, syncs changes in the background, and keeps its data model up to date. A social media feed refreshes every few minutes whether you are watching it or not.
JavaScript executing in background tabs keeps CPU cycles busy even when the tab is invisible. The browser allocates processor time to scripts running in tabs you are not looking at, which drains battery and keeps the system warmer than it would otherwise be. Chrome throttles background tab execution to some degree, but it does not stop it entirely, particularly for tabs that have declared active background tasks.
This is one reason why a browser with forty tabs open drains a laptop battery measurably faster than the same browser with five. The additional tabs are not just sitting there. Many of them are actively running code.
Extensions Are Heavier Than They Look
A password manager extension sounds lightweight. An ad blocker sounds lightweight. A dark mode extension sounds trivial.
Each one injects scripts into every webpage you visit. The ad blocker runs a filtering engine against every network request made by every tab. The password manager scans every page for login forms. The dark mode extension rewrites the CSS of every page you open. Individually these operations are fast. Across dozens of tabs, simultaneously, they compound.
Independent testing consistently shows that extensions can account for 200 to 400MB of additional RAM usage beyond what tabs alone would consume. An extension installed months ago and forgotten still runs on every page. If you have eight to twelve extensions installed, which is common for regular Chrome users, stripping that down to four or five genuinely useful ones often recovers several hundred megabytes.
The browser's built-in task manager is the clearest way to see this. In Chrome, press Shift and Escape together to open it. The list shows memory usage per tab, per extension, and per background process. Extensions showing 50MB or more of memory usage while you are barely using them are good candidates for removal.
Why Caching Looks Like a Leak
Browsers intentionally hold onto memory after you close tabs or navigate away from pages. This is not a bug. It is a feature.
When you close a tab and then reopen it, or hit the back button to return to a previous page, the browser wants to display it instantly rather than fetching everything from the network again. To do that, it keeps cached versions of recently visited pages in memory. If you never return to those pages, the cache eventually gets cleared. If you do return, the page loads immediately.
This means that closing a tab does not always result in an immediate corresponding drop in RAM usage. The browser holds the cached content in memory as a low-priority resource, ready to return the memory to the operating system when something else needs it. From Task Manager's perspective, the browser's memory usage barely changes after closing a tab, even though the tab is genuinely gone.
Garbage collection, the process that actually reclaims memory from closed tabs and expired caches, does not run instantly. It runs on its own schedule, triggered by factors including memory pressure and elapsed time. The delay between closing tabs and seeing memory drop in Task Manager can be minutes. This is consistently misread as the browser ignoring the tab closure when it is actually just deferring the cleanup.
The practical implication is that browser memory usage is not a real-time counter that rises and falls with each tab you open and close. It is a pool that expands when needed and contracts on the browser's own schedule.
Memory Saver and Tab Sleeping
Both Chrome and Edge now include a built-in feature called Memory Saver, which proactively discards inactive tabs to reclaim memory before you close them manually.
When Memory Saver is active, a tab that has been in the background for a set period gets its process terminated and its memory released. The tab icon remains in the browser bar. Clicking it reloads the page from scratch rather than resuming a suspended process. You might lose any unsaved state in the discarded tab, such as text typed into a form, but the memory is fully reclaimed immediately.
This is meaningfully different from tab freezing or sleeping, which preserves the tab's process in a low-power state. Sleeping keeps the process alive but throttles it. Discarding terminates it entirely. Discarding recovers more memory but at the cost of a fresh page load when you return to the tab.
Memory Saver is disabled by default in Chrome but can be enabled in Settings under Performance. On systems with 8GB of RAM or less it makes a noticeable difference to overall system responsiveness when many tabs are open. On systems with 16GB or more the benefit is less pressing but still measurable during heavy multitasking sessions.
The Difference Between Tabs and Web Apps
Not all tabs are equal and this affects how memory-related advice should be applied.
A tab showing a Wikipedia article is fundamentally a document. It uses modest RAM, runs minimal JavaScript, and becomes nearly inert in the background. Closing it genuinely frees its resources cleanly and quickly.
A tab running Notion, Figma, Google Sheets, or any similar web application is closer to running a desktop application in a browser window. It maintains persistent connections, runs complex JavaScript continuously, and stores application state in memory. These tabs use 300 to 800MB each, do not become inert in the background, and take longer to reload from scratch when discarded. Memory Saver is more cautious about discarding these tabs automatically for exactly this reason.
If your browser is consuming unusual amounts of RAM, opening Chrome's task manager and sorting by memory footprint almost always reveals that a small number of web app tabs account for the majority of usage. Three Google Sheets tabs, a Figma project, and a Notion workspace can collectively consume 2GB or more. Closing the tabs you are not actively using and reopening them only when needed is more effective than any setting adjustment.
What Actually Reduces Browser Memory Usage
With the underlying mechanics clear, the advice that genuinely helps becomes straightforward.
Reduce the number of simultaneously open tabs. Every open tab costs memory regardless of what it contains. The single most effective way to reduce browser RAM usage is to have fewer tabs open. Tab management extensions like OneTab or the built-in tab grouping in Chrome and Edge help organise tabs without keeping them all loaded simultaneously.
Audit your extensions. Open the browser's task manager and check what each extension is consuming. Remove anything you have not actively used in the past month. The memory recovered from extension cleanup is immediate and persistent.
Enable Memory Saver on systems with limited RAM. On machines with 8GB or less, enabling Memory Saver in Chrome or Edge's performance settings reduces the memory cost of background tabs substantially. The trade-off is that returning to a discarded tab requires a fresh load, which is worth it on systems where every gigabyte matters.
Restart the browser periodically. Long-running browser sessions accumulate memory that garbage collection does not fully reclaim. A weekly restart clears accumulated caches, closes leaked memory that garbage collection missed, and typically returns the browser to a baseline several hundred megabytes lower than a session running continuously for days.
Use the built-in task manager to find outliers. In Chrome, Shift and Escape opens it. In Edge, it is under the More Tools menu. Sorting by memory footprint takes ten seconds and immediately identifies which specific tabs and extensions are consuming disproportionate resources. Closing those individually is more targeted and effective than closing random background tabs.
Frequently Asked Questions
Why does Chrome use so much more RAM than Firefox?
Chrome gives every tab its own isolated process for maximum stability and security. Firefox groups tabs into a smaller number of shared processes, which reduces total memory overhead. With four tabs open the difference is modest. With twenty or more tabs open, Firefox's shared process model consistently uses 20 to 30 percent less RAM than Chrome under equivalent conditions. Edge uses the same Chromium architecture as Chrome but includes additional memory optimisation that often results in slightly lower usage than Chrome on the same hardware.
Does closing all tabs and leaving the browser open save RAM?
Partially. Closing tabs removes their active processes and stops their JavaScript from running. However, the browser itself retains a base memory footprint for its own processes, cached data, and extension scripts that continue running regardless of how many tabs are open. Fully restarting the browser reclaims more memory than closing tabs while leaving the browser running, because a restart clears caches and garbage collects memory that deferred cleanup had not yet processed.
Is 16GB of RAM enough for heavy browser use?
For most users, yes. A Chrome session with twenty to thirty tabs including several web apps typically uses 4 to 6GB of RAM. With 16GB, this leaves ample headroom for the operating system and other applications. Users regularly running fifty or more tabs simultaneously, using RAM-intensive web apps heavily, or running other memory-demanding applications alongside the browser may find 16GB constraining. For these workloads, 32GB eliminates browser-related memory pressure entirely.
Discussion (0)
Be the first to comment.