BrowsersMemoryWindows

Why your browser uses 4 GB of RAM — and when it is actually a problem

A look inside modern browser architecture: why each tab is a process, how tab discarding works, and what to do when memory runs out.

5 min read

Open ten tabs and Task Manager shows 3–4 GB for the browser. That is not a leak and not a virus. It is how modern browser architecture works: every tab, extension and service process lives separately. Let us look at where that helps and where it is time to intervene.

How a browser works inside

Chromium browsers (Chrome, Edge, Yandex Browser, Brave, Vivaldi, Opera) run several kinds of processes:

  • Browser process — interface, tabs, settings, network requests.
  • Renderer — the page engine. Usually one process per site, and with Site Isolation enabled, one per cross-site iframe.
  • GPU process — drawing, compositing, video.
  • Utility processes — media decoding, files, network, audio.
  • Extension processes — each extension with its own background work.

Process separation is about security and stability: a crashed tab does not take down the browser, and malicious code on one site cannot reach another. The price is overhead: every process has its own JavaScript engine instance, heap and service structures. That is why ten tabs from one site may use less memory than ten tabs from different sites.

Firefox uses a similar model (content processes plus isolation) but with a different engine and fewer background services.

Why “lots of memory” is not always bad

Windows gives applications free memory for caching. The browser keeps decoded images, compiled JavaScript and fonts so a tab opens instantly. When memory runs short, the system pages data to disk, and that is when switching tabs starts to stutter.

Rough guidance for a home PC with Windows 11:

RAM What is realistic
8 GB 10–15 tabs plus one heavy site. The browser and the system already compete for memory
16 GB 30–50 tabs, a messenger, an office suite. The comfortable minimum in 2026
32 GB Virtual machines, video editing, dozens of tabs without discarding

If the browser uses 5 GB on an 8 GB machine and the system starts hammering the disk, that is a real problem — and a “memory cleaner” is not the answer.

Step 1. Find the culprit

In Chromium browsers press Shift + Esc to open the browser’s own task manager. It shows memory, CPU and network for every tab, extension and service process.

What to look for:

  1. A tab that keeps growing. Open it, leave it for ten minutes and compare. Growth by hundreds of megabytes points to a specific site, not the browser.
  2. Extensions. Each one is a separate process. Five “useful” extensions can easily add 300–500 MB in the background.
  3. GPU process. If it takes a gigabyte, check hardware acceleration and update the graphics driver.
  4. Service processes. Network Service, Audio Service, Storage Service at 20–80 MB each are normal.

Firefox shows a similar picture in about:processes.

Step 2. Enable tab discarding

  • Chrome: Settings → Performance → Memory Saver.
  • Edge: Settings → System and performance → Sleeping tabs, with a timeout.
  • Yandex Browser: performance settings with memory saving and background tab discarding.
  • Firefox: tabs are discarded automatically under memory pressure; you can limit content processes in about:config.

A discarded tab keeps its address and form state but may lose scroll position and video. That is acceptable for messengers and mail, not for a video call — pin those tabs.

Step 3. Reduce background load

Check in order:

  • Extensions. Keep an ad blocker, a password manager and a translator. Disable the rest for a week and compare.
  • Pinned tabs. Each one starts with the browser. Mail, calendar and a messenger pinned permanently can cost 300–700 MB.
  • Updaters and “optimisers”. Utilities that “watch memory” consume it themselves.
  • Windows background apps. A messenger, cloud client and game launcher in the tray add up together with the browser.

Step 4. Check Windows settings

  1. The page file should stay system-managed. Disabling it only helps in myths: when memory runs out, applications crash with “out of memory”.
  2. Animation effects do not affect memory, but they make drawing harder on weak GPUs.
  3. Startup apps — see the Windows 11 guide: the memory you free will go to the browser.
  4. Graphics driver. An outdated driver is a common cause of a growing GPU process.

When it is time to add hardware

There are three honest signs:

  • With 8 GB the system constantly uses the page file, even with five tabs open.
  • Switching tabs takes seconds and the disk is at 100%.
  • A browser with 15 tabs and an office suite needs more memory than you physically have.

In those cases the fix is more RAM, not “browser acceleration”. For most scenarios 16 GB is the comfortable minimum, and 32 GB gives several years of headroom.

Myths worth closing

Myth Reality
“A browser should use 500 MB” No. Modern sites are applications. 2–4 GB during active work is normal.
“The ‘speed up browser’ button in a cleaner” The utility discards tabs that you immediately reopen.
“Disable JavaScript and memory will be freed” Half the web stops working, and the saving is smaller than one extension.
“You do not need to close tabs, they do not load the system” Inactive tabs load less, but they still hold memory and run timers.
“Firefox is always more efficient than Chrome” It depends on sites and process count. The difference rarely exceeds 20–30%.

What to do right now

  1. Press Shift + Esc and sort by memory.
  2. Close tabs you have not touched for a day.
  3. Disable extensions you have not used for a week.
  4. Enable tab discarding.
  5. Restart the browser every few days; it releases fragmented memory.

If the browser still eats memory on one specific site, the problem is the site. Tell us and we will add it to the review.

If you are choosing a browser and want to weigh privacy, extensions and sync as well as memory, use the browser picker.

Sources

Related reading

All articles →