Browser tab management extensions after the MV2 cutoff

Search this and half the results are listicles from 2022 recommending extensions that no longer install. The links still resolve, the screenshots still look right, and the store page returns nothing. That is not link rot in the usual sense. A specific deadline passed, and it removed a large part of the category in one move.

Anyone choosing a tab manager in late 2026 is therefore choosing from a smaller and much younger field than the search results suggest. That is worth knowing before installing anything, because the reason old recommendations died is the same reason to check the maintenance date of any new one.

The deadline that emptied the shelf

Chrome extensions are built against a manifest version, and the older one is finished. The published timeline is specific about the final step, dated 31 August 2026.

All remaining Manifest V2 extensions are removed from the Chrome Web Store. Manifest V2 extensions installed on Chrome 138 or earlier will remain installed, but will be unable to receive any updates and cannot be reinstalled from the Chrome Web Store once removed from Chrome. Source: developer.chrome.com

The step before it matters more for anyone who has not looked at their extension list in a while. From Chrome 138 onward, released 24 July 2025, all users on all channels had Manifest V2 extensions disabled, and the documentation states that users can no longer turn them back on.

Tab managers were hit harder than most categories. They tend to be small projects maintained by one person, often written years ago, often good enough that they were never revisited. Migrating a background page to a service worker is real work for no new features, and many authors did not do it.

The practical consequence is a rule for choosing. Check the last updated date on the store listing before reading the feature list. An extension updated within the last year survived a rewrite that killed most of its competitors, which is a stronger signal about maintenance than any review score.

Five categories, and what each one is actually fixing

The category name hides five different jobs. Choosing well starts with naming which job is needed, because an extension doing one of them will not help with the others.

Suspenders unload tabs from memory while leaving the title in the strip. They exist to make a large tab count survivable rather than to reduce it.

Session savers store the current set of tabs under a name so the window can be closed and restored later. They target the specific fear that stops people closing tabs, which is losing the trail rather than losing the page.

Vertical sidebars move the strip to the left edge so titles are readable at any count. They change legibility and nothing else.

Switchers put a search box over the open tabs, reached by a shortcut, so navigation happens by typing. They attack the visual scan directly.

Organisers create named groups, colour codes and rules for what goes where. They are the most demanding to keep up, because a grouping scheme is only useful while it is maintained.

The mismatch to avoid is common and expensive. Someone drowning in a visual scan installs a suspender, gets a faster machine and the same scan, then concludes tab extensions do not work. The fix belonged to a different category.

What the browser already does without an extension

A large part of what these extensions were invented for has been absorbed into the browser, and the extension API list confirms it, since Chrome now exposes tab groups, sessions, reading lists and a side panel as APIs of their own.

Grouping is native. Tabs can be grouped, named and colour coded, and groups can be collapsed to a single label. Suspending is native too, through the performance settings that free memory from tabs left idle. Tab search is native, reached from the small chevron at the end of the strip, and it searches recently closed tabs as well as open ones. A reading list is native, which covers most of what a session saver was doing for articles rather than for work sets.

Other browsers went further. Vivaldi publishes Tab Stacking for two level groups and Tab Hibernation for unloading idle tabs, both built in and free. Edge ships vertical tabs without an extension.

The honest summary is that three of the five categories are now largely redundant on a current browser. Suspenders, basic organisers and reading list style session savers duplicate something already present. What remains genuinely additive is the switcher, and the vertical sidebar on browsers that do not offer one.

The permission cost, and how to read it

A tab manager needs to see tabs, which means the tabs permission, which grants access to the URL and title of every open tab. That is a reasonable request for this category. The part worth understanding is how the warning behaves.

Some permissions may not display warnings when paired with other permissions. For example, the "tabs" warning won't show if the extension also requests "<all_urls>". Source: developer.chrome.com

An extension asking for access to every site absorbs the tab warning into a broader one. So a quiet install screen does not mean a narrow permission. It can mean the opposite.

Two habits follow from that, and both take seconds. Read the permission list on the store page rather than the install dialog, since the page lists them individually. And check the extensions page in Chrome settings for site access, setting anything that does not need every site to run on click instead.

