Anyone who keeps thirty tabs open knows the moment the tab strip gives up and shows a row of identical favicons with no titles. After a long run behind experimental flags, vertical tabs are now a standard option in Chrome.
How to turn it on
- Right-click an empty part of the tab strip, or the area beside it.
- Choose Show tabs vertically.
- Tabs move into a column down the side of the window, each showing its full page title.
The setting persists until you pick Show tabs horizontally. Tab groups still work, tabs still drag between windows, and the column can be collapsed to icons when you want the width back.
Why the horizontal strip fails, in numbers
This is worth doing properly, because it explains why the fix is not "make tabs smaller".
A horizontal tab strip divides a fixed width among a growing number of tabs. On a 1920-pixel-wide window, after window controls and the new-tab button, roughly 1,700 pixels are available. Chrome gives a tab about 240 pixels when there is room, and shrinks it as tabs multiply. Around nine or ten tabs each one drops near 170 pixels, which holds perhaps twenty characters — enough for "Gmail" and not for distinguishing two documents whose titles differ at the end. Past roughly twenty tabs each is near the minimum width, which is the favicon and nothing else.
At that point the strip has stopped being a list and become a row of identical squares. No amount of further shrinking helps, because the information you need — which page is which — was in the text that got cut.
A vertical column inverts the constraint. Each tab gets the full width of the sidebar, typically 200 to 300 pixels, regardless of how many there are. Adding tabs makes the list longer, not each entry narrower, and a long list scrolls. The titles survive.
The trade is which axis you spend. Vertical tabs consume horizontal space, which is abundant on the 16:9 displays nearly every laptop ships with, and return vertical space, which is the scarce axis when you are reading a page that scrolls downward. On a short, wide screen that is a straightforwardly good exchange. On a tall or narrow display it is not, which is the one case where the old strip genuinely wins.
Chrome is very late
Worth saying plainly, because it shapes what to expect. Firefox users have had vertical tabs through the Tree Style Tab extension since 2007 — eighteen years of a feature Chrome shipped this year. Vivaldi built its identity on tab management. Microsoft Edge added vertical tabs in 2021 and Arc made them the default. Firefox shipped its own native version recently.
Chrome's implementation is consequently the plainest of the group. Edge's version supports nesting and a wider set of controls; Vivaldi's supports two-level stacks, tiling and per-tab hibernation; Tree Style Tab genuinely nests tabs by which page opened which, which is the feature power users miss most. Chrome gives you a readable list in a column. If the list is all you wanted, it is enough.
The lateness has a dull explanation. Chrome has an enormous user base and a team that is cautious about changing the shape of the window, so the feature spent years behind flags while Google measured whether it helped or confused people. That caution is also why it is opt-in: nothing changes unless you ask.
The argument against
Here is the case the enthusiastic coverage leaves out. Vertical tabs do not solve tab overload. They make it comfortable.
Thirty open tabs is usually not a workflow; it is a to-do list you are storing in the wrong place, a set of articles you intend to read, and several pages you have forgotten the reason for. The horizontal strip collapsing was an unpleasant but honest signal that you had too many. Remove the signal and the number quietly goes up — the common report from people who switch is that they settle at a tab count they would previously have found unmanageable.
Whether that is a problem depends on what the tabs are. For a developer with twelve documentation pages open against a task, more legible tabs are a real gain. For someone whose tabs are an anxiety backlog, a more comfortable container for the backlog is not obviously progress.
Two alternatives are worth trying first, and both are free. Tab search — the small arrow at the end of the strip, or Ctrl+Shift+A — lets you type a few letters of a title and jump straight to it, which solves the find-the-tab problem without changing the window at all. Tab groups collapse a set of related tabs to a single coloured label, which solves the too-many problem rather than displaying it better.
Reading Mode, briefly
The same release strips more aggressively in Chrome's Reading Mode: ads, notification prompts and interstitials are removed and the article text appears in a side panel. It is a late arrival too — Safari shipped Reader in 2010 and Firefox's Reader View followed — and it works on the same principle, extracting what the page identifies as article content and discarding the rest.
It fails on the pages built to defeat it: articles split across numbered pages, text rendered as images, and sites whose markup gives no clear signal where the article begins. Where it works, it works very well, and on a heavily monetised news page the difference is not subtle.
