Speech timer
On time
Time left of 20 minutes
Bands are named as well as coloured: On time until 05:00 remains, Wrap up until 01:00, then Final minute, and Over time after zero.
This browser does not offer the Screen Wake Lock API, so the display can still dim or sleep while the timer runs. Set the screen timeout on the device before a talk or a class.
A presenter's clock with wrap-up and final warning bands that keeps counting when you run over.
What a speaker actually needs to see
Not the time of day, and not a wall of numbers: one figure, large enough to read from the back of a room, and an unmistakable signal of which part of the talk you are in. This timer gives you a single readout and three bands — on time, wrap up, and final minute — each labelled in words as well as coloured, so the signal survives a washed-out projector and colour-blind eyes alike.
Setting the bands
Set the total length of the slot, then the two thresholds. A twenty-minute conference talk usually wants wrap-up at five minutes remaining and the final band at one minute; a five-minute lightning talk works better at 1:30 and 0:30. The thresholds are measured in time remaining, which is how speakers think, and the timer will not let the wrap-up threshold fall inside the final band.
Over time keeps counting
When the clock reaches zero it does not stop and it does not hide. The readout switches to counting upward with a plus sign and the band changes to Over time, because a speaker who has run over needs to know whether that is by fifteen seconds or by four minutes. Chairs and session hosts get the same information from the back of the room.
Presenter mode
Full screen gives you a clean stage display with nothing but the band, the clock and the progress bar — no navigation and no advertising. Where the browser supports it, a screen wake lock keeps the display from sleeping mid-talk. Count-up mode swaps the readout for time used, for speakers who prefer to see how far they have come; the bands behave identically.
What the engine computes on every tick
Underneath, the speech timer is a count-up run. When you press start the page stores one number — the epoch at which the talk began — and on every tick it subtracts that anchor from the current time to get the elapsed milliseconds. Remaining time is the allotted total minus that elapsed figure, and the band is chosen from the remaining milliseconds alone: Over time at or below zero, Final minute at or below the final threshold, Wrap up at or below the wrap-up threshold, and On time above it. The three bands of the talk itself are On time, Wrap up and Final minute; Over time is the fourth state, the one past zero. Nothing accumulates from tick to tick, so a talk that has been running for an hour is read exactly as accurately as one that began a second ago, however irregular the ticks have been. The defaults, which you can change before the talk starts, are a talk of 20 minutes with wrap-up at 5 minutes remaining and the final band at 1 minute.
A worked example at a fixed instant
Take the default talk and start it at a fixed instant: 14 January 2026 at 09:00 UTC. The instant itself does not affect the figures; only the elapsed offsets below do. 12 minutes after the start, the engine reports 08:00 remaining, the band is On time, and the progress bar is 60% full. With count-up on, the very same instant shows 12:00 used instead of 08:00 left, and the band is still On time, because the band never looks at what the readout is showing — it is chosen from the remaining milliseconds whichever way they are displayed. The tab title at that moment reads 08:00 · On time, which is the readout and the band name joined with a dot, so the state is legible from a crowded tab bar without switching to the page.
Thresholds are inclusive: a walk through the bands
The thresholds are inclusive and the readout rounds seconds up, so the two agree at every boundary. One millisecond above the wrap-up threshold the readout shows 05:01 and the band is On time; at exactly 05:00 remaining the band is Wrap up. The moment the readout first shows 05:00 is therefore the moment the band changes — there is no second in which the clock reads 05:00 while the band still says On time. The same holds at the final threshold: at exactly 01:00 remaining the band is Final minute. With 400 ms remaining the readout shows 00:01 under the Final minute band, for the same reason that a talk 400 ms in still reads 20:00 rather than a second less: the display rounds up, so a fresh talk of 20 minutes reads 20:00 and a remainder is never shown as smaller than it is.
Over time, as the readout shows it
At zero the band is Over time and the readout shows 00:00. The plus sign appears with the first millisecond past zero, rounded away from zero like every other overtime figure, so 400 ms over reads +00:01. 1 minute 30 seconds past the end of the default talk the readout is +01:30, the band is still Over time, the line beneath the readout says “1 minute 30 seconds over the allotted 20 minutes”, the tab title reads +01:30 · Over time, and the progress bar is held at 100% rather than overflowing. With count-up on there is no plus sign to show, because time used simply keeps rising: the same instant reads 21:30 against a 20:00 total, and the Over time band and the line beneath carry the overtime instead.
How the thresholds are normalised
Every length you enter passes through one normalising step before it is used, and the same step runs on a shared link and on a restored session, so there is one set of rules whichever way settings arrive. The total is clamped to between 10 seconds and 8 hours. Each threshold is clamped to between zero and the total, and the wrap-up threshold can never sit inside the final band: ask for wrap-up at 02:00 with the final band at 03:00 and the final band wins, so wrap-up is raised to 03:00 while the final threshold stays at 03:00. That talk goes straight from On time to Final minute with no Wrap up band between — which is what a wrap-up threshold shorter than the final one must mean.
Bands are relative to your talk, not to the clock
The lightning-talk settings from above — a 05:00 talk with wrap-up at 01:30 and the final band at 00:30 — survive normalisation unchanged, and a shared link for them reads ?d=5m&warn=1m30s&final=30s&mode=down. They change what a given remaining time means: with 1 minute left, that talk is in the Wrap up band, where a default talk with 1 minute left is in the Final minute band. One consequence is worth knowing before you shorten a talk. Set a 03:00 total and leave the thresholds at their defaults, and the wrap-up threshold is capped at the total: it becomes 03:00 while the final band stays at 01:00. The talk then begins in the Wrap up band, and the idle display says so before you press start. That is the engine telling you the thresholds no longer fit the talk; set wrap-up to something below the total and the On time band returns.
Pause and resume
Pausing stores the elapsed time as a number and stops subtracting. Resuming moves the anchor so that the stored elapsed time is preserved and counting continues from it. In the fixed example, pausing 12 minutes in shows 08:00 remaining, and the readout still shows 08:00 after the talk has sat paused for 18 minutes, because nothing is being subtracted while it is paused. Resuming at that point re-anchors the run; 5 minutes later the engine reports 17:00 used, 03:00 remaining, and the band is Wrap up. Lengths are locked while the clock is running or paused — reset to change them — so the thresholds a talk was started with are the thresholds it finishes with, and the band can never jump because a setting moved under it.
Reload and the saved run
The running state is saved to this browser's local storage under the key wrldclock.timer.speech.v1 as epochs, never as seconds left, so a reload resumes where the wall clock says the talk should be rather than where the page last looked — including a reload after the device sat in a pocket. A saved run older than 12 hours is discarded and the timer opens idle. A running talk outranks a shared preset link: opening a link while a saved talk is running restores the talk, not the link; an idle or paused saved timer gives way to the link. Nothing about the run is sent to a server; the settings travel in the link and the run lives in this browser. The guide on shareable timer links lists the keys this timer reads.
Late ticks
Because the display is derived from the anchor whenever a tick runs, a tick that arrives late — whatever delayed it — reports the same figure an on-time tick would have. In the fixed example, a single tick 19 minutes in reports 01:00 remaining and the Final minute band: one subtraction against the anchor, with nothing counted in between and nothing to catch up. What the anchor guarantees is narrower and exact: whenever a tick does run, the readout and the band are correct for that instant, and a reload resumes from the stored epoch. It says nothing about whether a cue sounds at that instant, which depends on the device staying awake and the tab staying open — that part is described here, not simulated.
How to read the display
The stage shows four things, from the top: the band's name beside a megaphone icon; the giant readout; one line of plain words beneath it; and the progress bar. The readout is time left by default and time used with count-up on; past zero, in count-down mode, it is the overtime with a plus sign in front. The line beneath reads “Time left of 20 minutes” or “Time used of 20 minutes” during the talk, and once over it states the overtime in words — “1 minute 30 seconds over the allotted 20 minutes” in the example — so a chair at the back has the figure in two forms. The progress bar fills from zero to the total and stops there. Both the stage and the bar take the band's colour, but the name is always printed, so nothing depends on telling the colours apart.
Announcements, cues and the tab title
Entering Wrap up or Final minute is announced to screen readers with the band's name and a short hint — “Wrap up — Start moving toward your closing point.”, then “Final minute — Land the last idea and close.” — and the over-time announcement says that time is up and is marked assertive. An audible cue marks each change of band unless cues are muted. While the talk is running the tab title carries the readout and the band name — 08:00 · On time 12 minutes in — and reverts to the page title when the timer is idle.
What the timer does not do
It does not keep time on a server: the whole run — settings, anchor, mute state — lives in this browser, and a shared link carries nothing but the settings. The tab must stay open for the display to update; a reload within 12 hours resumes from the saved epochs. It does not stop at zero, hide the overtime, or round it in your favour: +01:30 means 1 minute 30 seconds over. It does not change the bands for count-up mode, and it does not choose a band from colour alone. It does not let the lengths change mid-talk; reset first. It does not keep a record of past talks, time individual sections within a talk, or run two talks at once. Where the screen wake lock is unsupported it says so plainly rather than pretending the screen will stay awake; that is a note the page reports about this browser, described here and not simulated.
Common misreadings
“05:00still looks safe.” It is not: thresholds are inclusive, and the band changes the moment the readout first shows the threshold. “The plus sign means time remaining.” The plus sign only ever appears past zero in count-down mode; +01:30 is 1 minute 30 secondsof overtime. “Count-up moves the bands.” It does not — 12 minutes in, both modes show the On time band. “The idle display is already in Wrap up, so something is wrong.” The total has been set below the wrap-up threshold and the threshold has been capped at the total; lower it. “Pausing lost time.” A paused readout does not move, and the resumed figure continues from where it stopped. “The readout is a second fast.” Seconds round up, so 00:01 is shown with 400 ms remaining and a fresh talk reads 20:00; the band is chosen from the exact remaining milliseconds, so it is not shifted by the display's rounding-up.
Further reading
The guide to speech timer warning bands works through the thresholds, the band selection and the over-time display in more detail, and the methodology page sets out how every timer on the site keeps time from epoch anchors. Everything described here runs in your browser; the figures on this page were computed from the engine when the page was built.
Questions
- Can I hand the timer to a room without explaining it?
- Yes. Copy preset link produces a URL such as ?d=18m&warn=5m&final=1m, so a conference organiser can send every speaker the same configured link. Nothing is stored on a server; the settings travel in the URL.
- What happens when the speaker runs over?
- The timer keeps counting, showing how far past the allotted time the talk has gone, and the band changes to Over time with both a colour and a written label. It never freezes at zero.
- Will the screen dim during a talk?
- The timer requests a screen wake lock while it is running and this tab is visible. Some browsers do not offer that API; where that is the case the page says so plainly, and you should set a longer screen timeout on the device.
- Is colour the only warning signal?
- No. Every band shows its name — On time, Wrap up, Final minute, Over time — next to the clock, an audible cue marks each change unless muted, and the change is announced to screen readers.
- Can I count up instead of down?
- Yes, with the count-up toggle. The readout shows time used rather than time left; the warning bands and the over-time behaviour are unchanged.
- What are the default lengths?
- A talk of 20 minutes with wrap-up at 5 minutes remaining and the final band at 1 minute. All three can be changed before the talk starts, and the preset link for the defaults reads ?d=20m&warn=5m&final=1m&mode=down. The total can be set anywhere from 10 seconds to 8 hours.
- What if I put the wrap-up threshold inside the final band?
- The engine raises wrap-up to match the final threshold. Asking for wrap-up at 02:00 with the final band at 03:00 gives wrap-up at 03:00, so that talk goes from On time straight to Final minute. Thresholds above the total are capped at the total.
- What happens if a shared link has a mistyped value?
- The parts that parse are used and the rest keep their defaults. A link reading ?d=18m&warn=five&final=1m opens a talk of 18:00 with wrap-up at 05:00 and the final band at 01:00: the mistyped wrap-up value is ignored and the default stands, so a mangled link still opens a working timer.