Open Task Manager with Chrome running and you might find the browser consuming more RAM than everything else on your computer combined. This is not a bug — it is architecture. Chrome runs every tab, extension, and plugin as a separate process for stability and security, so one crashing tab cannot take down the whole browser. The trade-off is memory: fifty tabs means fifty processes, plus overhead for each. Understanding this design is the first step, because the fixes all work with it rather than against it.

The single biggest fix is Memory Saver, built into Chrome since version 110. It automatically puts tabs you have not looked at in a while to sleep, freeing their RAM while keeping the tab visible — click back and it reloads instantly. Turn it on under Settings > Performance > Memory Saver, and choose a mode: Balanced waits longer before sleeping tabs, Maximum sleeps them aggressively and saves the most memory. You can add exceptions for sites that must stay live, like music players, chat apps, or dashboards. For most people this one toggle cuts Chrome's footprint by a third or more, which matters enormously on machines where 8GB of RAM has to stretch across everything.

Next, find out exactly what is eating the memory. Chrome has its own Task Manager — press Shift+Esc on Windows (or open the three-dot menu > More tools > Task manager) — which breaks down memory usage per tab and per extension. Sort by Memory footprint and the culprits reveal themselves: often a single tab with a heavy web app, or an extension you installed years ago and forgot. End the worst offenders right there. Do this audit once and you will usually find one or two surprises accounting for a gigabyte you did not know you were spending.

Extensions deserve their own audit because each one runs constantly in the background. Type chrome://extensions into the address bar and look at the list with fresh eyes: ask of each one, "Have I used this in the last month?" Coupon finders, old screenshot tools, and abandoned utilities are classic memory squatters. Remove what you do not need; toggle off what you use rarely. Fewer extensions means less RAM, fewer background operations, and a more stable browser after updates — and fewer extensions also means a smaller attack surface, which your student AI toolkit will thank you for when every tab counts during exam season.

Two settings tweaks finish the job. Under Settings > System, turn off "Continue running background apps when Google Chrome is closed" so Chrome stops consuming RAM after you quit it. Under Settings > Performance > Speed, consider turning off "Preload pages" — it makes some page loads feel faster by loading pages Chrome thinks you will visit, but it spends your RAM speculatively. Hardware acceleration is usually best left on, since it offloads rendering to the GPU; only toggle it off if you see visual glitches, and keep your graphics drivers current.

If Chrome still struggles after all of this, the honest answer may be hardware. A browser-first workflow with dozens of tabs genuinely wants 16GB of RAM in 2026, and no setting changes that math. But before spending money, try the nuclear option for a week: bookmark your essential tabs, close everything else, and run with Memory Saver on Maximum. Many people discover their "slow computer" was really a "forty-tab browser," and the fix was discipline, not dollars. Measure with Chrome's Task Manager before and after — the numbers do not lie, and watching a 6GB footprint drop to 2GB is deeply satisfying.