Too many tabs open? Sort them before closing any

When there are too many tabs open, the fix that sticks has three steps, done in this order. First, find and close duplicates and dead pages with the browser's own tab search, which takes a few minutes. Second, move everything that is still unfinished into named groups that can be closed and reopened later, so nothing is lost. Third, let the browser's memory settings handle whatever remains open, so the machine stops slowing down. Most advice skips straight to "close some tabs", which does not work because every tab is holding something and a two-pixel favicon gives no clue which ones still matter. This guide walks through the sorting first, using the exact menu names in Google Chrome as documented on October 18, 2026, and then covers why the count creeps back.

How to tell the strip has crossed the line

There is no fixed number. A strip of fifteen tabs can be unusable and a strip of eighty can be fine if it is grouped. The useful signals are practical ones.

• Titles are gone. Once every tab has shrunk to its icon, finding a page means hovering along the strip. That is the point where the strip stops working as navigation.
• The same page is open twice. A second copy of a document or inbox usually means the first copy could not be found. Duplicates are the clearest sign that the tab strip has failed as an index.
• Pages reload when clicked. In Chrome this is often Memory Saver at work rather than a fault. It means the browser has already decided some tabs are not in use.
• Fans spin up or typing lags. On a Mac, a heavy page in a background tab can still use memory and CPU.

Chrome can show how much memory a single tab uses. In Settings, then Appearance, a Mac user can turn on Show memory usage on tab hover preview card, and hovering over a tab then shows its memory use. That turns "the browser feels slow" into a list of specific tabs worth dealing with first.

Every open tab is a decision that was postponed

A tab stays open for one of two reasons. Either something in it is unfinished, or closing it would require deciding whether it will be needed again. The second reason accounts for most of the strip.

Opening a tab costs nothing and takes no thought. Closing one requires three small judgments: can this page be found again, is anything in it unsaved, and is the thing it was opened for actually done. Multiplied across ninety tabs, that is real work, and the browser offers no help with any of it. So the strip grows steadily and is only ever cleared in a panic, usually by quitting the browser and hoping session restore brings back the right ones.

This is why the forum threads that rank for this phrase keep returning to the same confession: the tabs are not open because they are being read. They are open because closing them feels risky. Any fix that does not remove that risk will be abandoned within a week.

Sort into four kinds before closing anything

Look at each tab and put it in one of four piles. The sort is quicker than it sounds, because most tabs fall into a pile at a glance and only a few need a second look.

1. Done, but kept "just in case"

Search results already read, articles already finished, a product page already compared. These can be closed without loss, because the page can be found again from history. In Chrome, closing by accident is reversible with Command + Shift + T on a Mac, which reopens the last closed tab or window.

2. Reading for later

Articles and videos that were opened with the intention of reading them. They are not tasks and do not need to sit in the strip. A reading list, a bookmark folder, or a saved tab group named "Read" holds them without the visual cost.

3. Work in progress for a specific project

A spec, a ticket, a spreadsheet and two reference pages that all belong to one job. These are the tabs that actually need to come back together. They belong in a named group, one per project.

4. Apps that are always open

Gmail, Slack, a calendar, a chat tool, a project board. These are not pages. They are applications that happen to run in a tab, and they are open all day by design. In most strips they are the oldest tabs, pinned or not, and they are the ones that get duplicated most often because a link from one app opens a fresh copy of another.

Once sorted, the result is often lopsided. Pile one tends to be the largest and can go immediately. Piles two and three move into groups. Pile four is small in number but is the reason the strip never feels clean, because it can never be closed.

Use Chrome's own tools for each pile

Chrome already has a tool for each of the first three piles. The Chrome Help page on managing tabs documents all of them.

Finding duplicates and dead pages. Tab Search lists every open tab and lets each one be closed from the list. It opens from the tab strip button or with Command + Shift + A on a Mac. Typing @tabs in the address bar and pressing Tab or Space searches open tabs from there as well. Searching a site name, such as the name of a document tool, shows every copy at once.

Closing many at once. Clicking the first tab and Shift-clicking the last highlights the whole range. Right-clicking any highlighted tab then offers bulk actions: add to group, move to another window, pin, mute, or close.

