How many slides for a presentation is one of the first questions people ask when a slot lands on the calendar, and one of the easiest to get wrong. The common answer is about one slide per minute, and that is a fine place to start. But a 10-minute talk built from dense charts needs far fewer slides than a 10-minute talk built from photos, and a slot that includes questions is shorter than it looks.
This guide gives you working ranges for 5 to 60 minutes, explains where the popular rules come from, and adds a simple method we call the slide budget: count your real speaking time, weight each slide by how heavy it is, and let the number fall out. It works the same whether you build slides by hand or generate a first draft with AI.
The short answer: about one slide per minute, adjusted for density
Most published guidance lands in the same place. Microsoft's own presentation advice suggests spending about 1 to 2 minutes on each slide and keeping a 10-minute talk to roughly 7 to 10 slides. Adobe's guide frames it as one minute and one point per slide, with simple slides taking as little as 30 seconds and data-heavy slides up to two minutes.
The adjustment that matters is density. As Arcdeck's slide-count guide puts it, a chart, table or process diagram often needs one and a half to three minutes, while a slide with a single image, quote or number can last 20 to 30 seconds. So two talks of the same length can honestly need very different slide counts.
How many slides for a 10, 20 or 30-minute presentation
Here is a consolidated range table. The middle column reflects where the sources above broadly agree; the right column tells you which way to adjust.
| Talk length | Typical slide range | Adjust down if... | Adjust up if... |
|---|---|---|---|
| 5 minutes | 3–6 | You show a chart or demo | Slides are mostly images |
| 10 minutes | 7–10 | Q&A is inside the slot | You use quick visual beats |
| 15 minutes | 10–14 | Content is data-heavy | Audience is non-expert and needs examples |
| 20 minutes | 12–18 | Most slides carry charts | Talk is story-led |
| 30 minutes | 18–25 | You plan live discussion | You use section dividers |
| 45 minutes | 25–35 | Workshop or exercise built in | Many short visual slides |
| 60 minutes | 30–45 | 10–15 minutes kept for Q&A | Keynote-style pacing |
The 10-minute row matches Microsoft's 7 to 10 slides, and the longer rows follow the ranges in Arcdeck's guide and Presenter's Arena's reference table, which lists 20 to 25 slides for 30 minutes. Adobe is slightly more generous for short talks, suggesting eight to 12 slides for 10 minutes when you lean on images and simple charts.
What counts toward the total
A title slide counts but takes seconds. Section dividers count but take seconds too. Backup and appendix slides placed after your closing slide do not count, because you only show them if someone asks. And questions are not slide time: if your 10-minute slot includes Q&A, you are really building for seven or eight minutes of speaking.
Where the famous rules come from (and when to use them)
Three formats come up whenever slide count is discussed. Each was designed for a specific situation, which is why none of them works as a universal law.
Guy Kawasaki's 10/20/30 rule
Guy Kawasaki's rule says a presentation should have ten slides, last no more than twenty minutes, and use no font smaller than thirty points. He wrote it as a venture capitalist tired of long pitches, and he applies it to any presentation meant to reach agreement, such as raising money or closing a sale.
"a normal human being cannot comprehend more than ten concepts in a meeting"
That line, from Kawasaki's original post, is the useful part. The ten slides are really ten concepts. His reasoning for twenty minutes is also practical: in an hour-long slot, setup and late arrivals eat time, so you finish early and leave room for discussion. Use 10/20/30 for pitches, sales meetings and decision meetings.
TED's 18 minutes
TED recommends that talks be 18 minutes or less, describing that as long enough to say something meaningful but short enough to hold attention. It also notes that shorter talks of 3 to 9 minutes can be just as impactful. TED does not prescribe a slide count, which is the point: the limit is on time and ideas, not slides.
PechaKucha 20x20
PechaKucha is the opposite extreme: 20 images, each auto-advancing after 20 seconds, for exactly 400 seconds. It shows that high slide counts work fine when every slide is light. Twenty slides in under seven minutes would be chaos with bullet points and perfectly comfortable with photos.
The slide budget method: work out your own number in five steps
Rules of thumb fail when your content is unusual. This method takes about five minutes and gives you a number you can defend.
- Find your real speaking time. Start with the slot length. Subtract Q&A, introductions, and a buffer of 10 to 15 percent for setup and transitions. A 20-minute slot with 5 minutes of questions gives you roughly 13 minutes of speaking.
- List your points, not your slides. Write each idea as a one-sentence headline. A 10-minute talk can usually carry about three main points, according to Arcdeck's guide. Most of your slides should map to one of these sentences.
- Weight each slide. Give each planned slide a time cost: light (an image, a quote, a single number) is 0.5 minutes; standard (a headline plus a short visual or two to three bullets) is 1 minute; dense (a chart, table or diagram you must explain) is 2 minutes. These weights sit inside the 30-seconds-to-two-minutes range Adobe describes.
- Add it up and compare. If your weighted total runs over your speaking time, cut or merge points first. Do not shrink fonts or speed up.
- Check with words. If you script, multiply your speaking minutes by your pace. PowerPoint's Speaker Coach recommends 100 to 165 words per minute, and EchoPitch's study of 25 famous speeches found a median of about 130. At 130 words per minute, 13 minutes of speaking is roughly 1,700 words of script.
A worked example: a 20-minute team update
Say you have a 20-minute slot for a quarterly team update, with 5 minutes reserved for questions. After a 10 percent buffer, you have about 13 minutes of speaking.
| Slide | Type | Weight (min) |
|---|---|---|
| Title | Light | 0.5 |
| The one-sentence summary | Standard | 1 |
| Results vs target (chart) | Dense | 2 |
| What drove the result | Standard | 1 |
| Customer quote | Light | 0.5 |
| Risk we are watching (chart) | Dense | 2 |
| Three priorities for next quarter | Standard | 1 |
| Priority 1 detail | Standard | 1 |
| Priority 2 detail | Standard | 1 |
| Priority 3 detail | Standard | 1 |
| What we need from you | Standard | 1 |
| Close and questions | Light | 0.5 |
| Total: 12 slides | 12.5 |
Twelve slides and 12.5 minutes fits inside 13 minutes with a little slack, and it lands inside the 12 to 18 range for a 20-minute talk. If you wanted to add a third chart, the budget tells you something else has to go.
Adjusting for the room: pitch, class, webinar and conference
The same length can call for different counts depending on the setting.
- Investor pitch or sales meeting. Keep close to Kawasaki's ten concepts and finish early so the meeting becomes a conversation. Put detailed financials and technical depth in the appendix.
- Classroom or student presentation. Rubrics often set a time limit rather than a slide count. Use the budget method and lean toward fewer, clearer slides so you are not rushing to hit the time limit.
- Webinar or virtual meeting. On a shared screen, your slides are most of what people see, so a few extra light slides that change every 30 to 60 seconds can keep the view from going static.
- Conference talk. If your slot is around 15 to 20 minutes, TED's 18-minute guidance is a useful model. Plan around three main ideas, and rehearse with the organiser's timer rules in mind.
- Board or executive briefing. Fewer slides, more pre-reading. A short main deck with the detail in an appendix lets the discussion go where the room needs it.
Rehearse with a timer before you trust the number
Every source here agrees on one thing: the count is a guess until you time it. PowerPoint's Speaker Coach reports your words per minute and how your pace varies over a rehearsal. Presenter's Arena offers a simple loop: start with eight slides for a 10-minute talk, rehearse with a timer, cut a slide if you rush and add one if there is dead air.
Two quick checks help. First, note the time at your halfway slide; if you are already past the midpoint of your speaking time, cut now rather than hoping to speed up later. Second, rehearse the close separately. It is the part most often squeezed when a talk overruns, and it is usually where your ask lives.
FAQ
How many slides for a 10-minute presentation?
About 7 to 10, including the title slide. Microsoft suggests 7 to 10, and Adobe allows eight to 12 if you rely on images and simple charts. Go lower if the 10 minutes includes questions.
How many slides for a 20-minute presentation?
Roughly 12 to 18, or nearer 10 to 14 if most slides carry charts or tables. For a pitch, Kawasaki's rule of ten slides in twenty minutes is a good ceiling.
How many slides for a 30-minute presentation?
Around 18 to 25 is typical, per Presenter's Arena's table. If you plan live discussion or a demo, use fewer.
Do backup slides count?
No. Put them after your closing slide and only show them if a question needs them. They do not use speaking time.
Is more slides with less text better than fewer dense slides?
Usually, as long as each slide makes one point. PechaKucha's 20 slides in 400 seconds works because each slide is a single image. What hurts audiences is too many ideas, not too many slides.
The right slide count is the one that fits your ideas into your real speaking time with room to breathe. Decide your points first, weight each slide honestly, and let a timed rehearsal have the final word. Do that, and the number takes care of itself.