Somewhere in every support team there is a debate about video. One side says customers do not read, so every article should be a video. The other says videos are slow, unsearchable, and go out of date. Both have watched customers struggle with the other format.
The way out is to stop picking a format for the help center and start picking one per question.
Where video is the clearer answer
- Flows that cross several screens. Seeing the path is easier than reading "then go to" five times.
- Spatial tasks: dragging, arranging, resizing, drawing, anything where position matters.
- First-time setup, when the customer does not know the product's layout yet and words like "sidebar" or "panel" mean little.
- Anything that looks scary. Watching someone connect a payment provider calmly reassures more than a warning box.
- Showing what "done" looks like, when the result is visual.
Where text is the better answer
- Lookups. "Where do I change my billing email?" deserves one sentence and a screenshot, not a 40-second video.
- Troubleshooting with error messages. People paste the error into search, so the error text needs to be on the page.
- Anything people copy: API keys, DNS records, code snippets, settings values.
- Long reference content, such as permission tables or plan limits.
- Readers at work, on a train, or anywhere without sound and patience.
| Question type | Lead with | Example |
|---|---|---|
| How do I do [multi-step task]? | Video, steps below | Set up your first automation |
| Where is [setting]? | Text and a screenshot | Change your billing email |
| Why do I see [error]? | Text | "Domain not verified" error |
| What does [feature] do? | Short video | What are smart folders? |
| What values do I enter? | Text with copyable blocks | DNS records for a custom domain |
| Getting started | Video, steps below | Your first 10 minutes |
The case for both on one page
For most how-to articles, the answer is not either-or. Put the video at the top for people who want to watch. Put numbered steps with screenshots underneath for people who want to skim, find one step again, or follow along at their own speed. The page serves both readers, and nobody has to hunt for the other format.
The written steps also do quiet work you do not see. Your help center search indexes text. So do Google and the AI assistants your customers increasingly ask first. A page that is only an embedded video has almost nothing for any of them to read. That is a big reason to never publish video-only help.
The maintenance question
The honest argument against video is upkeep. When a button moves, editing one sentence in an article takes a minute; re-recording a video takes much longer. That is why video-heavy help centers tend to fill up with clips showing an old interface.
Two habits help. Keep each video to one task, so one UI change breaks one short clip, not a long one. And produce the video and the text from the same source, so they cannot drift apart. More in the real cost of outdated tutorial videos.
How Steperly handles it
In Steperly, a help article starts as one recording of the task. The same recording gives you the narrated video, a clickable version, and the written steps with screenshots, all on one page in your branded help center. The reader chooses how to take it in. Because everything comes from the same recording, the video and the steps describe the same version of your product.
Setting up the help center itself? Start with how to build a help center, then make your first tutorials with how to make a software tutorial video.