Guides· 8 min read

Design System Showcase Video: Record It Straight From Storybook

Use story URLs, args, play functions and the pseudo-states addon to film your components, then cut a 90-second video that gets them adopted.

By disha Sharma

ShareXLinkedIn
Design system showcase video cover: a Storybook shot list card with four steps (state links with args, play functions, frozen pseudo-states and a reduced-motion shot) for recording components

Most design systems already have a well-documented Storybook. Every component is isolated, every variant is listed, and the props tables are up to date. Outside the team that built it, almost nobody opens it unless they already know what they're looking for.

That's not a documentation problem. Storybook is a reference, and a reference answers questions people already have. An engineer who has hand-built the same dropdown for two years has no reason to go looking for a better one. "It's in Storybook" was never a rollout plan.

The short answer: a design-system showcase video is a 60-120 second clip that shows 4-6 new or changed components moving through their real states, then tells people exactly where to get them. The best place to record it is Storybook itself, because it already has everything you need:

  • Story URLs that open one component on a clean canvas, with no Storybook toolbar in shot.
  • Args in the URL, so every state you film can be reopened later with a link.
  • Play functions, which click and type through a component the same way on every take.
  • The pseudo-states addon, which holds hover, focus and active styles still, so you can film them without chasing a cursor.

Record from Storybook, cut to a script that opens with what's new, and end on the package name. Below are the shot list, the Storybook setup and a timing table for a 90-second cut.

Why "Just Check the Storybook" Doesn't Drive Adoption

A reference tool is built for lookup. It shows what exists, but not what changed, why it matters or which old pattern it replaces. That context is what gets someone to switch.

A showcase video does the opposite job. It interrupts people who weren't looking and gives them one reason to try the new thing. That's why it belongs in your release notes, your design-system channel and your new-hire onboarding, not inside Storybook.

The takeaway: keep Storybook as the exhaustive reference, and make the video the announcement that sends people to it.

Pick 4-6 Components, Not the Whole Library

Trying to film 80 components turns the video into a slower Storybook. Choose a handful that each prove one thing about the system:

Pick one that shows...ExampleWhat viewers should notice
What's new this releaseA new combobox or date pickerThe problem it removes from their week
A full state cycleA button going default, hover, focus, loading, disabledEvery state is already built
A complex pattern holding togetherA modal or a data tableSpacing and type stay consistent under load
ThemingThe same card in light and dark modeTokens, not one-off CSS
Responsive behaviorA nav collapsing at a phone widthIt works on small screens without extra code

If a component doesn't teach one of these, it can stay in Storybook. Five well-chosen components prove the system is coherent better than 50 quick flashes.

Use Storybook as Your Film Set

This is the part most teams skip, and it's what makes the video easy to update next release.

1. Record the canvas, not the Storybook UI. Storybook's "open canvas in new tab" button gives each story its own iframe.html URL, built from the story id and viewMode=story. That page shows the component alone, with no sidebar or addon panel to crop out.

2. Put each state in a link. Storybook lets you set a story's args in the URL with an args query parameter, written as key:value pairs separated by semicolons, for example args=size:large;disabled:true. Keys and values are limited to letters, numbers, spaces, underscores and dashes, and anything else is removed. So use args for sizes, variants and booleans, and use a dedicated story for states that need longer text.

3. Script interactions with play functions. A play function is a short piece of code that runs after the story renders and interacts with the component: typing into fields, clicking buttons, opening menus. Storybook's Interactions panel lets you pause, rewind and step through each action, and the step function groups actions under labels. For a video, that means the same click-through plays the same way on every take. Your shot list becomes code your team already reviews.

4. Freeze hover and focus. The storybook-addon-pseudo-states addon, maintained by Chromatic, lets you force :hover, :focus and :active styles through story parameters, such as parameters: { pseudo: { hover: true } }. You get a clean still of each state, which is ideal for a "here are all five states" frame.

5. Lock the viewport for responsive shots. Storybook's viewport feature can be set per story through globals, using built-in sizes such as mobile1 (320 x 568 px) or tablet (834 x 1112 px). A locked viewport can't be changed from the toolbar, so the framing stays the same on every take.

One rule ties these together: if you can't reopen a shot from a URL or a story, you'll have to film it again by hand next release.

A 90-Second Showcase Structure

At about 150 spoken words per minute (National Center for Voice and Speech), 90 seconds is roughly 225 words of narration. Here's one way to spend them:

SectionTimeWordsWhat's on screen
What's new0-10 sabout 25The new component, already in use
The problem it removes10-25 sabout 35The old hand-built version next to it
Components and states25-70 sabout 1103-5 components, each running its play function
Theming and responsive70-80 sabout 25Light/dark swap, then a phone width
Where to get it80-90 sabout 30Package name, install command, Storybook link

