Storybook Controls gives you a graphical UI to interact with a component's arguments dynamically, without needing to code. It creates an addon panel next to your component examples ("stories"), so you can edit them live.
Controls does not require any modification to your components. Stories for controls are:
To use the Controls addon, you need to write your stories using args. Storybook will automatically generate UI controls based on your args and what it can infer about your component; but you can configure the controls further using argTypes, see below.
If you have written stories in the older pre-Storybook 6 style, you may want to read the args & controls migration guide to help understand how to convert your stories for args.
By default, Storybook will choose a control for each arg based on the initial value of the arg. This works well with some kind of args, such as boolean values or free-text strings, but in other cases you want a more restricted control.
For instance, suppose you have a
backgroundColor arg on your story:
By default, Storybook will render a free text input for the
This works as long as you type a valid string into the auto-generated text control, but it's not the best UI for picking a color. Let’s replace it with Storybook’s color picker component.
We can specify which controls get used by declaring a custom argType for the
backgroundColor property. ArgTypes encode basic metadata for args, such as name, description, defaultValue for an arg. These get automatically filled in by Storybook Docs.
ArgTypes can also contain arbitrary annotations which can be overridden by the user. Since
backgroundColor is a property of the component, let's put that annotation on the default export.
This replaces the input with a color picker for a more intuitive developer experience.
Up until now, we only used auto-generated controls based on the component we're writing stories for. If we are writing complex stories we may want to add controls for args that aren’t part of the component.
By default, Storybook will add controls for all args that:
It infers from the component definition if your framework supports it.
Appear in the list of args for your story.
You can determine the control by using
argTypes in each case.
The Controls addon can be configured in two ways:
As shown above, you can configure individual controls with the “control" annotation in the argTypes field of either a component or story.
Here is the full list of available controls you can use:
|Data Type||Control Type||Description||Options|
|array||array||serialize array into a comma-separated string inside a textbox||separator|
|number||number||a numeric text box input||min, max, step|
|range||a range slider input||min, max, step|
|object||object||json editor text input||-|
|enum||radio||radio buttons input||options|
|inline-radio||inline radio buttons input||options|
|check||multi-select checkbox input||options|
|inline-check||multi-select inline checkbox input||options|
|select||select dropdown input||options|
|multi-select||multi-select dropdown input||options|
|string||text||simple text input||-|
|color||color picker input that assumes strings are color values||-|
|date||date picker input||-|
If you need to customize a control to use a enum data type in your story, for instance the
inline-radio you can do it like so:
If you need to customize a control for a number data type in your story, you can do it like so:
Controls supports the following configuration parameters, either globally or on a per-story basis:
Since Controls is built on the same engine as Storybook Docs, it can also show property documentation alongside your controls using the expanded parameter (defaults to false). This means you embed a complete ArgsTable doc block in the controls pane. The description and default value rendering can be customized in the same way as the doc block.
To enable expanded mode globally, add the following to
And here's what the resulting UI looks like:
If you don't plan to handle the control args inside your Story, you can remove the warning with: