Breadcrumbs & Back
Show users where they are in a hierarchy and get them back to exactly where they came from — filters, scroll and all.
5 states5 edge casesDesktop + Mobile
01The problem
Users arrive at deep pages from many places — a search result, a notification, a filtered list, a link in chat. A breadcrumb tells them where the page sits in the product. But “up one level” and “back to where I was” are different destinations, and products that treat them as the same lose the user's filtered list and scroll position.
02When to use
Use when
- Hierarchies three or more levels deep: Workspace › Project › Folder › Document
- Detail pages reached from filtered or searched lists
- Pages users land on from external links and notifications
Avoid when
- Flat products where every page is one level below the sidebar.
- Linear flows — use a stepper.
03Recommended UX
Statecraft recommendation
Use breadcrumbs for location (up the hierarchy) and a separate back link for history (return to the exact list the user came from, with filters and scroll restored).
04Desktop behaviour
On desktop, breadcrumbs sit above the page title; a contextual back link and previous/next controls appear when the user came from a list.
Desktop rules
- Breadcrumb: every ancestor is a link; the current page is plain text and the last item.
- Collapse middle levels into “…” when the trail exceeds 4 items; keep first and last two.
- Back link names its destination: “← Overdue invoices (42)”.
- Previous / Next with position (“3 of 42”) for working through a list.
05Mobile behaviour
There's no room for a full trail on mobile. A single back control in the header carries most of the weight.
Mobile rules
3 mobile rules are included in Pro.
Statecraft Pro
Unlock the full pattern
Get the complete interaction flow, states, edge cases, mobile rules and implementation prompt.
- Interaction flow · 5 steps
- 3 mobile rules
- 5 states
- 5 edge cases with recommendations
- 3 microcopy comparisons
- Accessibility notes
- Developer notes
- Claude Code / Codex implementation prompt
Edge cases covered in this pattern
- Record no longer matches the list
- Object moved
- Ancestor without permission
- Back button after many edits
- Opened in a new tab