Skip to main content Home About the Design SystemRoadmap OverviewDesignersDevelopers OverviewColorGridIconographyInteractionsSpacingTypography Overview Global colorBox shadowTypographyBorderOpacitySpaceLengthIconBreakpointsMedia queries All elements Accordion Alert Announcement Audio player Avatar Back to top Badge Blockquote Breadcrumb Button group Button Card Chip Code block Call to action Dialog Disclosure Footer Health index Icon Jump links Menu dropdown Navigation link Navigation (primary) Navigation (secondary) Navigation (vertical) Pagination PopoverPlanned Progress stepper Scheme toggle Site status Skeleton Skip link Spinner Statistic Subnavigation Surface Switch Table Tabs Tag Tile Timestamp Tooltip Video embed OverviewColor PalettesCustomizingDevelopers All PatternsAccordionCall to ActionCardFilterFormLink with iconLogo wallSearch barSticky bannerSticky cardTabsTagTile All Personalization PatternsAnnouncement FundamentalsAccessibility toolsAssistive technologiesCI/CDContentContributorsDesignDevelopmentManual testingResourcesScreen readers Design/code status Release notes Get support

Button group

OverviewStyleGuidelinesCodeAccessibilityDemos
UsageWriting contentLayoutBest practicesUsageWriting contentLayoutBest practices

Usage

Use a button group to arrange each button as a separate element with a gap between them. On small screens, buttons are arranged vertically.

Number of buttons

To reduce cognitive load and avoid visual clutter, use three buttons maximum.

Examples of button group usage showing correct and incorrect number of buttons.

Writing content

For help with writing button content and character count guidance, go to the Writing content section on the Buttons page.

Layout

Placement

Button groups can be placed in dialogs, forms, wizards, and more. Button groups in these elements should always be aligned left.

Hierarchy

It is important to establish visual hierarchy between buttons in your designs. Buttons in groups are most often ordered from left to right with the primary action on the left.

Diagram showing button hierarchy in groups.

When it comes to wizards and other similar elements, the primary action is the Next button in the middle of the group.

Example of a button group in a wizard.

Best practices

Too many buttons

A group with three buttons.

Use three buttons max per group.

A group with six buttons, which is too many.

Do not use more than three buttons in a group.

Too many variants

A button group with one primary button and two secondary buttons.

Use one primary variant only mixed with other variants.

A button group with two primary buttons, which is incorrect.

Do not use more than one primary variant in a button group.

© 2025 Red Hat Deploys by Netlify