Pomodoro Timer

A full Pomodoro cycle in the browser: 25 minutes of focused work, a 5-minute short break, and a longer break after every fourth session. Every duration is adjustable, including how many work sessions trigger the long break, and the count of pomodoros you finish each day is kept in local storage so you can see the day's total without an account or a login.

Francesco Cirillo's technique is usually remembered as "work 25, rest 5", but the rule that makes it work is the one people drop: a pomodoro is indivisible. If something interrupts it, you do not pause the clock and resume — you void the session and start a fresh one. That sounds wasteful and is the entire point, because it turns "I'll just check this one message" into a decision with a visible cost. The breaks are equally non-negotiable in the original method: they are what stops the technique from being a stopwatch pointed at your own guilt.

The countdown here decrements once per interval tick rather than reading the wall clock, which matters if you switch tabs. Browsers throttle timers in background tabs — to once a second at best, far less in a tab that has been inactive for a while — so a timer left running behind another window can finish noticeably later than the clock on the wall says it should. Keep the tab visible if the exact minute matters, or treat the end-of-phase beep as the signal rather than the displayed number.

Two things are deliberately not saved. Your settings and the day's session count persist across reloads; the running timer itself does not, so refreshing the page restarts the current phase from the beginning. The daily count also resets when the date changes rather than rolling as a 24-hour window, so a session finished at 00:10 belongs to the new day even if the working session it was part of started the evening before.