RunToolRunPomodoro Timer
Boost productivity with the Pomodoro technique.
How to Use the Pomodoro Timer
Start a focus session
Begin a 25-minute work block and put distractions aside.
Take the short break
When the timer rings, rest for 5 minutes — step away from the screen.
Repeat and take a long break
After four focus blocks, take a longer 15–30 minute break.
What the technique actually proposes
Work in a fixed block, typically 25 minutes, then take a short break of about five. After four blocks, take a longer break of 15 to 30 minutes. The method was described in the late 1980s and named after a kitchen timer shaped like a tomato.
The specific numbers matter less than the structure. What the method really provides is a commitment device: for the length of one block you are doing one thing, and everything else waits. The timer is what makes that commitment external rather than a matter of willpower.
Why interruption is the real target
Returning to a task after an interruption is expensive — you have to rebuild the mental context you were holding. For anything with a lot of state in your head, such as debugging or writing, the recovery can cost more time than the interruption itself did.
A timed block gives you a defensible reason to defer interruptions rather than absorb them. The thought that arrives mid-block gets written down and dealt with in the break, which is usually both faster and better than acting on it immediately.
Breaks are part of the method, not a reward
The break is where the technique does half its work. Skipping breaks to maintain momentum produces a familiar pattern: strong output for two hours, then a sharp decline for the rest of the day. The break exists to prevent that decline, not to celebrate progress.
It works best as an actual change of state — standing up, looking at something further than arm's length, leaving the desk. A break spent scrolling on a screen provides very little of the recovery the method depends on.
When 25 minutes is the wrong number
Some work has a long warm-up. Complex problem-solving can take twenty minutes just to reach a productive state, and a timer that interrupts at that point is actively harmful. Longer blocks of 50 or 90 minutes suit that kind of work better.
Shorter blocks suit the opposite case: a task you are avoiding, where the barrier is starting rather than sustaining. Fifteen minutes is a small enough commitment to begin, and beginning is usually the whole problem.
What a timer cannot fix, and how this one runs
A timer imposes structure on time; it does not decide what to work on, and it does not help if the task is unclear. Time spent in a focused block on the wrong thing is still time spent on the wrong thing. Deciding what the block is for is the part that matters most and the part the tool cannot do.
The timer runs in your browser tab. Note that browsers throttle background tabs to save power, so timers can drift when the tab is hidden — keeping it visible, or relying on the completion sound rather than watching the countdown, is the reliable approach.