Pomodoro Timer: How to Focus in 25-Minute Sprints

By Bernard · Kitchener, Canada

The Pomodoro Technique replaces a vague plan to "work all afternoon" with a series of short, finite sprints. You pick one task, set a timer for 25 minutes, work until it rings, then take five minutes off. That is the whole method. This page covers how the cycle is put together, how to run it in the timer on this page, and what the research behind it actually supports.

What a Pomodoro Actually Is

Francesco Cirillo developed the method in the late 1980s while he was a university student, timing his study blocks with a tomato-shaped kitchen timer. Pomodoro is Italian for tomato, and the name stuck to the intervals themselves. One pomodoro is a single unit of work time: 25 minutes of focus followed by a 5-minute break. When the timer rings you stop, mark the pomodoro complete, and rest. After four pomodoros you take a longer break, typically 15 to 30 minutes.

Two rules matter more than the exact numbers. First, a pomodoro is indivisible. When something interrupts you mid-session, you either write the interruption down and handle it later or you abandon the pomodoro and start over. Second, the break is part of the method rather than a reward for finishing. The cycle holds together only when the rest between sprints actually happens.

The intervals are a starting point, not a law. Cirillo settled on 25 minutes because it was long enough to make progress on a task and short enough to keep attention without drifting. Most people who stay with the technique adjust the length to the work in front of them. The timer here allows work sessions of 1 to 90 minutes, short breaks of 1 to 30 minutes and long breaks of 1 to 60 minutes, so the classic rhythm is simply the default setting.

How to Run One Session

Everything runs in the browser. There is no account and no upload; your settings and your statistics stay on the device.

1. Pick one task and open the Focus tab. The default session is 25 minutes.
2. Press Play and work until the countdown reaches zero. When sound notifications are on, an 880 Hz tone sounds for 800 milliseconds at the end of the session.
3. The timer advances to a short break of 5 minutes. Leave the screen.
4. Repeat. After the fourth focus session the tool sends you into a long break of 15 minutes instead of a short one.

The row of dots under the clock shows where you are in the set: one dot per planned focus session, filled in as you complete them, with the current one pulsing while you work.

The controls are deliberately few:

• Play and Pause start and stop the current session without losing time.
• Reset returns the current session to its full length. It does not touch your statistics.
• Skip jumps to the next session immediately. The skipped session is not recorded, so a short day does not inflate the count.
• The Focus, Short Break and Long Break tabs switch sessions at once, but only while the timer is paused. Pressing a tab mid-session shows a reminder to pause first.

The settings panel holds four numbers and two switches:

• Work duration: 1 to 90 minutes, 25 by default.
• Short break: 1 to 30 minutes, 5 by default.
• Long break: 1 to 60 minutes, 15 by default.
• Sessions before a long break: 1 to 10, 4 by default.
• Sound notifications, which plays the tone at the end of every session.
• Auto-advance, which starts the next session on its own instead of waiting for you to press Play.

Every value is clamped to its range as you type, and both the settings and the day's statistics survive a page reload. The stat strip keeps three totals for the current day: focus time, sessions done and breaks taken. Those counters reset when the date changes. While the timer runs, the browser tab shows the remaining time and the name of the session, so you can watch the countdown from another tab; pausing the timer returns the tab to the plain tool name.

Worked Example: A Two-Hour Focus Block

Start at 09:00 with the default settings. Four focus sessions of 25 minutes give 100 minutes of work, interrupted by three short breaks and closed by one long break.

Elapsed time is 2 hours 10 minutes, of which 1 hour 40 minutes is focused work. The stat strip reports exactly that: 1h 40m of focus time, four sessions done, three breaks taken.

The same set stretches when you change the numbers. Raise the work duration to 45 minutes and the four sessions fill 3 hours 30 minutes, with the long break landing at the end. Drop it to 15 minutes and the set finishes inside an hour and a half, which is often enough to get started on a task you have been avoiding all week. Nothing about the ratio has to stay fixed; the long break is what keeps the tail of a long set from turning into grind.

Tracking sessions this way also fixes estimates. Once you know that a weekly report costs about three pomodoros, "three pomodoros" becomes a plan you can put on a calendar, while "a couple of hours" stays a guess.

What the Research Says