Open on what's new, not on "welcome to our design system". Viewers drop off fast. Wistia's data shows videos under a minute average a 52% engagement rate, meaning typical viewers watch about half (Wistia). Anything important belongs in the first half.

End on the exact place to switch: the package name, the version and the Storybook link. A generic "check it out" wastes the one moment the viewer is ready to act.

Show Motion, but Respect Reduced Motion

Motion is the one thing a props table can't show: how a loading state eases in, or how a modal enters and leaves. That's the strongest reason to make a video at all.

It's also a reason to film one extra shot. WCAG 2.1 success criterion 2.3.3 (Animation from Interactions, level AAA) says motion triggered by interaction should be possible to turn off, unless it's essential. The W3C notes that animation can cause dizziness, nausea and headaches for people with vestibular disorders. Its examples point to the prefers-reduced-motion CSS media query as one way to do it.

If your components respect prefers-reduced-motion, show it. A few seconds of "same modal, reduced motion on" tells engineers the accessibility work is already done. If they don't yet, that's worth knowing before you promote them.

Accuracy Matters More Here Than Anywhere

This audience builds the real components. They'll notice if the spacing, easing or color in the video is slightly off. A showcase that doesn't match the code undermines the trust it's meant to build.

That's the main argument for recording from Storybook rather than redrawing components in a design tool. Storybook renders your actual code. If you want a polished version for an external launch, start from material that's just as real. Poko Motion can work from your repository or from a screen recording you've already made. Our guide to choosing between a repo, PDF, deck or recording explains what each gives you.

One honest limit: a video can't replace the docs. Props, edge cases and migration notes still belong in Storybook and in your changelog.

Where to Use the Video

  • Release notes and changelogs: put the video at the top of the design-system release post. Our guide to building a video changelog covers the format.
  • Your design-system channel: post it with the install command in the message, so nobody has to open the video to copy it.
  • New-hire onboarding: a 90-second tour of the system's best components is a faster start than a Storybook link.
  • Open-source READMEs: if the library is public, the video helps outside teams decide whether to adopt it. See why your README needs a video.

Each placement needs the same thing in the first 10 seconds: what's new and why it matters to that viewer.

Your Next Step

Open your design system's last release notes and pick the component you most want people to adopt. Give it one story with a play function that runs through its states, open that story's canvas URL, and record 20 seconds. That clip is the middle of your first showcase video, and it can be re-recorded next release from the same link.

Disha Sharma
About the author

Disha Sharma

Marketing, Poko Motion

Writes about AI video workflows, product storytelling, and motion video.

Questions, answered.

What is a design system showcase video?

A design system showcase video is a short clip, usually 60 to 120 seconds, that shows a handful of new or changed components moving through their real states and then tells viewers where to get them. It works as an announcement, not a reference. Storybook stays the full documentation, while the video gives engineers and designers who weren't looking a clear reason to switch from the old pattern.

How do you record a component from Storybook without the toolbar?

Use the "open canvas in new tab" button in Storybook. It opens the story on its own iframe.html page, using the story id and viewMode=story, with no sidebar or addon panel on screen. You can add an args query parameter to that URL to open the component in a specific state, such as a large or disabled button, so each shot can be reopened later from the same link.

Can Storybook play functions be used to record demo videos?

Yes. A play function runs after the story renders and interacts with the component, for example typing into a field or clicking a button. Because it is code, the same sequence plays the same way on every take. The Interactions panel lets you pause, rewind and step through each action, and the step function groups actions under labels, which makes a play function a repeatable shot list.

How many components should a design system video show?

Show four to six components, each chosen to prove one thing about the system: what's new this release, a full state cycle, a complex pattern such as a modal or data table, theming, and responsive behavior. Covering the whole library turns the video into a slower version of Storybook. Leave every other component in Storybook, where people can look it up when they need it.

How long should a design system showcase video be?

Aim for about 90 seconds. At roughly 150 spoken words per minute, the National Center for Voice and Speech's average, that gives about 225 words of narration. Spend the first 10 seconds on what's new, most of the time on components and their states, and the last 10 seconds on the package name and Storybook link. Wistia's data shows viewers often watch about half, so lead with the news.

Keep reading

#design systems#storybook#component library#developer tools#product videos#video marketing#accessibility

Poko Motion · the fastest AI motion video generator

Make your first video
in 5 minutes.

Paste a link, a doc or a deck. A swarm of AI agents builds the video while you watch.