Password Generator
Cryptographically random passwords with a live entropy meter.
Utilities & Converters
25/5 focus cycles that keep accurate time in a background tab.
A time management method developed by Francesco Cirillo in the late 1980s, named after the tomato-shaped kitchen timer he used as a student.
The structure is fixed: 25 minutes of single-task work, a 5-minute break, repeated four times, then a 15–30 minute long break. One 25-minute interval is a "pomodoro" and is treated as indivisible — if you are interrupted, the pomodoro is void rather than paused.
The mechanism is less about the specific durations than about two things. First, it makes starting easier, because committing to 25 minutes is psychologically cheaper than committing to a task of unknown length. Second, it enforces breaks that people otherwise skip, and skipped breaks are what turn a productive morning into an unproductive afternoon.
No, and treating 25/5 as sacred is the most common way people bounce off the technique.
The 25-minute figure was chosen because it suited Cirillo's own studying. Work requiring deep context — writing, complex debugging, mathematical reasoning — has a warm-up cost of ten to fifteen minutes before full engagement, and a 25-minute cap interrupts it just as it becomes productive. 50/10 or 90/20 suits that work far better.
Shallower work with natural break points — email, code review, admin, data entry — fits 25/5 well, and shorter intervals can help when concentration is difficult.
The 90-minute figure has some grounding: the ultradian rhythm literature suggests human alertness cycles on roughly a 90-minute period. The evidence is suggestive rather than conclusive, but it matches many people’s experience.
| Work | Break | Suits |
|---|---|---|
| 25 min | 5 min | The classic. Admin, study, shallow tasks |
| 50 min | 10 min | Writing, coding, analysis |
| 90 min | 20 min | Deep work, matched to ultradian cycles |
| 15 min | 3 min | Difficult concentration, ADHD, task initiation |
| 45 min | 15 min | Matches a lecture or meeting block |
Because browsers throttle background tabs to save battery. A setInterval running at one second is clamped to once per minute or slower in a hidden tab, and a naive timer that counts ticks will run minutes late over a 25-minute interval.
Two techniques fix it, and this timer uses both. The countdown is computed from a wall-clock timestamp taken at start — so however irregularly the tick fires, the remaining time is always calculated from the actual elapsed duration rather than accumulated. And the tick itself runs in a Web Worker, which is throttled far less aggressively than the main thread.
The result is accurate to within a second over a full interval regardless of whether the tab is visible, which is the entire point of a timer you start and then switch away from.
Something that is not a screen. This is where most attempts at the technique fail.
The break exists to let the attention system recover, and scrolling a feed for five minutes does not do that — it substitutes one demanding visual task for another. Standing up, walking, looking at something more than six meters away, getting water, or doing nothing at all all work considerably better.
The distance-viewing point has a physiological basis: sustained near-focus fatigues the ciliary muscle, and the 20-20-20 guidance from optometry bodies — every 20 minutes, look at something 20 feet away for 20 seconds — maps almost exactly onto a Pomodoro break. Taking the break at a window is a genuinely better use of it than taking it at your phone.
Yes, and accurately. The countdown is computed from a wall-clock timestamp and ticked from a Web Worker, so background throttling does not cause drift.
Yes, if you grant notification permission. There is also an audible chime, which works whether or not notifications are allowed.
Yes. Work, short break, long break and the number of cycles before a long break are all adjustable, and your settings persist on your device.
Cirillo's rule is that an interrupted pomodoro is void — restart it. In practice, pausing works fine for most people; the strict rule exists to discourage treating interruptions as acceptable.
Eight to twelve is a realistic full day of focused work, which is four to five hours of genuine concentration. Anyone claiming sixteen is either counting shallow work or not taking the breaks.
Yes. The page is cached by a service worker after your first visit and needs no connection.
No. Settings and session counts are stored on your device in localStorage only.