b2KIT

Breadcrumb Designer

Create breadcrumb navigation patterns with separator styles, icons, and responsive truncation.

Tested tool guide Tested browser tools Checked August 16, 2026

What Breadcrumb Designer does and how it behaves

Breadcrumb Designer focuses on the compact path that shows where a page sits within a site hierarchy. Enter the trail's labels, choose how adjacent levels are separated, add icons where useful, and compare responsive truncation choices for narrower layouts. It helps answer component-level questions such as which levels should remain visible and whether separators read clearly. The common mistake is treating a breadcrumb as browsing history. Its items should represent hierarchical location, so a shortened mobile version still needs to communicate the current page's place in that hierarchy.

How the result is produced

1

Trail structure

Arrange breadcrumb items from the broadest retained level toward the current page, then compare labels, icons, and separators. Separator glyphs are visual boundaries rather than additional destinations. Keep the current item distinguishable from linked ancestors because it identifies the page being viewed, while the preceding items provide routes to higher levels of the hierarchy.

2

Responsive truncation

Responsive truncation shows how a long breadcrumb can be shortened as horizontal space decreases. Check which intermediate levels disappear, whether an omission indicator could be mistaken for a link, and whether the remaining labels still establish location. Truncation changes the displayed path rather than the site's underlying hierarchy, so assess the compact and full-width forms separately.

Good uses

  • Prototyping the Home > Catalog > Category > Product trail for an ecommerce product page.
  • Comparing slash, chevron, and icon separators for a documentation site's breadcrumb component.
  • Choosing which hierarchy levels remain visible in a mobile breadcrumb for deeply nested account settings.

Limits and checks

  • The designer cannot determine whether the proposed trail matches the site's actual information architecture.
  • A visually clear icon or separator may still be ambiguous to assistive technology unless the implemented component has appropriate semantics.
  • Responsive truncation can hide the very parent level users need, especially when several pages have similar names.

Common questions

Does a good-looking trail automatically satisfy breadcrumb accessibility guidance?

No. Visible separators and icons do not by themselves define the component's meaning. In an implemented page, the breadcrumb should be exposed as labeled navigation, and a linked current-page item should use aria-current="page". Confirm keyboard behavior, focus indication, accessible names, and screen-reader output in the finished interface; the design alone cannot prove those properties.

Should the breadcrumb show every hierarchy level on mobile?

No. Responsive truncation can remove intermediate labels when space is tight, but the remaining trail should still orient the user and preserve a clear current-page cue. There is no universal number of levels for every hierarchy. Compare compact variants using representative page names, nesting depths, and viewport widths before selecting a pattern.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools