docs/data/material/components/steppers/steppers.md
Steppers display progress through a sequence of logical and numbered steps. They may also be used for navigation. Steppers may display a transient feedback message after a step is saved.
{{"component": "@mui/internal-core-docs/ComponentLinkHeader"}}
:::info This component is no longer documented in the Material Design guidelines, but Material UI will continue to support it. :::
The Stepper component displays progress through a sequence of logical and numbered steps. It supports horizontal and vertical orientation for desktop and mobile viewports.
Steppers are implemented using a collection of related components:
import Stepper from '@mui/material/Stepper';
import Step from '@mui/material/Step';
import StepLabel from '@mui/material/StepLabel';
Horizontal steppers are ideal when the contents of one step depend on an earlier step.
Avoid using long step names in horizontal steppers.
A linear stepper allows the user to complete the steps in sequence.
The Stepper can be controlled by passing the current step index (zero-based) as the activeStep prop. Stepper orientation is set using the orientation prop.
This example also shows the use of an optional step by placing the optional prop on the second Step component. Note that it's up to you to manage when an optional step is skipped. Once you've determined this for a particular step you must set completed={false} to signify that even though the active step index has gone beyond the optional step, it's not actually complete.
{{"demo": "HorizontalLinearStepper.js"}}
Non-linear steppers allow the user to enter a multi-step flow at any point.
This example is similar to the regular horizontal stepper, except steps are no longer automatically set to disabled={true} based on the activeStep prop.
The use of the StepButton here demonstrates clickable step labels, as well as setting the completed
flag. However because steps can be accessed in a non-linear fashion, it's up to your own implementation to
determine when all steps are completed (or even if they need to be completed).
Actionable steps mean that they control the content update of a section. From an accessibility standpoint, this means that each StepButton requires an aria-controls attribute pointing at the content section element.
{{"demo": "HorizontalNonLinearStepper.js"}}
Labels can be placed below the step icon by setting the alternativeLabel prop on the Stepper component.
{{"demo": "HorizontalLinearAlternativeLabelStepper.js"}}
{{"demo": "HorizontalStepperWithError.js"}}
Here is an example of customizing the component. You can learn more about this in the overrides documentation page.
{{"demo": "CustomizedSteppers.js"}}
Vertical steppers are designed for narrow screen sizes. They are ideal for mobile. All the features of the horizontal stepper can be implemented.
{{"demo": "VerticalLinearStepper.js"}}
Use alternativeLabel prop on the vertical Stepper component to reverse the placement of the label and content.
{{"demo": "VerticalLinearAlternativeLabelStepper.js"}}
StepContent uses Collapse by default.
Use slots.transition and slotProps.transition to replace it with another transition or to pass transition props.
The content of a step is unmounted when closed. If you need to make the content available to search engines or render expensive component trees inside your modal while optimizing for interaction responsiveness it might be a good idea to keep the step mounted with:
<StepContent slotProps={{ transition: { unmountOnExit: false } }} />
This component implements a compact stepper suitable for a mobile device. It has more limited functionality than the vertical stepper. See mobile steps for its inspiration.
The mobile stepper supports three variants to display progress through the available steps: text, dots, and progress.
The current step and total number of steps are displayed as text.
{{"demo": "TextMobileStepper.js", "bg": true}}
Use dots when the number of steps is small.
{{"demo": "DotsMobileStepper.js", "bg": true}}
Use a progress bar when there are many steps, or if there are steps that need to be inserted during the process (based on responses to earlier steps).
{{"demo": "ProgressMobileStepper.js", "bg": true}}