Overview
Use Toolbar to keep actions close to the content or selection they affect while preserving a stable reading and keyboard order.
Project actions
Change the selection state and open the overflow actions in this live preview.
Anatomy
Toolbar combines optional selection, context, primary actions, supporting status, and secondary overflow in one horizontal region.
- 1Leading control
Selects the current scope or identifies the action context.
- 2Context title
Names the collection, object, or mode affected by the actions.
- 3Primary actions
Keeps the most frequent and important actions immediately available.
- 4Overflow
Discloses lower-frequency actions without crowding the toolbar.
- 5Supporting status
Communicates selection, result, or synchronization context.
When to use
Use Toolbar when several actions share a clear object, selection, or collection scope.
Recommended
- Act on a collection or selection
Place above DataTable, List, or content workspaces where actions affect the current scope.
- Keep repeated actions stable
Give frequent actions a predictable location across states and screen sizes.
- Separate primary and secondary actions
Keep high-value actions visible and move occasional actions into overflow.
When not to use
Prefer focused controls when there is no shared action scope or only one obvious action.
Avoid
- Do not replace page navigation
Use Navbar, Tabs, or Breadcrumb for destinations and hierarchy.
- Do not wrap form submission
Place form actions near their fields or in the form footer.
- Do not collect unrelated actions
Every control should affect the same object, selection, or workspace.
Variants
Surface and density variants adapt Toolbar to page, panel, and floating workspace contexts.
Plain
Blends into a page or panel that already provides containment.
Bordered
Defines the action region on open or mixed surfaces.
Raised
Keeps actions prominent above scrolling or layered content.
Sizes
Small, medium, and large tune density without changing semantics.
States
Toolbar preserves context while individual controls communicate their own availability and progress.
| State | Trigger | Visual response | Interaction |
|---|---|---|---|
| Default | No transient operation | Context and available actions | Tab or arrow keys reach controls |
| Selection | One or more objects selected | Count and bulk actions appear | Actions apply to the stated scope |
| Overflow open | More actions activated | Secondary action group is disclosed | Escape closes and restores focus |
| Loading | Actions are updating | Progress status appears | Existing context stays visible |
| Disabled action | Action is unavailable | Individual control loses emphasis | Disabled control cannot activate |
| Wrapped | Horizontal space is limited | Actions continue on a new line | Reading order remains logical |
Behavior
Toolbar manages grouping, overflow disclosure, and toolbar-level keyboard movement while composed controls retain their native behavior.
Keyboard movement
Left and Right arrows move between visible toolbar controls; Home and End jump to boundaries.
Overflow
Secondary actions open from a named trigger and close with Escape.
Wrapping
Controls wrap in DOM order instead of shrinking below usable sizes.
RTL
Arrow direction follows the document writing direction.
Accessibility
Toolbar provides a named toolbar region, native controls, predictable focus order, and status announcements.
| Key | Action |
|---|---|
| Tab | Moves into or out of the toolbar and through disclosed overflow controls. |
| ←→ | Moves between visible toolbar controls and wraps at the ends. |
| HomeEnd | Moves to the first or last visible toolbar control. |
| EnterSpace | Activates the focused control using its native behavior. |
| Esc | Closes overflow and restores focus to More actions. |
- Give every toolbar a concise accessible label.
- Use native buttons, links, inputs, and selects inside the toolbar.
- Give every icon-only action an aria-label.
- Keep DOM order aligned with visual and responsive order.
- Disable individual actions rather than the whole region.
- Announce loading or selection feedback without replacing context.
Content guidelines
Action labels should be concise, specific, and understandable within the toolbar’s stated scope.
Name the scope
Use a short object or collection title.
Migration projects
Use verb-first actions
Describe the result of activating the control.
Assign owner
Quantify selections
State the current bulk-action scope.
3 selected
Keep overflow neutral
Use a familiar accessible label for secondary actions.
More project actions
Examples
Toolbar supports controlled overflow when applications need to coordinate disclosure with other workspace state.
Selection toolbar
The same project action composition shown in a contained enterprise surface.
Props / API
Toolbar extends div attributes and composes application-owned native or design-system controls through named slots.
Props