How to Reduce Chrome's Memory Usage (Without Closing Your Work)
Why Chrome eats RAM, which built-in settings actually help, and how to cut memory pressure by parking tabs instead of keeping them alive.
Chrome runs each tab as its own process. That design keeps one crashed page from taking down the browser, but it means every open tab — even one you haven't looked at in days — holds its own slice of memory. With 60 or 80 tabs open, it's normal to see Chrome using the majority of your RAM. Here's how to bring it down without losing anything.
1. Turn on Chrome's Memory Saver
In Settings → Performance, Chrome's Memory Saver puts inactive tabs to sleep and reclaims their memory; the tab reloads when you click it. It helps, but it has limits: sleeping tabs still clutter your tab strip, some sites lose state on reload, and Chrome decides what sleeps — not you.
2. Find the heavy tabs
Chrome's own Task Manager (Window → Task Manager, or Shift+Esc on Windows) shows memory per tab. The usual offenders are web apps left open all day — mail, chat, dashboards, docs — and media-heavy pages. Anything at hundreds of megabytes that you touch twice a day is a candidate for closing and reopening on demand.
3. Park tabs instead of keeping them alive
The biggest wins come from changing what a "kept" tab is. Most open tabs aren't work in progress — they're bookmarks you're afraid to file. A parked tab costs zero RAM: it's just a labeled icon that opens the site when clicked. Tabrows is built around this — park hundreds of sites as icons in an overlay, grouped into labeled sections, and keep only the tabs you're actively using live.
4. Close whole windows, keep the structure
If your tabs are organized one-project-per-window (see our guide to managing 100+ tabs), memory management becomes trivial: finish a project, close its window, and its RAM comes back at once. With labeled window pills in an overlay you can also minimize a window and still see exactly what's in it — so "out of sight" stops meaning "lost."
Quick checklist
- Memory Saver ON in Chrome's Performance settings.
- Check Chrome's Task Manager for tabs using hundreds of MB.
- Park reference and “later” tabs as icons — zero RAM until clicked.
- One project per labeled window; close the window when the project ends.
- Restart the browser occasionally — long-lived sessions accumulate leaks.