How open tabs eat into memory

Chrome has no fixed tab limit. Too many tabs is the point at which a Mac's memory pressure graph in Activity Monitor leaves green during normal work, and that point depends on what is open far more than on how many tabs there are. Twenty tabs of documentation can cost less than six live web apps such as mail, chat and a design tool. The quickest way to know whether the current count is too many takes two screens: Activity Monitor for the verdict, then Chrome's own Task Manager to find the tab responsible.

Google's own advice is short and honest about the trade. Its help page on speeding up Chrome says that the more tabs are open, the harder Chrome has to work, and recommends closing the ones not in use (Google Chrome Help). The rest of this page covers how to tell whether that advice applies to a particular Mac, which Chrome settings change the answer, and the case where closing tabs is not the fix at all. Settings and menu names below were checked against the vendors' help pages on 18 October 2026.

Why the tab count is a poor measure

Chrome looks like one application and runs as many processes. The browser frame, the GPU work, extensions and the renderers that draw page content run separately, partly for stability and partly for security, since content from different sites is kept apart. The practical result is that a tab is not a fixed unit of cost.

A static article finishes loading and then mostly sits there. A web app keeps working after it loads. Mail polls for new messages, chat holds a live connection and redraws, a design tool keeps a large canvas in memory, and a video call keeps the GPU busy. Each of those is closer to a running program than to a page.

That explains a pattern many people notice without being able to name it. Opening twenty pages from one help centre rarely slows a Mac down. Opening mail, chat, a wiki, a calendar, a design file and an AI chat slows it down quickly, even though that is six tabs. The useful count is not tabs. It is how many of the open tabs never go idle.

There is also a second kind of too many that has nothing to do with memory. Once the tab strip stops showing titles, finding the right tab means hovering across a row of icons. The Mac stays fast, but the person using it slows down. The two problems feel the same and have different fixes, so the next sections separate them.

Reading memory pressure on a Mac

The first stop is Activity Monitor, in the Memory tab. Apple's guide is explicit that free memory on its own says little: having free or unused memory does not necessarily improve performance, because macOS gets its best performance by using and managing all of the memory available (Apple Support).

The number that matters is the Memory Pressure graph at the bottom of the window. Apple describes its three colours:

Colour	Apple's description	What it means for tabs
Green	Using all of its RAM efficiently	The current tab count is fine
Yellow	Might eventually need more RAM	Worth finding the heaviest tabs
Red	Needs more RAM	Too many live tabs for this Mac

Apple's companion page on memory usage lists what feeds the graph: free memory, swap rate, wired memory and file cached memory. It also explains Compressed, the memory macOS squeezes from inactive apps to make room for active ones, and Swap Used, the space on the startup disk used to move data in and out of RAM (Apple Support).

A small amount of swap is normal. Swap that climbs through the day is the signal to watch, because each return to something that was pushed out costs a wait. Much of what gets described as Chrome feeling slow is the Mac reading state back from disk.

One more check settles a lot of arguments. Apple's guide explains how to find out whether memory can be added: hold the Option key, choose System Information from the Apple menu, then click Memory under Hardware. If the Memory Slots pane does not appear, the Mac has no upgradeable memory. On those machines, the installed amount is permanent, and the practical tab ceiling is set by it.

Finding the tab that costs the most

Activity Monitor can say that Chrome is the heaviest thing running. It cannot say which tab, because Chrome's processes appear under similar names. That is the job of Chrome's Task Manager.

Google's help gives the path: at the top right of Chrome, select More, then More tools, then Task Manager. Then select Memory to sort the list by memory use, look for any items labelled Background page, select the task to close and click End Process. Google adds a warning worth taking seriously: any unsaved work in that task will be lost.

Sorting by memory usually ends the investigation in under a minute. Two or three rows tend to account for most of the total, and they are rarely the ones a person would guess. Documentation tabs left open for a week often sit near the bottom. A single web app with a long running session, or an extension with a background page, often sits near the top.

Two details confuse people the first time they read this list. Rows and tabs do not match one to one, because several tabs on the same site can share a process. And one tab can appear as several rows when the page embeds content from other sites, such as video players, maps or payment frames.