There is a second risk that no permission screen shows, which is that ownership can change after installation. An extension is updated silently, and a project transferred to a new owner keeps the same install base and the same granted permissions. Nothing in the browser announces the transfer. The defence is unglamorous: keep the count of installed extensions small enough to review occasionally, and remove the ones that solved a problem that no longer exists.

Picking a category from evidence rather than from a list

The category needed is not obvious from the inside, because the discomfort of a crowded window feels like one thing. A week of rough notes separates it, and the notes only need three tallies.

Count the times a machine slows down or a fan spins up while working in the browser. Count the times more than five seconds goes into finding a screen that is already open. Count the times something is closed and then hunted for again in history. Whichever tally is largest names the category: the first is a suspender or the built in performance setting, the second is a switcher, the third is a session saver or a reading list.

Two results are common and both are informative. If the tallies come out roughly level, the problem is volume rather than arrangement, and no extension fixes volume. If the second tally dominates by a wide margin, which is the usual outcome for anyone running many applications rather than reading many articles, then the issue is not the tabs at all but what is being kept inside them.

One more thing belongs in that week of notes, because it changes the answer more than any feature comparison. Note which of the open tabs would break something if it were unloaded. A chat client, a queue dashboard, a call tool and a notification page are not documents, and every category above treats them as documents. The count of live services in the window is the number that decides whether an extension can help at all. Two or three is a browser problem. Seven is a layout problem.

Where every tab extension stops

Three limits are structural. No extension in any category crosses them, which is useful to know before spending a week trying.

The first is the profile boundary. An extension is installed into a profile and sees only that profile's tabs. Someone running three profiles for three accounts needs three installations, three sets of settings, and gets three separate views with no combined list.

The second is background suspension for live services. A chat tab that has been unloaded is not holding a connection, and messages arrive when it is brought forward again. A suspender makes this worse deliberately, and an organiser does not touch it. No arrangement of tabs makes a suspended tab receive a message.

The third is where outside links land. A link clicked in a calendar application or a mail client goes to the system default browser, and macOS holds one default at a time with no rule for sending a work link into a work context. That decision is made before the browser opens, so nothing inside it can intervene.

The five categories side by side

Category	Fixes	Now native	Cannot fix
Suspender	Memory pressure	Yes, in performance settings	The visual scan
Session saver	Fear of losing the trail	Partly, reading list and groups	Live services
Vertical sidebar	Unreadable titles	In some browsers	Account separation
Switcher	Time spent scanning	Partly, tab search	Cross profile view
Organiser	No structure	Yes, tab groups	Keeping itself maintained

Reading the last column as a set makes the shape of the ceiling clear. Everything an extension can reach lives inside one profile and treats every tab as a document. The things it cannot reach are exactly the things that make a work day feel heavy: several accounts, a handful of applications that must stay connected, and links arriving from outside.

When the tab is the wrong unit

Every category above accepts one premise, which is that the work is a set of pages inside one window and the job is to arrange them better. That premise holds for research and reading. It stops holding when most of the day is spent in six or seven applications that are open permanently and signed into more than one account.

For that shape, the alternative is to stop arranging tabs and give each application its own persistent space with its own session. Two accounts of one service become two entries rather than two tabs, switching happens by name or shortcut, and whether something is allowed to sleep becomes a per application setting rather than a browser wide policy. That layout is described under Workspaces, and the surrounding behaviour, meaning notification handling and where an external link is sent, is covered under Features.

The category has free and paid entries. The community maintained option is examined in the comparison with Ferdium, and the subscription products, where Wavebox publishes a free tier of two groups holding two apps each alongside paid plans, are covered in the comparison with Wavebox.

What to change first

Open the extensions page today and remove anything disabled or not updated in the past year, since a disabled Manifest V2 extension is dead weight that cannot be revived. Then use the browser's own tab groups and tab search for two weeks before installing a replacement, because three of the five categories are now duplicating something already there. If the remaining problem is several accounts and a handful of always on applications rather than untidy tabs, a per app layout such as SpaceDeck addresses the column that extensions cannot reach.