What a session manager is, and what it will not fix

The search usually starts after something went wrong. A browser crashed with thirty tabs open, or a restart wiped a research session that took two hours to assemble, or somebody on a team mentioned a session manager as though everyone already knew what one was. The phrase is doing a lot of work, and it points at three unrelated categories of software depending on who is saying it.

Sorting out which one is meant takes about a minute, and it saves installing the wrong thing. After that comes the harder question, which is whether a session manager addresses the problem that actually caused the frustration, because for a lot of people on a Mac it does not.

Three unrelated tools answer to the same name

The first meaning is a browser add-on that saves the set of tabs and windows currently open, gives the set a name, and reopens it later. This is what most search results assume, and it is almost certainly the meaning intended by anyone talking about tab clutter.

The second meaning is a login switcher. Some tools describe themselves as session managers because they save and swap the cookies that keep an account signed in, letting one browser window hold several accounts on the same service. The Edge add-on catalogue lists entries under this description, such as tools whose stated purpose is to share or clear login state rather than to restore tabs. The two categories look similar in a store listing and do completely different things.

The third meaning is infrastructure. Session Manager is the name of a capability inside AWS Systems Manager for opening a shell on a remote instance without an open SSH port. Terminal multiplexers like tmux and screen are also called session managers, because they keep a shell session alive after the connection to it drops. Anyone who arrived at this term through a DevOps document is reading about a different subject entirely.

Telling them apart takes one question: does the tool remember which pages were open, which account was signed in, or which remote process is still running. Those are three different kinds of state, and no single product covers all three.

What a browser session actually holds

A session, in the browser sense, is the arrangement of the browser at a moment in time. That means the list of open windows, the tabs inside each window and their left to right order, which tab was active, which tabs were pinned, and in most implementations the back and forward history of each individual tab.

It does not include the thing people most often assume it does. Authentication lives in cookies and site storage, which belong to the browser profile, not to the saved session. Restoring a session on a machine that is signed out produces a screen full of login pages. Restoring it on the same profile produces working pages, because the profile still holds the cookies.

Chrome writes this state to disk continuously. Inside a profile directory there is a folder named Sessions containing files named Session_ and Tabs_ followed by a long number. Those files are the raw material behind both crash recovery and the startup setting, and they are the same files an extension reads or replicates in its own storage.

The built in version of the feature is described plainly in the Chrome help documentation:

You can tell Chrome to re-open the same pages you were looking at when you quit. Your cookies and data are saved, so any websites you were logged into before open again. Source: support.google.com

That single setting covers the most common reason people go looking for a session manager. It restores one arrangement, the last one. Everything a dedicated tool adds is about having more than one arrangement, and choosing between them.

The four features it gets confused with

Every browser already ships with something adjacent, which is why the category feels crowded. The differences are not cosmetic.

Feature	Restores a whole window set	Holds several named sets	Separates signed in accounts	Survives a browser crash
Bookmarks folder	Only by opening the folder manually	Yes	No	Yes
Tab groups	Within one window	Yes	No	Depends on sync being on
Continue where you left off	Yes	No, only the last one	No	Yes
Browser profiles	Each profile restores its own	One per profile	Yes	Yes
Session manager add-on	Yes	Yes	No	Depends on where it saves

Bookmarks are the closest free substitute and get dismissed too quickly. A folder of bookmarks opened with the "open all" command does most of what a saved session does, minus the per tab history and the automatic capture.

Tab groups are the feature Google has invested in most recently, and they are genuinely useful inside a single window. They are also tied to the account signed into the browser when saving and syncing are enabled, which means a change made on one machine is not local to that machine.

Profiles are the only item on that list that separates accounts, and they are also the heaviest, since each profile is a separate set of cookies, extensions and settings that the browser has to keep resident.

Where the saved data lives, and why it matters later

