Breadcrumbs

Breadcrumbs are a single-line trail of links from a root page down to the one being read, separated by a repeated glyph, showing where the current page sits in a hierarchy and giving one click back to every level above it. The last item is where you already are, so it is not a link. The trail describes structure, not the route somebody took to arrive: two different things that get confused because both look like a line of page names.

The separator is chosen once for a product and never changes at runtime, which is why this family ships seven of them rather than one: a slash reads as a path, a chevron as travel, a pair of stacked dots as nesting with no direction at all. Length is the other half of the problem. Past a certain depth a trail has to fold, and it folds in the middle, the root and the current page carry the meaning, and the steps between them are what you can afford to put behind an ellipsis.

21 blocks

Chevron

The default trail: docs, file browsers, nested settings

Right arrow head

Denser chrome, where the separator should sit closer to the crumb behind it

Forward slash

Paths and URLs, where the trail is a literal address

Dot

Quiet trails that sit under a page title and should not compete with it

Double dot

Trails that need a mark with no direction: a hierarchy read by nesting, not by travel

Arrow head

The same arrow with even spacing on both sides

More vertical

Toolbars where the separator should read as a rule rather than a glyph

Chevron, folded

Docs and file browsers whose trail can be longer than its room

Dot, under a title

Page headers where the trail must stay quiet and never change the header's height

More vertical, folded toolbar

Document toolbars with avatars and a Share action beside the trail

Chevron, opens

Docs sites and file explorers, where a level should be one pick away

Forward slash, switcher

Dev-tool headers: workspace, project and branch, each one switch away

Double dot, switcher

Help centres: move to another section or article without going back up

Arrow head, editor path

Code editors and file browsers: the bar is the fastest way between files

Double dot, peek

Trails where a level needs a hint before you leave the page

Right arrow head, path

A drive or file tree, where the trail is a path you can walk and copy

Right arrow head, glide

Settings and admin pages, where the trail should read like the segmented controls around it

Dot, sticky

Long articles and docs, where the header trail scrolls away

Arrow head, back

App headers and phones, where the way back matters most

More vertical, glide toolbar

Document toolbars with Preview and Share next to the trail

Forward slash, address

File and route paths, where people may want to type the address

01

Using Breadcrumbs

Reach for it when

  • Content sits more than two levels deep and people arrive mid-tree from search
  • A file or asset browser where each parent is a real place you can open
  • Settings panels nested under sections, where the page heading alone does not say which section owns them
  • You need a way back up that costs one line instead of a sidebar

Reach for something else when

  • A flat site with one level of sections: the trail only repeats the nav, so let the nav's own active state do it
  • A linear process like a checkout or an application: a step indicator shows progress and what remains, which ancestry cannot
  • The trail would be the only navigation on the page: breadcrumbs supplement a nav rather than replace one
02

Where it shows up

01

Documentation hierarchies

Docs are entered mostly from search, deep in a tree the reader never walked. The trail says which section they landed in and offers the parent page, which is often the overview they were actually looking for.

02

File and asset browsers

Folders are places, so the trail doubles as navigation: every crumb is a real listing, and the current folder's own control can offer its siblings without making anyone climb back up a level first.

03

Nested settings

Configuration pages bury a panel two or three levels under a section. A heading says what the panel is. Only the trail says which section owns it, and what else lives beside it at the same depth.

04

Category catalogues

A product page sits under a chain of categories that each list something real. The trail turns those into one-click listings, and it is also how a crawler learns the shape of the catalogue behind the page.

03

Questions

Should the current page be a link in a breadcrumb trail?

No. The last crumb is the page you are already on, so it should not be a link; mark it as the current item so assistive technology announces it that way. It can still carry an affordance of its own, such as a control listing sibling pages, but clicking the label itself ought to do nothing at all.

What should breadcrumbs do when the path is too long for one line?

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.