The Pomodoro technique: what the break research says about 25/5

The Pomodoro technique is the most searched time-management method in our keyword database and the one with the thinnest direct evidence. Work for 25 minutes, rest for five, repeat. Almost every page explaining it treats the 25 as settled. It is not. The break research supports scheduled short breaks fairly well; it says nothing in favour of 25 minutes over 24, 50 or "until my attention fades", and the only head-to-head trials found no productivity difference between those options C^[6]. This guide explains the method as Francesco Cirillo wrote it, separates evidence from folklore, compares the variants, shows where a ringing timer damages the work it is meant to protect, and ends with a worked week. It pairs with our guides to time blocking, the Eisenhower matrix and how to prioritise tasks, which decide what goes into the intervals in the first place.

The method in two minutes

Cirillo developed the technique as a student in the late 1980s, using a tomato-shaped kitchen timer (pomodoro is Italian for tomato), and published it as a free guide in 2006 and a book in 2018 ^[1]. The core loop:

1. Pick one task and write it down.
2. Set a timer for 25 minutes and work on that task only.
3. When the timer rings, make a mark and take a five-minute break away from the work.
4. After four intervals, take a longer break of 15 to 30 minutes.

Three rules matter more than the numbers. An interval is indivisible: if you abandon it, it does not count. Interruptions get a fixed script (note it, promise to come back, do so after the interval). And you record every interval, which turns the day into a count you can review. Cirillo's framing is about estimating and protecting effort, not a biologically ideal span, and the book gives no study behind the 25 ^[1].

What the evidence supports and what it does not

No trial has tested the technique against a control group at a scale that could show whether it raises output. What exists is a handful of small student studies plus a larger literature on breaks, planning and interruptions. The table separates the two.

Component	What the research found	What it means for the method	Grade
Scheduled short breaks	A 2022 meta-analysis of micro-breaks (up to about ten minutes) found a small but reliable gain in vigour and a reduction in fatigue; performance improved for clerical and creative tasks but not for cognitively demanding ones [2]	The five-minute break is the best-supported part of the method, and it is supported as a wellbeing measure, not as a performance boost	A
Longer breaks	A 2022 systematic review found that breaks generally improve wellbeing and can improve performance, with the effect depending on activity, timing and whether the person chose the break; longer breaks did more for performance [3]	The 15 to 30-minute break after four rounds is at least as important as the five-minute ones	B
Pre-set versus self-chosen breaks	In a single-day study with 87 students, groups on fixed 24/6 or 12/3 schedules reported less fatigue and distraction and finished similar work in slightly less time than students who chose their own breaks [4]. In a two-hour session with 94 students, Pomodoro, Flowtime and self-regulated breaks did not differ in productivity, task completion or flow, and fatigue rose faster in the Pomodoro group [5]. A 2025 scoping review counted three randomised trials in total, with 87 participants between them [6]	Fixed breaks probably help people who otherwise never stop; they do not make anyone produce more. The entire direct evidence base is smaller than one mid-sized office	C
Brief diversions and vigilance	In a 40-minute lab vigilance task, participants given two brief diversions kept their detection performance while the uninterrupted group declined [7]	Switching away briefly can prevent the slow slide in attention on monotonous work; the study is one lab experiment, not a workplace trial	B
Time-boxing as an if-then plan	If-then plans tying an action to a cue have a medium-to-large effect on goal attainment across 94 studies [8]; specific, difficult goals outperform vague ones [9]	"At 9:00 I start the budget draft for 25 minutes" is an implementation intention. Much of what people attribute to the tomato is the plan, not the timer	A
Interruption handling	Interrupted workers in a lab simulation finished faster but reported more stress, frustration and effort [10]	Cirillo's script for deferring interruptions addresses a real cost; the cost is to strain more than to output	B
Time management in general	Moderately related to performance and more strongly to wellbeing in a 2021 meta-analysis [11]	Expect to feel more in control before you see more work done	A

The parts of the method with good evidence (short breaks, a longer break, a written plan for each interval, a script for interruptions) are not specific to 25 minutes. The one claim that is specific to the method, that fixed intervals beat working until you need a break, has been tested in fewer than 300 students and has come out even.

The 25-minute folklore

