How Many Slides Per Training Hour? Density Rules for Generated Decks
Asking how many slides per training hour you need sounds like a formatting question and is really a cognitive load question. Generated decks in particular tend to run long, because generation reflects the structure of the source document rather than the rhythm of a delivered session, and a 40-page policy produces 60 slides that nobody can sit through. Knowing the target density before you generate, and what to cut afterwards, is what turns raw output from an AI slide generator into something deliverable. Key Takeaways 🖥️ Sign In to Access Your Dashboard The Baseline Numbers There is no universal figure, but the ranges are consistent enough to plan against. Format Slides per hour Time per slide Instructor-led, discussion-heavy 12 to 15 4 to 5 minutes Instructor-led, standard 15 to 20 3 to 4 minutes Instructor-led, technical walkthrough 20 to 25 2 to 3 minutes Self-paced with narration 25 to 30 2 minutes Self-paced, reference-heavy 30 to 40 1 to 2 minutes The instructor-led numbers surprise people who have sat through 60-slide corporate sessions. Those sessions overran, or the instructor skipped slides, which is the same problem expressed differently. Self-paced runs denser because learners control pace and can re-watch. Density is not a virtue there either, but the ceiling is higher. Why Generated Decks Run Long Generation follows the structure of what you feed it. A policy document has sections, subsections, and definitions, and each of these looks like a slide boundary to a generator. Delivered sessions do not work that way. A session has beats: an opening, three or four substantive moves, a practice element, and a close. Ten source sections might map to four session beats, and the generator has no way to know that. Three patterns produce the overshoot: Definitional slides: Source documents define terms formally. Sessions introduce terms in passing while doing something with them. Definition slides are the single largest category of cuttable content. Section headers as slides: Useful in a document, dead air in a session. Exhaustive enumeration: A policy listing twelve categories becomes twelve bullet points or three slides. A session needs the two categories that matter and a reference handout for the rest. Cutting Down to Deliverable Length Work in this order. Cut every standalone definition slide: Fold the definition into the slide where the term is first used. Merge section headers into the following slide: The heading becomes the title. Collapse enumerations: Show the two or three items that matter, and move the full list to a handout. Learners will not retain twelve items from a slide regardless. Convert content slides to prompts: Where the instructor will talk through a point, the slide needs an anchor, not the full argument. This alone typically removes 20% of a generated deck. Move reference material out: Tables, thresholds, and specifications belong in a document learners can search, not in a deck they watch once. The same logic applies to audio, as covered in what changes when learners listen instead of read. 📄 Generate a Free PDF Sample Course in Your Cloned Voice One Idea Per Slide The rule is simple and almost universally violated. When a slide carries two ideas, the second gets less attention or none, because the audience is still processing the first when the instructor moves on. This is a straightforward consequence of working memory limits, described in cognitive load theory. Practical tests. If your slide title contains “and”, it probably carries two ideas. If a slide has more than five bullets, it carries several and If you cannot state the slide’s single point in one sentence, it has not got one. Splitting a dense slide into two raises the slide count and lowers the cognitive load, which is a good trade even though it moves the density number in the wrong direction. The count is a planning heuristic, not a target to optimise. Vary Density Within a Session Constant pacing produces attention decay regardless of the count. A workable rhythm alternates. Several quick slides establishing context, then one substantial slide the group stays on for eight minutes, then a practice element with no slide at all, then quick slides again. The slides that anchor discussion are the ones worth designing carefully. Most of the rest are signposts. Treating every slide as equally important is why decks feel flat, and it is also why they take three times longer to build than they need to. Plan the beats first and generate against them, rather than generating from the document and hoping the rhythm emerges. Where the Effort Moves To be clear about scope: no generator knows your session rhythm, because that depends on your audience, your instructor, and how much discussion you want. The cutting decisions are yours. What generation changes is where the effort goes. Producing a first-pass deck from source material takes minutes rather than a day, so the instructor’s time moves from building slides to deciding which ones survive. That is the higher-value use of it, and the version that reaches learners is better for it. For a provider building decks across 20 courses Metric Before After Time to first-draft deck 6 hours 20 minutes Instructor time on slide editing 6 hours 90 minutes Average deck length, 2-hour session 58 slides 34 slides Sessions overrunning Frequent Rare Cutting a Generated Deck Down Frequently Asked Questions If your last generated deck felt bloated, the cause was the source document’s structure rather than the generator. Plan the session beats first. 👉 Book a Live Platform Demo with an EdTech Expert