Event-defined timing · private rehearsal

Lightning Talk Rehearsal Timer

Match the event’s total slot, reserve time only when questions count inside it, rehearse through exact overtime, and compare runs without uploading your topic or slides.

Match the written event format

Presets start as talk-only slots. Add a Q&A reserve only when the organizer says questions count inside the total allocation.

Total slot: 1:00–15:00. Q&A may be zero; at least 0:10 must remain for the talk.

5:00 total · 0:00 elapsedTalk-only slot

Total time remaining

5:00

Ready — the full selected slot is available for the talk

SparkTalk ceiling: 600750 words at 120–150 wpm

Keyboard: Space start/pause · N save run · R reset · F fullscreen

Optional one-idea map

A scalable rehearsal aid, not a rule published by the conferences cited below.

Talk budget 5:00

Spark

0:000:45

Name the one question, surprise, or problem worth the room’s attention.

Core idea

0:452:45

Show the example, demonstration, lesson, or result that carries the talk.

Takeaway

2:454:15

Make the useful implication easy to repeat after the session.

Handoff

4:155:00

Finish the thought and hand the stage to the next speaker.

Session rehearsal log

Only durations and the Q&A reserve stay in this tab; no topic, code, claim, or slide is collected.

Complete or pause a rehearsal, then choose “Save run & reset” to compare another attempt.

Current published formats

“Lightning Talk” Does Not Mean One Universal Clock

A lightning talk is short by design, but its exact duration, question period, and slide policy belong to the event. Current conference instructions range from a one-minute option to five-minute talks and ten-minute slots that include audience discussion. That variation changes both the amount you can say and the moment when you must hand the room back.

Start with the latest speaker guide or acceptance email. Confirm whether the published number is speaking time or the entire stage slot, whether questions are inside it, and whether the organizer changes slides for you. Then configure the same conditions here and rehearse through the final second.

Before writing the ending

  • • Find the exact total allocation.
  • • Separate talk time from in-slot Q&A.
  • • Check slide count and file rules.
  • • Learn the stage and handoff cue.

Examples, not defaults

Compare the Rule Before Selecting the Preset

These 2026 organizer pages demonstrate why a configurable timer is more accurate than a fixed five-minute countdown. Each row links to the event’s own published instruction. Your current invitation can still override an older or general event page.

Published exampleClockOperational detailSource
PyCon US 2026Up to 5 minutesThe event also accepts a one-minute talk. Slides are encouraged, not required.Organizer page ↗
EuroPython 20265 minutesThe conference FAQ defines its lightning talks as five-minute presentations.Organizer page ↗
Akademy 20265 minutesNo Q&A is allocated, and the call recommends no more than three slides.Organizer page ↗
IPA Christchurch 202610 minutes totalQuestions and discussion are inside the slot; the presenter guide suggests about eight minutes of talk plus two minutes of Q&A.Organizer page ↗

Clock arithmetic

Protect the Total Slot, Not Just the Last Sentence

If an event gives ten minutes including two minutes of questions, the talk budget is eight minutes. The timer first counts down that speaking budget, changes to the reserved Q&A clock at the handoff, reaches 0:00 at the end of the full ten minutes, and then shows overtime. If questions happen after the slot, leave the reserve at zero.

Leave a small real-world margin for applause, a moderator transition, or one slow slide change. A rehearsal that touches the limit under ideal conditions is not yet schedule-safe.

10:00

Organizer’s total stage slot

− 2:00

Questions inside that allocation

= 8:00

Maximum talk budget before handoff

Editorial constraint

Make One Idea Survive the Speed

A short slot does not reward a normal talk played faster. Choose one audience-level problem, insight, demonstration, or story. The opening should make the question legible; the middle should provide the strongest example or evidence; the ending should state what the audience can now understand, try, or remember.

The optional four-beat map in the timer allocates 15% to the spark, 40% to the core idea, 30% to the takeaway, and 15% to the handoff. Those proportions are an editing aid, not a conference rule. Ignore them whenever the subject or event format needs a different shape.

Spark

Give the room a reason to care now.

Core idea

Use the clearest proof, example, or demo.

Takeaway

State the useful implication plainly.

Handoff

End the thought and return the stage.

Visual discipline

Slides Are a Tool, Not the Definition