The most complete summary available is a 2025 scoping review published in BMC Medical Education by Eren Ogut, which screened roughly 6,500 records and analysed 32 studies covering more than 5,000 people. Eighty-eight per cent of those studies reported positive outcomes, and the review's own summary is that time-structured pomodoro sessions consistently improved focus, reduced mental fatigue and held up sustained task performance better than self-paced breaks.

The randomised trials carry the most weight. Across them, structured intervals produced around 20 per cent less mental fatigue than letting people break whenever they felt like it, with modest gains in focus and motivation. One comparison described in the review is worth repeating: a group working in timed intervals studied about 90 minutes against 120 minutes for the control group, yet rated their focus higher, 8.5 against 6.2 out of 10, and scored better on the following test, 82 per cent against 70 per cent.

The caveats are real and the review states them itself. It rates the certainty of the evidence as moderate to low. Much of the data is self-reported rather than measured, the studies are small and short-term, positive results are more likely to reach publication in the first place, and most of the strongest evidence comes from students working through demanding material, which does not automatically transfer to every kind of job.

At least one experiment points the other way. A 2023 study in the British Journal of Educational Psychology compared 25 students taking pomodoro breaks with 35 taking breaks they scheduled themselves. It found no difference between the two groups in mental effort or in task completion, although the self-regulated group chose longer sessions and reported more fatigue and less concentration.

Read together, the picture is a well-supported scaffold for starting and sustaining focus, not a guarantee and not settled science. The part that is clearest in the data is also the part people skip: the breaks are doing real work.

Choosing Your Interval Length

25 minutes is a default, not a measurement of your attention span.

• Long sessions of 45 to 50 minutes suit writing, coding and design, where recovering context after a break costs more than the extra fatigue.
• The classic 25 suits mixed work: admin, email, reading, revision.
• Short sessions of 10 to 15 minutes suit tasks you keep postponing and low-energy days. Many people who find starting hard report that a short, clearly bounded sprint with a visible countdown lowers the barrier, and while the dedicated research on that is thin, it costs nothing to try.
• The sessions-before-a-long-break counter has to move with the work length. At 45-minute sessions, drop the count to 2 or 3 so a full set does not run past three hours.

Other rhythms exist, and the differences are worth knowing before you commit to one:

The first two fit inside this timer: set the work duration to 52 and the short break to 17, and the interval rhythm changes without any other change. Flowtime does not fit, because it counts up from the moment you start and sizes the break to the work you actually did; a countdown timer can only approximate it by setting a long session and stopping early.

Mistakes That Break the Cycle

Most people who abandon the method do so for one of these reasons.

• Working through the break. Two sessions are fine, the third is not. Focus that is never allowed to recover reads as a loss of willpower when it is really a loss of rest.
• Multitasking inside a session. A pomodoro is one task. If a second task appears, write it down and return to the first; a session that covers three things is a session that finishes none of them.
• Ignoring the ringing timer. The countdown is the entire mechanism. If you keep working after it rings, you are running an open-ended session with extra steps.
• Skipping the capture list. Interruptions have to go somewhere. Without a note to park them, every thought becomes a reason to stop.
• Treating the count as a score. Twelve shallow pomodoros beat six honest ones on the counter and lose on the work. Track the number to calibrate estimates, not to compete with yourself.
• Planning in hours. An afternoon is not a plan; four pomodoros is. Converting tasks into pomodoros is what makes the cycle useful for the next day.
• Using the timer in meetings or on call. If your day is genuinely interrupt-driven, a fixed 25-minute block will fight the job rather than help it.

Who Gets the Most Out of It

The method pays off most for work that arrives as a pile of tasks you keep deferring: study and revision, writing, coding, design assets, admin you can name but never start, side projects that only get weekend scraps of attention. It also helps anyone who works alone from home, where the boundary between work and everything else has to be built rather than inherited from an office.

It fits least well for people who live inside long stretches of flow, for on-call and support roles where interruptions are the job, and for collaborative work where a timer stops someone else as well as you. In those cases the useful parts are the capture list and the honest breaks, not the fixed interval.

There is also a practical middle ground. Sessions do not have to be sacred: if the timer rings exactly as a hard problem opens up, finish the thought, then take the break you owe yourself. The rhythm can bend once in a while. It cannot bend every session, or the structure that makes it work disappears.

Everything the method needs is on this page. Pick a task, set the interval you can actually keep, and let the timer decide when the break starts.

Bernard

Kitchener, Canada · SO reputation 7981 · Badges: 2🥇38🥈33🥉 · SO member since 2010