Study Pomodoro Timer

What the founding document says, in its own words

The technique has a named author and a freely published description, so there is no need to work from the internet’s version of it. Francesco Cirillo wrote The Pomodoro Technique as a paper, dated 19 October 2006 for version 1.0 and 15 June 2007 for version 1.3, released under a Creative Commons licence. Here is what it prescribes, quoted rather than paraphrased.

The interval and the short break. “The traditional Pomodoro is 30 minutes long: 25 minutes of work plus a 5-minute break.” In the step-by-step instructions the short break is given as a range: “When the Pomodoro rings, mark an X next to the activity you’ve been working on and take a break for 3-5 minutes.” So the break box above, at 5 minutes, sits at the top of Cirillo’s range rather than at a fixed value.

A pomodoro cannot be divided. “A Pomodoro can’t be interrupted; it marks 25 minutes of pure work. A Pomodoro can’t be split up; there is no such thing as half of a Pomodoro or a quarter of a Pomodoro. The atomic unit of time is a Pomodoro. (Rule: A Pomodoro Is Indivisible.) If a Pomodoro is definitively interrupted by someone or something, that Pomodoro should be considered void, as if it had never been set; then you should make a fresh start with a new Pomodoro.”

The ring is not negotiable in either direction. “When the Pomodoro rings, this signals that the current activity is peremptorily (though temporarily) finished. You’re not allowed to keep on working ‘just for a few more minutes’, even if you’re convinced that in those few minutes you could complete the task at hand.”

A longer break after every fourth. “Every four Pomodoros, stop the activity you’re working on and take a longer break, from 15 to 30 minutes.” And on how long: “Breaks at the end of a set should last from 15 to 30 minutes”, with the caution that “breaks that consistently exceed 30 minutes risk interrupting the rhythm between sets of Pomodoros”.

What a break is for, and what it is not. “During this quick break, it’s not a good idea to engage in activities that call for any significant mental effort. For example, don’t start talking about work-related issues with a colleague; don’t write important emails or make imperative phone calls, etc.” Checking a reading list, answering a message about the group project and skimming the next slide deck are all excluded by that sentence, which is the rule most commonly dropped when the method gets repackaged as a timer.

The clock has to be visible. “Whoever is using the Pomodoro, whether one person or more than one, should always be able to clearly see how much time is left.”

Six rules, and what this timer implements

Laid against the paper, the tool at the top of this page does part of the job. Being specific about which part is more useful than claiming it does all of it.

That last row is worth dwelling on, because it is where the gap between a pomodoro timer and the Pomodoro Technique lives. Cirillo’s first objective is titled “Find Out How Much Effort an Activity Requires”. The interval exists to be a unit of measurement: you mark an X for each one, and you learn over weeks that a problem set costs you four and not two. A timer with no record keeps the unit and throws away the measurement.

Where 25 minutes comes from, and what it rests on

The paper explains the choice, and it is more candid than its reputation. Cirillo names two competing pressures. On granularity: “As a unit of measure, much smaller time intervals such as 10 minutes might not be interrupted, but they don’t allow us to achieve appreciable results, and tracking becomes much too intrusive. So as far as this first force, half an hour seems to be ideal.” On attention: “It’s been proven that 20- to 45-minute time intervals can maximize our attention and mental activity, if followed by a short break”.

That second sentence is the only claim in the paper that the interval length has an evidential basis, and it carries a footnote marker to entry 15 of the bibliography. Entry 15 reads, in full: “Yona McGregor e Tony Buzan, A Guide to Animal Farm, Hodder & Stoughton, 1998; ISBN 0-340-66401-0.” That is a study guide to George Orwell’s novel. The bibliography has seventeen entries and no primary research in attention or memory anywhere in it. So the “it’s been proven” in the founding document is not supported by the founding document, and anyone can check that in a few minutes by downloading the paper and turning to its last page.

