Primary

Primary buttons are used highlight the strongest call to action on a page and are visually most prominent. They are most effective when they appear only once. Not every screen requires a primary button.

Normal

The default button size for primary buttons, it is used whenever a call to action is required in the design.

See all states usage

Small

Small primary buttons can be used when the call to action does not have to appear prominently in the design.

See all states usage

Secondary

Secondary buttons are less prominent calls to action, and are usually there to support the primary button. It gives the user an alternative option, and therefore ensures there is flexibility in the design.

Normal

The default button size for secondary buttons; it is used whenever an alternative call to action is required in the design.

See all states usage

Small

Small secondary buttons can be used when the call to action does not have to appear prominently in the design.

See all states usage

Tertiary

Tertiary buttons are the third options for button styles and are often used for less consequential actions on the page like 'Close'.

Normal

The default button size for tertiary buttons, it is used whenever a minor call to action is required in the design.

See all states usage

Small

Small tertiary buttons can be used when the call to action does not have to appear prominently in the design.

See all states usage

Button with icon

Buttons with icons help visually indicate the action to be taken, in addition to its label.

Icon before

Buttons where the icon appears in front of the label.

See all states usage

Icon after

Buttons where the icon appears after the label.

See all states usage

Ghost button

Buttons with icons help visually indicate the action to be taken, in addition to its label.

See all states usage

Small

Buttons where the icon appears after the label.

See all states usage

Anatomy

Buttons are fundamental elements in user interfaces, serving as interactive components that facilitate user actions and engagement.

Button anatomy

Buttons typically have a label and can include an icon before or after the label.

  1. Label:

    Text describing the button action. Use action verbs or phrases to tell the user what will happen next, and follow the button label content guidelines.

  2. Button:

    The selectable area of the button.

  3. Icon (optional):

    Most buttons don’t need an icon. Use an icon to add additional affordance where the icon has a clear and well-established meaning.

Types of buttons states

Buttons can have different states depending on their use case and the actions they inspire

Primary

Most prominent and visually emphasized button.

Default

Button states

Hover

Button states

Pressed

Button states

Disabled

Button states
  • Primary actions, such as submitting a form, completing a purchase, or initiating a critical user journey.
  • Limited to one or a few primary buttons on a page to maintain focus.
Secondary

Important but less visually prominent button

Default

Button states

Hover

Button states

Pressed

Button states

Disabled

Button states
  • Less visually dominant than the primary button. It is used to represent actions that are important but not as critical.
  • Secondary actions, like canceling an operation, navigating to less critical sections, or providing alternative options.
Tertiary

Least consequential and visually subtlest button

Default

Button states

Hover

Button states

Pressed

Button states

Disabled

Button states
  • Less visually dominant than the secondary button. It is used to represent actions that are not very important in the design.
  • Tertiary actions include closing a window or cancelling an action
Link

Text button that indicates clicking will lead to an external source or a different area within the product

Default

Button states

Hover

Button states

Pressed

Button states

Disabled

Button states
  • While typical buttons are actions, links are redirections
Content guidelines

Some basic guidelines to ensure your button usage is coherent and does not break the flow of the design

Use sentence case capitalization

Only capitalize the first letter of the button and any proper nouns. Most feature names aren't capitalized or considered proper nouns when following our capitalization guidance.

Do
Button states

Keep your button labels clear and concise to help the user better identify the action. The label should aptly describe the outcome of clicking it.

Don't
Button states

Avoid having too many buttons in a single page. Upto one primary button, and four to five secondary buttons can be considered for the product.

Do
Button states

Align buttons to text and form fields on the right side to establish a visual flow for the user.

Don't
Button states

Don't scatter buttons around the design. Logically grouping your buttons together can help reduce the cognitive load on your users.