How to Demo a Product Where the Interaction Is the Keyboard
August 22, 2026
For editors, terminals, command palettes and power tools, the pitch is speed — the thing happens in a keystroke instead of four clicks. That is precisely what a click-based capture cannot show.
The screenshots come out looking like a screen that changed for no visible reason.
Put the keystroke in the caption
The single highest-value fix. If a step happened because of Cmd+K, the caption says so: "⌘K opens the command palette from anywhere." Now the unexplained change has a cause.
Write the actual key names rather than describing them. "Press the shortcut" tells the reader nothing; "⌘⇧P" is the thing they will remember and try.
Show the before and after as separate steps
- Before: the state where the user needs something.
- After: the palette open, the file jumped to, the command run.
- The caption on the second step carries the keystroke and the point.
- Do not compress both into one step, which is where the "changed for no reason" impression comes from.
Contrast against the slow way, once
For a keyboard-first product the argument is comparative, and it is worth one explicit moment: a caption noting that the same thing takes four clicks and two menus elsewhere.
Once, not throughout. A demo that keeps insisting on its own speed is less convincing than one that demonstrates it and moves on.
Where video genuinely wins
This is one of the few categories where a short video beats an interactive demo on the core claim, because speed is temporal and steps are not. Watching six operations happen in four seconds is the argument.
The strongest pairing is a short video for the speed claim and an interactive demo for the detail — the video proves it is fast, the demo lets an evaluator read what actually happened at each stage. Exporting the demo to video gives you both from one recording.
Frequently asked questions
- How do you demo keyboard shortcuts in a product demo?
- Put the actual keystroke in the caption -- "⌘K opens the command palette from anywhere" -- and split the before and after into separate steps. Compressing both into one step is what makes a screen look like it changed for no reason.
- Should a keyboard-driven demo compare against slower tools?
- Once, explicitly -- a single caption noting the same action takes four clicks and two menus elsewhere. A demo that keeps insisting on its own speed is less convincing than one that demonstrates it and moves on.
- Is video better than an interactive demo for a fast, keyboard-first product?
- For the speed claim specifically, yes, because speed is temporal and steps are not. The strongest pairing is a short video proving it is fast plus an interactive demo letting evaluators read each stage -- exporting the demo to video gives you both.
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 →