ComparisonsGitHubX

Breadcrumb

<nav aria-label="breadcrumb"></nav>

A breadcrumb is a horizontal trail of links from the current page back toward the site root. Each segment represents a level in the hierarchy — home, category, subcategory, and finally the current page, which is shown as plain text rather than a link.

The pattern is wayfinding: it answers “where am I?” and offers one-click jumps to ancestor pages. It does not replace primary navigation; it supplements it on deep or nested routes.

Also known as

  • Breadcrumb trail
  • Breadcrumb navigation
  • Hierarchy path

Component Anatomy

PartRole
RootLandmark nav labeled for breadcrumbs
ListOrdered list of segments — reflects hierarchy left to right
ItemWrapper for one segment and its following separator
LinkClickable ancestor — navigates to that level
PageCurrent location — not a link; marked as the active page
SeparatorVisual divider between segments (chevron, slash, etc.)
EllipsisCollapsed middle segments when the trail is too long

Common use cases

Use a breadcrumb when users land on nested pages and may need to climb back up the tree:

  • Docs and reference sites — section → subsection → article
  • E-commerce — department → category → product
  • Settings or admin — org → workspace → resource
  • Deep app routes — dashboards with several levels of drill-down
  • SEO and sharing — reinforces page hierarchy in the UI (and in structured data when mirrored in markup)

Avoid a breadcrumb when the site is flat (only one or two levels — top nav is enough), when users rarely arrive mid-hierarchy (e.g. everything is reached from a single hub), or when primary navigation already shows location clearly (tabs, sidebar with active state). Do not use breadcrumbs as the only way to move between major sections.

Full trail shows every ancestor (good for shallow trees). Collapsed trail hides middle segments with an ellipsis (good for deep paths). The last segment is always the current page and should match the page title when possible.

<Breadcrumb />