Design Core C · Industry convention

Variant

A Variant is an approved version of one component for a different size, strength, or setting.

See how it works
You might call it style variantcomponent option

See how it works

Original worked exampleVariant

Another example

One Button component has three variants: primary, secondary, and destructive. It doesn't need three separate components.

Main parts

  1. 01Foundation or token
  2. 02Applied component
  3. 03Visible state and rule

Use it when

Use one when the component structure stays the same but its look or meaning changes.

Do not use it when

Never use variants to pack unrelated actions into a confusing set of props.

Name used in code

variant="primary"

Before you ship

Check content order, shared design values, component consistency, contrast, zoom, and layout changes by screen size. Verify every theme, language, and state. If there is motion, offer an equal reduced-motion experience.

Request you can copy

Outcome: Use or define Variant to make the visual experience clear and easy to use. User context: One Button component has three variants: primary, secondary, and destructive. It doesn't need three separate components. Design concept to apply: Variant. Why it fits: Use one when the component structure stays the same but its look or meaning changes. Do not use it when: Never use variants to pack unrelated actions into a confusing set of props. Design requirements: Set the content order, shared design values, and reusable components. Define how the layout changes by screen size and state. Keep useful design choices separate from decoration. Inclusion and resilience: Check contrast, zoom, languages, themes, and reduced motion when needed. Do not use color or effects as the only way to show meaning. Acceptance criteria: The design stays clear on phones and desktops, at zoom, in every theme, and in all supported languages. Interactive states stay clear and consistent. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Brand limits, amount of content, supported themes and languages, target devices, and design-system rules.

Check this request

Review the current use of Variant. Definition: A Variant is an approved version of one component for a different size, strength, or setting. Release checks: Check content order, shared design values, component consistency, contrast, zoom, and layout changes by screen size. Verify every theme, language, and state. If there is motion, offer an equal reduced-motion experience. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.

C
How official is this term?

Industry convention

People often use this term at work. The listed sources may support practice or limitations. They do not define every part of the term.

No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks.

Scope
Design systems
Document status
stable
Checked on
2026-07-30

Evidence sources & scope

Authority source · Google · stable Material Design Components Scope: Material component vocabulary Role here: Helpful background, not a definition Source covers: canonical name, definition, interaction, keyboard behavior, accessibility

Copy it yourself

The browser could not copy this. Select the request below and copy it yourself.