How long should each slide be in a narrated video?

Most slide-to-video tools default to roughly two minutes of narration per slide. That number is a reasonable starting point and wrong for a lot of real decks — not because two minutes is bad, but because the right length depends on what is on the slide, and decks are not uniform.

Where two minutes comes from

A slide with a headline, three bullets and a chart takes about 90 seconds to two minutes to explain out loud at a natural pace. Not read aloud — explained. That is the distinction that matters: a script that reads the bullet points verbatim is both faster and worse, because spoken language and written slide language are different registers. Good narration says what the bullet means.

So the default is really “enough time to explain one idea properly”, and the honest answer to “how long should a slide be” is: as long as it takes to explain its one idea.

When slides need to be shorter

Title, section and agenda slides. Fifteen seconds. Narration like “Next, how the approval flow works” is enough. Paying two minutes here makes the video feel padded within the first minute.

Slides the viewer already knows. A company-mission slide in a deck shown only to employees does not need a minute and a half.

Pure visuals. If the slide is a diagram you are talking over, the audio should carry it and the script should be tight.

When slides need to be longer

Dense data. A slide with a table of twelve rows genuinely takes longer to walk through. If it needs four minutes, the problem is usually not the narration — it is that the slide should have been two slides.

Process diagrams. Anything with arrows between boxes needs each step named, and steps cannot be rushed without losing the thread.

The real fix is usually splitting, not pacing

When a slide needs more than about three minutes, look at the slide rather than the script. It is almost always carrying two ideas that deserve two pages. Splitting does three things at once: it shortens each narration, it gives the viewer a chapter boundary to return to, and it makes the update loop cheaper because you re-render a smaller unit.

The corollary: do not try to solve density by speeding up the voice. Faster narration reads as unconfident and hurts comprehension more than a slightly long video does.

Why chapter navigation changes the arithmetic

If the video has per-slide chapters, length is much less punishing. A twenty-minute training video with chapters is a reference document people return to; the same video without chapters is something they watch once and lose. Chapters are the difference between “too long” and “long, but I can find the part I need”.

This is also why a single continuous video often beats splitting a deck into five short clips: one link, one asset to maintain, and navigation handles the rest.

A working rule

• Structural slides (title, agenda, transition): under 30 seconds
• Standard content slides: 90 seconds to 2 minutes
• Dense or procedural slides: up to 3 minutes, then split
• Whole video: aim for something a person will finish in one sitting. If a deck produces more than about 20 minutes, consider whether it is really one video or three.

That last point is the one teams skip. A 40-slide deck can be converted as a single video, and sometimes should be — but a 40-page compliance module is usually three videos that share a link, and viewers will complete all three where they would abandon one long one.

Whatever length you land on, the check is the same: watch the output on a phone. Pacing problems that are invisible on a desktop are obvious on a small screen.