A horizontal tab strip is a decision nobody made

Every mainstream browser arranges tabs in a single row across the top, and the arrangement has survived two decades of screens changing shape in the opposite direction. A tab strip running left to right consumes the dimension that is scarce and ignores the one that is plentiful. Twenty tabs in a row means every tab is a sliver of an icon and two characters, so the mechanism people use to remember what they have open stops working exactly at the point where remembering matters most.

Zen Browser puts the strip on the side, and this is not a cosmetic preference. A vertical list uses height, and height is what a modern display has in surplus; a list is also a shape in which names stay readable as the list grows, which a row is not. The panel can collapse to give the width back when a page needs it, and the whole argument is settled in about an hour of use: either the vertical arrangement is obviously better for the way one works, or it obviously is not, and there is very little middle ground.

Workspaces are the part that is not just layout

Once tabs live in a list, they can be grouped, and grouping them by what they are for - rather than by when they were opened - changes the way a browser is used. A workspace for the project being worked on. A workspace for the reading that accumulates in the background. A workspace for the two sites that are checked every morning. Switching between them is a single action, and the effect is closer to swapping desks than to closing windows: the unrelated context disappears from view without being destroyed, and comes back intact.

Splitting the window works alongside that idea rather than replacing it. Two pages side by side, resizable, in one window with one address bar: this is the arrangement a person actually needs when comparing a document with its source, or watching something change while reading about it. The alternative - two windows, dragged into position, losing their geometry the next time anything is maximised - is a workaround that people perform dozens of times a day without noticing they are performing it.

Quiet, in the specific sense

The browser is built on a mature open source engine rather than on a new one, which is the sensible choice for a project whose value is in the shell rather than the rendering. On top of that shell sit the things that reduce interruption: advertising and tracking scripts blocked by default rather than after a settings tour, a compact mode that hides the toolbars so the page gets the space, and a preview that shows the contents of a link when the pointer rests on it, so that a doubtful link can be judged without being followed. Behavioural collection is off by default and the data that exists stays on the machine, which is stated as a design position rather than as a certification.

The performance claim, read carefully

Browsers make their speed claims in a way that rewards scepticism, and this one is no exception. The claims here are comparative and they are about cold start and memory pressure relative to mainstream browsers, on the same engine family, with an emphasis on older hardware. What is true and durable is narrower: a shell with fewer default services running, a smaller installation, and fewer background processes doing things nobody asked for will feel lighter on a machine that was already struggling. What is not guaranteed is that any given page will render faster, because the renderer is not the part that was changed.

That distinction matters when choosing. If the machine is old, or the memory is small, the difference is real and noticeable. If the machine is new, the difference is a preference about how much of the computer should be idle, which is a legitimate preference and a different argument.

What it costs to switch

Three costs are honest to state. The vertical arrangement has a learning period, and the first day feels wrong in a way that the first day of any layout change always does. Extension compatibility follows the engine, which means the store is not the one most people are used to and a few extensions will be missing or behave differently. And a browser built by a smaller project than the ones it competes with carries a support risk that is worth naming: the question is not whether it works today, which it does, but whether it will still be maintained in three years, which nobody can promise.

For a person who keeps dozens of tabs open and has stopped being able to find anything among them, the trade is straightforward: an unfamiliar layout in exchange for a list that stays legible. For a person who keeps four tabs and closes them, none of this solves a problem they have, and the default browser is fine. Both answers are correct, and knowing which person one is takes about an hour of trying.