Pomodoro Timer — Online Focus Timer

The break is the part that does the work

A fixed working interval, a short break, repeated, with a longer break after several rounds. The defaults here are 25 minutes of focus, 5 minutes short, 15 minutes long, all editable, with a count of completed sessions.

Most people treat the 25 minutes as the technique and the break as an interruption of it. That is backwards, and it is why the technique tends to stop working for them after a week.

Two mechanisms, and neither is about the number 25

A bounded interval makes starting easier. Committing to 25 minutes is a much smaller decision than committing to a task, and starting is where avoidance actually happens. You are not deciding to finish the thing; you are deciding to sit with it for 25 minutes, which is a decision you can make while still dreading it.

The break keeps the interval repeatable. Work through it and you borrow from the next one. Do that a few times and the method has quietly become ordinary uninterrupted work with a timer running — which is fine, but it is not the technique, and it does not produce the thing that made the technique useful.

The underrated part: it gives you a unit

Counting completed intervals turns "I worked on it today" into a number. And a number is what makes estimating possible.

Hours at a desk are a poor measure because they include everything that happened at the desk. Completed focus blocks are a measure of the work, so after a few weeks you can say a task of a certain kind takes four of them — which is a far more useful thing to know than that it took an afternoon.

Where it does not suit the work

Some tasks have a long spin-up. Debugging something intricate, or writing where the whole shape has to be held in mind, can take twenty minutes just to load — and an alarm at that point is a cost rather than a help.

Meetings, collaborative work and anything reactive do not fit it either, since you do not control the interval.

Lengthening the interval, or abandoning it for a particular task, is a reasonable response and not a failure. The technique is a tool for a class of problem, not a discipline to be loyal to.

Three ways it goes wrong

• Treating the timer as a target rather than a boundary — racing it, which reintroduces exactly the pressure the interval was supposed to remove.
• Spending the break on the same screen. Scrolling for five minutes is not rest; the eyes and the attention are still doing the same thing.
• Letting the ritual become the work. Configuring the timer is not progress on the task.

On the timing itself

The countdown is computed from the clock rather than by decrementing a counter each tick. That matters because browsers throttle timers in a hidden tab — a naive countdown loses time whenever you switch away, which is precisely when a focus timer is supposed to be running. Here the remaining time stays correct however long the tab has been in the background, and it catches up the moment you return to it.

Nothing is uploaded and no session data leaves the page. For measuring how long something actually took rather than bounding how long you spend, see the stopwatch.