What Cirillo actually concludes, two sentences later, is a range: “In light of these two forces, we’ve come to consider the ideal Pomodoro as 20 - 35 minutes long, 40 minutes at the most. Experience shows that the Pomodoro Technique works best with 30-minute time periods.” Note that the 30 there is the whole cycle, 25 of work plus the break. And the note that follows describes how the number was arrived at:

“In various work groups which experimented with the Pomodoro Technique in mentoring activities, each team was allowed to choose the length of their own Pomodoro on the condition that this choice had to be based on observations regarding effectiveness. Generally, the teams started off with hour-long Pomodoros (25 minutes seemed too short at first), then moved to 2 hours, then down to 45 minutes, then 10, till they finally settled on 30 minutes.”

Trial and error by teams who were judging their own effectiveness. That is a reasonable way to design a working practice and a poor basis for a claim that 25 minutes is optimal. The honest reading is that 25 is a convention that many people find usable, and that the paper itself invites you to move it between about 20 and 40.

What the break research supports, and what it does not

There is a real literature on breaks. It supports something weaker and more general than the Pomodoro Technique is usually credited with, and the weaker claim is worth more than an overstated one.

A meta-analysis of short breaks. Albulescu and colleagues (PLoS ONE, 2022) pooled studies of micro-breaks, which they define as “short discontinuities in one’s tasks of no longer than 10 minutes”, across “22 independent study samples (N = 2335)”. Their results, in their own numbers:

The first two are described by the authors as “statistically significant but small”. The third is not statistically significant. Sub-group analysis found significant performance effects “only for tasks with less cognitive demands”, which is not the category a problem set or a chapter of organic chemistry falls into. A meta-regression found that “the longer the break, the greater the boost was on performance”, and the paper’s conclusion is that “for performance, recovering from highly depleting tasks may need more than 10-minute breaks”.

Read plainly: the sourced benefit of a five-minute break is that you feel less tired and more energetic, by a small margin. The claim that it makes you get more done did not reach significance, and the evidence that did appear points at longer breaks for harder work. That is an argument for Cirillo’s 15 to 30 minute break after every fourth interval, which is exactly the rule this timer has no field for.

A mechanism, from a lab task. Ariga and Lleras (Cognition, 2011) is the study usually cited when anyone claims breaks restore attention, and it is worth knowing what it did. Eighty-four observers across four groups performed “a visual vigilance task” for 40 minutes without breaks. Those who had to hold digits in memory and retrieve them only at the end showed vigilance performance that “steeply declined over time”. Those asked “to sporadically recollect the digits during the vigilance task” showed no such decline: “the vigilance decrement was averted”. The authors propose that the decline is goal habituation rather than resource depletion, and that briefly deactivating and reactivating the goal prevents it.

Three caveats that usually get dropped. The “breaks” in that experiment were digit probes lasting about two seconds, not five-minute rests. The task was watching a screen for a visual target, not reading or solving problems. And nothing in the design compares one interval length against another. It is good evidence that interrupting a long vigil with a brief switch of task prevents a decline in that vigil. It is not evidence for 25 minutes, for 5, or for studying.

The claim this page does not make

Searching for a controlled comparison of study-interval lengths, a test of 25 minutes against 50 or against 15 on anything resembling coursework, turned up nothing in the peer-reviewed record that I could read and cite. What came back was a non-peer-reviewed preprint, a small study in an elementary-school setting reporting an effect in a form I could not interpret, and a long tail of blog posts citing each other. So there is no sentence on this page claiming that the Pomodoro Technique improves grades, retention or output, because I could not find one to stand behind. If you find the interval useful, that is a perfectly good reason to use it, and it does not need a research claim propped under it.

A browser clock counts callbacks, not time

The note under the buttons says to keep the tab open, and there is a specific mechanism behind it worth understanding, because it decides whether the clock above can be read as a record of your real study time.

