Edge tabs keep multiplying: the tools already built in

Edge accumulates tabs faster than most browsers for a structural reason: it puts more things in tabs. A document opened from a link, a PDF, a search result, an item from Collections, a page pushed from a sidebar tool. Each of those lands in the same horizontal strip, and by mid afternoon the titles have collapsed into favicons. Edge also ships more built-in machinery for this than any other mainstream browser, and most of it is switched off or hidden by default. Knowing which of the five features answers which part of the problem is more useful than another round of closing tabs.

Five features, five different problems

Sleeping tabs handles resource cost. Vertical tabs handles legibility. Tab groups handles grouping within a window. Collections handles material you want to keep. Workspaces handles returning to a project days later. They overlap far less than the marketing suggests, and turning all of them on at once tends to produce a browser that feels busier rather than calmer.

The question worth asking before touching any of them is which symptom is actually annoying. A laptop with the fan spinning is a resource problem. Being unable to find the tab you want is a legibility problem. Losing an entire afternoon of research when the window closes is a persistence problem. The three have separate answers.

Sleeping tabs, and the ten things that stop it working

This is the feature that runs without being configured, and the one most people have never opened the settings for.

Sleeping tabs puts background tabs to sleep after two hours of inactivity to free up resources for active tabs, new tabs, and other applications on your device. Source: support.microsoft.com

Two hours is the default, and it is adjustable. The path is Settings and more, then Settings, then System and performance, then Performance, where Automatically put tabs to sleep can be confirmed as on and the interval chosen from a list. Sleeping tabs fade in the strip to show they have released resources, and clicking one wakes it immediately.

The part that explains most complaints is the exclusion list. Microsoft publishes the activities that stop a page from sleeping: the page is currently visible, it shares a browsing instance with another page, it is an internal company site, it is currently being inspected by DevTools, it is playing audio, it is capturing a window or screen, it is capturing user media such as a webcam or microphone, it is being mirrored or cast, it is on the user's block list in Settings, or it is using WebUSB. A window full of chat and video tools will therefore keep almost all of its tabs awake, correctly, because putting a call to sleep would break it.

The block list works in the other direction for sites that should never sleep. On the same Performance screen, Always keep these sites active takes a full URL, and entries can be edited or removed from the three dot menu next to each one. Fade inactive tabs can also be switched off if the dimming is more distracting than useful.

Vertical tabs, and what legibility buys

The tab strip has a hard limit. Past roughly twenty tabs, titles disappear and only favicons remain, which is a problem because two documents from the same service share a favicon. Vertical tabs move the list to the side of the window, where a title has room to be a title.

The trade is horizontal space. On a laptop screen, a permanently expanded vertical list takes a noticeable bite out of the page area, and the panel can be collapsed to icons when that matters. The gain is that scanning becomes reading rather than guessing, and that closing the right tab stops being a small risk each time.

Legibility also changes behaviour in a way that is easy to miss. When titles are readable, duplicates become visible, and duplicates are a large share of an overloaded window. Three copies of the same document, opened from three different links across a morning, are invisible as favicons and obvious as titles.

Tab groups and Collections do different jobs

Tab groups keep related tabs adjacent inside one window, with a name and a colour, and collapse to a single labelled chip. This is a working memory tool. It survives as long as the window does, which makes it right for a task that spans a few hours and wrong for a project that spans a fortnight.

Collections is a saving tool rather than a grouping tool. Items are added deliberately and stay after the browser closes, with notes alongside them. The distinction matters because using tab groups as storage is one of the more common ways an afternoon of research disappears.

Workspaces was rebuilt, and the differences are worth reading

Edge Workspaces groups related tabs into a named workspace that can be reopened later with everything intact. The feature was rebuilt, and the newer version is not a superset of the older one. Microsoft publishes a direct comparison.

	Previous Workspaces	New Workspaces
Task support	Multiple tasks shared across groups	Multiple tasks for individual use
Sharing and collaboration	Supported	Not supported
Inviting others	You can invite others to join	You cannot invite others to join
Edge version	Requires version 114 or later	Requires version 144 or later
OneDrive storage	Requires sufficient storage	Not required
Locking tabs	Supported	Not supported
Sorting in the menu	Order of creation, custom sortable	Most recently used