Our science summary lists "the Pomodoro 25/5 rhythm is scientifically optimal" among the claims this site does not make. The number has no origin in research. Cirillo chose it from a kitchen timer, and the comparative studies used 24/6, 12/3 and 25/5 interchangeably with no difference in output ^[4][5]. Pages that call 25 minutes the brain's natural attention span usually lean on two other myths documented as unsupported: the "10-minute lecture limit" and the "8-second attention span" ^[12]. Attention declines with monotony and recovers with variety; it does not run on a fixed clock.

The honest statement is narrower: short, regular breaks help you feel better across a working day, and a fixed interval makes sure they happen. The length is a design choice to make from your work, not a constant.

Variants compared

Pattern	How it runs	Suits	What the evidence says	Cost
Classic 25/5	Four rounds, then 15 to 30 minutes off	Starting an avoided task, clerical batches, study with recall practice	Short breaks lower fatigue [2]; no productivity edge over alternatives [5]	Rings inside most writing or coding tasks; tested only in students
50/10	Two rounds, then a longer break	Writing, analysis, anything with a warm-up	Same break evidence; longer uninterrupted span avoids mid-task switches [13]	Ten minutes is at the upper edge of the micro-break range that was studied [2]
90/20	One long interval, one long break	Deep work with no meetings	Often justified by a "90-minute ultradian cycle"; a controlled test over nine hours found no 90-minute rhythm in cognitive performance or alertness [14]. Use it for the long span, not the biology	Fatigue builds; hard to fit into a meeting-heavy day
Flowtime	Work until focus fades, note the time, rest for a proportional break	Experienced workers who notice their own fatigue	Matched Pomodoro and self-regulated breaks in the one trial that compared them, with slower fatigue increase than 25/5 [5]	Relies on self-monitoring, which is exactly what people who never take breaks lack

When the timer harms deep work

The method's weakness is structural: a bell that rings on a schedule ignores the state of the work.

• It cuts into flow. Flow arises when challenge matches skill with clear goals and immediate feedback ^[15], and it is moderately associated with performance, although which causes which is unresolved ^[16]. A forced stop every 25 minutes removes the long unbroken span that absorbed work tends to need.
• It creates attention residue. When people leave a task unfinished to switch to something else, part of their attention stays with the first task and the second suffers; finishing, or at least reaching a stopping point, reduces the residue ^[13]. A timer that rings mid-paragraph manufactures residue four times an hour.
• It does not raise performance on hard tasks. The micro-break meta-analysis found performance gains for clerical and creative work but not for cognitively demanding tasks ^[2]. For the work that most needs protecting, the break helps how you feel, not how much you finish.
• It can be an interruption. The lab evidence on interruptions concerns stress and effort, not lost minutes ^[10]; a self-imposed one carries the same cost when it arrives at the wrong moment.

The method earns its reputation in the opposite situation: a task you are avoiding, a monotonous queue, a study session, or a day in which you otherwise never stand up. Starting is the hard part of procrastination, and a 25-minute commitment is a small enough promise to keep; our guide to how to stop procrastinating covers that mechanism.

Choosing your interval

Use the work, not the tomato, to pick the length.

1. Is the task demanding and uninterrupted? Choose 50/10 or 90/20 and stop at natural breakpoints, not at the bell. Set the timer as a floor ("at least 50 minutes") rather than a ceiling.
2. Is the task monotonous or clerical? Choose 25/5. The vigilance and micro-break evidence applies most directly here ^[2][7].
3. Is starting the problem? Choose the shortest interval you can promise yourself, even 10 or 15 minutes, and lengthen it once you have started.
4. Do you forget to stop? Fix the breaks first and let the work interval float; a timer that only marks breaks is Flowtime.
5. Do you feel worse by mid-afternoon? Lengthen the midday break before shortening the work intervals; the review evidence points to longer breaks for recovery ^[3].

Fatigue is best understood as a signal about the cost and benefit of continuing rather than an empty tank B^[17], another reason to let the state of the work, not the clock, end a long interval.

A worked week

A knowledge worker with about eight hours of meetings a week, mostly around midday, has sorted the week with the Eisenhower matrix and blocked the calendar. Intervals change with the kind of work in the block.

Day	9:00 to 11:00	11:00 to 12:00	13:30 to 15:00	15:00 to 17:00
Monday	Weekly plan, then 50/10 on the quarter's main project	Meetings	Admin batch, 2 × 25/5 (email, approvals)	50/10 on project; stop at a breakpoint
Tuesday	90/20 on the project (no meetings before noon)	25/5 to clear review queue	Meetings	2 × 25/5 reading and notes
Wednesday	50/10 × 2 on a second important task	Meetings	50/10 on project	Admin batch, 2 × 25/5
Thursday	90/20 on the project	Meetings	2 × 25/5 on an avoided task; lengthen if it catches	50/10 on project
Friday	50/10 × 2 to finish the week's deliverable	Admin, 25/5	Review: count intervals, compare with estimates, plan Monday	Open, no timer

