Answer: Run 25-minute focus sessions with 5-minute breaks, customisable lengths and a log of completed pomodoros.
Focus deeply, rest intentionally
This Pomodoro timer runs the classic 25/5 focus cycle — 25-minute work sessions separated by 5-minute breaks, with a longer break after four rounds — right in your browser tab, with chimes and session counting.
The Pomodoro Technique, created by Francesco Cirillo in the late 1980s, is timeboxing made physical: a timer commits you to one task for one interval. Its power is less about 25 minutes specifically than about starting.
The canonical protocol from Cirillo's book: choose one task; set a timer for 25 minutes (one 'pomodoro'); work on nothing else until it rings; take a 5-minute break; after four pomodoros take a longer 15-to-30-minute break. If you're interrupted, the pomodoro is void — you handle the interruption and start a fresh one.
The rules encode two ideas. First, the timer is unbreakable: a pomodoro cannot be paused, which forces either genuine focus or an honest restart. Second, breaks are mandatory, not optional — recovery is what makes the fourth pomodoro possible. Cirillo named the method after the tomato-shaped kitchen timer he used as a university student.
The table shows common configurations. The 25/5 default suits focused knowledge work; longer 50/10 rounds suit deep work like coding or writing where re-entry into the problem is expensive; shorter 15/3 rounds help with admin chores or ADHD-style task initiation where starting is the hardest part.
Experiment deliberately: track sessions completed per configuration for a week each. The measure of a good interval is not comfort — it's how many rounds you complete before quality collapses.
| Focus / short break / long break (min) | Name | Best suited for |
|---|---|---|
| 25 / 5 / 15-30 | Classic Cirillo | General knowledge work |
| 50 / 10 / 30 | Deep work | Coding, writing, design |
| 45 / 15 / 30 | Ultradian rhythm | Long creative sessions |
| 15 / 3 / 15 | Micro-pomodoro | Admin, task initiation |
| 90 / 15-20 / 30 | Full cycle | Deep work with long re-entry |
The specific 25-minute number has no magic in the literature; what has support is the underlying structure. Studies on brief breaks from sustained attention (the 'vigilance decrement' literature, e.g. Ariga and Lleras 2011) found short diversions restored performance on long tasks. Evidence on 'attention restoration' similarly supports scheduled recovery.
Timeboxing itself is a well-established productivity practice: committing to a bounded interval reduces procrastination by shrinking the commitment ('just 25 minutes'), and a visible timer creates mild productive urgency. The technique's popularity persists because it packages these mechanisms into a zero-tool, zero-cost protocol.
Protect the break: stand up, look away from the screen, drink water — a break spent scrolling social feed isn't recovery for the attention systems that work drains. Silence notifications during pomodoros; the technique assumes one task, and notifications are interruptions by definition.
Adapt shamelessly. Developers often run 50/10; writers sometimes 45/15; students revising flashcards may prefer 20/5. Keep the invariant parts — one task per interval, a real break between, a longer break every few rounds — and tune the durations to your attention span and task type.
['Adaptations keep the method useful beyond solo desk work. Students pair pomodoros with active recall: one interval of practice testing, break, then review of misses. Teams run shared timers for focus blocks (some companies schedule org-wide no-meeting pomodoro hours), and stand-ups count completed intervals as a lightweight status metric.', "For deep work with expensive re-entry — debugging, proofs, long-form writing — extend the interval (50 or 90 minutes) and protect it harder: phone in another room, status set, one artifact open. The break discipline matters more, not less: research on sustained attention shows performance decays without genuine disengagement, and micro-breaks that never leave the screen don't restore it.", 'Finally, track honestly: log completed pomodoros and what each produced. After two weeks the data shows your real daily capacity and best hours — most people find 8 to 12 solid pomodoros is a full day, and that capacity is worth planning around rather than fighting.']
What is the Pomodoro Technique?
A time-management method created by Francesco Cirillo: work in 25-minute focused intervals ('pomodoros') separated by 5-minute breaks, with a 15-to-30-minute break after four rounds. One task per interval; an interrupted pomodoro restarts.
Why 25 minutes per pomodoro?
25 minutes was the length of Cirillo's original kitchen timer, not a research-derived optimum. What matters is the bounded commitment and enforced breaks. Many people use 50/10 or 45/15 for deep work — tune to your task.
What should I do during pomodoro breaks?
Genuinely rest: stand, stretch, look out a window, get water. Avoid feeds and email — research on attention breaks suggests brief, low-demand diversions restore focus better than switching to another screen task.
How many pomodoros should I do per day?
Cirillo's book treats 8 (about 4 hours of focused work) as a solid day; 16 is an extreme day. Quality beats count — 6 clean pomodoros on one hard problem outperform 12 fragmented ones.
Can I pause a pomodoro?
In the classic rules, no — an interrupted pomodoro is void and you start fresh. The strictness is the point: it trains you to protect focus and to handle interruptions quickly rather than surrender to them.