Google Chrome multiple tabs: acting on several at once

Most writing about having a lot of tabs open in Chrome is about closing some of them. That advice skips the question that decides how much of a working day disappears into small movements: which operations in Chrome act on more than one tab at a time, and which only ever act on the one currently in front. Chrome has a fair number of the first kind. They are almost all hidden behind a click that nobody performs by accident.

Selection is a state the tab strip remembers

Clicking a tab switches to it. Holding Cmd and clicking a second tab does something different. It adds that tab to a selection while leaving the first one selected too. Shift and click selects a continuous run between the current tab and the one clicked. Selected tabs are drawn in a lighter shade than the rest of the strip, which is the only visual sign that anything has changed.

From that point every tab operation applies to the whole set instead of one tab. Closing closes all of them. Pinning pins all of them. Muting mutes all of them. Right clicking any tab in the selection gives a menu whose items are worded in the plural, which is the confirmation that the selection took.

Dragging is the one worth learning first. Grabbing any tab inside a selection drags the entire set, so eight tabs can be reordered, pulled into a group, or thrown into another window in one movement. Without the selection, the same rearrangement is eight separate drags, each one requiring a decision about where the tab lands.

The selection is fragile in a specific way. It survives dragging and it survives the context menu, but a plain click anywhere in the strip clears it and switches to the tab clicked. That means the pattern is always the same: build the selection, then act immediately. Anyone who builds a twelve tab selection, gets distracted, and comes back to it will be building it again.

Moving a set out of the window it is stuck in

The tab strip has exactly one ordering. Everything in it is in a queue with everything else, and a research tab sits next to a chat tab because they were opened in the same minute, not because they belong together. A second window is the cheapest way to buy a second ordering.

Dragging a selection off the strip and dropping it on the desktop creates a new window containing exactly those tabs. The right click menu offers the same thing as a command, along with an option to move the selection into a window that is already open. That second one matters more than it looks, because it is the only way to consolidate: two windows that grew separately can be merged back down without touching a single address bar.

Once tabs live in separate windows, macOS starts helping. Each window can be sent full screen, which turns it into its own Space, and swiping between Spaces then switches between sets of tabs rather than between individual pages. Each window can be parked on a different display. The standard macOS shortcut for cycling windows of the front application moves between them without going near the mouse.

The cost is that the windows are anonymous. Chrome titles a window after whichever tab is active in it, so the name changes as work moves, and the app switcher shows several entries with the same icon. This is where the arrangement starts to leak, and it is the reason Workspaces exist as a separate idea in browsers built around named sets rather than around one strip.

Opening a set on purpose instead of accumulating one

Tabs multiply because opening one is free and opening a considered set of them is not obvious. Chrome has three mechanisms for the second thing.

A bookmark folder can be opened as a unit. Right clicking a folder in the bookmarks bar gives an option to open everything inside it, and the whole folder arrives as tabs in one action. The matching operation runs the other way: the Bookmarks menu has an entry that takes every tab in the current window and saves it into a single new folder. Together they turn a window into something that can be put away and taken out again, which is the part that closing tabs alone never provides.

Startup pages are the second mechanism. Settings has an option to open a specific page or set of pages when Chrome launches, and it can capture whatever is open at that moment rather than making anyone type addresses. Anyone who begins every morning by opening the same five services is doing by hand what this setting does once.

Pinned tabs are the third. A pinned tab shrinks to the width of its favicon, moves to the left of the strip, resists being closed by the usual shortcut, and comes back after a restart. Pinning is also the clearest statement about what a tab is for: pinned means always on, unpinned means passing through.

For the mistakes rather than the plans, Chrome restores closed tabs in a known order. The Mac shortcut list gives this one plainly:

Reopen previously closed tabs in the order they were closed: ⌘ + Shift + t Source: support.google.com

Pressed repeatedly it walks back through the recent history of closures, and it will also reopen a closed window with its tabs intact.

Two tabs visible at the same moment

Selecting, moving and grouping all still show one page at a time. When the task is comparison, that is the wrong shape. Chrome now ships a split view, and the Mac keyboard shortcut list documents it as ⌘ + Option + n, which opens split view in the active tab. It divides the content area into two panes inside one tab.

