How to Find Which Chrome Tab Is Using the Most Memory or CPU

Antti Savolainen

Chrome feels sluggish, the fan spins up, or your laptop's battery is draining fast — and somewhere among your open tabs is the one actually responsible. Chrome has a built-in tool that answers exactly this, separate from whatever task manager your operating system ships with, and it's one keystroke away.

Step 1: open Chrome's Task Manager

Press Shift+Esc on Windows or Linux to open it instantly. On a Mac, Shift+Esc isn't bound by default — instead, click Window in the menu bar and choose Task Manager. On any platform, right-clicking an empty area of the tab strip and choosing Task Manager from the context menu also works.

A separate window opens listing every Chrome process — this is not part of your regular tab strip, so it stays open and updates live while you keep using Chrome normally.

Step 2: read the columns that actually matter

Each row is one Chrome process, labeled by tab title, extension name, or subsystem (GPU Process, Network Service, Utility). Three columns matter most:

  • Memory footprint — the actual physical RAM that process is using right now. This is the one to check first for a "why is my computer slow" complaint.
  • CPU — percentage of a CPU core the process is actively consuming. A tab pinned near 100% here is doing continuous work — auto-refreshing content, running a script in a loop, or rendering something animation-heavy.
  • Network — live data transfer. Useful for catching a tab that's silently still streaming or polling in the background after you thought you were done with it.

Step 3: sort to find the worst offender

Click any column header to sort every row by it — click Memory footprint and the biggest consumer jumps to the top instantly, no scanning required. If Chrome feels slow rather than just memory-heavy, sort by CPU instead; a tab sitting at a high, steady CPU percentage while sitting in the background is a stronger sign of a problem than one that's simply large.

Rows aren't only tabs. Watch for extension rows here too — most extensions run a background process the entire time Chrome is open, independent of which tabs are active, so one can show up near the top of the memory list even though you never explicitly opened anything from it.

Step 4: end the process safely

Select the row for the tab (or extension) you've identified and click End process at the bottom of the window, or double-click the row. This closes only that process — every other open tab, window, and extension keeps running exactly as it was, because Chrome's per-tab architecture is what makes isolating one process possible in the first place.

If the row belongs to a tab you still need, closing its process this way is the same as closing the tab itself: reopen it with Ctrl+Shift+T / Cmd+Shift+T if you change your mind, or just navigate back to it.

Step 5: deal with repeat offenders

If the same extension keeps showing up high on the memory or CPU list run after run, that's worth a permanent fix rather than repeatedly ending its process. Open chrome://extensions and disable or remove anything you don't actively rely on — it's a lasting reduction, unlike ending a process, which Chrome will simply recreate the next time that extension needs to run.

For the deeper explanation of why Chrome's memory use scales with tab count in the first place — the per-process architecture Task Manager is showing you — see Why Chrome Uses So Much Memory.

When the fix is fewer open tabs, not a better diagnosis

Task Manager is great for catching a specific runaway tab, but it doesn't help with the more common case: dozens of ordinary tabs, none individually a problem, adding up. If you keep finding yourself back in Task Manager because the real issue is tab count, not a single bad actor, the fix is having somewhere to put tabs you're not using right now.

Amazing Tabs lets you close tabs for real instead of just identifying which one to blame:

  • Save a tab with one click, then close it completely — its process ends and the memory is reclaimed for good, not just discarded-and-pending.
  • Search saved tabs instantly with ⌘K / Ctrl+K by title or content, so closing them doesn't mean losing track of them.
  • No more hunting for the culprit tab in a list of forty near-identical titles — the tabs you're not actively using aren't in the strip at all.
  • Free for up to 100 saved links.

Stop diagnosing which tab to blame — close the ones you're not using. Add Amazing Tabs to Chrome — free, no signup. Save it once, find it in seconds, anywhere.

Quick recap

  • Open Task Manager with Shift+Esc (Windows/Linux) or Window menu → Task Manager (Mac).
  • Sort by Memory footprint or CPU to bring the worst offender to the top instead of scanning manually.
  • End the process to close only that tab or extension — everything else keeps running.
  • Watch for extension rows, not just tabs — background service workers count too.
  • Repeat offenders need a permanent fix (chrome://extensions), not repeated manual process-ending.

Further reading: Why Chrome Uses So Much Memory for the architecture behind what Task Manager shows you, How to Freeze (Discard) a Tab in Chrome Manually for reclaiming memory without fully closing a tab, or Why Is Chrome Frozen? if the whole browser — not just one tab — has stopped responding.

Add Amazing Tabs to Chrome — free → Install from the Chrome Web Store. 100 saved links free, upgrade only if you want unlimited and cross-device sync. See pricing for the full breakdown — including the $99 lifetime deal (capped at 200 spots).

  • chrome task manager
  • chrome memory usage
  • chrome tabs
  • performance

FAQ

  • How do I open Chrome's Task Manager?

    Press Shift+Esc on Windows or Linux — it opens directly, no need to go through a menu first. On Mac, use the Window menu in the menu bar and choose "Task Manager," since Shift+Esc is not bound by default. You can also right-click an empty part of the tab strip and choose "Task Manager" on any platform.

  • What does "Memory footprint" mean in Chrome's Task Manager?

    It's the actual physical RAM that process is using right now, not a shared or estimated figure — each row (a tab, an extension, or a subsystem like GPU) gets its own process and its own memory footprint. Click the "Memory footprint" column header to sort every row from highest to lowest and the worst offender rises straight to the top.

  • Can I end a tab's process from Task Manager without losing my other tabs?

    Yes. Select the row and click "End process" (or double-click it) — this closes only that tab's process. Every other tab, window, and extension keeps running untouched, since Chrome's per-tab process model is exactly what makes this possible.

  • Why does Chrome's Task Manager show more rows than I have tabs open?

    Because it lists every Chrome process, not just tabs — a GPU process, a network service, a utility process, and one row per active extension all show up alongside your actual tabs. If the list looks longer than expected, scan for extension rows; a background service worker from an extension you forgot about is a common quiet contributor.

  • Does Chrome's Task Manager show the same numbers as my OS's task manager?

    No, and that's normal. Windows Task Manager or macOS Activity Monitor report a single "Google Chrome" or "Google Chrome Helper" entry per OS-level process, which can bundle multiple Chrome-internal processes together or split them differently than Chrome's own view. For finding a specific misbehaving tab, Chrome's built-in Task Manager is the more precise tool because it labels each row by page title.

Was this article helpful?