How long should a demo be?

The honest answer is: as long as one clear thing takes, and no longer. In practice that lands most product demos between thirty and sixty seconds, which is also roughly how long someone deciding whether to try your product will give you.

Length follows structure, not the other way round

Do not aim at a duration; aim at a structure and let the duration fall out. A demo that works has four beats. **The state before** — what the viewer's problem looks like, two or three seconds, usually just the screen you start on. **The action** — what you actually do, and this is most of the video. **The result** — the thing that came out, held long enough to read. **What now** — where to go, a few seconds at the end. Skip any of the four and the demo feels incomplete no matter how long it is; include all four for one task and you land in the thirty-to-sixty range without trying.

Start at the action

The most common way a demo runs long is the runway: signing in, navigating, explaining the layout, arriving at the feature after twenty seconds. Cut all of it. Start on the screen where the interesting thing is about to happen, with realistic data already in place. Nobody watching a demo needs to see a login form, and every second before the first meaningful action is a second in which people leave. If context genuinely is needed, it is one sentence of text on screen, not a navigation sequence.

Pace: slower than feels right while recording

You know where everything is; the viewer is seeing it for the first time. Pause about a second wherever something appeared that needs reading — a result, a menu, a confirmation — and let a zoom move settle before doing the next thing. Recording at your own working speed is the reason people say a demo felt "rushed" without being able to say what was wrong: individually each step was visible, but none was on screen long enough to be read. That is also why a shorter demo with pauses beats a longer one without them.

Cutting when it runs long

When the demo is 90 seconds and needs to be 40, cut whole steps rather than shaving frames off each one — trimming pauses is exactly the wrong move, because the pauses are what make it legible. Ask which steps the *sentence* needs. Configuration usually goes. Alternative paths go. Anything you are showing because you are proud of it rather than because it serves the task goes. And if two genuinely different things need showing, that is two demos: two forty-second videos are watched far more than one eighty-second video, and they can go in different places.