Free Pomodoro Timer for Students

Francesco Cirillo devised the Pomodoro technique in the late 1980s, as a university student in Italy who could not get through a chapter without drifting. He set a kitchen timer shaped like a tomato — pomodoro in Italian — for a short stretch and made a deal with himself to work until it rang, and nothing else. He wrote the method up later and published it. The tomato in the name is a kitchen timer, not a metaphor.

The original method is short enough to state in full. Choose one task. Set the timer. Work on that task only until it rings. Stop, and take a short break. After four rounds, take a longer one. Everything else written about it since is elaboration on those five lines.

Two details from the original get dropped in most retellings, and both are the good part. First, the block is meant to be indivisible: you do not pause a pomodoro halfway and resume it after a phone call. It either completes or it is abandoned and restarted. That sounds fussy until you notice that a paused, half-attended block is exactly the thing that makes you feel like you studied for three hours and remember none of it. Second, the technique was designed as a measuring instrument. You count the blocks a piece of work consumed, and the count is the point, three weeks in, you know that a problem set costs you four blocks and a reading response costs two, which is planning information you did not have before.

• One task per block, chosen before the timer starts.
• The block runs to the bell. No pausing, no half credit.
• A short break after every block, a longer one after four.
• Count what you complete. The count tells you how long your work actually takes, which is the number every plan you make depends on.

This is the most useful thing to understand about the technique, and it is why people who try it and quit usually quit for the wrong reason. A timer does not manufacture concentration. What it does is make the first step cheap enough that you take it.

Compare two commitments. "Study organic chemistry tonight" has no edge and no end, so agreeing to it means agreeing to an unknown amount of discomfort, and the honest response of a tired brain is to defer. "25 minutes on the chapter 9 problems, then I stop" has a visible end, a known cost, and a defined subject. It is a small enough ask that arguing with it takes more effort than doing it. The technique wins at the negotiation stage, before any focusing happens.

There is a second effect that runs quietly underneath. Once the timer is going, the recurring question — should I be doing something else right now — has a scheduled answer. Not now. In eleven minutes. Deferring a distraction to a fixed, near point is far easier than resisting it indefinitely, and that is most of what the running clock is doing for you.

The diagnostic use of this is worth taking seriously. If you can start fine but drift after ten minutes, a timer is treating the wrong problem, and adding more timers will not help. Look at your phone's position, your sleep, whether the task is defined tightly enough to have a next physical action, and whether you are working somewhere that interrupts you. Timed blocks are weak against all four.

Twenty-five minutes sits in a specific sweet spot. It is short enough that you cannot credibly claim you are too tired for it, which is the whole trick, and long enough to get past the two or three minutes of throat-clearing that begin any piece of work — finding the file, remembering where you stopped, re-reading the last paragraph you wrote.

It also produces clean arithmetic, which matters more than it should. A 25-minute block plus a 5-minute break is exactly half an hour. Two rounds is an hour. Four rounds is two hours and a long break. When you are planning a week around gaps between lectures, being able to do that math in your head without a calculator is a real advantage over an idiosyncratic 37-minute interval.

The five-minute break is short on purpose. It is deliberately too brief to start anything with its own gravity — a five-minute break cannot become an episode. It is long enough to stand up, refill a glass and let your eyes focus on something farther away than a screen, and that is all it is for.

The cost of 25 is re-entry. Every block spends its first minutes reloading context, so with short blocks, a larger share of your total time goes to reloading. For work made of small repeatable units — flashcards, short problems, vocabulary, reading a section at a time — that cost is near zero and 25 is ideal. For work where you hold a whole structure in your head, it is expensive, and that is the case for a longer block.

Treat 25/5 as the default rather than the rule. The right length is a function of two things: how expensive it is to reload the task, and how much uninterrupted time you actually have.

Fifty minutes is for work with a high reload cost. A proof you are halfway through, a problem set where each question depends on the last, a draft where you are holding an argument in your head, a lab report, a dense reading you are annotating as you go. Stopping at 25 in the middle of that costs you the structure, and you pay to rebuild it. Pair a 50 with a 10 or 15 minute break, because a longer block earns a longer recovery and five minutes will not feel like enough.

Forty-five is the sensible single-sitting default and the one to reach for if you are unsure. It is long enough for real work on a hard task and short enough that a 90-minute evening holds two of them with a break in between. It is also the session length Semora's Smart Plan uses by default when it lays study sessions across your calendar, with 25 and 50 available as alternatives.

Fifteen exists for the gaps, and college is mostly gaps. The stretch between a lecture ending and the next one starting, the twenty minutes before a lab, the bus, the line at the dining hall. A 15-minute block will not get you through a problem set, but it will get you through a flashcard deck, one worked example, the outline of a paragraph, or the first ten minutes of the thing you have been avoiding for four days, which is often all that thing needed. Use it as a wedge, not as your main method.