There is also a lighter way to check without opening anything. Chrome on Mac has a setting under Appearance called Show memory usage on tab hover preview card. With it on, hovering over a tab shows how much memory it is using, which is often enough to spot the heavy one while working (Google Chrome Help).

What Memory Saver does, and what it leaves alone

Chrome's Memory Saver releases memory from tabs that are not being used. In Google's words, Chrome deactivates tabs that are not currently in use, and an inactive tab reloads automatically when it is opened again. The switch sits under More, then Settings, then Performance.

Memory Saver has three levels, each changing how soon tabs become inactive:

1. Moderate, where tabs become inactive after a longer period.
2. Balanced, which Google recommends, after what it calls an optimal period.
3. Maximum, where tabs become inactive after a shorter period.

Turning on Inactive tabs appearance draws a ring around the icon of any deactivated tab, which makes it visible which tabs have been released.

The exceptions matter as much as the setting. Google lists activities that may prevent a tab from being deactivated: active audio or video, including calls, screen sharing, page notifications, active downloads, partially filled forms, pinned tabs, and connected USB or Bluetooth devices. Sites can also be added to a list called Always keep these sites active.

That list describes most of the tabs people keep open for work. A chat app sends notifications, a mail draft is a partially filled form, and the tools people pin are pinned tabs. Memory Saver works very well on reading material and does little for the always on apps that cause the problem in the first place. Chrome also shows a notification recommending tab deactivation when performance is poor, a setting called Performance issue alerts that is on by default.

A number, if one is needed

People often want a figure anyway, so here is a defensible way to produce one for a specific Mac rather than a generic rule.

Work normally for a day with Memory Saver on Balanced. Each time the memory pressure graph turns yellow, note how many tabs are open and how many of them are live web apps. After a few occurrences, the live app count at which yellow appears is the practical limit for that machine. The total tab count at that moment matters much less, since reading tabs are being released by Memory Saver anyway.

The result will differ widely between machines. A Mac with more installed memory tolerates more live apps before yellow appears, and other software running alongside, such as editors, virtual machines or video tools, draws from the same pool. That is why generic tab limits online contradict each other: they leave out the two variables that decide the answer.

What happens	Where to look	What to change
Pauses when switching apps	Memory pressure and Swap Used	Reduce live web apps, not reading tabs
One site slows everything	Chrome's Task Manager, sorted by Memory	End that process or keep it in its own window
Closing tabs changes nothing	Extension and Background page rows	Turn off or remove unused extensions
The Mac is fast but finding tabs is slow	The tab strip itself	Change where apps live, not how many are open

The last row is not a memory problem. It shows up in the same search because it produces the same frustration.

When the problem is where the apps live

Closing tabs works while most of what is open is reading material. Once six or eight web apps stay open because the work needs them, closing is not an option, and the question changes from how much memory they use to where they should live.

A single window is a single line. Everything competes for the same strip, targets shrink as the count grows, and reaching a specific tool means scanning instead of aiming. That cost grows with the number of always on services and does not respond to any memory setting.

The alternative is to give each web app its own place, so switching happens through a sidebar or a keyboard shortcut rather than a row of icons. An app aggregation browser does this, keeping each app in its own container and, in some products, showing unread counts on sidebar icons so that a tab does not have to stay open just to watch for messages. How grouping by project or client works is set out on the Workspaces page, and whether the specific services in daily use are covered is listed on the Supported apps page.

This does not shrink total memory use. Six live web apps need roughly what six live web apps need, wherever they are drawn. What changes is that each app is easy to find, easy to attribute in Activity Monitor, and easy to close as a whole when a project ends.

What to change first

Open Activity Monitor and read the memory pressure colour before closing anything, then sort Chrome's Task Manager by Memory and look at the top five rows. If those rows are reading tabs, turning on Memory Saver at Balanced is the whole fix; if they are the apps that stay open all day, try SpaceDeck, whose free plan holds one workspace with up to three apps and shows unread counts on sidebar icons without keeping those tabs open.