The Pomodoro Technique, Explained

After reading this you can plan a work session as a repeating cycle of focus blocks and breaks, compute how long a run of rounds will take, and avoid the timing mistakes that make the method feel worse than working straight through.

What the Pomodoro technique is

The Pomodoro technique splits work into fixed blocks of focus separated by short rests. The classic block is 25 minutes of single-task work followed by a 5-minute break. After four focus blocks you take a longer break, usually 15 to 30 minutes. The name comes from a tomato-shaped kitchen timer (pomodoro is Italian for tomato).

The core idea is that a countdown running against you changes your behavior. When a timer says 25:00 and starts falling, you are more likely to close the extra browser tab and start the task you were avoiding. The break is not a reward you have to earn. It is a scheduled part of the cycle, which is why the technique repeats.

Here is a concrete run. You start at 9:00 with a 25-minute focus block. At 9:25 the timer switches to a 5-minute break. At 9:30 the next focus block begins. Repeat that four times and you reach 9:00 + 4 × 30 = 11:00, minus the last break you may skip, with four focused blocks behind you and a long break due.

When to use it, and when not to

The technique fits work that you can pause cleanly and resume: writing, coding, studying, email triage, clearing a backlog of small tasks. It works best when the problem is starting rather than sustaining. If a 25-minute countdown gets you to open the document, most of the value is already captured.

It fits poorly when interruptions are unavoidable or when the work has a long warm-up. A task that takes 20 minutes to load into your head, then flows for two hours, is hurt by a break at minute 25. In that case lengthen the focus block to 50 or 90 minutes, or do not use a fixed timer at all. Surgery, live support shifts and anything with hard external deadlines are not candidates for a self-imposed break schedule.

If breaks keep arriving at the wrong moment, change the block length before you abandon the method. A 25-minute block is a starting point, not a rule. Many people settle on 45 or 50 minutes of focus with a 10-minute break.

The timing math

A Pomodoro run is defined by four numbers: the focus length f, the short break s, the long break l, and the number of focus blocks between long breaks, n. One full group is n focus blocks, n-1 short breaks, and one long break at the end.

T_{\text{group}} = n \cdot f + (n-1) \cdot s + l

Here T_{\text{group}} is the total clock time for one group of rounds. The term n \cdot f is your actual working time. The break terms (n-1) \cdot s + l are overhead you accept in exchange for staying fresh.

The fraction of the group spent working is the useful ratio to watch:

\rho = \frac{n \cdot f}{n \cdot f + (n-1) \cdot s + l}

where \rho is the working fraction. With the classic numbers f = 25, s = 5, l = 15 and n = 4, the working time is 100 minutes and the total is 100 + 15 + 15 = 130 minutes, so \rho = 100/130 \approx 0.769. You work about 77% of the wall clock and rest 23%.

A worked example with the default settings

Four classic rounds starting at 9:00

Use the demo defaults: focus 25, short break 5, long break 15, long break after every 4 rounds. Start the clock at 9:00.

9:00 to 9:25, focus block 1 (25 min). Timer switches with a sound.
9:25 to 9:30, short break (5 min).
9:30 to 9:55, focus block 2. 9:55 to 10:00, short break.
10:00 to 10:25, focus block 3. 10:25 to 10:30, short break.
10:30 to 10:55, focus block 4. This is the fourth block, so the long break follows.
10:55 to 11:10, long break (15 min).

Check the math against the formula: T_{\text{group}} = 4 \cdot 25 + 3 \cdot 5 + 15 = 100 + 15 + 15 = 130 minutes. Starting at 9:00, the group ends at 11:10, which is 130 minutes later. Working time is 100 minutes, so \rho \approx 0.769.

The four 25-minute focus bars carry the work; the three short breaks and one long break add 30 minutes of overhead, for 130 minutes total.

Reading the cycle and pacing yourself

The timer gives you two signals: the number falling toward zero and the switch event at each transition. Treat the countdown as a soft budget, not a stopwatch you race. If you finish a task with 8 minutes left, do not stop the block. Use the remaining time to review, refactor or plan the next task. The block is a container, and a partly empty container still counts.

Count completed focus blocks, not tasks. A common tally is a mark per finished block. Four marks means a long break. Over a working day of, say, 6 hours you might fit 12 focus blocks (roughly three groups of four at 130 minutes each, which is 390 minutes, leaving time for lunch and slack). That is 300 minutes of tracked focus, a useful and honest number to compare across days.

The switch fires with a sound and an optional notification even when the tab is in the background in most browsers, so you do not have to keep the timer visible. Keep the tab open, though: closing it stops the countdown.

Common mistakes

Skipping breaks to "stay in flow." If you skip every short break, you have not done Pomodoro, you have done a long unstructured block that happens to have a timer. The breaks are what make repeated focus sustainable across hours. If you genuinely enter flow often, that is a signal to lengthen the block, not to delete the break.

Setting blocks too short. A 10-minute focus block with a 5-minute break gives \rho = 10/15 \approx 0.667. You rest a third of the time and never build momentum. Short blocks suit only tiny, well-defined chores.

Working during breaks. Checking email in the break defeats the recovery. The break should move your attention away: stand, look at something distant, get water. If you answer messages, the next focus block starts with a divided mind.

Counting interrupted blocks. If a colleague pulls you away for 6 minutes mid-block, that block no longer represents 25 minutes of focus. Restart it or mark it as broken. Otherwise your daily tally overstates your real focus.

Related timers on this site

If you want a plain elapsed-time count without rounds, use the Online Stopwatch, which also records laps and splits. For a single one-shot duration that ends in an alarm, the Countdown Timer is simpler than a full Pomodoro cycle. To be alerted at a specific clock time such as 14:30, use the Online Alarm Clock. If you coordinate focus sessions with people in other regions, check overlapping hours on the World Clock, and convert any 24-hour shift times with the Military Time Converter.

Frequently asked questions

Why 25 minutes and not 30?

Twenty-five minutes is the length the technique's originator used with a kitchen timer, and it happens to be short enough that starting feels cheap. There is nothing special about the number. If 30, 45 or 50 minutes fits your work better, use it; the math and the tool both adjust.

Should I take the short break away from the screen?

Yes if you can. The purpose of the break is to let attention recover, and a screen keeps the same visual and cognitive load. A 5-minute break spent standing or walking recovers more than 5 minutes of scrolling.

What happens if I close the browser tab?

The countdown stops, because everything runs locally in the tab. Keep the tab open to keep the timer ticking. In most browsers the sound and notification still fire when the tab is in the background.

How many focus blocks should I aim for in a day?

Eight to twelve completed 25-minute blocks is a realistic full day of focused work, which is 200 to 300 minutes. Beyond that, most people see quality drop. Track the count rather than the hours you sat down.

Can I make the long break shorter or skip it?

You can. The long break exists to reset attention after several rounds. If you feel fine, a 10-minute long break may be enough; if you are drained, 30 minutes helps more. Skipping it entirely tends to make the next group harder.

Try it yourself in the tool