• 15 minutes: flashcards, one worked problem, an outline, admin, or breaking the seal on a task you keep postponing.
• 25 minutes: anything made of small repeatable units — problem sets with short questions, reading a section at a time, vocabulary, note clean-up.
• 45 minutes: the general-purpose block. Two of them plus a break fills a standard evening session.
• 50 minutes: deep reading, proofs, essay drafting, code, lab reports — work where losing the thread costs you more than the extra fatigue.
• Break pairing: 5 after a 15 or 25, 10 after a 45, 10 or 15 after a 50.

The break has two jobs. It has to be genuinely different from the work, and it has to end. Most people fail the second one, and a break that does not end is just the end of the session.

Different means different in kind, not different in content. Standing up is the single most reliable version — leave the chair, walk to another room, refill a glass, look out of a window at something far away, stretch your shoulders, wash a plate. Anything that moves your body and changes what your eyes are doing will return you to the desk in better shape than five minutes of sitting still in the same posture.

The failure mode is a feed. This is not a moral point about phones, it is a mechanical one: a feed has no natural end, so nothing in it tells you the five minutes are up, and it recruits exactly the attention you were trying to rest. You come back having neither rested nor worked. If you must have your phone in the break, make it a call to someone, or a specific reply you owe, because both of those finish.

The long break after four rounds is different and should be treated as such: fifteen to thirty minutes, eat something, go outside if there is any outside available. It is the one place a genuinely restorative pause fits. The one exception to all of the above is the honest one — if the bell catches you mid-sentence or mid-derivation, finish the thought and then break. Following the rule off a cliff is not the point of the rule.

Interruptions come in two kinds and they need different handling. External ones arrive from outside: a roommate at the door, someone in the library asking a question, a message that lights up the screen. Internal ones arrive from you: the sudden memory that you have not emailed the professor about the extension, or that you need to check whether the lab is in room 4 or room 6.

Internal interruptions have a good, cheap fix. Keep a scrap of paper or a note on your phone beside you and write the thought down in five seconds, then go straight back. The writing is the deal: you are not ignoring the thought, you are scheduling it for the break. Most of what breaks a study block is not the world, it is a brain trying to make sure you do not forget something, and a written line satisfies it completely.

External ones on campus need a sentence, not a system. The strict version of the technique is to inform the person you are mid-block, agree a time to come back, and then actually come back. The practical version is "give me twelve minutes" said out loud. Both work because they make the interruption finite instead of open-ended.

Then there is the question of what to do with the damaged block. The original rule is strict: an interrupted pomodoro is void, and you start it again. That is stricter than most people need, but the principle behind it is worth keeping — a block you half-attended should not go in the count as a completed one, because the count is your record of how long work takes, and a padded record makes every plan you build on it wrong. A workable compromise: if you lost under a minute, carry on. If you lost five, reset the block and start it again.

• Keep a capture list within reach and use it in under five seconds.
• Say the finite version out loud: not "I'm busy" but "give me twelve minutes".
• Put the phone out of arm's reach. Face-down on the desk is still within reach.
• Lost under a minute, keep going. Lost five, reset the block rather than counting it.

The largest limit is the one this page opened with, and it is worth stating flatly: the technique does not tell you what to work on. It is a container, and it will hold whatever you put in it, including the wrong thing. The symptom is unmistakable once you know to look for it — you start the timer, and then spend the first six minutes deciding what the block is for. That is not a focus failure. That is a planning failure showing up at the moment you sit down, and it needs a plan, not a longer timer.

A related limit: timers do not create hours. If your week holds fourteen hours of work and six hours of usable gaps, timed blocks will make that arithmetic visible faster, which is genuinely useful, but the arithmetic does not change. At that point the decision you need is which deadline slips or gets a smaller version of your effort, and that is a triage question.

The technique also fits some work badly. A three-hour lab, a group meeting, a seminar, an exam, a shift — these have their own clocks and do not want yours. Timed blocks are for solo, self-directed work where nothing external is setting the pace. Trying to Pomodoro a group project meeting will annoy everyone in it.

Two smaller traps. Counting blocks can quietly become the activity — the number is a measurement, not a score, and eight shallow blocks is worse than four real ones. And a vague task fails inside a 25-minute box in the same way it fails across an entire evening. "Work on the essay" is not a block. "Outline section two" is. If you cannot say what the block is for in one short phrase, the problem is upstream of the timer.

The mistake in most study advice is imagining an evening. A college week is not shaped like an evening, it is shaped like a lecture at 9:30, another at 12:30, a lab on Thursday and a shift on Saturday. The hours that actually decide your semester are the awkward 60 to 105 minute gaps between classes, and almost nobody uses them, because a gap does not feel like enough time to start anything. A timer is very good at exactly that objection.

