What this page is, and what it is not claiming
The 25-minute work block followed by a 5-minute break is the convention popularised by the Pomodoro Technique, a time-management method Francesco Cirillo began developing in the late 1980s and named after the tomato-shaped kitchen timer he used. That is the entire historical claim this page makes, and it is the only one we are confident stating.
What we are deliberately not doing is attaching research findings to the split. You will find plenty of pages asserting that twenty-five minutes matches some natural attention span or produces a measured percentage gain in output. We have not verified any of that, so we are not repeating it. Treat 25/5 as a workable default that a lot of people like, not as a result.
What can be stated exactly is the arithmetic, and that is what the tables below are: one full pomodoro cycle is 30 minutes of wall-clock time, so cycles land on the half hour and a run of eight takes exactly 4 hours. Every figure in both tables is computed by the same function the tests exercise, from a start time of 09:00.
Eight cycles, to the minute
This is the schedule the tool actually runs: plain 25/5 alternation, no long break. Focus time is the total work you have banked once that block is done; the elapsed column is wall-clock time from the start, including breaks.
| Cycle | Work ends | Break ends | Focus banked | Breaks taken | Elapsed total |
|---|---|---|---|---|---|
| 1 | 09:25 | 09:30 | 25 minutes | 1 | 30 minutes |
| 2 | 09:55 | 10:00 | 50 minutes | 2 | 1 hour |
| 3 | 10:25 | 10:30 | 1 hr 15 min | 3 | 1 hr 30 min |
| 4 | 10:55 | 11:00 | 1 hr 40 min | 4 | 2 hours |
| 5 | 11:25 | 11:30 | 2 hr 5 min | 5 | 2 hr 30 min |
| 6 | 11:55 | 12:00 | 2 hr 30 min | 6 | 3 hours |
| 7 | 12:25 | 12:30 | 2 hr 55 min | 7 | 3 hr 30 min |
| 8 | 12:55 | 13:00 | 3 hr 20 min | 8 | 4 hours |
The property worth noticing is that a 25/5 cycle is exactly half an hour, so a run started on the hour puts every cycle's end on the hour or the half hour. The work blocks themselves end five minutes earlier — at 09:25 and 09:55, not on the grid — which is exactly what the Work ends column above shows. Started at 09:00, the eighth block ends at 12:55 and the session closes at 13:00. That makes the cycle unusually easy to plan a day around — the same property the 15 minute timer page describes for the quarter-hour grid.
The variant with a long break
The classic technique replaces every fourth short break with a longer one. The tool leaves that decision to you: a fifteen-minute break is a choice about your day, and a countdown is in no position to make it. Here is what it costs, computed the same way.
| Cycle | Break length | Work ends | Break ends | Elapsed total |
|---|---|---|---|---|
| 1 | 5 min | 09:25 | 09:30 | 30 minutes |
| 2 | 5 min | 09:55 | 10:00 | 1 hour |
| 3 | 5 min | 10:25 | 10:30 | 1 hr 30 min |
| 4 | 15 min (long) | 10:55 | 11:10 | 2 hr 10 min |
| 5 | 5 min | 11:35 | 11:40 | 2 hr 40 min |
| 6 | 5 min | 12:05 | 12:10 | 3 hr 10 min |
| 7 | 5 min | 12:35 | 12:40 | 3 hr 40 min |
| 8 | 15 min (long) | 13:05 | 13:20 | 4 hr 20 min |
Twenty minutes of extra rest across a morning, and the neat half-hour alignment is gone from the fifth cycle onward — the trade is real in both directions, which is why the tool does not decide it for you.
Where the cycle actually breaks
Three failure modes come up far more often than any question about the length of the blocks.
- The break that becomes the session. A five-minute break is only five minutes if something ends it. This is the single strongest argument for letting the timer roll into the next phase on its own rather than waiting for you to press start — the moment the decision to resume is yours, the break is negotiable.
- The interrupted block. A pomodoro that gets interrupted at minute eighteen is not a pomodoro, and pretending otherwise makes the count meaningless. Reset and start it again; the counter only moves when a full work block completes, which is the honest accounting.
- The tab you closed. Nothing is stored between visits. Close the tab and the cycle count is gone. If the number matters to you, write it down — a browser page is not a record.
How the timing works underneath
Each phase is an ordinary countdown from this site, with the same guarantee: when the phase starts, the instant it should end is recorded, and every animation frame subtracts the current clock reading from it. Nothing is accumulated tick by tick, so a throttled or briefly frozen tab cannot make a work block quietly longer than the next one. The alarm for each phase is booked on the browser's audio clock when the phase begins, which is what lets it sound on time while you are in another tab — the situation a focus timer lives in almost by definition.
The measurements behind that design, including what a naive tick-counting timer actually loses when the thread freezes for three seconds, are published in full on the online countdown timer home page — measured in Node v22.20.0 on one Windows desktop, with no browser involved, which is a limit worth knowing before you lean on the figures. One caveat specific to a focus timer: a browser may suspend a silent audio context in a hidden tab, so a phase whose alarm matters is a phase worth leaving visible. If you want a single block instead of a cycle, the 20 minute timer and 30 minute timer pages cover the two lengths nearest to a pomodoro.