How many Pomodoros before a long break, and why four

What the method actually specifies

The Pomodoro Technique was worked out by Francesco Cirillo in the late 1980s, using a kitchen timer shaped like a tomato — a pomodoro in Italian. The core loop is simple: work for one timer interval, record the interval, take a short break, repeat. The conventional parameters people attach to it are 25 minutes of work, a 5-minute break, and a longer break of 15 to 30 minutes after four completed intervals.

Those numbers are worth taking seriously as a default and worth taking with a grain of salt as a rule. Cirillo was solving a practical problem — how to keep track of time and resist the urge to switch tasks — with a physical timer and a sheet of paper. He tuned the interval by experiment, not by measurement of attention spans. The four-interval cycle is a convention that has been copied so many times it now looks like a law of nature.

Where "four" comes from, mechanically

Two hours. Four intervals of 25 minutes plus three short breaks of 5 minutes comes to 115 minutes of wall clock, and if you count the 5-minute break that precedes the long one, almost exactly two hours. That is a familiar block: a lecture, a class period, half a morning, the length of a film. The cycle probably survived because it maps onto existing schedules rather than because it maps onto a brain rhythm.

It is also a tidy unit for planning. "Six Pomodoros of writing" is easier to schedule and estimate than "two hours of writing", and the breaks are built into the estimate instead of being stolen from it.

What the break research actually supports

The useful findings are about short breaks in general, not about four of them. Sustained attention declines over time — the vigilance decrement is one of the more reliable effects in the literature — and brief interruptions that let attention recover reduce that decline. A 2022 meta-analysis of workplace micro-break studies found small but consistent benefits for short breaks, with the clearest effects on fatigue and vigour, and some benefit for performance on tasks that demand sustained attention.

What that literature does not give you is a magic number. It does not say 25 minutes rather than 40, or four intervals rather than three. The evidence supports the shape of the method — work in bounded blocks, break before you are depleted, stop checking work during the break — not the specific dial settings.

The 90-minute "ultradian rhythm" story you will see attached to focus advice is a further extrapolation. A rest-activity cycle of roughly 90 minutes is well documented in sleep and in some physiological measures; importing it wholesale into waking desk work as "the brain's natural focus block" goes beyond what the evidence supports. If 90 minutes works for you, it is because it fits the task and your schedule, which is a good enough reason.

Why the long break is the part people skip

A 5-minute break is easy to justify. A 20-minute one feels like theft from the working day, so it is the first thing to disappear when a deadline approaches — exactly when it is most needed. There are two arguments for keeping it.

The first is cumulative recovery. Several short breaks reduce fatigue but do not fully reverse it; a longer interruption once every couple of hours is what stops the afternoon from becoming a slow decline into low-quality output. If you have ever had a morning where you were sharp at nine and useless by eleven-thirty, you have felt the difference between micro-recovery and actual rest.

The second is that the long break can hold things the short ones cannot: food, daylight, movement, a conversation. Those are the interventions with the best evidence behind them for restoring cognitive performance, and they do not fit into five minutes.

What the break has to be, to count

Attention residue is the reason a "break" spent scrolling a feed often leaves you more scattered than before. The mind keeps a thread of the interrupted task — and of whatever you scrolled — active, so the break never functions as a genuine switch. The practical test is simple: after the break, can you tell what you are about to do next? If yes, it was a break. If you have to re-read your own notes to remember, it was a different task.

Things that reliably work, in descending order of evidence: stand up and move; go outside or look out of a window at something far away; drink water; talk to someone about something else. Things that reliably do not: email, social feeds, "just checking" the thing you were working on, and any puzzle that is cognitively demanding enough to compete — which is most of them, including the ones on this site. A puzzle is a good cognitive change of scenery once; the third one in a row is procrastination with a nicer name.

Choosing your own cycle

Four is a fine starting point. If you want to tune it, tune it against the task rather than against folklore:

• Shallow, interruptible work — email, admin, triage. 25/5 is well matched. The cost of stopping is low, so break often.
• Writing and reading — 45 to 50 minutes of work with a 10-minute break. Composition needs a longer runway before the ideas arrive; five minutes is not enough to get back into a paragraph.
• Programming or anything with heavy state — 50 to 90 minutes, because reloading context costs more than the fatigue saved. Use a longer, cleaner long break afterwards.
• Learning something new — shorter intervals and shorter breaks, because the limiting factor is consolidation rather than stamina.

Then set the long break threshold by feel with one rule attached: when the 5-minute break stops restoring you twice in a row, take the long break early. That signal is more informative than the count. The timer's job is to make you notice the signal, not to overrule it.

The honest summary

Four Pomodoros is a convention with a satisfying arithmetic justification and no direct experimental support. The parts of the method that are supported are unglamorous: define the task, work on only it, stop on a timer rather than on depletion, and take breaks that are genuinely different from the work. Those four things survive any change to the numbers.

Try it yourself

Run one cycle with the default 25/5 and one with 50/10 on a task of roughly the same difficulty. Note when your attention first slips, not when the timer rings. One of the two will fit the work better, and you will know which within a morning.

Open the Pomodoro timer  →

Editorial note: The 4-interval cycle is a convention, and optimal interval lengths vary by task and person. Claims about a universal 90-minute focus rhythm should be treated as popular advice rather than established science.