Two storage models exist. Local tools keep saved sessions in the extension's own storage inside the browser profile, which means no account, no server, and no recovery if the profile is deleted. Cloud tools keep them on a vendor server, which means the sessions follow the reader to another machine and continue to exist if the profile is wiped, at the cost of a subscription and a third party holding a list of every URL saved.

The second model carries an exit cost that is easy to overlook at install time. Partizion, a paid workspace tool, states its policy directly on its pricing page: at the end of a trial the account is closed automatically and the data is deleted from its servers fourteen days later. That is an honest and clearly stated term, and it is also the shape of the risk. Saved sessions held on someone else's server are only as durable as the billing relationship.

The practical hedge is export. Session Buddy, one of the longest running tools in the category, lists import and export across more than fifteen formats as a headline feature, and any tool that can write a plain list of URLs to a file protects against both vendor exit and personal exit. Checking that the export exists before committing months of saved work is a two minute job.

There is a third storage model that gets ignored because it is not marketed as a session manager at all. A plain text file of URLs, kept in a notes app or a repository, survives browser changes, vendor shutdowns and machine migrations without depending on anything. It captures less, since it has no per tab history and no automatic snapshot, and it demands manual upkeep. For a set of pages that changes once a month rather than once an hour, that upkeep is close to zero and the durability is absolute.

The lifespan problem specific to extensions

An extension is not a durable purchase, and the last two years proved it at scale. Chrome finished removing the old extension platform from its store, and the documentation states the outcome without ambiguity:

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

That deadline passed on 31 August 2026, which produces a useful shortcut. Anything still listed in the Chrome Web Store today has been migrated, so the old test of reading a manifest version is no longer necessary. Presence in the store is now the evidence.

What still varies is maintenance. Session Buddy shows a store version of 4.1.2 dated April 2026 against roughly a million users. Tab Session Manager shows 7.4.0 dated July 2026 against roughly a hundred thousand. The Workona tab manager extension shows 3.1.33 dated January 2025 against roughly two hundred thousand. A store listing that has not moved in over a year is not automatically abandoned, but it is the single most useful signal available before installing.

What a session manager does not fix

Restoring tabs is a recovery feature. It answers the question of how to get back to where things were. It does not answer the question of why forty tabs accumulate in the first place, and those two problems feel identical from the inside while having different solutions.

Three specific frustrations survive every session manager on the market. The first is identity. A browser notification badge says only that something happened in the browser, not that it happened in the work Slack rather than the personal one, and a saved session does not change what the Dock icon can tell the reader.

The second is switching cost. Once a session is restored, all of it lands in one window as tabs, which is exactly the state that prompted the search. Finding the right tab among thirty is not made faster by having a good way to reopen those thirty.

The third is memory, and it is worth being precise rather than dramatic about it. Chromium documents the overhead of the security architecture that gives each site its own process:

On desktop in Chrome 67, this is about 10-13% when isolating all sites with many tabs open. Source: chromium.org

That is the cost of a design decision, not of bad software, and reopening a saved set of forty tabs pays it forty times over.

Deciding what to actually install

Three questions settle it. If the goal is recovering from crashes and restarts, the startup setting already in the browser covers it, and no install is needed. If the goal is switching between several named sets of pages for different projects, a session manager is the right category, and the choice comes down to local storage versus a subscription with sync. If the goal is keeping two accounts on the same service usable at once, no session manager helps, because that state lives in the profile.

The third case is where most of the daily friction sits for anyone running Gmail, Slack, a project tracker and a document editor at the same time. Giving each of those its own window rather than its own tab changes what the Dock and the app switcher can tell the reader, which is the idea behind Workspaces, and whether the specific services in daily use are covered is answered by the list of supported apps.

What to change first

Open the browser startup setting and confirm it is restoring the last session, since that removes the crash problem at zero cost. Then spend one working day counting how often the action is reopening a closed set of pages versus hunting for a window that was already open. If the second number is larger, the fix belongs at the window level rather than the tab level, and that is the problem SpaceDeck is built around.