Pomodoro Timer
Free Pomodoro technique timer for productivity. 25-minute work sessions with 5-minute breaks. Customizable focus timer with notifications
The Pomodoro Technique is the most-cited productivity method developed in the late 1980s — 25 minutes of focused work, 5 minute break, repeat four times, then a 15-30 minute long break. The interesting research finding from the last two decades: it is the rhythm and the break, not specifically the 25 minutes, that does the work. This timer runs the classic Pomodoro cycle, lets you customize the durations if your task suits a different rhythm, and tracks Pomodoros completed across the day so the "I worked all day and got nothing done" feeling has a counter-evidence.
Why the rhythm works
Three mechanisms are doing real work in the Pomodoro Technique. First, the commitment device: "I will work on X for 25 minutes" is a smaller, more actionable promise than "I will finish X". Second, the break: focused attention degrades after 20-40 minutes for most tasks, and a 5-minute break recovers it (research on attentional fatigue, Sievertsen et al. 2016 on schoolchild test performance over the day). Third, the count: completed Pomodoros are a visible metric of effort that bypasses the "I felt like I worked but did I?" question.
What is NOT special about 25 minutes specifically: it was the duration on Cirillo's tomato-shaped kitchen timer (the Italian word "pomodoro" means tomato). Studies of programmer focus suggest 50-90 minute work blocks may suit deep-work tasks better; for writing 60-90 minutes; for tedious data entry the original 25 may be best. Adjust to your task.
Working example: a writing session
Input
Goal: draft a 1500-word blog post Work block: 50 minutes Break: 10 minutes
Output
Session 1 (50 min): outline + first 400 words. Hit a wall at minute 38. Break (10 min): walked outside, no screens. Session 2 (50 min): wrote 600 words. Got into flow at minute 15. Break (10 min): made coffee. Session 3 (50 min): final 500 words + first revision pass. Long break (30 min): lunch, did not touch the post. Session 4 (50 min): second revision, line edits. Total: 200 min focus / 50 min breaks = 80% focus ratio over 4 hours. Distraction-free time: 200 min. Equivalent to a typical "8-hour day" of unstructured work for most knowledge workers.
The breaks are non-negotiable. Skipping them does not give you more work time; it gives you reduced-quality work over the same wall-clock time. The metric that matters is total focused-quality minutes, not total wall-clock-at-desk minutes.
Adaptations that work
- 52/17 — popularized by DeskTime data analysis. The "most productive 10%" of their users averaged 52 minutes of work, 17 minutes of break. Suits longer attention spans and complex tasks.
- 90/20 — based on ultradian rhythms (BRAC, Basic Rest-Activity Cycle, ~90 min cycles). Good for deep work like programming or writing where context-switching is expensive.
- Time-boxing — set a hard deadline ("I will spend 25 minutes deciding on architecture") to force a decision under bounded time. Different from focus blocks; useful for analysis paralysis.
- Tomato Timer + No Music — adding "no music, no notifications, phone in another room" matters more than the exact duration. Most studies of focus blame the environment, not the duration choice.
When the technique fails
- Calls and meetings — Pomodoros assume uninterrupted blocks. Calendar-driven days fragment the rhythm. Block off Pomodoro time on the calendar explicitly.
- Creative flow — when you hit a flow state at minute 23 of a 25-minute Pomodoro, the alarm breaking you out is counterproductive. Override the break and finish the thought.
- Tasks under 25 minutes — small tasks (reply to that email) should not start a Pomodoro. Batch them in a single "admin" Pomodoro at the start or end of day.
- Open-ended tasks with no obvious "done" — like reading a long document. The Pomodoro structure works best when you can pre-commit to a subgoal ("read sections 1-3 in this 25-min block").
When to reach for this tool
- You are trying to make consistent progress on a long project and need a structure that bypasses motivation.
- You have ADHD or attention-regulation challenges and benefit from external time cues rather than internal monitoring.
- You want a non-judgmental metric of effort ("today I did 8 Pomodoros") to compare across days.
- You are studying or doing tedious work and need scheduled breaks to maintain quality.
What this tool will not do
- It will not enforce focus. The timer counts time; you have to do the work. If your phone is in your hand during "focus" time, the timer is irrelevant.
- It will not measure productivity. Pomodoros completed is a proxy for effort, not output. A 4-Pomodoro day on hard problems can produce more than an 8-Pomodoro day on busy-work.
- It will not work without practice. The first week of Pomodoros is awkward. Most users report the benefit shows up after 10-20 cycles, once the rhythm becomes habit.
Pomodoro counts and settings are stored in browser localStorage, locally on your device. No remote tracking; clearing browser data resets the counter.
Frequently asked questions
Should I do exactly 25 minutes?
Start there; adjust based on the task. Cirillo's original 25/5 is a starting point, not gospel. Once you have a few weeks of practice, you will notice which tasks fit which durations. Coding flow usually wants 45-90; admin tasks fit the original 25; reading depends on the text.
What should I do during the break?
Not screen-related work. Walk, get water, look out the window. The break's purpose is attention recovery, and continuing to engage screens (even "casual" social media) does not let your attention reset. The hardest part for most people is making the breaks count.
Does Pomodoro work for creative work?
Mixed. For the "I have to start" problem, yes — a 25-minute commitment is easier to make than "do creative work today". For maintaining flow, the breaks can be disruptive. Many writers report longer (50-90 min) blocks work better for sustained creative output.
Is it OK to skip breaks if I am in flow?
Yes, once or twice. Repeatedly skipping breaks defeats the technique — attention degrades, you just stop noticing. The trick: when you skip a break, take the next one slightly longer (15 min instead of 5) to repay the deficit.
How many Pomodoros should I aim for per day?
6-12 for most knowledge workers. Beyond that, quality degrades. Cal Newport estimates 4 hours of true deep work is the ceiling for most people. 8 Pomodoros = ~3.3 hours of focused time and is realistically what a typical workday holds, with the rest being meetings, admin, and recovery.
What is the relationship between Pomodoro and Getting Things Done (GTD)?
Complementary. GTD is about choosing what to work on (capture, clarify, organize, reflect, engage). Pomodoro is about how to execute once chosen. Many people use GTD for planning and Pomodoro for the "engage" phase.
Related tools
View current time in multiple cities and timezones. Compare time zones, find time difference. Free world clock with daylight saving support
Calculate days between dates, working days excluding weekends and holidays. Add/subtract time from dates. Support for Poland, USA, Germany, UK, France holidays
Calculate exact age in years, months, days from birthdate. Find days between two dates, upcoming birthday countdown. Free online age calculator
Professional metronome with tap tempo, time signatures (4/4, 3/4, 6/8), accent patterns, and visual beat indicator. Free online metronome for musicians
Build cron expressions visually with schedule preview. Validate crontab syntax for Linux, Kubernetes, AWS. Free online cron job generator
Sleep sound machine with white, pink, brown noise, rain, ocean waves & nature sounds. Sleep timer with fade-out, binaural beats for deep sleep & focus. Free ambient noise generator
Last updated · E-Utils editorial team