PyCon US explicitly says slides are encouraged but not required. Akademy recommends no more than three. Neither fact creates a rule for another event; together they show that a lightning talk can work with a few purposeful visuals or none at all.

A slide should shorten the explanation: show the diagram, result, image, code fragment, or contrast that would take longer to describe. Delete title cards, agendas, dense bullet lists, and repeated conclusions when they consume more seconds than they save.

Test the actual mechanics

  • • Export in the required format and aspect ratio.
  • • Make code and chart labels readable from the back.
  • • Rehearse every click and animation at speaking pace.
  • • Prepare a sentence that replaces a failed live demo.
  • • Know whether a technician or the speaker advances.

Draft sizing

Use Word Counts as Ceilings, Then Rehearse Aloud

At 120–150 spoken words per minute, the rough ranges below describe uninterrupted speech. They do not account for audience response, a live demonstration, slide transitions, breathing, or questions. The timer recalculates the range from the talk budget after any Q&A reserve is removed.

1 minute

120–150 words

One crisp point

3 minutes

360–450 words

One point plus evidence

5 minutes

600–750 words

Room for a focused example

8 of 10 minutes

960–1,200 words

With two minutes reserved for Q&A

Three-pass practice

Measure Clarity, Mechanics, and the Handoff

One successful stopwatch run is weak evidence. Change one thing at a time, save each result, and compare whether the talk reliably finishes with enough room for the event’s transition.

  1. 1

    Idea-only pass

    Explain the central idea without slides. Ask a listener to repeat the takeaway in one sentence; revise the premise if they remember only the setup.

  2. 2

    Full technical pass

    Use the real deck, demo, microphone posture, transitions, and any organizer-defined Q&A reserve. Keep going when a phrase or click is imperfect.

  3. 3

    Schedule-protection pass

    Start from the actual introduction cue, finish the final sentence, and hand control back before the total slot ends. Save the run and repeat until the margin is dependable.

Conference-ready ending

Finish Before the Organizer Must Finish for You

Write a final sentence that makes sense even if no question follows. Do not introduce a new subject in the last seconds. When Q&A is inside the slot, stop the talk at the handoff signal and invite a question without spending the reserve on a second conclusion.

Watch the stage manager’s signals and respect a hard stop. The next speaker, captioner, technician, and audience schedule all depend on the same clock. A clean early finish is stronger than an important sentence delivered after the allocation has expired.

Lightning-talk FAQ

Practical Answers Before the Next Run

How long is a lightning talk?

The organizer decides. Current published examples include one minute, five minutes, five to ten minutes, and a ten-minute total slot that includes questions. Read the current event instructions instead of assuming that every lightning talk is five minutes.

Does a lightning-talk slot include Q&A?

Sometimes. Akademy 2026 specifies no Q&A, while IPA Christchurch 2026 includes questions and discussion inside its ten-minute allocation. Set a reserve only when the organizer says that Q&A consumes the published total slot.

How many slides should a five-minute lightning talk have?

There is no universal slide count. PyCon US says slides are encouraged but not required, while Akademy recommends no more than three. Follow the event rule and use only the visuals that make the single idea faster to understand.

How many words fit in a five-minute lightning talk?

A continuous delivery at 120–150 words per minute is about 600–750 words. Treat that as an upper planning range, not a script target. Slides, laughter, demonstrations, pauses, and the handoff all reduce usable speaking time.

What should I cut when the talk runs long?

Cut extra background, a second example, dense slide narration, repeated conclusions, and optional demo steps before increasing speaking speed. Protect the premise, strongest evidence or demonstration, useful takeaway, and clean handoff.

Is the four-beat map an official lightning-talk format?

No. Spark, core idea, takeaway, and handoff are an optional SpeechTimer rehearsal aid that scales to the available talk budget. The published event brief remains authoritative.

Does SpeechTimer save my talk or slides?

No. The tool does not request a title, topic, speaker name, script, slide deck, or recording. The optional rehearsal log keeps only timing results and the Q&A reserve in the current browser tab.

Continue rehearsing

Sources and independence

Format statements on this page were checked against the linked 2026 organizer pages for PyCon US, EuroPython, Akademy, and IPA Christchurch. They are examples of published variation, not universal standards or promises about a future edition. SpeechTimer is an independent rehearsal utility and is not affiliated with, endorsed by, or an official timer for those organizations or events.