Someone asks this question in almost every kickoff call I sit in on: "how many slides should this be?" It's usually the wrong question, but I get why people ask it. A number feels safe. It's something you can hit, check off, and move on from. The problem is that slide count on its own tells you almost nothing about whether a presentation will land.

I've built decks with 8 slides that ran 40 minutes long, and decks with 60 slides that got through in 12. Count alone doesn't predict pacing, clarity, or whether the audience stays with you. What predicts those things is the relationship between your content, your delivery format, and how much you're asking each slide to do.

Why slide count is the wrong question to start with

Most guidance on this topic starts with a magic number — 10 slides, 15 slides, "one slide per minute." These rules aren't wrong exactly, they're just answering a narrower question than the one people actually have. They assume a specific format: a live, spoken pitch where you control the pacing. That's one type of presentation. It's not the only one.

In my experience, the more useful first question is: will anyone read this without you in the room? That single distinction changes the right slide count more than any rule of thumb does.

The "one minute per slide" rule — and where it actually breaks

The one-minute-per-slide heuristic is popular because it's easy to apply: a 20-minute talk gets roughly 20 slides. It works reasonably well for narrative, spoken presentations where each slide supports a point you're making out loud.

It breaks down in a few specific situations I run into constantly:

  • Data-heavy slides where the audience needs 30–60 seconds just to read a chart before you start talking about it — the slide "costs" more time than the rule assumes.
  • Transition or divider slides (section headers, agenda recaps) that take five seconds but still count toward your total, quietly inflating the number without adding content.
  • Q&A-driven sessions where you might spend three minutes on slide 4 and skip slides 9 through 14 entirely depending on what the room asks about.

I wouldn't recommend applying this rule rigidly to anything with dense visuals or an unpredictable audience. It's a starting estimate, not a target.

Format changes the answer more than topic does

The biggest variable most advice on this topic skips is how the deck will actually be consumed. A hypothetical example: imagine the same quarterly update built three ways — as a live executive readout, as an async Slack-shared PDF, and as a self-guided onboarding walkthrough for new hires. Same content, three very different slide counts, because each format asks the deck to carry a different amount of the communication load.

A rough way I think about it:

  • Live, presenter-led talk: slides support you — keep them sparse, let your voice carry detail. Slide count tracks closer to speaking time.
  • Leave-behind or "read without me" deck: slides have to carry the full argument on their own, which usually means more slides, each doing less — because you're not there to fill gaps verbally.
  • Webinar or recorded walkthrough: a middle ground, but viewers can rewind, so slightly denser slides are more forgivable than in a live room.

One thing people overlook is that these three formats often get built from the same base deck by just trimming or duplicating slides, which is exactly how you end up with a 45-slide "leave-behind" that's actually a live pitch deck someone forgot to adapt. If you're starting from a structured base, a PowerPoint template built around a clear layout system makes that kind of format-specific trimming much less painful than reworking freeform slides.

A more durable method: count content units, not slides

Instead of asking "how many slides," I ask clients to count content units first — the number of ideas, data points, or decisions the presentation actually needs to convey. Then we decide how many slides each unit needs, which is rarely one-to-one.

A single idea might need:

  • One slide, if it's simple and visual (a single chart, a short statement).
  • Two or three slides, if it's a process or comparison that benefits from being built up in stages rather than dumped on one crowded slide.

This is where a lot of "keep slides simple" advice quietly fails people — it tells you to remove content from a slide, but doesn't tell you where that content should go instead. The answer is usually: onto its own slide, sequenced, not into a footnote or a smaller font. If you're mapping out a multi-stage idea like this, it's often easier with a purpose-built diagram layout than trying to force it into a generic bullet-point slide.

Working this way, your slide count becomes a byproduct of your content structure rather than a target you're trying to hit. In practice, that usually lands somewhere between 1 and 2.5 slides per content unit, depending on format.

When more slides actually help

There's a common mistake in treating "fewer slides" as automatically better. Splitting one dense slide into three simpler ones almost always improves comprehension in a live setting, even though it raises your count. I often notice teams resist this because they're anchored to a target number rather than to what the audience needs to process at each moment.

The trade-off worth naming: more slides means more transitions, and every transition is a small chance to lose momentum, especially if you're advancing manually and fumbling the clicker. If you're going to split content across more slides, it's worth investing a bit more in visual consistency — matching layouts, fonts, and color use — so the extra transitions read as one continuous idea rather than a series of separate ones. This is one area where the underlying layout and formatting structure of your deck matters more than people expect once slide count starts climbing.

A quick gut-check before you present

Before finalizing a deck, I run through three questions rather than counting slides:

  • Does every slide need me in the room to make sense, or does it need to stand alone?
  • If I removed this slide entirely, would the argument still hold together?
  • Am I building toward a single decision, or am I documenting everything I know about the topic?

If you're documenting everything you know, that's a report, not a presentation — and it should probably be formatted as one instead of forced into slides.

Next time someone asks you how many slides a deck should have, try answering with a question of your own: who's going to be looking at this, and will you be standing next to them when they do?