ButtonGroup

Button groups keep related actions visually connected so compound controls read as one unit.

Basic Usage

Use a button group when several adjacent actions belong to the same workflow.

Regular buttons can sit at the start of a group when the first action gives context to the controls that follow.

Separators help signal a tighter relationship between controls, especially when a leading action anchors the group.

Split-button patterns keep the primary action obvious while still exposing closely related secondary options.

Button groups should scale cleanly with the shared button size system so they can fit toolbars and denser control areas.

Vertical orientation keeps related actions grouped when horizontal space is limited or the controls need to read more like a menu.

Button groups can combine buttons with adjacent fields and overlays when the control should still read as one compact action bar.

Dropdown triggers work well at the end of a group when the primary action remains visible but secondary actions need extra space.

Popover triggers work well when a grouped action needs lightweight supporting content instead of a menu.