How Many Slides in a Presentation?

When people ask how many slides a presentation should have, the answer they are looking for is a number, and "about one slide per minute" is the closest thing to a universal one. It is popular for a good reason: it keeps you honest. If you have thirty minutes and forty-five slides, you are going to rush; if you have five minutes and twenty slides, you have built a flip-book. Matching slides to minutes gives your audience time to absorb each idea before the next one arrives.

The trap is treating it as a law instead of an average. Slides are not all the same weight. A section divider or a single full-bleed image might sit on screen for fifteen seconds, while a chart you actually walk through can hold attention for three minutes. So the real rule is: your total slide count should land near your minute count, but individual slides can vary wildly. Aim for the average, not a metronome.

Use one-slide-per-minute as a ceiling when you are unsure. It is far more common to have too many slides than too few, and going over the count is a reliable sign you are trying to say too much. If you are consistently blowing past a slide a minute in rehearsal, the fix is almost never talking faster — it is cutting slides or merging ideas until each one earns its place.

5-minute presentation: 5-6 slides. There is only room for one message. Use a title, three to four content slides, and a close — no agenda slide, no filler. This is the format for a lightning talk, a demo, or a quick internal update.

10-minute presentation: 10-12 slides. Enough for a small setup, three supporting points, and a conclusion. This is the classic short-pitch length, and it maps almost exactly to Guy Kawasaki's 10-slide pitch-deck rule described below.

15-minute presentation: 12-15 slides. You can afford a little context and one deeper example. Keep the structure to three or four sections so the audience can follow the through-line without an agenda crutch.

20-minute presentation: 15-20 slides. The standard conference-talk length. One idea per slide still holds; the extra time goes into one or two slides you genuinely walk through — a chart, a story, a live demo — rather than more slides.

30-minute presentation: 20-30 slides. Now you have room for a proper arc: setup, three to five sections, and a strong close. Budget a few minutes for questions and plan for roughly 25 slides so you are not racing the clock.

45-minute presentation: 30-40 slides. A workshop or lecture length. At this point, breaks in pace matter more than raw count — use section dividers, a recap slide or two, and moments that invite the room in so it does not become a monologue.

60-minute presentation: 40-50 slides, and usually fewer. An hour is rarely all talking; leave 10-15 minutes for discussion and questions, which means you are really presenting for 45-50 minutes. Fewer, richer slides beat a wall of them at this length.

Guy Kawasaki's 10/20/30 rule is the most-cited slide-count formula, and it is worth knowing even if you are not raising money. The ten slides he suggests are a specific pitch sequence: problem, solution, business model, underlying magic, marketing, competition, team, projections, status, and a summary or ask. The twenty-minute cap assumes a one-hour meeting where half the time disappears to logistics and questions. The 30-point minimum font is really a proxy for "you have too much text."

The rule works best exactly where Kawasaki intended it: an investor pitch, a sales meeting, or any high-stakes conversation where you want dialogue, not a lecture. In those rooms, ten tight slides that provoke questions beat forty that answer questions nobody asked. If that is your situation, it is a genuinely good default to start from.

For other formats, borrow the spirit rather than the exact numbers. A 45-minute training session obviously needs more than ten slides. But the underlying principles — hard cap on length, big readable text, one idea per slide, and leaving room for the audience — travel everywhere. The specific "10" is for pitches; the discipline of ruthlessly limiting slides is for everyone.

1. Confirm your actual speaking time. Not your slot — your speaking time. A 60-minute meeting with introductions and Q&A might leave you 40 minutes of talking. Subtract those minutes first, because everything downstream is paced against the time you actually hold the floor.

2. List one idea per slide, not one topic. Write out every distinct point you need to make, and give each its own slide. If a slide is trying to carry two ideas, split it; if two slides make the same point, merge them. This gives you a natural, content-driven slide count before you think about the clock at all.

3. Sanity-check against one slide per minute. Compare your count to your speaking minutes. Roughly equal is healthy. Far more slides than minutes means you will rush — start cutting. Far fewer usually means a few slides are doing heavy lifting, which is fine as long as you have genuinely rehearsed talking through them.

4. Move supporting detail into an appendix. The backup numbers, the detailed methodology, the extra examples — they do not belong in the main flow, but you want them for questions. Park them on appendix slides after your close. This is one of the fastest ways to bring a bloated deck back down to size without losing anything.

5. Rehearse out loud and cut what stalls. Say the whole talk start to finish and time it. You will feel the slides that kill momentum — the ones you apologise for, skim past, or explain away. Every one of those is a candidate to cut. The slide count that survives two honest run-throughs is the right count for you.

It is tempting to decide on a slide count first and then fill it, but that is planning the container before you know the contents. A presentation that is genuinely about three ideas does not become better by being padded to twenty slides, and a rich forty-minute topic is not improved by being squeezed into ten. The count should emerge from the content: figure out your one message and the three-to-five sections that support it, and the slides fall out of that structure.

This is why writing before designing helps so much with slide count specifically. When you outline the whole talk as a document — headings for sections, bullets for evidence, dividers where slides break — you can see the shape of the argument and count the real ideas before you have built anything. Reordering or cutting is free at that stage. By the time you turn it into slides, the number is already close to right because it reflects the thinking, not a quota.

A content-first tool like Eazy leans into exactly this. You write and structure the presentation in a real editor, drop in slide dividers where you want breaks, and the deck is built from that document — so your slide count mirrors your outline instead of a template you have to fill. You can also bring in a PDF, Word file, spreadsheet, or a web link and have it read into editable content, then let the content decide how many slides it becomes. Start with a thought, not a prompt — and the slide count takes care of itself.