Interval timer
Get ready
0 of 8 rounds done
08:50 left in the whole session
This structure runs 8 minutes 50 seconds end to end, of which 5 minutes 20 seconds is work.
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.
Rounds of work and rest with optional prepare and cool-down phases, and a cue for each.
How a session is built
A session is a lead-in, then a run of rounds, then a cool-down. Each round is a work interval followed by a rest interval, and the rest after the final round is dropped automatically because there is nothing left to recover for. Set prepare or cool-down to zero to leave either one out. The stage always shows which phase you are in and which round you are on — round three of eight, in plain words.
Cues you can follow without looking
Each phase has its own audible cue: a double beep to get ready, a bright two-note rise into work, a single low tone for rest, and a three-note flourish at the end of the session. That matters when your eyes are on the floor or a bar. Every cue is paired with a visible phase change and a written announcement, and the whole set can be muted.
Common structures
The defaults are 40 seconds of work with 20 seconds of rest across 8 rounds. Another structure the compiler accepts is 30 seconds of work with 30 seconds of rest, repeated 10 times. A third is 20 seconds of work with 10 seconds of rest, repeated 8 times — the pattern commonly called Tabata; the name here describes the pattern only. To the timer all three are the same thing — numbers to compile — and it has no view on which, if any, you should use.
Timing you can trust mid-session
Every phase boundary is computed from the instant the session started rather than from counted ticks, so round 8 begins exactly where the arithmetic says it should, not late by whatever the ticks lost. Switch tabs, lock the phone, come back — the session is where it should be, and a reload resumes it rather than restarting it.
The plan the engine compiles
Before the clock starts, the session you have set is compiled into a flat plan: an ordered list of steps, each tagged prepare, work, rest or cool down, each with a length, and each with a cumulative offset from the start of the session. The defaults — 10 seconds to get ready, 40 seconds of work, 20 seconds of rest, 1 minute of cool-down and 8 rounds, every one of them yours to change — compile to 17 steps: one get ready, 8 work, 7 rest and one cool down. There are 7 rests rather than 8 because the rest after the final round is dropped when the plan is compiled, not skipped while it runs. The offsets are what make the plan useful. Work round 1 starts at 00:10, its rest at 00:50, work round 2 at 01:10, and so on until work round 8 starts at 07:10 and ends at 07:50; the cool-down runs from 07:50 to 08:50. The whole structure lasts 8 minutes 50 seconds, of which 5 minutes 20 seconds is work and 2 minutes 20 seconds is rest — the same two figures the page prints beneath the settings. Nothing about the plan depends on when you press start; it is the same list whether the session runs tonight or next year.
Where am I? One subtraction
When the session is running, the page stores exactly one thing about it: the instant it started. On every tick it subtracts that anchor from the current time to get the elapsed time, then walks the plan to the first step whose end offset lies beyond it. That lookup — not a countdown of its own for each phase — is what the stage displays. Some positions in the default session, each computed from a fixed elapsed value: at the start, the step is Get ready with 00:10 left in it. At exactly 10 seconds the position is already Work · round 1 of 8 with 00:40 left; 300 milliseconds later it still reads 00:40, because seconds are rounded up. At 3 minutes 25 seconds the position is Work · round 4 of 8 with 00:25 left, 3 rounds complete and 05:25 left in the whole session. At 5 minutes it is Rest · round 5 of 8 with 00:10 left and 5 rounds complete. At 8 minutes it is Cool down with 00:50 left and all 8 rounds done. At 8 minutes 50 seconds the plan reports the session complete with 00:00 left in the final step, and 5 minutes after that it reports exactly the same thing: the finish line is a fixed point, not a moving one. The engine can also list the step boundaries that fall between any two readings, in order. Between 3 minutes 25 seconds and 5 minutes it finds 3 ends crossed: Work · round 4 of 8, Rest · round 4 of 8, Work · round 5 of 8. The guide to rounds and phases walks the same lookup through more positions.
Other structures, compiled the same way
The compiler has no special cases for the structures described above; they are the defaults with different numbers. The twenty-on, ten-off pattern with 8 rounds and no lead-in or cool-down — fixed inputs of 20 seconds work and 10 seconds rest, with prepare and cool-down both set to zero — compiles to 15 steps. The first is Work · round 1 of 8 at 00:00 and the last is Work · round 8 of 8, ending at 03:50; there is no rest after it, so the session is 3 minutes 50 seconds long with 2 minutes 40 seconds of work. Set rounds to one and keep the other defaults, and the plan is just get ready, work, cool down — 3 steps, 1 minute 50 seconds in total — because the only rest in the structure would have followed the final round. Prepare and cool-down are left out of the plan entirely when they are zero rather than compiled as empty steps, which is why a session with both at zero begins on work round 1 at 00:00 and ends the moment the last work interval does.
What the settings will and will not accept
Settings are normalised before they are compiled, and that normalisation is the whole of the input checking. Rounds are held between 1 and 99: asking for 0 yields 1, and asking for 120 yields 99. Work must be at least 1 second — a work interval of zero is raised to it, since a round with no work is not a round — while prepare, rest and cool-down may all be 0 seconds, which is how they are switched off. Every phase is capped at 1 hour: a work interval set to 2 hours is held at 1 hour. A value below zero is raised to the floor, so a prepare of minus 5 seconds becomes 0 seconds, and a value that is not a number at all falls back to the default, so an unreadable round count becomes 8. Shared links go through the same normalisation after their own forgiving parse. Copy preset link for the defaults produces ?prepare=10s&work=40s&rest=20s&rounds=8&cooldown=1m; a hand-typed ?work=30&rest=30&rounds=10&prep=0&cool=0 opens the thirty-on, thirty-off session — 30 seconds of work, 10 rounds, 9 minutes 30 seconds end to end. Bare numbers are read as seconds on this timer, and every key has a short form: w, r, n, prep and cool; the guide on shareable timer links lists every key and token form. A token the parser cannot read is ignored and the default kept, so ?work=forty&rest=0:30&rounds=250 opens with work still at 40 seconds because forty is not a duration, rest at 30 seconds because 0:30 is, and 8 rounds because 250 is outside the allowed range.
How to read the stage
The stage shows five things, top to bottom. The phase label names the step the clock is in — Get ready, Work, Rest or Cool down — and every cue is paired with that visible change; it reads Session complete once the plan is finished, when the tab title says the same. The large readout is the time left in that step, never in the session: it opens each step at the full length of the step, and because seconds round up the last second of a work interval of 40 seconds reads 00:01; the readout does not show 00:00 until the whole session is complete. The line beneath it reads round and total during work and rest, as in Round 4 of 8, and switches to rounds done — 8 of 8 rounds done — during the lead-in, the cool-down and at the finish. The bar is progress through the whole session as a whole percentage: 39% at 3 minutes 25 seconds of the default 8 minutes 50 seconds. The quiet line under the bar is the time left in the whole session, 05:25 at that same moment. Once the session starts, the tab title carries the readout and the phase, so the position above shows as 00:25 · Work. Beneath the settings a footnote states the compiled totals before you start — for the defaults, that the structure runs 8 minutes 50 seconds end to end, of which 5 minutes 20 seconds is work — and the written announcement under the controls repeats each phase change in words.
Where the timer stops
The clock does not count, so it cannot fall behind: a late tick simply finds the elapsed time further along the plan. From a session started at 3 March 2026 at 18:30 UTC — a fixed instant chosen for the example — a run reads 3 minutes 25 seconds after 3 minutes 25 seconds; paused there, it still reads 3 minutes 25 seconds another 10 minutes later, and on resuming its anchor moves to 10 minutes after the original start so that the elapsed time continues from 3 minutes 25 seconds rather than jumping. What the clock cannot do is tick when the page is not there to tick, so the tab must stay open. The running session is saved as that anchor — an epoch, never a number of seconds left — under the key wrldclock.timer.interval.v1, and a reload within 12 hours reopens the page at whatever position the wall clock now implies, with the same structure; a saved session older than that is discarded and the timer opens fresh. A session in progress outranks a shared preset link, so following a link while one is running resumes the session rather than replacing it. Cues are raised by the page as it ticks, which has consequences that are described here rather than simulated: a boundary that passes while the tab is closed is not sounded, and audio cues may be suppressed while the screen is locked, which is why the timer requests a screen wake lock where the browser supports one. The structure is locked from the moment the session starts — through pauses and past the finish — until Reset, which returns to the start so it can be changed. At the finish line the readout freezes at 00:00 rather than running on. And it is a clock, not a coach: it offers no view on what the intervals should be.
Common misreadings
Five things are regularly read the wrong way. First, the round number on a rest step belongs to the work that has just finished, not the work that comes next: Rest · round 5 of 8 means round 5 is done and the next work interval has not begun, and the count of completed rounds at that moment is 5. Second, the readout is the step, not the session; the session figure is the quiet line beneath the bar, and the two agree only during the last step of the plan. Third, the readout never reaches 00:00 mid-session: the instant a step would read zero, the next step has begun and shows its full length, so the last displayed second of any step is 00:01. Fourth, the two totals are different quantities: 8 minutes 50 seconds end to end counts the lead-in, every rest and the cool-down, while 5 minutes 20 seconds of work counts only the work intervals, and neither includes time spent paused, because a pause keeps the elapsed balance and the plan is measured in running time. Fifth, and from links rather than the stage: a bare number in an interval-timer link is seconds, so work=40 is 40 seconds here, whereas the Pomodoro timer reads the same bare token as 40 minutes.
Questions
- What are the default settings?
- 10 seconds to get ready, 40 seconds of work, 20 seconds of rest, 1 minute of cool-down and 8 rounds. That compiles to 17 steps and runs 8 minutes 50 seconds end to end, of which 5 minutes 20 seconds is work. Every value can be changed before the session starts.
- Why is there no rest after the last round?
- Because it would be dead time. The session moves straight from the final work interval to the cool-down, or ends there if the cool-down is set to zero.
- Can I share a session with a class?
- Yes. Copy preset link for the defaults produces ?prepare=10s&work=40s&rest=20s&rounds=8&cooldown=1m — every duration token carries its unit and rounds is a plain count; a bare number in a hand-typed duration is read as seconds — and it opens the same session for anyone who follows it.
- Does the timer keep time if the phone screen locks?
- The clock itself does, because elapsed time is measured against the system clock rather than counted. Audio cues may be suppressed while the screen is locked, so the timer requests a screen wake lock where the browser supports one.
- What happens if I reload in the middle of a session?
- The running session is saved as the instant it started, never as seconds left, so a reload within 12 hours reopens it at the position the wall clock now implies, with the same structure. A saved session older than that is discarded and the timer opens fresh. The tab must be open for the clock to tick and for cues to sound.
- Why does the readout never show 00:00 during a step?
- Because seconds round up and the position is recomputed on every tick. A step shows its full length at its first instant, and the moment it would read zero the next step has already begun. The readout reaches 00:00 only when the whole session is complete, and it stays there.
- How many rounds can I set?
- Up to 99, with work, rest, prepare and cool-down each up to 1 hour. The page shows the total session length and how much of it is work.
- Is this suitable as medical or training advice?
- No. It is a clock. Choose intervals appropriate to your own fitness, and take advice from a qualified coach or clinician rather than from a timer.