Browser vertical tabs: what the sidebar fixes

A horizontal tab strip stops being readable long before it runs out of room. Somewhere around fifteen tabs the titles shrink to three or four characters. Past twenty five, only favicons remain, and two Google Docs tabs become indistinguishable. Browser vertical tabs move that strip to the side of the window, where each title gets the full width of a column and the list scrolls the way every other list on the machine scrolls.

The feature is no longer niche. Chrome ships it, Firefox ships it, Edge ships it and lets administrators switch it off by policy. That makes the interesting question narrower than it used to be. Not whether vertical tabs are available, but which part of a crowded window they actually repair, and which part they leave exactly as it was.

What moving the strip actually changes

A horizontal strip has a fixed total width and divides it by the number of open tabs. Every new tab makes every existing tab narrower. The layout is a subtraction problem, and the thing being subtracted is the only part that carries meaning: the text. A vertical strip inverts the constraint. Each tab gets a fixed height and the full column width, and the list grows downward past the bottom edge, where scrolling handles the overflow.

Chrome describes the change in exactly those terms.

Vertical tabs move your tab strip to the side of your window. You can: Find all page titles, Scroll through list of tabs, Resize the width of tab strip to fit your needs Source: support.google.com

Three practical consequences follow. Titles survive at counts where they used to vanish, so identifying a tab becomes reading rather than guessing. Position becomes stable and meaningful, because a list that scrolls does not reshuffle widths every time something opens. And tab group names, which are truncated to a colored dot in a crowded horizontal strip, stay spelled out.

There is a fourth effect that matters more than people expect. In a horizontal strip, tabs beyond the visible range are effectively hidden, which is why tab search exists as a separate feature. In a vertical strip they are one scroll away and still in order. The mental model shifts from searching a pile to walking a list.

Turning it on in each browser

The switch lives in a different place in each browser, and in Safari it does not exist at all.

Browser	Where the setting is	Notes
Chrome	Right click blank space on the tab strip, choose Show Tabs Vertically. Also under Settings, Appearance, Tab position	The Mac View menu carries the same item
Firefox	Right click the toolbar near the top, choose Turn on Vertical Tabs. Also Customize sidebar, Vertical tabs	Arrived in Firefox 136, inside the sidebar
Edge	The tab actions button at the top left of the tab strip	Availability is governed by the VerticalTabsAllowed policy
Safari	Not available	The sidebar shows Tab Groups, not a vertical tab strip

Firefox tied the feature to its redesigned sidebar rather than treating it as a standalone toggle, which is worth knowing before hunting for a checkbox in the wrong panel.

With vertical tabs, your open and pinned tabs appear in the sidebar instead of along the top of the browser. To turn on vertical tabs, right-click on the toolbar near the top of the browser and select Turn on Vertical Tabs. Source: firefox.com

Edge is the one case where the option can be missing on a managed Mac rather than misplaced. Microsoft publishes a policy named VerticalTabsAllowed, described as configuring availability of a vertical layout for tabs on the side of the browser, in its Edge policy reference. On a work device where the item never appears, the setting is the likely reason, and no amount of menu hunting will surface it.

The column has a price, and it is horizontal

A vertical strip converts a problem of text width into a problem of content width. On a 27 inch display that trade is close to free. On a 13 inch MacBook it is a real decision, because the column sits next to pages that were designed on wide monitors and that respond to a narrower viewport by collapsing navigation, hiding sidebars, or triggering a mobile layout.

Two habits soften this. The first is resizing the strip deliberately rather than accepting the default: a narrow column that still fits twenty characters is usually enough to distinguish tabs, and twenty characters is far more than a crowded horizontal strip ever gives. The second is collapsing the strip when the current task needs the full page, then expanding it when navigating again. Both browsers that support the layout keep the collapsed state per window, so a reading window and a working window can differ.

There is also a smaller cost that shows up in the first hour. Every reflex built around a horizontal strip points the wrong way. Reaching for the close button lands in the wrong corner, and the muscle memory for grabbing the third tab from the left has to be rebuilt as third from the top. Keyboard shortcuts are unaffected, which is the argument for leaning on them during the adjustment: Command with a number still jumps to a position, and tab search still opens with Command, Shift and A.

