Pomodoro Timer

A Pomodoro timer is a work-break interval clock that divides your focused work time into fixed-length blocks separated by short breaks, with a longer break after every few blocks. The pattern was developed by Francesco Cirillo in the late 1980s and named after the tomato-shaped kitchen timer (pomodoro is Italian for tomato) that Cirillo used as a university student. The classical cadence is twenty-five minutes of focused work followed by five minutes of break, repeated four times before a longer fifteen- to thirty-minute break. This page describes how the Pomodoro Technique works, why the specific 25/5/15 cadence is the default, how to use the timer above, and how to adapt the durations to your own attention span and task type. The timer runs entirely in your browser, remembers your settings between visits, and supports keyboard shortcuts so you never have to leave the keyboard mid-focus.

The Pomodoro Technique is widely taught in universities, used by software developers, writers, designers, students, and translators, and forms part of many productivity books and courses. Its appeal is that it is small, mechanical, and falsifiable, you either worked for twenty-five minutes or you did not. That binary, low-friction measurement is what makes it durable; you do not need a journal or a habit tracker to know whether today was a good day.

How to Use the Pomodoro Timer

1. Pick the Work phase using the phase tabs (it is selected by default).
2. Click Start, or press the Space bar, to begin the 25-minute work block.
3. Work on a single task until the timer reaches zero. If a thought or interruption arrives, write it down and return to the task instead of breaking focus.
4. When the timer reaches zero you hear three short beeps and the timer auto-advances to the Short Break phase (default 5 minutes). Stand up, look away from the screen, drink water, stretch.
5. After the short break the timer auto-advances back to Work. Repeat this pattern.
6. After the fourth completed work block the timer auto-advances to the Long Break (default 15 minutes) instead of a short break. Use it for a real break, a walk, food, eye rest.
7. Reset restarts the current phase to its full duration. Skip advances to the next phase immediately. Both also work via the R and S keyboard shortcuts.

The settings panel lets you change the durations of all three phases, the number of work cycles between long breaks, whether audio cues play, and whether the timer auto-advances. All settings persist in your browser via localStorage so your next visit starts exactly where you left off.

The Timing

The Pomodoro Technique does not have a single numerical formula in the way a financial calculator does. Instead it has a timing rule, a cadence, that defines how long each phase lasts and how the phases alternate. The classical cadence is:

• Work block: 25 minutes
• Short break: 5 minutes
• Long break: 15 minutes
• Cycles between long breaks: 4 completed work blocks

Expressed as a sequence, one full Pomodoro "round" is: Work 25 → Break 5 → Work 25 → Break 5 → Work 25 → Break 5 → Work 25 → Long Break 15. After the long break the cycle counter resets and you begin a new round of four work blocks. The total elapsed time for one full round, including the long break, is 25 × 4 + 5 × 3 + 15 = 100 + 15 + 15 = 130 minutes, or just over two hours.

Why 25 minutes? Francesco Cirillo chose it because it is short enough that the cognitive cost of starting a hard task is low, committing to "twenty-five minutes" feels easier than committing to "the morning", and long enough to reach a state of genuine focus rather than a quick glance at the task. Research on attention and ultradian rhythms suggests sustained focus is difficult to maintain much beyond 90 minutes without a break, so a 25-minute work block sits well below that ceiling while leaving room for several blocks per session.

Why 5 minutes for short breaks? Long enough to actually disengage, stand up, refill water, look out a window, and short enough that you do not lose the thread of what you were doing. Why a longer break after every fourth block? After roughly 100 minutes of focused work the marginal value of an additional work block drops sharply; a 15-minute break gives your brain a real recovery cycle rather than a token pause.

The timer above lets you adjust any of these values. Many practitioners tweak them, some prefer 50/10, some prefer 90/20, some prefer 30/5. The cadence that you actually use consistently is the right cadence for you.

Real-World Worked Examples

Example 1, A two-hour focused writing session

You sit down at 09:00 to write a report. You click Start on a 25-minute work block. You write, uninterrupted, for 25 minutes. The timer beeps, you take a 5-minute break (stand up, look out the window). At 09:30 you start your second work block and write for another 25 minutes. By 11:00 you have completed four work blocks and taken three short breaks. The timer auto-advances to a 15-minute long break. By 11:15 you have had a real break, a snack, a walk around the room, and the cycle counter has reset. By 12:30 you have completed eight work blocks (roughly 200 minutes of focused writing) and taken the appropriate mix of short and long breaks. This is a realistic Pomodoro day.

