Pomodoro timer
Focus
Focus interval 1 of 8
A full session of 8 intervals takes about 4 hours 5 minutes including breaks.
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.
Work in 25-minute focus intervals with short breaks and a longer break after every fourth.
Why fixed intervals help
Deciding how long to work is itself a decision, and decisions are the thing concentration is made of. A fixed interval removes the question: you work until the timer says stop, then you stop. The default here is the widely used pattern of 25 minutes of focus, a five-minute break, and a longer 15-minute break after every fourth interval — long enough to make progress, short enough that starting is never daunting.
How to run a session
Set your interval lengths and a session goal — eight focus intervals is a solid working day, four is a strong morning. Press start, or press the space bar. Each phase ends with a distinct chime and a visible change of state; with auto-advance on, the next phase begins immediately, and with it off each phase waits for you. Skip phase moves on without waiting, and counts the interval as done.
Breaks are part of the method
The break is not a reward for the work — it is what makes the next interval possible. Stand up, look at something further than arm's length away, and come back. If you routinely skip breaks, shorten the focus interval instead: a 20-minute interval you actually finish beats a 45-minute one you abandon.
Adjust the lengths to the work
Twenty-five minutes suits reading, admin and study. Deep work often wants 50 minutes with a 10-minute break; a long-break interval of two rather than four suits shorter sittings. Every length here is editable, and the session goal shows the estimated wall-clock length including breaks so a plan can be checked against the afternoon you actually have.
What the engine does, in its own terms
Underneath the buttons is a phase sequencer, and its header states the design in two sentences that the rest of this page unpacks. The first: the pattern is the widely used one — a fixed focus interval, a short break after each interval, and a longer break after every 4th — with the common defaults of 25 minutes of focus, a short break of 5 minutes and a long break of 15 minutes, every value configurable. The second: timing is anchored to epochs. When a phase ends, the next phase is chained from the previous phase’s end instant, not from the moment the tick noticed, so a hundred consecutive phases end exactly where arithmetic says they should, with no accumulated tick latency. Two further numeric defaults follow: a long break replaces the short break after every 4 focus intervals, and 8 focus intervals count as a finished session. All five numbers are defaults the settings panel lets you change, and the sixth setting, auto-advance, has a section of its own below. Every figure below was produced at build time by calling the same functions the timer runs, with fixed inputs stated in each example, and the site-wide version of this account is on the methodology page.
The default session, phase by phase
A default session is 15 phases long — rolling one forward to its end crosses exactly that many boundaries, and the engine's estimate sums exactly that many phase lengths — because a goal of 8 focus intervals ends on the last focus interval and the break that would follow it never starts. In order: Focus, Short break, Focus, Short break, Focus, Short break, Focus, Long break, Focus, Short break, Focus, Short break, Focus, Short break, Focus. That is 8 focus intervals, 6 short breaks and one long break; the long break follows the 4th focus interval, and the next would follow the 8th, which is where this session stops. Adding the phase lengths gives the estimate shown beneath the settings panel: a default session takes about 4 hours 5 minutes including breaks. Set the goal to 4 instead and the sequence is Focus, Short break, Focus, Short break, Focus, Short break, Focus — about 1 hour 55 minutes, with no long break, because the long break that would follow the 4th interval is precisely the break the session never reaches. Set the cadence to every 2 intervals and the first four phases become Focus, Short break, Focus, Long break. The preset quoted in the questions below, work=50m&break=10m&long=25m&every=3&goal=6, normalises to 50 minutes of focus, short breaks of 10 minutes, long breaks of 25 minutes every 3 intervals and a goal of 6; that session runs Focus, Short break, Focus, Short break, Focus, Long break, Focus, Short break, Focus, Short break, Focus and takes about 6 hours 5 minutes.
Why the next phase starts from the previous one's end
A timer that waits for a tick to notice a boundary and then starts the next phase from that tick is late by the tick’s latency every time, and across a session those latencies add up. This engine does the arithmetic the other way round. Start a default session at a fixed epoch — every example on this page uses an anchor of 1,800,000,000,000 milliseconds, a Date.now() value in the engine’s own terms, and because every figure is a duration measured from that instant its value is immaterial — and the focus interval is scheduled to end exactly 25 minutes later. Suppose the tick that notices that boundary arrives 3 seconds late, for whatever reason the tick interval was irregular. The engine still chains the next phase from the boundary: Short break is scheduled to end 30 minutes after the session started, not 30 minutes 3 seconds, and at the moment of that late tick the readout already shows 04:57 rather than a fresh 05:00. The lateness changed when the transition was noticed, never when it was deemed to have happened. Repeat that across the 15 phases of a default session and the last one ends precisely 4 hours 5 minutes after the first began, which is the figure the estimate promised. The cadence and the chaining are worked through at greater length in Pomodoro intervals as the engine runs them.
What happens while you are away
Because the display is derived from the anchor rather than from counted ticks, the engine does not care how long it has been since the last call. Its own header puts it plainly: rolling a session forward is safe to call from a 250 ms tick or after the tab has been backgrounded for twenty minutes, and the result is identical either way. Here is that claim computed. Start a default session at the same fixed epoch and make a single call 1 hour 4 minutes later. The engine crosses 4 phase boundaries in one pass, reports 2 focus intervals complete, lands in Focus — focus interval 3 of 8 — and shows 21:00 remaining, exactly what a page that had ticked all along would show. The same roll-forward runs on reload: the running state is saved as epochs, never as seconds left, so a reload picks the session up where the wall clock says it should be, including reloads that happen while the phone was in a pocket. One limit is built in: a saved session more than 12 hours old is discarded and the timer opens fresh and idle. Note what is described here rather than simulated. A closed page makes no calls, so no boundary is noticed and no chime sounds; when the page is next opened the arithmetic is caught up in a single step without a chime, and a written announcement says whether the session resumed or finished while the page was closed.
Auto-advance off, skipping, and the end of a session
Auto-advance is on by default, and with it on the next phase is already running by the time the boundary is noticed. Turn it off and the engine still crosses the boundary on the next call, but queues the following phase paused at full length rather than running it. With the default lengths, the same late tick after the first focus interval leaves the session in Short break, status paused, with 05:00 on the readout and the awaiting-advance flag set to true. Nothing counts down until you press start or the space bar, and because a queued phase is stored as a remaining balance rather than an end instant, however long you wait before pressing it the phase starts at its full length: press start on that queued break 1 hour after it was queued and the readout begins at 05:00, with the break scheduled to end 5 minutes after the press. Skip phase abandons the current phase and queues the next one the same way: skipping a fresh default focus interval leaves Short break queued, paused, with one focus interval counted as done — which is what the copy above means when it says a skipped interval counts. A session ends on a focus boundary, never on a break: when the goal is reached the engine marks the session finished and goes idle instead of queuing another break. A single call at the end of a default session's 4 hours 5 minutes crosses 15 boundaries, reports finished = true with 8 of 8 focus intervals complete, and the readout rests at 00:00.
How to read the display
The large readout is the time remaining in the current phase, formatted by the same function the four engine timers use. Seconds are rounded up, so a fresh default focus interval reads 25:00; one millisecond after starting it still reads 25:00, and it first reads 24:59 once a whole second has gone. Above the readout is the phase label — Focus, Short break, Long break — replaced by Session complete once the goal is reached; beneath it is the focus-interval count against the goal, and a row of markers fills in as intervals complete. While a phase is running the tab title carries the same information in compact form: with 21 minutes 30 seconds left in a focus interval it reads 21:30 · Focus, so the state is visible from another tab. Each boundary is also written out as a text announcement — which phase finished, which started and, with auto-advance on, how long it runs — paired with the chime, so nothing depends on hearing it. Every setting — the three lengths, the cadence, the goal and auto-advance — is locked once a session has started, and it stays locked after the session finishes, until Reset clears the session and unlocks them all. The note beneath the settings is the engine's session estimate for whatever lengths and goal are currently set, and it changes as you edit them.
Preset links, and what a mangled one does
Every value on this page can be set from the query string, which is what Copy preset link produces: for the defaults it builds ?work=25m&break=5m&long=15m&every=4&goal=8&auto=1, and opening that link configures the timer before you press start. Parsing is deliberately forgiving about form and strict about validity. Durations accept compound tokens such as 1h30m, clock tokens such as 25:00, and bare numbers read as minutes; counts must be whole numbers inside the engine’s range. Anything it cannot understand is ignored and the default is kept, so a mangled link still opens a working timer. Take the deliberately broken ?work=soon&break=10m&every=99: the focus token is not a duration, so focus stays at 25 minutes; the break token parses, so the short break becomes 10 minutes; and the cadence is out of range, so it is ignored rather than clamped and stays at every 4 intervals. A value that reaches the engine as a setting is treated differently from a token in a link: it is clamped to the engine’s range rather than dropped. A cadence of 99 becomes 12 and a cadence of 1 becomes 2; a goal of 99 becomes 24 and a goal of 0 becomes 1; a focus length of 100 hours becomes 4 hours, a ceiling the settings form’s own fields stop short of; one of a single millisecond becomes 5 seconds, and one that is not a number at all falls back to 25 minutes. Finally, a session already under way outranks a preset link, so opening someone else’s link mid-session carries on with your own; reset first if you want theirs. The guide on shareable timer links lists every key and token form the parser accepts.
What this timer does not do
It does not keep running while the page is closed. The engine computes rather than waits: with no page open there is no tick, and the session is caught up only when the page is next loaded, which is why the reload behaviour above matters more than it might first appear. It does not keep a history. What is saved is the current settings, the current session and whether the chime is muted; Reset replaces the session with an idle one, and there is no log of past sessions and no account, and nothing you enter is transmitted to our servers. It does not measure or predict your work. The opening sections of this page are the site's own usage notes; from the engine section onward, the page describes how the timer runs the pattern, the widely used one with the common defaults, and nothing in that description measures or predicts your work. And it does not guess at lengths: every value is either an engine default named above or one you set, and a value it cannot read is replaced by the default rather than by an estimate.
Common misreadings
A readout of 25:00 that seems to hold for a moment before 24:59 is the round-up rule, not a stalled timer: the display changes once a whole second has elapsed. A four-interval session with no long break is not a fault; the long break would follow the 4th focus interval, and the session finishes there instead. A transition that appears a beat late after a busy moment has not shifted the schedule: the following phase was chained from the boundary, and the readout already reflects the lateness. A preset link that seems to do nothing has usually met a session still under way, which outranks it; reset and open the link again. A count token outside the engine's range in a link is ignored, not clamped, so every=99 leaves the cadence at 4. A page that reads Session complete after an absence finished where the clock says it finished, not when you returned. And the estimate beneath the settings is a sum of phase lengths, nothing more: pauses, and time spent waiting with auto-advance off, are not in it.
Questions
- What are the default interval lengths?
- 25 minutes of focus, a short break of 5 minutes, and a long break of 15 minutes after every 4th focus interval. All four values, plus the session goal, can be changed.
- Can I share my configuration?
- Yes. Copy preset link builds a URL such as ?work=50m&break=10m&long=25m&every=3&goal=6, which opens the timer already configured. It is parsed entirely in your browser.
- Does the timer keep running if I switch tabs?
- Yes. Timing is computed from the system clock rather than from a tick counter, so a backgrounded tab catches up exactly when you return, and the tab title shows the remaining time while you are away.
- What happens if I reload in the middle of an interval?
- The session resumes where the clock says it should be, including any phase boundaries that passed while the page was closed. The phase, the cycle count and the remaining time are all restored.
- Is the chime required?
- No. The chime is generated in the browser with the Web Audio API and can be muted; every cue is paired with a visible change of phase and a written announcement, so nothing depends on hearing it.
- How long does a default session take?
- About 4 hours 5 minutes including breaks: 8 focus intervals of 25 minutes, 6 short breaks of 5 minutes and one long break of 15 minutes. The figure is the sum of the 15 phases the engine schedules; pauses are not included.
- Why does a four-interval session have no long break?
- Because a session ends on its last focus interval. With the default cadence the long break follows the 4th focus interval, and a goal of 4 finishes at exactly that point, so the sequence is Focus, Short break, Focus, Short break, Focus, Short break, Focus and the estimate is 1 hour 55 minutes. Raise the goal, or lower the cadence, and the long break appears.
- What if I come back after a long absence?
- A saved session is restored only if it is no more than 12 hours old; anything older is discarded and the timer opens fresh and idle. Within that window the session is rolled forward to the current time, crossing every boundary that passed while the page was closed, so a session that ended while you were away reads Session complete.
“Pomodoro Technique” is a trademark of Francesco Cirillo. WRLD CLOCK is an independent tool that counts 25-minute focus intervals and breaks; it is not affiliated with, endorsed by, or certified by the trademark holder, and no course, book or certification is implied. See our about page for who builds these tools.