Chrome slow on a Mac: the tabs to move out before you reinstall

A Mac that ran Chrome comfortably a year ago can start stalling on a tab switch, and the advice arrives in the same order every time: clear the cache, disable extensions, reinstall the browser. The reinstall is the step most people eventually reach, and it is the one least likely to change anything, because a fresh copy of Chrome opens against the same profile, the same extensions and the same forty tabs.

The useful question is narrower. Some of what feels slow is Chrome working as designed, some of it is a handful of specific tabs, and a small part is the Mac itself. Those three have different fixes, and only one of them is a setting.

Separate the three complaints hiding inside "slow"

The first complaint is switching. Clicking a tab and waiting, or watching a tab reload a page that was open a moment ago. That is usually Chrome's memory management doing exactly what it was told to do, and it is the one case where a settings change helps directly.

The second complaint is rendering. A single site scrolls badly, video stutters, a text field lags behind typing. That is normally one page or one extension, not the browser. It follows the site across profiles and across browsers, and it stops when that tab is closed.

The third complaint is the machine. Fans audible, other apps sluggish, battery draining faster than it used to. Chrome is often the largest contributor, but the cause is the total number of live processes rather than any single tab, and closing five tabs changes it measurably.

Sorting a slowdown into one of those three before touching any setting saves most of the work, because the second and third cases are diagnosable in about two minutes with tools that are already installed.

Find out which tabs are actually costing something

Chrome ships its own process monitor, and on a Mac it is faster to read than Activity Monitor. Open the Task Manager from the More menu under More tools, then click the Memory column to sort by memory use. Google's own guidance on speeding up Chrome adds a detail worth knowing: look for rows labelled "Background page", which are extensions rather than open pages. An extension sitting near the top of that list is a stronger candidate than any tab.

Select a row and click End process to stop it. Google notes plainly that unsaved work in that task is lost, so a partially written message is a reason to save first rather than a reason to skip the step.

Chrome can also put the number on the tab itself. Under Settings and then Appearance, Mac users get a switch called "Show memory usage on tab hover preview card". Once it is on, hovering a tab gives its memory use without opening anything, which turns the vague sense that a tab is heavy into a figure that can be compared against the others.

Activity Monitor is the second pass rather than the first, because Chrome appears there as many processes rather than one. Its Energy tab is the part worth reading on a laptop, since it ranks by energy impact over time rather than by memory at this instant, and a tab that quietly runs timers all day shows up there and nowhere else.

What Chrome's performance settings already do

Under Settings and then Performance, Chrome exposes four controls that most slowdown articles mention without describing.

Memory Saver deactivates tabs that are not in use and reloads them when they are clicked again. It has three levels. Moderate deactivates after a longer period, Balanced is the level Google marks as recommended, and Maximum deactivates after a shorter one. Maximum gives back the most memory and produces the most reloads, so the two complaints it addresses pull against each other. There is also a switch called Inactive tabs appearance, which draws a ring around the icon of a deactivated tab, and turning it on removes most of the confusion about why a tab reloaded.

Energy Saver reduces Chrome's image capture rate and background work. Two limits matter. It only runs when the device is unplugged or the battery is low, and it does not run at all when the Mac is plugged in. Google also states that tabs using video conferencing and playing audio are not affected, and that noticeable changes in gaming and video performance are expected when it is on.

Preload pages makes navigation feel faster by fetching pages ahead of time. It is a spend rather than a saving, so on a machine that is already short of memory it is a reasonable thing to switch off.

Performance issue alerts are on by default. When Chrome detects poor performance it offers a notification with a Fix now button, which deactivates tabs on the spot.

The tabs Memory Saver will never reclaim

This is the part that most speed-up advice leaves out, and it decides whether the settings above will help at all. Google publishes the list of settings and activities that prevent a tab from being deactivated:

Active audio or video, including playback and calls. Screen sharing. Page notifications. Active downloads. Partially filled forms. Pinned tabs. Connected USB or Bluetooth devices.

Read that list next to the tabs that are open on a working Mac at four in the afternoon. The chat tab holds a notification permission. The music tab is playing audio. The mail tab is pinned. The dashboard has a half filled filter form. Every one of them is excluded by name.