Example 2, Studying for an exam with a customised cadence

You are studying for a difficult exam and find that 25-minute blocks are too short, you spend the first five minutes re-orienting yourself each time. You open the settings panel and change the work duration to 45 minutes and the short break to 10 minutes. You leave the long break at 15 minutes and the cycles-per-long-break at 3 (one long break every 135 minutes instead of 100). With these settings your session is: Work 45 → Break 10 → Work 45 → Break 10 → Work 45 → Long Break 15. Each round takes 170 minutes and contains three work blocks rather than four. The cadence is more relaxed, the focused blocks are deeper, and the overall session feels less interrupted.

Example 3, Quick task batching

You have a list of small administrative tasks, responding to twelve short emails, filing three invoices, booking two appointments. You do not want a long focus block; you want to clear the list. You set the work duration to 15 minutes, the short break to 3 minutes, and disable audio cues. You click Start and treat each 15-minute block as a sprint: clear as many items as you can before the beep. After three blocks you take a 5-minute break and reset. The cycle counter shows "Cycle 3 of 4" so you know when the next long break is coming. By mid-morning the list is clear and you have a Pomodoro log of three completed blocks to point to.

Example 4, Tracking the cycle counter over a week

The cycle counter on this timer persists across sessions via localStorage. If you complete three work blocks on Monday, four on Tuesday, two on Wednesday, and zero on Thursday, the counter still shows seven completed work cycles and "3 more until long break". On Friday you do two work blocks and the timer auto-advances to the long break because seven plus two is nine, and nine mod four equals one, so the next work block would have been followed by a short break rather than a long break, except that you manually skipped to the long break. The cycle counter is a low-friction way to keep an honest record of focused-work time across days.

Where Pomodoro Shows Up

The Pomodoro Technique is used across many disciplines and contexts. Software developers use it to break up long coding sessions and to write documentation without losing flow. Writers use it to ship articles and chapters in small, measured increments rather than waiting for a single multi-hour block of inspiration. Students use it to study for exams and to write dissertations in survivable chunks. Designers use it to alternate between focused creative work and short recovery breaks. Translators and editors use it to keep their focus sharp across long documents. Researchers use it to chunk reading and writing into manageable units. Even surgeons, pilots, and air-traffic controllers use analogues of timed focused work followed by breaks, the broader principle that sustained attention benefits from regular recovery is well established in occupational psychology.

Outside of individual work, Pomodoro-style cadences show up in classroom teaching (work periods separated by recess), in music practice (focused practice on one piece followed by a break before switching), in physical therapy (sets and rest intervals), and in cooking (active cooking followed by oven time as a built-in break). The specific 25/5 numbers are not magical, the underlying principle of bounded focus with regular recovery is.

Common Mistakes When Using a Pomodoro Timer

Mistake 1: Treating the break as part of the work. The break is for genuine disengagement. If you spend the 5-minute break scrolling social media on your phone or reading email, you have not actually rested; you have just changed context without recovering. Use the break to look out a window, walk around, drink water, or stretch. The quality of your break determines the quality of your next work block.

Mistake 2: Skipping breaks because you are "in flow". Flow is valuable but it is not infinite. Pushing through three work blocks back-to-back without a break tends to produce diminishing returns by the third block and visible fatigue by the fourth. Take the break. The break is what allows the next block to be a real work block rather than a tired imitation.

Mistake 3: Using the timer as a way to avoid starting. If you spend ten minutes tweaking Pomodoro durations, picking a task list, and deciding which task to start with, the timer is functioning as procrastination, not as productivity. Set sensible defaults (the timer ships with 25/5/15), pick a task, click Start, get to work.

Mistake 4: Making the work block too long. A 90-minute work block sounds disciplined but in practice it almost always fragments, you start the timer, work for 25 minutes, check email, work for another 15 minutes, get a message, work for another 10, and so on. The work block is not the time between starting and finishing; it is the time of actual focused attention. 25 minutes is a defensible default precisely because it is hard to fragment.

Mistake 5: Letting the cycle counter grow without resetting. If you do two work blocks today, two tomorrow, three the day after, and never take the long break that the timer suggests, the cycle counter will eventually mis-predict when the next long break should be. Use the "Reset cycle count" button if you know you have been off-cycle for a while.

Mistake 6: Ignoring the keyboard shortcuts. Pressing the Space bar is faster than clicking Start with the mouse, and keeping your hands on the keyboard keeps you in focus mode. The same is true of R to reset and S to skip. If you find yourself clicking the buttons, you are breaking flow.