Pinned tabs change shape too

Pinning is the one existing habit that behaves differently after the switch, and it is worth revisiting on day one. In a horizontal strip, a pinned tab shrinks to a favicon and parks at the far left, which works well for four or five icons that are recognizable at a glance and badly for anything more. Two chat tools with similar logos become a coin flip.

In a column the pinned section sits at the top of the sidebar and Firefox keeps pinned tabs there alongside the open ones. That opens a use that was previously impractical: pinning by name rather than by icon, which means the always on tools can be twelve items instead of five and still be readable. A useful arrangement is to pin everything that is open every day, in the same order every day, so the top of the list becomes a fixed launch bar and everything below it is genuinely temporary. Position then carries information. Anything that has drifted below the pinned block for a week is either something to pin or something to close.

That arrangement also exposes the limit of the approach faster than any argument does. Once the pinned block holds a mail client, two chat tools, a task tracker, a calendar, and an AI assistant, the browser is no longer being used as a browser. It is being used as an application launcher whose applications happen to share one window, one profile, and one set of cookies. The tab strip was never designed for that job, which is why notifications from a pinned tool interrupt the page in front of them, and why a second account for any of those tools requires a whole second profile. A catalog of the services that people most often end up pinning, and how they behave when each one gets its own window, is kept in Supported apps.

What the sidebar does not fix

Layout changes what a tab looks like. It does not change what a tab is.

Memory behaves identically. A page that Chrome has deactivated in the background keeps its title and favicon in the strip whether that strip runs across the top or down the side, so a vertical list can look healthy while half of it has been unloaded and will reload on click. Session identity behaves identically too. Every tab in one window shares the cookies and logins of one profile, which is why a second work account still cannot sit beside the first without a separate profile or a browser designed around that separation.

The subtler point concerns the count itself. A vertical strip removes the pain signal without removing the cause. When titles disappear from a horizontal strip, that is a crude but effective prompt to close something. Make forty tabs legible and the prompt goes away, which is comfortable in week one and expensive by week four, when the list has quietly reached seventy and scrolling has replaced scanning. The layout raised the ceiling. It did not change the rate at which tabs accumulate.

Match the fix to the actual failure

Most people arrive at this feature carrying one of three complaints, and only one of them is a layout problem.

The complaint that vertical tabs solve outright is legibility. Ten to thirty tabs, all part of a single job, and the only real problem is telling them apart. The sidebar handles this completely and nothing else needs to change.

The second complaint is retrieval across contexts. The strip holds a client project, an internal dashboard, three reference pages, and the tools that run all day, and the difficulty is not reading a title but finding the right one among unrelated things. Vertical tabs make this legible without making it shorter. Tab groups are the closer match, since they name and collapse a context, and pinning keeps the always on tools anchored at the top instead of drifting.

The third complaint is that a single window holds several jobs and several identities at once. That is not a strip problem in any layout, and it is where a different shape of tool applies. A browser built around separate spaces gives each context its own window and its own session, so switching contexts changes the entire surface rather than scrolling within one list. The design and its trade offs are covered in Workspaces, and the pattern of giving each web app a dedicated place instead of a shared tab strip is described in Features.

Where vertical tabs and tab groups overlap

These two features are frequently presented as alternatives, which understates how well they combine. A tab group is a labeled, collapsible, persistent unit. A vertical strip is a place where that label has room to be read. In a horizontal strip a collapsed group is a colored dot with a few letters, so groups tend to be created and then forgotten. In a column, five named groups read like a table of contents, and expanding one is closer to opening a folder than to hunting through a strip.

The combination has a natural stopping point. Groups organize pages inside one browsing session, and they do nothing about the fact that everything in the window is signed in as the same person. Once the list is sorted by client or by employer rather than by topic, the boundary being drawn is an identity boundary, and no arrangement of the tab strip can enforce it. Tools built for that job are compared side by side in Compared with Wavebox.

What to change first

Turn vertical tabs on and use them for a week without changing anything else. If titles were the whole problem, the work is done and the sidebar is the answer. If the list is now legible but still exhausting to scroll, the problem was never the layout: it was the number of separate jobs living in one window, and the next move is to give each of those jobs its own window rather than its own row. SpaceDeck is built on that second answer.