Which Extension Is Slowing Chrome? Find It in 3 Steps (2026)

When Chrome feels sluggish and you suspect an extension, open Chrome’s own Task Manager with Shift+Esc (Search+Esc on ChromeOS). It lists every tab and extension with live CPU and memory columns, so you sort by usage and the resource hog rises to the top within seconds. From there you disable, remove, or work around it. The full three-step diagnosis follows.

Step 1: Open Chrome’s Task Manager (Shift+Esc)

Chrome ships a process monitor most people never open. On Chrome 150 (current stable, July 2026), press Shift+Esc on Windows or Linux, or Search+Esc on a Chromebook. On macOS there is no default key, so use the menu: Window > Task Manager, or the three-dot menu under More Tools > Task Manager.

A window appears listing every tab, extension, and internal Chrome process. Each extension shows up on its own line, prefixed Extension: followed by its name. This is the ground truth. It shows what each add-on actually costs right now, not what its listing claims.

Step 2: Sort by CPU and Memory to Find the Culprit

By default the Task Manager shows the CPU column. Click the CPU header once to sort descending, and whatever is working hardest jumps to the top.

The Memory footprint column tells the other half of the story, and it is hidden by default. Right-click any column header and tick Memory footprint (and Network, if you want to catch an extension phoning out constantly). Now click that header to sort by RAM.

Watch the rows for a few seconds while you do nothing. An extension that sits high on CPU while you are idle is the one to suspect. Note its name.

What High CPU vs High Memory Actually Means

The two columns point at different problems, and confusing them sends you chasing the wrong fix.

A healthy extension idles close to 0% CPU when you are not touching it. Sustained CPU on an idle add-on is a red flag: an old ad blocker with a bloated ruleset, a coupon extension polling in the background, or one stuck in a loop after an update. High memory that climbs over an afternoon points at a leak. Reading which column is high, not just that something is, points you at the right fix.

Step 3: Disable, Remove, or Suspend the Culprit

Once you have a name, confirm it, then decide.

Disable to test. Go to chrome://extensions and toggle the suspect off. Use Chrome for a while. If the sluggishness lifts, you found it. This is reversible, so it is the right first move before deleting anything.

Remove if you don’t need it. If the extension is one you forgot you had, click Remove. Fewer extensions means fewer background workers and injected scripts on every page.

Keep it but cut its reach. For an extension you rely on that is heavy only on certain sites, check its options for a site allowlist, or set it to run on click instead of on every page (chrome://extensions > the extension > Details > Site access > On click).

When the Culprit Is a Tab, Not an Extension

Run the Task Manager and a surprising number of times the extensions are idling near zero while a stack of tabs holds hundreds of megabytes each. That is not an extension problem, and disabling add-ons will not touch it.

SuperchargePerformance targets exactly this case. It suspends idle tabs with chrome.tabs.discard(), and on its default Medium setting it goes after the memory hogs first: any tab holding 200 MB or more is unloaded once it has sat idle for three minutes, ahead of the regular timer. Tabs playing audio, holding unsaved form input, pinned, or on your allowlist are spared (25-plus web apps like Gmail, Docs, and Figma are protected automatically). Its toolbar badge shows a running estimate of the memory reclaimed, so the effect is visible rather than a claim. It runs locally, keeps no account, and sends nothing about your browsing off the machine.

It does not disable your other extensions for you; that stays a decision you make in chrome://extensions. What it removes is the tab-memory pressure that the Task Manager so often reveals is the real cause.

What to Do Next

If one extension sits at the top of the CPU column even while you sit idle, disable it and see whether Chrome recovers before you remove anything. If the memory column is dominated by tabs rather than extensions, the fix is suspending idle tabs, not uninstalling add-ons. If nothing stands out yet Chrome still drags, the bottleneck is likely elsewhere: hardware acceleration, an overloaded profile, or a heavy page itself, each of which is a different diagnosis.