Skip to content
FixingBook
Verifiedbeginnerest. 10 minutes

Reduce Chrome memory usage that slows down your whole computer

Diagnose which tabs and extensions are eating RAM and cut Chrome memory usage by half with built-in tools — no extensions required.

Confirmed working on: Chrome 135+ · Edge 135+ · Brave (Chromium 135+)

Before you begin

Match the environmentUse this guide only for Chrome 135+, Edge 135+, Brave (Chromium 135+) or a clearly compatible setup.
Protect recoveryBack up important data and save encryption or account recovery keys before changing system state.
Know when to stopMake one change at a time and stop if the result differs from what the guide describes.

Problem overview

Chrome consumes multiple gigabytes of RAM, the fan spins up, and the entire system becomes sluggish : even with what seems like a normal number of tabs.

Common causes

  • Extensions running background processes in every tab
  • Web apps with memory leaks left open for days
  • Memory Saver disabled or misconfigured

Solution 1: Find the real culprits with Chrome’s Task Manager

  1. Press Shift + Esc (or Menu → More tools → Task Manager).
  2. Click the Memory footprint column to sort descending.
  3. End the worst offenders with End process : the tab can be reloaded later.

Extensions appear in this list too. Anything using over ~200 MB persistently deserves scrutiny.

Solution 2: Enable and tune Memory Saver

  1. Open chrome://settings/performance.
  2. Turn on Memory Saver and select Aggressive.
  3. Add sites you never want discarded (your mail, docs) under ‘Always keep these sites active’.
Expert Tip

Combine with tab groups and the built-in ‘Organize tabs’ feature : collapsed groups are prioritized for discarding.

Solution 3: Audit extensions properly

chrome://extensions → enable Developer mode → inspect 'service worker'

Disable everything, then re-enable one at a time over a day of normal use. Most users find one or two extensions cause the bulk of memory growth.

Caution

Beware of ‘RAM cleaner’ extensions : they add overhead and cannot free memory the OS hasn’t asked Chrome to release.

Confirm the result

  1. Repeat the exact action that originally triggered the problem.
  2. Confirm the original error or symptom is gone and no new warning has appeared.
  3. If the guide changed a driver, service, package, or system setting, restart once and test again.
  4. If the result is worse or unexpected, stop. Reverse only the last change using its documented restore option; if none is documented, use your backup or qualified support.

Questions about this fix

Does Memory Saver discard the tab content I was working on?

Form inputs and scroll position are usually restored, but unsaved work in web apps may reload. Pin or exclude critical sites from Memory Saver.

Did this fix work for you?

Weighted Consensus Protocol

Consensus0%
Required100% (Weight 3)
Contributors0
Verified By YouNo
Your Weight--

Did this solution resolve your issue?

Confirming if this works strengthens verification statistics on the registry.

Sign In to VerifySign in required to verify

FixingTeam10,000 rep

Official Project Maintainers

The core engineering and moderation team behind FixingBook. We curate, verify, and maintain the standards of the troubleshooting ledger.

Spotted something outdated? Suggest an edit. Maintainers review submissions within 48 hours.
Share:XReddit

Discussion (0)

No comments yet. Share your experience or verify if this fixed your issue!

Join the Discussion