Memory Saver reclaims the tabs that were going to be closed anyway, and leaves the permanent ones running. That is not a defect. Deactivating a tab that is mid call or mid upload would be worse than the memory it saves. But it means the ceiling on what any performance setting can do is set by how many permanent tabs are in the strip, and no amount of tuning moves that ceiling.

Chrome offers the inverse control as well. An "Always keep these sites active" list under Performance protects specific sites from deactivation, entered as an address. Google documents that a bare domain also covers its subdomains, that a leading dot restricts the rule to the exact host, and that asterisks work as wildcards inside the host and query but not as a prefix or suffix of the host.

Extensions, and why reinstalling does not remove them

Extensions are the other half of the cost, and they are cheap to test. Open the Extensions page from the More menu and switch off the ones that are not in daily use, then reopen Task Manager and compare. Extensions with a "Background page" row are running whether or not any tab needs them.

This is also where the reinstall habit breaks down. Reinstalling Chrome replaces the application. Extensions, permissions, cookies, signed in sessions and the set of tabs that reopens all live in the profile, which the new copy picks up unchanged. A reinstalled Chrome therefore behaves almost identically to the one it replaced, which is why the step so often feels like it did nothing.

Google documents a narrower tool for the same intent, Reset settings to default, under its guidance on making Chrome run better. It is worth reaching for before a reinstall rather than after, because it is the step that actually touches the profile.

The window tools that help the hunting, not the cost

Chrome has added several features that make a crowded window easier to live with, and it is worth being clear that none of them make a tab cheaper to run.

Tab search is the fastest of them. It is pinned in the tab strip by default and opens with Command + Shift + A on a Mac, or by typing @tabs in the address bar and pressing space. It searches the titles of every open tab, which removes the favicon reading that a full strip otherwise requires.

Vertical tabs move the strip to the side of the window, so page titles stay readable no matter how many tabs are open. It is reachable from the View menu on a Mac, from a right click on the strip, or from Settings under Appearance where Tab position can be set to Vertical.

Split view puts two sites in one window, with one view active and the other inactive. Google notes that toolbar items such as back, forward and the address bar apply to the active view only, and that tab specific features such as Translate and Reading mode also act on the active view rather than both.

Tab groups are the one that changes behaviour rather than layout. A group can be collapsed to its name or coloured circle, closed without being deleted, and Google states that when browsing history and tabs are synced with a Google Account, changes to groups are saved and synced across devices. A collapsed group still holds live tabs, so the tab strip gets shorter while the process count stays the same, which is exactly the distinction to keep in mind.

Moving the permanent tabs out of the tab strip

Once the exclusion list is clear, the structural fix follows from it. The tabs that Memory Saver refuses to deactivate are the ones that were never really browsing. A chat window, a mail window and a music player are applications that happen to be delivered over the web, and keeping them in a tab strip is what forces the browser to stay open all day.

Chrome can hand them their own window. From the More menu, choose Cast, save, and share, then Install page as app. Some sites also offer an Install button at the right of the address bar. The result opens from the Applications folder, appears in the Command Tab switcher, and Google lists notifications and icon badges among the extra capabilities a web app gets. Safari has an equivalent item, Add to Dock, reached from the Share button in its toolbar.

Route	Where the window comes from	Browser extensions	Separate sign in per app
Chrome, Install page as app	The Chrome profile it was installed from	Those of that profile	No
Safari, Add to Dock	Safari	Not supported	Yes
A dedicated site to app tool	A Chromium browser already installed	Supported per app	Yes

The honest limit is worth stating. A standalone window still runs a renderer process, so the memory does not disappear. What changes is the shape of the problem. The browser window goes back to being something that can be closed at the end of a task, the tabs that were pinned and permission holding are no longer in it, and Memory Saver is finally pointed at a strip where every tab is disposable. The trade-offs between the three routes, including how extensions and separate sign ins are handled, are set out on Features, and the step by step version is in the Guide.

What to change first

Open Task Manager, sort by memory, and write down the top five rows. If extensions lead the list, switch them off before touching any setting. If the list is topped by the same chat, mail and music tabs that have been open for weeks, no performance setting will reach them, and the change that helps is giving those three their own windows with Kagemusha or with the route built into the browser already installed.