Grouping work in progress. Right-click a tab, choose Add tab to group, then New group, and give it a name and color. Closing it with Close group does not delete it. The group is saved and can be reopened later from the bookmarks bar or from the Tab groups menu. With tab sync turned on, saved groups follow the Google Account to other devices. One caution from the same page: deleting a group removes it from every device signed in to that account, so close groups rather than deleting them unless the work is truly finished.

Seeing titles again. Vertical tabs move the strip to the side of the window, where full titles stay visible and the list can scroll. On a Mac, it is under View, then Show Tabs Vertically.

Labeling windows. If projects live in separate windows, right-click the empty space next to the New tab button and choose Name window. The name shows when switching between windows.

Let the browser handle performance

Sorting fixes the clutter. Performance is a separate problem and Chrome handles most of it automatically if it is allowed to.

The Chrome Help page on performance settings explains Memory Saver. When it is on, Chrome deactivates tabs that are not in use and reloads them when they are clicked. It is found in Settings, then Performance, with three levels: Moderate, Balanced (recommended) and Maximum. Maximum deactivates tabs sooner and saves the most memory.

Two details on that page change how Memory Saver behaves with a large strip.

• Some tabs are never deactivated. The page lists active audio or video, screen sharing, page notifications, active downloads, partially filled forms, pinned tabs, and connected USB or Bluetooth devices as things that can prevent deactivation. Pinned tabs in particular stay awake. Pinning twenty tabs to tidy the strip quietly removes them from memory savings.
• Exceptions can be set by site. Under Always keep these sites active, specific sites can be added so they are never deactivated. This is useful for a web app that must keep receiving messages, but every site added there is a site that keeps using memory.

Chrome also shows a Performance issue alerts notification that recommends deactivating tabs when browsing slows down, and it is on by default. Clicking Fix now accepts the suggestion.

On a MacBook running on battery, Energy Saver is the other setting on the same page. When it is on, it works whenever the device is unplugged or the battery is low, and Chrome limits background activity, including stopping background tabs that use a lot of CPU. The help page notes that tabs running video calls or playing audio are not affected, so a meeting in a background tab keeps working. Energy Saver can change how games and video perform, and it does not turn on while the laptop is plugged in. For a long strip of tabs on a laptop, Memory Saver at Balanced plus Energy Saver on battery covers most of the slowdown without closing anything.

Neither setting removes clutter. They only make clutter cheaper to keep. That is useful while the sort is in progress, but it also makes it easy to postpone the sort indefinitely, which is how the strip reached its current size.

If a single tab has frozen the browser, the Task Manager, under More tools, lists each page and extension with an End process button.

Why the count comes back

A cleared strip tends to fill up again, and the reason is usually pile four.

The always-open apps keep generating new tabs. A link in Slack opens a document in a new tab. A calendar invite opens a meeting page. An email link opens a ticket. Each of those is a fresh tab in the same strip as the apps themselves, and each one starts the postponed-decision cycle again. A second Google or Slack account makes it worse, because the link may open in the wrong account, and the fix is to open yet another tab and sign in there.

So the long-term fix is to separate pile four from the other three. Two approaches are common.

A separate window or profile for apps. Keep one window, or one Chrome profile, that holds only the always-open apps, and do browsing in another. The Chrome Help page on profiles covers adding one from the profile icon. This is free and works, though links still open wherever the system sends them.

An app aggregation browser. These keep each web app in its own window or panel outside the tab strip. One such browser lists its approach on its features page: unread counts for services such as Slack and LinkedIn appear on the sidebar icon without keeping a tab open, links open in the app and account they belong to, and a command palette on Command + K jumps to any app, tab or page. The list of supported apps shows which services it covers. The trade-off is another program to learn, and on that product, a free plan capped at one workspace and three apps.

What to change first

Run the four-pile sort once, close pile one, and move piles two and three into named tab groups. Then take the always-open apps out of the tab strip, either into their own window or into an app browser such as SpaceDeck, so new links stop landing in the same strip as everything else.