25:00
cycle: 1
tomato-dark
tomato-dark
tomato-dark
tomato-dark
00:00

25 Minute Timer

Twenty-five minutes is the pomodoro. One block of focused work, then a short break, repeated four times before a longer rest, and the reason most timer sites exist at all.

What a 25 minute timer is good for

The work block is the whole design. Twenty-five minutes is long enough to get properly into a piece of writing, a problem or a stack of code, and short enough that the end is always in sight when the work is unpleasant. That second property is what makes it usable on a bad day.

Students use it for revision, where the fixed end matters more than the length: it converts an open evening of dread into four defined blocks. Programmers use it for the same reason, and people who hate email use it to make the inbox finite.

It also suits any work where the temptation is to keep going past the point of usefulness. A writing sprint that ends on a timer tends to leave you knowing what comes next, which makes the restart after the break considerably easier than stopping when you run dry.

How to use this timer

The countdown above is already set to 25 minutes. Press play to start it, or use the boxes to change the length if you want something else. The alarm keeps ringing until you stop it, so it still reaches you from another tab or another room.

Reset returns the clock to 25 minutes rather than to zero, which is what you want when you are running the same block more than once.

Where the 25 minute pomodoro came from

Francesco Cirillo was a university student in the late 1980s, struggling to study for more than a few minutes at a time. He took a tomato-shaped kitchen timer from the counter, wound it up, and challenged himself to work until it rang. The Italian for tomato is pomodoro, and the name stuck to the method rather than the vegetable.

The interval settled at twenty-five minutes through trial rather than research. Cirillo experimented with longer and shorter blocks and found twenty-five was the point where the work was substantial but the commitment still felt small. The five minute break, four blocks before a longer rest, came from the same practical tinkering.

The mechanical timer mattered more than it sounds. Winding it was a physical act of committing to the block, and the ticking was a constant reminder that the time was running. Software timers lose both, which is part of why a visible countdown and a real alarm still earn their place.

Frequently asked questions

Why is a pomodoro 25 minutes and not 30?

Because that is what Cirillo landed on when he was experimenting on himself as a student, not because a study identified it as optimal. Twenty-five felt long enough to do real work and short enough to commit to without flinching. A round thirty was available and he did not pick it.

What happens after four pomodoros?

You take a longer break, usually fifteen to thirty minutes, instead of the usual five. The idea is that four blocks is roughly the point where a short pause stops being enough, so the cycle builds in a proper rest before starting the next set of four.

Can I change the length and still call it a pomodoro?

Purists would say no, and Cirillo is firm that the method is the whole system rather than the number. In practice most people adjust it, and a fifty minute block with a ten minute break follows the same logic. What you lose by changing it is the ability to compare your blocks against anyone else's.

Does pomofox track how many pomodoros I have done?

Yes. The homepage timer shows your cycle count as you work through a set of four, and logging in keeps your focus statistics over time so you can see how many blocks you have completed across days and weeks.

Related timers