Frequently Asked Questions

What is the Pomodoro Technique? The Pomodoro Technique is a time-management method developed by Francesco Cirillo in the late 1980s. It divides focused work into 25-minute intervals called pomodoros, separated by 5-minute short breaks. After every fourth work interval you take a longer 15- to 30-minute break. The technique helps reduce the cognitive cost of starting a hard task by breaking work into bounded, measurable blocks.

Why is it called Pomodoro? Pomodoro is Italian for tomato. Francesco Cirillo used a tomato-shaped kitchen timer during his university years and named the technique after it. The technique is named after the timer, not after the work pattern.

How long should a work block be? The classical default is 25 minutes, and most practitioners find that length a good starting point. Some prefer 15-minute blocks for shallow administrative work; others prefer 45- or 50-minute blocks for deep technical or creative work. The right length is the one you can consistently focus within for the full duration without fragmenting attention. Try the default for two weeks before changing it.

How long should a short break be? The classical default is 5 minutes. That is enough to stand up, refill water, and look away from the screen, but not long enough to lose the thread of the work. Avoid taking breaks longer than 10 minutes between work blocks, extended breaks make it harder to re-enter focus.

How long should a long break be? The classical default is 15 minutes, though many practitioners extend it to 20 or 30 minutes. The long break is a real break, not a token pause, use it for food, a walk, eye rest, or a genuine change of context. After the long break the cycle counter resets and a new round begins.

How many work blocks should I do per day? There is no universal answer; it depends on the type of work and your stamina. A reasonable starting target is eight completed work blocks (two rounds of four) per day, which represents roughly 200 minutes of focused work. Some practitioners reach twelve or sixteen blocks per day. Quality matters more than quantity, five deep work blocks are worth more than twelve fragmented ones.

Can I customize the durations? Yes. The settings panel on the timer above lets you change the work, short break, and long break durations, the number of cycles between long breaks, the audio cues, and the auto-advance behaviour. All settings are saved in your browser so they persist across visits. The defaults are the classical Pomodoro values; change them if your work demands it, but give the defaults a fair trial first.

Does the timer work offline? Yes. Once the page has loaded, the timer runs entirely in your browser. There is no server round-trip, no telemetry, no data sent off your device. The audio cues are synthesised in real time using the Web Audio API, the cycle counter is stored in localStorage, and the keyboard shortcuts are bound locally. You can use the timer on a plane or in a coffee shop with no internet connection.

Can I use the timer for tasks other than work? Yes. Pomodoro-style cadences work for studying, writing, coding, cleaning, exercising (set-based training), reading, language practice, music practice, and any other activity that benefits from focused bursts separated by recovery. Some people even use it for cooking, 25-minute active prep followed by 5 minutes of cleanup.

What happens if I close the tab while the timer is running? The timer stops because the JavaScript interval no longer runs. The phase and remaining time are not preserved across reloads, but the cycle counter, durations, audio setting, and auto-advance setting are preserved via localStorage. If you need a timer that survives a tab close, use a system-wide timer or a dedicated desktop app rather than a browser-based one.

Is there a way to track how many work blocks I do over time? This timer shows the cycle counter on screen and remembers it across sessions, but it does not keep a long-term log of completed work blocks. If you want a per-day or per-week log, pair the timer with a simple spreadsheet or note: each completed work block gets a tick mark, and at the end of the week you count the ticks. The Pomodoro Technique was designed to be light on infrastructure; a paper log is usually enough.

What if I miss a work block, should I restart the round? There is no rule that says you must restart the round if you miss a work block. Most practitioners treat missed blocks as lost time and resume from the next block. The cycle counter continues to count from where it left off. If you find you are missing many blocks in a row, that is a signal to look at why, typically the work block is too long for the task, or the task itself is unclear.

References

• Cirillo, F. (2006). The Pomodoro Technique. Self-published. The original exposition of the 25/5 cadence and the four-cycle-long-break rule.
• Knuth, D. E. (1997). The Art of Computer Programming, Volume 1: Fundamental Algorithms (3rd ed.), Addison-Wesley. Discusses the value of time-boxed work intervals in software practice.
• Newport, C. (2016). Deep Work: Rules for Focused Success in a Distracted World. Grand Central Publishing. Independent confirmation of the value of bounded, distraction-free work blocks.

Also try these free tools:

• Countdown Timer
• Sleep Calculator
• Habit Tracker Guides