← Back to blog

How to Write Demo Captions That People Actually Read

August 9, 2026

The screens in an interactive demo do most of the work, and the captions decide whether that work lands. They are also the part most often written last, quickly, in the tone of internal documentation.

A demo viewer is skimming and clicking. Captions have to survive that, which rules out most of how people naturally write.

One idea per step, under fifteen words

A caption is a signpost, not an explanation. It should tell someone what they are looking at and why it matters, then get out of the way.

If a step needs two ideas, it is two steps. Splitting is nearly always better than a longer caption, because clicking is cheap and reading is not.

Write the benefit, not the mechanic

"Click Approve" describes what your finger does. "Approving here notifies finance automatically" describes why anyone would care.

The screen already shows the mechanic. The caption's job is the part the screen cannot show, which is consequence.

Second person, present tense

"You can see every change" reads better than "users are able to view all changes". Present tense and direct address are shorter and less formal, both of which help at skim speed.

It also keeps you honest: passive constructions hide who does what, which is exactly the information a demo caption exists to supply.

Mistakes that get captions skipped

  • Restating the button label. If the button says Export, do not caption it "Click Export".
  • Internal vocabulary. Nobody outside your company knows what a Workspace Flow is.
  • Hedging. "You can optionally configure" is three words of throat-clearing.
  • Exclamation marks. They read as compensating for something unremarkable.
  • Repeating the same opener on every step. Five consecutive captions starting "Now you can" become invisible.

Give the last step a job

The final caption is the one most likely to be read, because the viewer has invested attention and is looking for the point.

Do not waste it on "and that's it". Use it to state what they just saw and what to do next -- it is the only caption that reliably gets a decision out of anyone.

Frequently asked questions

How long should demo captions be?
Under fifteen words, with one idea per step. Viewers are skimming and clicking rather than reading closely, and if a step needs two ideas it should be two steps, since clicking is cheap and reading is not.
What should a demo tooltip say?
The consequence rather than the mechanic. The screen already shows what to click, so the caption should say why it matters, for example that approving here notifies finance automatically rather than simply "click Approve".
What are common mistakes in demo captions?
Restating the button label, using internal product vocabulary, hedging words like "optionally", exclamation marks, and opening every caption the same way, which makes them blend together and get skipped entirely.

Keep reading

This is what Demorta does

Click through it — the same kind of demo you can record of your own product.

Try it on your own product

Record your first interactive demo free.

Five demos on the free plan, forever. No credit card, no trial countdown, no sales call. Install the Chrome extension, click through your product once, and you have a shareable link in about ten minutes.

Start free →