InfyCalculator
📈

Presentation Slide Count & Timing Calculator

How many slides for a talk of a given length, how long your current deck will run, or how many slides and minutes your script needs — by pace (1 slide per 1–3 minutes, rapid Ignite-style slides or your own), with Q&A, demos and buffer, a word budget, a run-of-show timetable and rehearsal targets.

Work out
Total slot length
Q&A / discussion reserved
Demos, videos or exercises inside the talk
Style
Time per slide
Slides you currently have (0 to skip)
Speaker-note words per slide
Script length
Or paste your script or speaker notes
Your speaking pace
Automatic buffer (8% of the slot, 1–10 min)
Buffer
Main sections
Loading calculator…

How it works

Speaking time = slot − Q&A − demos − buffer (8%, 1–10 min, or your own); slides = speaking time ÷ minutes per slide (3 dense, 2 standard, 1 visual, 0.3 rapid, or your own); words = speaking time × wpm; deck run time = slides × time per slide (or words per slide ÷ wpm) + Q&A + demos + buffer; script time = words ÷ wpm

The right number of slides follows from the minutes you will actually speak, not the length of the slot. Subtract questions, demos and a buffer for the late start and the projector fight, then divide by a realistic time per slide. Business and conference decks average about two minutes per slide, dense training or data reviews three, and image-led storytelling one. Rapid formats like Ignite fix 15–20 seconds; you can also set your own pace. The calculator works three ways: slides for a slot, the run time of a deck you already have (from the style or from the words in your speaker notes), or slides and minutes for a finished script, which you can paste in to have the words counted. The word budget matters just as much — at 140 words a minute a 20-minute talk is only 2,800 words, roughly eleven typed pages. It is the reason most talks run long: speakers script for the slot, not the speaking time. The run-of-show table splits the talk into opening, sections and close with start times, so you can check your pace in rehearsal. Rehearse to finish under time, because adrenaline, laughter and clicker fumbles add 10–15% on the day.

Worked example

A 30-minute slot with 5 minutes of Q&A, a 4-minute demo and a 2.4-minute buffer leaves 18.6 minutes of speaking — about 9 slides at a business pace (range 7–12) and 2,600 words at 140 wpm. A 22-slide deck would need around 44 minutes at that style, so it should be cut or merged by roughly half. Switch to “Run time of my deck” and the same 22 slides come to 44 + 5 + 4 + 2.4 = 55.4 minutes, 25.4 minutes over. A 2,000-word script at 140 wpm takes 14.3 minutes, about 7 slides, and fits the slot with 4.3 minutes to spare.

Frequently asked questions

How many slides do I need for a 10, 20 or 30-minute presentation?

At a business pace of about 2 minutes per slide, plan on 4–5 content slides for 10 minutes of speaking, 10 for 20 minutes and 15 for 30 — fewer if part of the slot is Q&A. Visual, image-led decks run about twice as many. The table under the results lists other lengths at your chosen pace.

How long will my presentation take?

Choose “Run time of my deck” and enter your slide count. The calculator multiplies it by the time per slide for your style — or, if you know the words of speaker notes per slide, by words ÷ speaking pace — then adds Q&A, demos and buffer and compares the total with your slot.

How many words should my script be?

Multiply your speaking minutes by your pace: at 140 words a minute, 10 minutes is about 1,400 words. Paste a script under “From my script” to have it counted and timed.

Is there a slide limit?

No rule — Guy Kawasaki’s 10/20/30 (10 slides, 20 minutes, 30-point font) is a pitch heuristic; keynote speakers often use 60+ image slides in 40 minutes. What matters is time per idea.

Do build/animation steps count as slides?

Count each click that changes what the audience reads as a partial slide (~half); builds slow you down more than they seem.

Related calculators

Planning estimate based on industry-average rates; your narrator, editor or team will run faster or slower, so calibrate against one finished piece.