Skip to main content


Stories are the entrypoint to your components. They are simple modules that export your components and can add additional metadata to describe and parametrize them. You can create them anywhere in your project's src/ folder; they should be named as *.stories.jsx or *.stories.tsx. Ladle searches your project and loads all the stories into a single playground so you can develop and test them.

Ladle automatically creates sidebar navigation and routes based on the filenames and names of exported stories:


export const Button = () => <button>My Button</button>;
export const HeaderOne = () => <h1>Header</h1>;


export const Simple = () => (
<li>Item 1</li>
<li>Item 2</li>

Ladle creates three different routes and a tree navigation while following some simple naming conventions:

  • First letter is capitalized
  • CamelCase is split into spaces
  • - turns into a space
  • -- turns into a nested story

Story Tree Navigation

Name Customization

Sometimes it might be useful to ignore file/export names and set a custom name explicitly. A single story can be renamed as:

export const Button = () => <button>My Button</button>;
Button.storyName = "Renamed Button";

All story names and titles need to be string literals.

You can also replace the filename (level name) part:

export default {
title: "Level / Sub level",
export const Button = () => <button>My Button</button>;

/ can be used to create sublevels. This creates following navigation structure:

└─ Sub level
└─ Button


Ladle supports story decorators, so you can wrap all stories in a file with additional React component(s). This is useful if your stories/components rely on React Context and libraries like react-router or redux. In the example bellow , we are adding an extra margin: 3em to each story:

export default {
decorators: [
(Story: React.FC) => (
<div style={{ margin: "3em" }}>
<Story />

decorators is an array, so you can compose multiple components together. You can also set a global decorator or provider.

Controls, Args and ArgTypes

Stories can be parametrized. You can define the props that your component expects and then update them through the UI without changing the code or creating multiple additional stories with the same component. The example below covers all available args and argTypes that Ladle currently supports:

import type { Story } from "@ladle/react";

export const Controls: Story<{
label: string;
disabled: boolean;
count: number;
colors: string[];
variant: string;
size: string;
}> = ({ count, disabled, label, colors, variant, size }) => (
<p>Count: {count}</p>
<p>Disabled: {disabled ? "yes" : "no"}</p>
<p>Label: {label}</p>
<p>Colors: {colors.join(",")}</p>
<p>Variant: {variant}</p>
<p>Size: {size}</p>

Controls.args = {
label: "Hello world",
disabled: false,
count: 2,
colors: ["Red", "Blue"],
Controls.argTypes = {
variant: {
options: ["primary", "secondary"],
control: { type: "radio" },
defaultValue: "primary",
size: {
options: ["small", "medium", "big", "huuuuge"],
control: { type: "select" },

Ladle detects args / argTypes and provides the Control UI so you can update the component without touching the code. You can define primitive types through args and enums through argTypes:


You can also create multiple stories by assigning different default args / argTypes to the same component:

import type { Story } from "@ladle/react";

const Card: Story<{
label: string;
}> = ({ label }) => <p>Label: {label}</p>;

export const CardHello = Card.bind({});
CardHello.args = {
label: "Hello",

export const CardWorld = Card.bind({});
CardWorld.args = {
label: "World",


There are limitations in place to support features like the automatic code-splitting or meta file. Some parts of the stories' syntax must be static and serializable.

storyName, title and meta need to be serializable

export default {
title: "Welcome",
meta: {
key: "value",
export const Story = () => "Hey";
Story.storyName = "Renamed";

however, this does not work

export default {
title: "Welcome" + " Everybody",
meta: {
key: 1 + 2,
export const Story = () => "Hey";
const newName = "Renamed";
Story.storyName = newName;

Story names and files need to be unique

File names and named exports (or storyNames) are normalized and used together as a unique identifier for each story. There cannot be two stories with the same ID. If that occurs, Ladle tells you what stories and files are clashing and you need to rename something.

Do you want to work on Ladle and other web tooling? Our team at Uber is hiring!