The count matters more than the schedule. Comparing the intervals planned with the intervals completed is the only measurement the method gives you, and it is a good one: people underestimate how long tasks take even when they know they usually do B^[19], and the estimate-versus-actual gap is the figure to watch.

Timers and apps

A timer is a timer. The clock app on your phone, a kitchen timer or a browser tab all do the job, and the evidence gives no reason to pay for one. Where an app earns a place is in the record: a count of intervals per day and per task to review on Friday. Task managers such as TickTick include a Pomodoro timer beside the task list, which keeps the count attached to the work. Our focus planner has a session timer at 25, 50 or 90 minutes that logs completed sessions in your browser only, so the count lives beside the day template. Dedicated focus apps are compared on the best focus apps page.

Demand note: who searches for this

In the United States "pomodoro technique" draws about 49,500 searches a month with a keyword difficulty of 69, down 33 percent year on year and declining about 3.4 percent a year over three years (DataForSEO, retrieved 2026-11-09) ^[18]. Interest is international: 12,100 monthly searches in the UK, 9,900 in Germany ("pomodoro technik"), 2,400 in France ("technique pomodoro"), 1,900 in Spain ("técnica pomodoro") and 320 in Czechia ("pomodoro technika"). German, French, Spanish and Czech readers get localised versions of this page rather than a translation.

What to do next

Decide the intervals from the work, then put them into a day that can hold them. The focus planner takes your meeting hours, break pattern (including "every 25 minutes"), energy across the day and interruption sources, and returns a template day with deep-work blocks in your higher-energy windows, a micro-break every 50 to 90 minutes and a longer midday break. Its session timer and seven-day log give you the interval count this guide recommends tracking, stored only in your browser.

Frequently asked questions

What is the Pomodoro technique?

A time-management method by Francesco Cirillo: work on one task for 25 minutes, take a five-minute break, and take a longer break of 15 to 30 minutes after four rounds. Each interval is indivisible, interruptions are deferred with a short script, and every completed interval is recorded ^[1].

Is 25 minutes the scientifically best work interval?

No. The number comes from a kitchen timer, not a study. The only trials comparing fixed intervals with self-chosen breaks used 24/6, 12/3 and 25/5 and found no difference in productivity; in the two-hour study, fatigue rose faster in the 25/5 group ^[4][5]. What the research does support is taking short, regular breaks, which lower fatigue and raise vigour with a small effect ^[2].

Does the Pomodoro technique work for studying?

The direct studies were all done with students, and they show that pre-set breaks reduce reported fatigue and distraction without reducing how much gets done ^[4]. The method fits study sessions well, especially combined with recall practice in the last minutes of each interval. It is less suited to long problem sets where a bell would interrupt a line of reasoning.

What is the difference between Pomodoro and Flowtime?

Pomodoro fixes the work interval and the break. Flowtime lets you work until your focus fades, note how long that was, and take a break proportional to it. In the one trial that compared them, they did not differ in productivity, task completion or flow, and fatigue rose more slowly with Flowtime ^[5]. Flowtime depends on noticing your own fatigue, which not everyone does.

Should I use 25/5, 50/10 or 90/20?

Match the interval to the work. Use 25/5 for monotonous, clerical or avoided tasks, 50/10 for writing and analysis, and 90/20 only when you have an uninterrupted morning. The 90-minute figure is often justified by a 90-minute brain cycle, but a controlled test found no such rhythm in waking performance ^[14], so treat it as a long block, not a biological rule.

Do I need a Pomodoro app?

No. Any timer works. The useful feature of an app is the record of completed intervals per task, which you can compare against your estimates at the end of the week. Our focus planner includes a timer at 25, 50 or 90 minutes that logs sessions in your browser only.

Sources and evidence