The limit is two. A split view is for a document and the thing being written from it, or a design and the page it describes. It is not a layout for five services.

The older answer is still available and still valid: two Chrome windows sized to half the screen each, with macOS handling the tiling. That approach scales past two, survives Chrome updates, and lets each half be scrolled, zoomed and reloaded as a fully independent window. It costs screen space, and on a laptop display two halves of a browser are narrow enough that many web applications switch to their mobile layout.

What Chrome does on its own once the count climbs

Chrome deactivates tabs that are not being used. The behaviour has a name and a settings page.

To save your computer's memory and help active tabs run smoothly, Chrome deactivates tabs that you aren't currently using. When you access an inactive tab, it automatically reloads. Source: support.google.com

Settings has a Performance section with three levels of aggressiveness, described by Google as Moderate, Balanced, and Maximum. Moderate waits longer before deactivating a tab, Maximum waits a shorter time. Balanced is the default recommendation.

The more useful half of that page is the list of conditions under which Chrome will refuse to deactivate a tab at all. Google names active audio or video including calls, screen sharing, page notifications, active downloads, partly filled forms, pinned tabs, and connected USB or Bluetooth devices. Every one of those is a case where a silent reload would destroy work or drop a connection.

There is also an exclusion list. Sites added to the always active list are never deactivated, and Google documents the pattern format for entries as [scheme://][.]host[:port][/path][@query], where a bare domain also covers its subdomains and a leading dot restricts the rule to that exact host. A chat tool, a dashboard that polls, and anything holding a long form are the obvious candidates.

None of this reduces the number of tabs. It reduces what the inactive ones cost, which is a different problem and a smaller one.

Finding the one tab that matters among the many that do not

Past roughly twenty tabs the favicons stop being distinguishable, and three of them are the same grey document icon. At that width, hunting by eye is slower than searching, and Chrome has two search surfaces for open tabs.

The first is the control at the right hand end of the tab strip, which lists every open tab by title and filters as characters are typed. It reaches across all open Chrome windows rather than only the current one, which makes it the fastest way back to a tab that was dragged into a second window and then forgotten. It also lists recently closed tabs underneath the open ones, so a mistaken close and a misplaced tab are recovered from the same box.

The second is the Task Manager, reached from the Window menu on macOS. It lists every tab and every extension as a separate row with its memory footprint and its share of processor time, and the columns sort. This answers a question the tab strip cannot: not which tab is wanted, but which one is responsible for the fans spinning. The answer is frequently an extension rather than a page, and occasionally a single tab left open on a site that is running an animation nobody is watching.

Both tools reward better tab titles, which is a thing under partial control. Many web applications put the workspace or account name at the front of the document title, and services that do not are exactly the ones that end up unfindable in a list of forty. Where a page title is useless, pinning the tab at least fixes its position, so the search becomes spatial rather than textual.

The line the tab strip cannot cross

Every technique above rearranges tabs that share one set of cookies. That is the boundary. Cookies belong to the profile, not to the tab, so two tabs in the same window cannot hold two live sessions on the same service unless that service builds multi account support itself. No amount of selecting, grouping or splitting changes it.

Container	Two accounts of one service, live at once	Opens as a set in one action	What closing it costs
Tabs in one window	No	Yes, from a bookmark folder	Every tab in the window
A second window	No	No	Only that window
A second Chrome profile	Yes	Yes, with startup pages	Only that profile's windows
One window per service	Yes	Yes	Only that service

The last row is the shape that browsers built for aggregation use. Each web application gets its own persistent window with its own session, so the question of which account is in front is answered by which window is in front. The differences between the products in that category are worth reading before switching, because they disagree about pricing model and about how much of the browser they replace, which is the ground covered in Compared with Wavebox.

What to change first

Spend one week using Cmd click before every drag and before every close, and use the bookmark folder round trip once on the set of tabs that is currently permanent. If after that the friction that remains is about accounts rather than about arrangement, the tab strip is not the thing to fix, and a browser that gives each service its own window is the next thing to try. SpaceDeck is built on that model for macOS.