Tab Menu

A tab menu is the set of destinations an app is made of, drawn as one repeated item: a glyph, a label, and a chosen state that is the only thing on screen saying where you are. This family draws that item four ways, a fixed sidebar rail, a header row underlined in brand ink, a row of labels with no glyphs at all, and the same row with its icons kept.

The name describes the shape, not the semantics. Where each item has an address of its own, these are links inside a navigation landmark, and the real work is marking the current one with something other than colour, since a filled pill or a bar survives a grayscale screenshot and a coloured word does not. Width is the other constraint. Destinations that do not fit are usually handled by letting the row scroll, which hides the tail of the nav behind a gesture nobody mentions; wrapping keeps every destination visible, and an underline then has to stay attached to the label it belongs to.

18 blocks

Dashboard nav

App sidebars: a rail of destinations where one row is always the page you are on

Dashboard nav, spine

A rail that should stay quiet on any surface: no fill, just a line and a mark

Dashboard nav, ink

A rail that carries a head and a foot, on the dark ink surface

Underline nav

Section switching in a page header: the chosen one named in brand, the rest folded into More

Underline nav, elastic

A header nav that sits on the page with no card and may wrap

Underline nav, peek

A header nav whose sections have something to preview

Subtle nav

Quiet switching: labels only, where an icon would be noise

Subtle nav, capsule

Quiet switching in the look of the segmented control

Subtle nav, headline

A page whose nav should also name it

Icon nav

Switching where the glyph carries as much as the word

Icon nav, expand

A tight toolbar of sections where only the current one needs its name

Icon nav, stack

A phone bottom bar, or any five-section strip

Pill nav

Four or five sections of one page, switched from a header

Pill nav, follow

Sections of one long page

Pill nav, more

More sections than a row can hold

Sidebar with groups, and the icon rail

App navigation that has to fold away for room

Sidebar, flyout

A rail that opens panels instead of widening

Sidebar, folded

A sidebar with many groups that must never hide news

01

Using Tab Menu

Reach for it when

  • An app with a small, stable set of destinations that does not change as the reader moves between them.
  • A fixed sidebar rail where every row wants a glyph and a label and the whole row should be the target.
  • A header row under a page title, where the chosen section should be named in brand ink rather than a weight change.
  • Switching where the labels are short and an icon would only add noise.

Reach for something else when

  • Destinations that nest three levels deep: collapsible sidebar groups or a tree view show a hierarchy that a flat row has to pretend is not there.
  • Facets of one record that stay on the same page. Those are tabs, and the difference is whether the address changes, not what the control looks like.
  • A destination list long enough to wrap twice: a command menu or a grouped dropdown handles the tail better than a nav that has become a paragraph.
02

Where it shows up

01

Dashboard sidebar

A fixed rail of destinations down the side of an application. Rows fill the rail's full width so the whole row is the target, and the glyph does the recognising while the label does the confirming.

02

Page section headers

A row sitting under a page title, moving between the areas of one section. The chosen item is named in brand ink with a bar beneath it, which is legible from further away than a weight change would be.

03

Workspace settings nav

Account, billing, members, integrations. Labels only, because glyphs for abstract areas are guesses the reader has to decode twice, and the words are short enough that the row still fits.

04

Icon-led switching

Places where the glyph carries as much as the word: media kinds, view modes, tool categories. The two together travel across languages better than an icon on its own, which has to be learned first.

03

Questions

Should tab menu items be links or buttons?

If each item is a destination with an address of its own, use links. Real anchors can be opened in a new tab, middle-clicked and copied, and a screen reader announces them as navigation. Reach for buttons with tab semantics only when the address does not change and content swaps in place. The visual treatment is identical either way; the underlying element is not.

How should the current destination be marked?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.