1. The Pomodoro Technique: The Life-Changing Time-Management System — Cirillo, F. (2018), book C (retrieved 2026-11-09)
2. "Give me a break!" A systematic review and meta-analysis on the efficacy of micro-breaks for increasing well-being and performance — Albulescu, P.; Macsinga, I.; Rusu, A.; Sulea, C.; Bodnaru, A.; Tulbure, B. T. (2022), meta-analysis A doi.org/10.1371/journal.pone.0272460 (retrieved 2026-11-09)
3. Role of work breaks in well-being and performance: A systematic review and future research agenda — Lyubykh, Z.; Gulseren, D.; Premji, Z.; Wingate, T. G.; Deng, C.; Bélanger, L. J.; Turner, N. (2022), systematic review B doi.org/10.1037/ocp0000337 (retrieved 2026-11-09)
4. Understanding effort regulation: Comparing 'Pomodoro' breaks and self-regulated breaks — Biwer, F.; Wiradhany, W.; oude Egbrink, M. G. A.; de Bruin, A. B. H. (2023), RCT C doi.org/10.1111/bjep.12593 (retrieved 2026-11-09)
5. Investigating the Effectiveness of Self-Regulated, Pomodoro, and Flowtime Break-Taking Techniques Among Students — Smits, E. J. C.; Wenzel, N.; de Bruin, A. (2025), RCT C doi.org/10.3390/bs15070861 (retrieved 2026-11-09)
6. Assessing the efficacy of the Pomodoro technique in enhancing anatomy lesson retention during study sessions: a scoping review — Ogut, E. (2025), systematic review C doi.org/10.1186/s12909-025-08001-0 (retrieved 2026-11-09)
7. Brief and rare mental "breaks" keep you focused: Deactivation and reactivation of task goals preempt vigilance decrements — Ariga, A.; Lleras, A. (2011), RCT B doi.org/10.1016/j.cognition.2010.12.007 (retrieved 2026-11-09)
8. Implementation Intentions and Goal Achievement: A Meta-analysis of Effects and Processes — Gollwitzer, P. M.; Sheeran, P. (2006), meta-analysis A doi.org/10.1016/S0065-2601(06)38002-1 (retrieved 2026-11-09)
9. Building a practically useful theory of goal setting and task motivation: A 35-year odyssey — Locke, E. A.; Latham, G. P. (2002), review A doi.org/10.1037/0003-066X.57.9.705 (retrieved 2026-11-09)
10. The cost of interrupted work: more speed and stress — Mark, G.; Gudith, D.; Klocke, U. (2008), RCT B doi.org/10.1145/1357054.1357072 (retrieved 2026-11-09)
11. Does time management work? A meta-analysis — Aeon, B.; Faber, A.; Panaccio, A. (2021), meta-analysis A doi.org/10.1371/journal.pone.0245066 (retrieved 2026-11-09)
12. Attention span during lectures: 8 seconds, 10 minutes, or more? — Bradbury, N. A. (2016), review A doi.org/10.1152/advan.00109.2016 (retrieved 2026-11-09)
13. Why is it so hard to do my work? The challenge of attention residue when switching between work tasks — Leroy, S. (2009), RCT B doi.org/10.1016/j.obhdp.2009.04.002 (retrieved 2026-11-09)
14. Ultradian rhythms in cognitive performance: no evidence for a 1.5-h rhythm — Neubauer, A. C.; Freudenthaler, H. H. (1995), observational B doi.org/10.1016/0301-0511(95)05121-P (retrieved 2026-11-09)
15. Flow Theory and Research — Nakamura, J.; Csikszentmihalyi, M. (2009), review B doi.org/10.1093/oxfordhb/9780195187243.013.0018 (retrieved 2026-11-09)
16. A systematic review and meta-analysis of the relationship between flow states and performance — Harris, D. J.; Allen, K. L.; Vine, S. J.; Wilson, M. R. (2023), meta-analysis B doi.org/10.1080/1750984X.2021.1929402 (retrieved 2026-11-09)
17. Mental fatigue: Costs and benefits — Boksem, M. A. S.; Tops, M. (2008), review B doi.org/10.1016/j.brainresrev.2008.07.001 (retrieved 2026-11-09)
18. Keyword database: DataForSEO Labs keyword overview and historical search volume, US/UK/DE/FR/ES/CZ (data/research/keywords) — Productivity Signal research (2026), dataset A dataforseo.com/apis/dataforseo-labs-api (retrieved 2026-11-09)
19. Exploring the "planning fallacy": Why people underestimate their task completion times — Buehler, R.; Griffin, D.; Ross, M. (1994), RCT B doi.org/10.1037/0022-3514.67.3.366 (retrieved 2026-11-09)