Two lines in that table change how the feature can be used. Sharing, collaboration and joining are not supported in the new version, and tab locking is gone. Anyone who was using a shared workspace as a lightweight way to hand a set of links to a colleague needs a different mechanism for that.

The requirements are also specific. A desktop running Windows 10, Windows 11 or macOS, desktop only. Edge version 144 or later. Signed in with a Microsoft account or a Microsoft Entra account. Syncing needs Workspaces and Tab Groups turned on under Sync in Profile settings, which is where missing or stale workspaces usually trace back to.

To create one, open the Search tabs icon in the top left, choose Manage workspaces, then the New Workspace drop down, and pick either a workspace made from the current tabs or a blank one. Naming and theme are set at that point and can be edited later from the three dot menu next to the workspace.

A weekly pass that actually holds

Features stop the count from hurting. They do not stop it from climbing, because nothing in Edge closes a tab that a person might still want. A short recurring pass is what keeps the number stable, and it works better when the order is fixed rather than improvised.

Start with duplicates, since closing them loses nothing. Then take the pages that are genuinely finished: a booking confirmed, a form submitted, an article read. Then move anything that is really a task into whatever holds tasks, because a tab cannot carry a date and will keep sitting there until it becomes invisible. What remains after those three passes is either an application or an unfinished project, and only the second of those belongs in a workspace.

Fifteen minutes on a Friday covers a normal week. The reason to fix the order is that starting with the hard decisions means never reaching the easy ones, and a pass that ends in frustration does not get repeated.

Search tabs is the fastest way out of a full window

The control in the top left corner of the window, the one that leads to Manage workspaces, is primarily a tab search. Typing a few characters filters everything currently open by title and address, which turns finding a tab from a scanning problem into a typing problem.

It is worth using deliberately rather than as a rescue. Searching for the domain of a service that should only be open once will show every copy of it, and duplicates are the cheapest tabs to close because nothing is lost. In a window that has been open for a working week, duplicates are routinely a quarter of the total.

The other habit worth building is closing from the search results rather than the strip. Closing from the strip means aiming at a sliver, and a mis-click closes something that mattered, which is exactly the experience that teaches people not to close anything.

The same features have arrived elsewhere

Part of the reason Edge users kept Edge was the tab tooling, and that gap has narrowed. Chrome now ships vertical tabs as a standard feature, and it has a split view for putting two pages side by side in one window, reached on a Mac with Command+Option+N.

That changes the comparison rather than settling it. Sleeping tabs, Collections and Workspaces still behave differently from their Chrome counterparts, and profile handling differs too. But the argument for staying purely because the tab strip is better is weaker than it was a year ago, and anyone who moved to Edge for vertical tabs alone has a genuine choice again.

It also means the underlying limit is now the same in both. Both keep every tab and every session inside one profile, so both hit the identical wall the moment two accounts of one service need to be open at once.

Where the built-in tools stop

All five features operate inside one browser profile, and that boundary is where the remaining friction lives.

A profile holds one set of cookies. Two accounts of the same service cannot both be signed in inside it, no matter how the tabs are grouped, coloured or slept. A workspace containing a work mail tab and a personal mail tab will open both, and one of them will be signed out or will silently displace the other. The usual response is a second Edge profile, which works and costs a window switch and a separate set of extensions and settings each time.

The second boundary is the difference between a tab and an application. Mail, chat and calendar are open every day, hold a live session and carry notifications. Sleeping tabs correctly refuses to sleep most of them. Vertical tabs makes them easier to find but still puts them in the same list as a search result. A tool designed around this gives each service its own persistent window with its own session, which is a different shape from a tab list. That model is described in Workspaces, and the way it compares to browsers built for the same job is set out in Compared with Wavebox.

What to change first

Turn on vertical tabs for a week before changing anything else, because a readable list is what makes the other decisions obvious. Then check the Performance screen once: confirm the sleep interval and add the two or three sites that must never sleep. If the same set of services opens every morning regardless of what project is running, those are applications rather than tabs, and a browser that treats them that way is SpaceDeck, with the covered services listed in Supported apps.