Pomodoro Timer

How to Use the Pomodoro Timer

1. Pick one task before you click Start. The Pomodoro Technique works best when a single concrete objective occupies the full 25 minutes.
2. Press Start to begin the first work interval. The large mm:ss display and the progress bar both tick down together so the remaining time is legible at a glance.
3. Ignore interruptions until the work phase ends. If something truly urgent happens, either tap Pause or Reset and start a fresh pomodoro later - a half-finished interval does not count.
4. Take the 5-minute break that starts automatically. Stand up, look out a window, drink water. Do not doomscroll on the same screen you just worked on.
5. Repeat four times, then take a longer 15-30 minute break. The session counter tracks how many intervals you have completed in the current run.
6. Use Skip if your meeting ends early and you want to jump to the break, or Reset to abandon the current interval cleanly.

What This Tool Does and How It Works

Under the hood the timer is a small state machine with two phases (work and break) and a completed-session counter. On each tick it schedules the next update with setInterval at a 1 Hz cadence, but it does not rely on that interval for accuracy - the remaining time is recomputed from a stored Date.now() end timestamp every frame, so throttled background tabs, laptop sleep, or a dropped tick will never silently desync the display.

When the work phase hits zero the state transitions to break, a new 5-minute end-timestamp is set, and the progress bar switches colors. The counter for completed pomodoros increments only on a clean work-to-break transition, which is why Reset does not inflate your session count. Everything is held in Preact component state - there is no backend call, no Service Worker, and no attempt to reach navigator.serviceWorker, so a throttled or airplane-mode tab behaves identically to an online one.

When You Would Use the Pomodoro Timer

• Clearing a backlog of small tickets where each one fits inside a single 25-minute interval and the break forces a ship-or-park decision.
• Writing a tricky document section where the knowledge-worker urge to "just check Slack for a second" is what usually derails the hour.
• Pair programming with a driver/navigator swap at every interval so attention stays fresh and neither person monopolizes the keyboard.
• Studying for a certification exam where active recall in 25-minute blocks beats passive re-reading for hours.
• Getting started on a task you are procrastinating - committing to just one pomodoro is a low enough bar to break the freeze.
• Structuring a solo deep-work morning into four intervals with a long break at the end as a natural stopping point before lunch.

Common Pitfalls and Edge Cases

Treating every interruption as "pause the timer" defeats the point. Cirillo's rule is that a broken pomodoro is a discarded pomodoro - you cannot bank 17 minutes of work against the next one. Another trap is packing the 5-minute break with another cognitively heavy activity like reading a news feed; the break exists so the prefrontal cortex can rest, not to cram a different category of attention on top. Teams sometimes try to synchronize pomodoros across a whole office - this usually fails because meetings, on-call rotations, and individual rhythms collide. Use it solo or within very small pairs. Finally, remember that this implementation uses a fixed 25/5 cadence; if you genuinely need 50/10 or 90/20 ultradian cycles there are configurable tools elsewhere, but the default here exists to preserve the classic Pomodoro cadence Cirillo published.

The Pomodoro Technique in Context

Francesco Cirillo developed the technique in the late 1980s as a university student in Italy, naming it after the tomato-shaped kitchen timer (pomodoro is Italian for tomato) he used. He self-published the method as a short booklet in 1987 and later expanded it into the 2006 book The Pomodoro Technique. The psychology it leans on is legitimate: a bounded window reduces task-initiation anxiety, a visible countdown converts abstract "work" into a game with a clear finish line, and forced breaks fit attention-restoration research. It is not a silver bullet - most academic evidence is small-scale self-report - but the underlying mechanics are consistent with mainstream advice on sustainable focus.

Comparison to Other Focus Tools

Dedicated apps like Toggl Track, Be Focused, or Forest add features this page deliberately does not: cross-device sync, analytics dashboards, gamified streaks, and deep integrations with task managers such as Todoist or Linear. If you want to correlate pomodoro counts with shipped tickets over months, use one of those. Against a browser extension like Marinara or StayFocusd, this tool trades site-blocking for simplicity. Against a physical kitchen timer, the advantage is the session counter and the long-break nudge; the disadvantage is that you can close the tab in a moment of weakness. For a one-tab, zero-install, zero-data-collection focus session, this is the straightest line.