Browsers deliberately slow down page timers in tabs you are not looking at, to save battery. Mozilla’s documentation sets out the specifics, which differ by browser: “Firefox Desktop has a minimum timeout of 1 second for inactive tabs”, “Firefox for Android has a minimum timeout of 15 minutes for inactive tabs and may unload them entirely”, and Chrome applies graded throttling in which ordinary throttled timers “are checked once per second” while timers in an intensive throttling state “are checked once per minute”. Separately: “The timeout can also fire later than expected if the page (or the OS/browser) is busy with other tasks.”

Now the part that is about this page rather than about browsers. The clock above subtracts one second each time its timer fires, rather than comparing two readings of the system clock. Those are not the same design. A tick-counting clock has no way to notice that four seconds passed instead of one, so every delayed or batched callback is lost from the count permanently, and the displayed time drifts behind real time without ever catching up. Which throttling state a given browser applies to this particular timer depends on conditions listed in that documentation, and is not something measured here; the general point holds regardless. If you switch tabs for twenty minutes, do not read the clock on your return as a statement about how long you worked.

What this page does not know

How much real time has passed. See above. It knows how many times its timer fired.

Whether you were working. It counts elapsed intervals, not attention. An interval you spent on your phone counts identically to one you spent on the chapter, which is precisely the case Cirillo’s void rule exists to handle and this timer does not implement.

When your long break is due. The completed-blocks counter is the only clue, and the fourth block arrives with no prompt. Of everything the paper prescribes and this page omits, the 15 to 30 minute break is the one the break research most supports.

Anything about you. There is no published interval length that is correct for a person, because there is no study establishing one. The 20 to 40 minute window in the paper is a working range arrived at by teams judging themselves, not a measurement.

Your state. Nothing here is medical or psychological advice, nothing here diagnoses anything, and a timer is not a treatment for difficulty concentrating. If that difficulty is the real problem, the person to ask is at your institution’s student health or disability service, not on this page.

Sources

• Francesco Cirillo, The Pomodoro Technique, the author’s own paper, version 1.0 dated 19 October 2006 and version 1.3 dated 15 June 2007, released under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 licence: the 25-minutes-plus-5 definition, the 3 to 5 minute short break, the indivisibility and void-if-interrupted rules, the ban on working a few more minutes past the ring, the 15 to 30 minute break every four intervals, the restriction on what a break may contain, the requirement that the remaining time be visible, the two forces behind the interval length, the 20 to 35 minute conclusion with 40 as a maximum, the mentoring-teams note on how 30 minutes was settled on, and bibliography entry 15.
• Albulescu, Macsinga, Rusu, Sulea, Bodnaru and Tulbure, “‘Give me a break!’ A systematic review and meta-analysis on the efficacy of micro-breaks for increasing well-being and performance”, PLoS ONE 17(8), 2022, e0272460: the definition of a micro-break as no longer than 10 minutes, the 22 samples and N of 2,335, the vigour and fatigue effect sizes of d = .36 and d = .35, the non-significant performance effect of d = .16 at p = .116, the sub-group result for less cognitively demanding tasks, the meta-regression on break length, and the conclusion about needing more than 10 minutes to recover from highly depleting tasks.
• Ariga and Lleras, “Brief and rare mental ‘breaks’ keep you focused: Deactivation and reactivation of task goals preempt vigilance decrements”, Cognition 118(3), 2011, 439–443: the 40-minute visual vigilance task, the four groups totalling 84 observers, the digit-probe manipulation and its roughly two-second duration, the steep decline without it and the averted decrement with it, and the goal-habituation account.
• MDN, setTimeout(), “Reasons for delays longer than specified”: the minimum timeouts for inactive tabs in Firefox Desktop and Firefox for Android, Chrome’s throttling and intensive throttling states with their once-per-second and once-per-minute checks, and late timeouts when the page or system is busy.

Every quotation on this page was read against the sources above on 1 October 2026. Nothing you type leaves your browser. If you are trying to work out how long a reading assignment will take rather than how to divide it up, the reading page estimator covers that. More: the rest of the MyCampusKit tools.