Run the arithmetic on a real Tuesday. Your lecture ends at 10:45 and the next one starts at 12:30. That is 105 minutes. Take off ten for walking and settling somewhere, and you have 95. That holds a 50-minute block, a 10-minute break and a 25-minute block, with time to pack up, which is a genuine hour and a quarter of work you would otherwise have spent on your phone in a corridor. Do that on three days and you have added the best part of four hours to your week without touching your evenings.

Then match the block to the gap rather than the gap to the block. This is the whole discipline. A 50 does not fit a 40-minute window and attempting it produces a rushed, resentful 40 minutes. A 15 fits almost everywhere. Decide the length when you see the gap, not the night before.

For evenings, pick a daily total and stop there. Ninety minutes a day, five days a week, is a serious amount of study. Ninety minutes a day is also the daily total Semora's Smart Plan uses by default, though out of the box it plans weekends too, so left alone it will schedule seven days at 90 minutes rather than five, and you turn weekends off if you do not want them. In blocks, ninety minutes is two 45s with a break between them, or a 50, a 25 and a 15 if you want the long one first. A 50 plus a 25 is 75, not 90 — close enough on a tired evening, but count it honestly. The reason to fix the total in advance is that an open-ended evening tends to produce either four hours of guilt-driven grinding or none at all, and the fixed total reliably beats both.

• 15 to 25 minute gap: one 15-minute block. Flashcards or a single problem.
• 30 to 45 minutes: one 25 and a 5, or a straight 45 if you can skip the break.
• 45 to 60 minutes: one 45. This is the most common between-class gap and the most wasted.
• 60 to 90 minutes: a 45, a 10, then a 25 if there is room.
• 90 to 105 minutes: a 50, a 10, then a 25.
• Two hours or more: two 50s with a 10 between them, then a real break before deciding whether to continue.

The timer on this page is complete for what a timer does, and it costs nothing. Semora's Focus timer is a Pro feature in the app, and it offers exactly the same lengths — 15, 25, 45 or 50 minutes of focus, 5, 10 or 15 minutes of break. That is deliberate. There is no reason for the tool on this page and the one in the product to disagree with each other.

The difference is not the countdown. It is what the countdown is attached to. In Semora, a focus session starts from something specific: open a deadline and start a focus session against it, and the block carries that task's name with it, so the block is already defined before it begins. Start one from a Smart Plan study block and it arrives pre-set to that block's own length, and finishing the focus phase marks that block done. The counting problem — did that session actually happen, against what — stops being something you track on paper.

On iPhone and iPad, a running session is stored on the device rather than held in memory, so backing out of the screen or relaunching the app resumes the same session at the correct remaining time, and the end-of-phase alert is a real scheduled notification. It fires with the app in the background and the screen off, which is what you want, because the alternative is a timer that only works if you sit and watch it.

The part a standalone timer structurally cannot do is decide what the block is for. That is Smart Plan, and it is the honest reason the two sit next to each other in the app. Smart Plan reads every deadline across your courses, looks fourteen days ahead, and lays study sessions into your actual days — 90 minutes a day in 45-minute sessions by default, weekdays from 5pm and weekends from 10am, with 25, 45 and 50 minute sessions available and daily totals of 60, 90, 120 or 180. Weekends are included by default and can be switched off. It schedules around your class meeting times, because the syllabus scan already recorded when your classes are. When a deadline moves, the plan reschedules. You get a timer that already knows what it is counting down for.

If what you need first is simply knowing what is due, that part costs nothing. The free tier covers 5 syllabus scans a calendar month, up to 4 courses in a single semester (one semester total, because a free account cannot start a second term) full deadline and task tracking, weighted grade tracking with your semester GPA, and same-day reminders. Smart Plan, the Workload dashboard, flashcards, the AI tutor and the Focus timer sit on the Pro side, at $3.99 a month or $19.99 a year, which is about $1.67 a month. Pro is purchased in the iOS app and applies to your whole account, the web app included.

• Same focus lengths as this page: 15, 25, 45, 50. Same breaks: 5, 10, 15.
• Start a session from a specific deadline and the block is named before it starts.
• Start it from a Smart Plan block and it opens at that block's length; completing the focus phase marks the block done.
• On iPhone and iPad the session survives leaving the screen or relaunching, and the end-of-phase alert is a scheduled notification that fires in the background.
• Smart Plan decides what the block is for: 14-day horizon, 90 minutes a day in 45-minute sessions by default, weekends included unless you turn them off, scheduled around your class meetings.
• Focus timer and Smart Plan are Pro — $3.99 monthly or $19.99 yearly, bought in the iOS app, applied account-wide.