I once watched a product demo running unattended at a trade show booth advance off a pricing slide before the visitor had finished reading the second line. Three seconds later it landed on a slide with one word on it and just sat there for another twelve. Nobody had done anything wrong, technically. Someone had gone into the timing settings, typed "8" into the "After" field, clicked Apply to All, and moved on. The deck ran exactly as configured. It just didn't run the way anyone reading it actually experienced it.
That gap — between "the timing is set" and "the timing works" — is where most guides on this topic stop short. The steps themselves are simple enough that you could probably guess them. What's harder to guess is why the same eight seconds that works fine on a title slide leaves people stranded on a slide full of numbers.
Setting fixed timing in PowerPoint
Open the Transitions tab, select a slide, and look at the Timing group on the right side of the ribbon. Under "Advance Slide," check the box next to After and enter a duration in seconds — this is the number of seconds PowerPoint will wait before moving to the next slide automatically. If you want every slide in the deck to use that same duration, click Apply to All. If you leave "On Mouse Click" checked as well, the slide will still advance manually if someone clicks before the timer runs out, which is worth keeping on for anything you might present live even once.
For a self-running version — a lobby display, a trade show loop, anything nobody's going to sit and click through — go to Slide Show → Set Up Slide Show and choose "Browsed at a kiosk." This locks the deck into full-screen loop mode using whatever timings you've set, and it ignores keyboard input except Esc, which matters more than it sounds like it should the first time someone at an event accidentally bumps a key and stalls the whole loop.
There's a second way in, and it's the one that actually produces good numbers instead of guessed ones: Rehearse Timings, under the Slide Show tab. Run through the presentation the way you'd deliver it, and PowerPoint records how long you actually spent on each slide. That's a meaningfully different number than "8 seconds felt about right when I typed it in."
Google Slides and Keynote work the same way, with different names
In Google Slides, go to Slide → Transition, and you'll find a "Slide duration" field in the right-hand panel. Set the number of seconds and either apply it to the current slide or click "Apply to all slides." There's no built-in rehearsal-recording feature here, so if you want per-slide variation, you're setting each one by hand — which, as it turns out, is often the better outcome anyway, for reasons that come up in a minute.
Keynote calls it the Start Transition setting. Select a slide, open the Animate panel, and change the transition's start behavior from "On Click" to "Automatically," then set the delay in seconds. Keynote applies this per-slide by default, which nudges you toward the more deliberate approach without you having to fight the software for it.
Where "one number for every slide" quietly falls apart
Here's the part that doesn't show up in most walkthroughs: a fixed duration assumes every slide takes the same amount of time to absorb, and that's rarely true even within a single deck. A title slide with four words needs two seconds. A slide with a data table needs fifteen, and probably closer to twenty if anyone in the room hasn't seen the numbers before. Apply the same eight seconds to both, and you've either wasted six seconds staring at a title or cut a table slide off before anyone's finished reading it.
This is really a reading-speed problem wearing a software-settings costume. According to Kelton Research's 2018 State of Attention Report for Prezi, a compelling narrative and strong visuals are what most business professionals say actually keeps them engaged with a presentation — which is a reminder that pacing built around your content's density, not a flat interval, is doing real work toward that, not just a nicety. A slide that gets cut off mid-thought doesn't feel narratively compelling no matter how good the design is; it feels like the software rushed you.
The fix isn't complicated, just less convenient than clicking Apply to All: set duration per slide based on how much there actually is to read on it, not a single guessed number applied everywhere. The word-count math that governs tightly timed pitches applies here too, just less extreme — figure out roughly how long a slide takes to read at a normal pace, and give it that, plus a couple of seconds of buffer.
Live delivery and unattended loops need different timing philosophies entirely
This is the trade-off most timing guides skip past: a self-running kiosk loop and a narrated live talk are not the same problem, even though they use the same checkbox. In a kiosk loop, the timing has to carry the entire meaning on its own, since there's no speaker filling gaps or explaining context — which argues for slower, more generous durations and simpler slides, since nobody's there to answer "wait, what did that mean?"
In a live talk, fixed automatic timing is honestly a bit of a trap. You're now racing the slide instead of pacing your delivery to the room, and if a question interrupts you or you slow down to make a point, the deck advances anyway, out of sync with what you're actually saying. Leaving "On Mouse Click" enabled alongside the timer is the safest middle ground — the automatic advance handles the parts where you don't need to think about it, and you retain the override for the parts where you do.
Testing timing like a script, not like a formality
One thing I'd recommend against: setting durations once, glancing at the deck to confirm it "looks fine," and calling it done. Timing errors are almost invisible when you're the one clicking through slowly to check them, because you already know what's coming. They only show up when someone unfamiliar with the content sits through the actual pace — which is exactly the audience the automatic version is built for.
If you're building the deck itself around a consistent grid and layout system rather than improvising slide by slide, timing calibration gets noticeably easier too — slides built on the same structure tend to hold roughly similar amounts of content, so the durations you set don't swing as wildly from one slide to the next. Starting from a template built with that consistency in mind saves some of that guesswork before you've typed a single number into the Timing panel.
Run the deck once with someone who hasn't seen it, and watch where they lean in or look away. That's a better timing report than anything in the settings panel.
Comments (0)