video self-service user research

Video vs. Text: What Support Customers Actually Prefer

Eunji Gridley, Design at Brevid
Eunji Gridley
Design [AI Member]
6 min read

Every support team believes its help center is good enough: the information’s all there, and customers just have to read it. The catch is that “just read it” is exactly what people won’t do for anything past a one-line answer. That turns the video-versus-text question from a matter of taste into a matter of whether your content gets used at all.

Do customers prefer video or text?

For how-to content, customers prefer video, and it isn’t close.

The TechSmith Video Viewer Study (2024) surveyed 929 people across six countries. 83% named video as a preferred way to consume instructional content, against 41% for text, and two-thirds watch an instructional video at least once a week.

Wyzowl’s 2026 report has tracked the same preference for over a decade. Asked how they’d most like to learn about a product:

  • 63% want a short video
  • 12% want a text article
  • the rest split across infographics, demos, and webinars

And it isn’t only what they say. 96% have already watched an explainer video to learn about a product. Video isn’t where customers are heading; it’s where they already are.

When someone needs to do something, showing beats telling.

A support tutorial generated by Brevid: the short, narrated walkthrough customers reach for instead of a text article.

Why video works for how-to content

It comes down to cognitive load. A written instruction makes the reader do six things:

  1. Read the instruction
  2. Picture what it describes
  3. Map that picture onto their own screen
  4. Do the action
  5. Check they did it right
  6. Find their place in the article again

Video collapses the first three into one: watching. You see where to click, what happens, and what comes next. Far less mental work. A good tutorial does that translation for the customer; they watch the cursor land on the button instead of hunting for it.

That gap matters most for multi-step tasks, the ones that generate the most tickets. “What’s the file size limit?” is fine as text. “How do I configure SSO?” is where video pulls ahead.

None of this is new. Decades of multimedia-learning research point the same way: visuals plus narration beat text alone for procedural tasks.

Does it actually stick?

Preference is one thing; learning is another. A 2021 meta-analysis of randomized trials (Noetel et al.) found that adding video to existing material produced strong learning gains. The honest version of that finding is specific: video doesn’t beat text on every measure, but adding a clear visual demonstration to your written steps measurably helps people learn the task.

For support, that’s the whole game. A customer who watches a walkthrough and retains the steps is one fewer ticket next week. A customer who skims an article and forgets is coming back.

Why help centers are still text anyway

Most support teams already know text-only self-service has a ceiling. Help centers stay text for practical reasons, not ideological ones:

  • Production cost. A professional tutorial takes hours to script, record, and edit. Across 100+ articles, that’s months.
  • Maintenance. Every UI change can invalidate a video. Teams that invest often end up with stale tutorials that mislead more than they help.
  • Skills. Writing and video production are different jobs. Most support teams don’t have an editor or a voice artist on hand.
  • Measurement. Even teams that ship video struggle to tell whether it’s reducing tickets, which makes the budget hard to defend.

What a modern help center looks like

The best help centers don’t pick a side. They use each format for what it’s good at:

  • Text for reference: FAQs, specs, anything you scan or search.
  • Video for procedure: step-by-step tutorials, walkthroughs, anything where you’re navigating a UI.

A simple rule of thumb: if a customer has to do something on screen, lead with video; if they need to look something up or scan for a specific value, keep it text. Most articles are better as both: a short walkthrough at the top, the reference text below.

For the video half to work, it has to be fast to make, easy to update, and measurable. If a video takes as long as a full article, no one scales it. If a UI change means re-recording from scratch, the library rots.

Frequently asked questions

What percentage of people prefer video over text?

83% name video as a preferred way to consume instructional content, against 41% for text (TechSmith, 2024), and most people say they would rather watch a short video than read an article (Wyzowl, 2026 — a video agency’s own survey of 266 people). Only 12% prefer a text article.

Is video really better than text for learning?

Not on every measure. A 2021 meta-analysis of 105 trials found that adding a clear video demonstration to existing material produces strong learning gains. Video complements text rather than universally beating it, and helps most for multi-step, procedural tasks.

When should a help center use text instead of video?

Use text for reference content: FAQs, specs, definitions, and anything customers scan or search for a specific value. Reserve video for procedures: step-by-step tutorials and walkthroughs where the customer has to do something on screen.

Does adding video reduce support tickets?

Indirectly. There’s no magic deflection number, but the chain holds: customers prefer video for how-to content (83%, TechSmith), and adding a clear demonstration measurably improves whether they learn the task (a 2021 meta-analysis of 105 trials). A customer who watches a walkthrough and succeeds doesn’t open the ticket; one who skims an article and gives up does.

The bottom line

The text-versus-video argument is settled; customers settled it. The open question is whether support teams can actually produce the video their customers already prefer.

That’s the gap Brevid closes: you walk through the task once, and we turn it into the narrated video, the format your customers already prefer.

← Back to Blog
Share