Pomodoro Timer

1. Pick one task — anything that needs a chunk of focused attention. Studying, coding, a draft, deep email triage.
2. Start a 25-minute timer(or any focus duration from the preset row). Work on the task only — no Slack, no Twitter, no "quick checks." If something else pops into your head, jot it down for later and return to the task.
3. When the timer rings, take a 5-minute break. Stand up, walk, stretch, drink water. Stay off screens if you can.
4. Repeat. After four focus sessions, take a longer 15–30 minute break to recharge.
5. Track tasks vs. pomodoros: estimate how many sessions a task should take, then compare estimate to actual. Over a week this gives a useful sense of your real working pace.

Scenario presets explained

The classic 25/5 schedule fits most knowledge work, but engineers, writers, and researchers often need longer focus blocks. These are the patterns most teams have converged on.

When the Pomodoro Technique doesn't work

• You're in deep flow. If you're genuinely absorbed and producing, don't interrupt for the sake of the rule. Cirillo himself said the timer is a tool, not a contract.
• Tasks shorter than 5 minutes. Batch them into a single pomodoro instead — one focus session for "clear inbox + respond to standup + close 3 review comments."
• External constraints (live customer calls, paired-coding sessions, meetings). Pomodoros require uninterrupted control of your own time.
• You ignore the break. Skipping breaks defeats the technique. The break is the part that lets focus regenerate.

Pomodoro Technique reference

Where it came from, why 25 minutes, the variations that have evolved since 1987, and the small decisions that make the difference between a productive day and another stack of unfinished tabs.

Why is it called “Pomodoro”?

Pomodorois Italian for “tomato.” The technique was invented in the late 1980s by Francesco Cirillo, an Italian university student. He used a tomato-shaped kitchen timer on his desk to enforce 25-minute work intervals — and the name stuck. The original technique was set down in his 1992 self-published book; the trademark followed in 2003.

Why 25 minutes?

There's no strong scientific case for exactly 25 minutes — Cirillo picked it as the longest stretch he could keep focused without his mind drifting. The research on sustained attention generally supports bursts of 25–90 minutes with restorative breaks, not any single magic number. What matters more than the length is the structure: defined work, defined break, a fixed boundary between the two.

The Ultradian Rhythm Hypothesis (Nathan Kleitman, 1960s) proposed that the brain cycles through ~90-minute periods of alertness followed by 20-minute troughs. Some researchers use this as a rationale for the 90/20 schedule. The 52/17 split was popularized by a 2014 DeskTime study of high-performing employees. None of these are betterthan 25/5 — they're alternatives for different work types.

Pomodoro variations worth knowing

• Classic 25/5/15— Cirillo's original. Best for tasks with low ramp-up cost (studying, reading, simple writing).
• 52/17 — From a 2014 DeskTime study of the most-productive 10% of their users. Better for tasks where 25 minutes is just warm-up.
• 90/20 (Ultradian) — Tracks the 90-minute attention cycle. Suited to research, design, music practice, and any work with high context-switch costs.
• Flowtime / Flowmodoro (Zoë Read-Bivens, 2015) — No fixed timer. Start working, record your start time, work until you feel yourself break focus, then take a break proportional to your focus duration (15-min focus → 3-min break; 60-min focus → 12-min break). Used by people who find arbitrary timer interruptions disruptive.
• Animedoro (Josh Chang, 2019) — 60 minutes of focused work followed by 20 minutes of break, where the break is intentionally long enough to watch one anime episode (or any reward activity). High-stamina study version.
• Time-blocking — Not a pomodoro variant per se, but commonly combined: pre-schedule specific tasks into calendar blocks of 25/50/90 minutes, then run a pomodoro inside each block.

The original rules (and how people actually use it)

What to do during the break

The break is the part most people get wrong. It's not “watch a YouTube video” or “scroll Twitter” — those keep your attention engaged in the same way work does, so when the bell rings you're no fresher than before. Better options:

• Stand up. Walk to another room. Look out a window.
• Drink water. Get a snack.
• Light stretches — shoulders, neck, wrists if you're typing.
• Short breathing exercise (e.g. box breathing 4-4-4-4 for 1–2 minutes).
• For long breaks: a short walk outdoors, a real meal, time away from any screen.

Built-in reliability features

• Wall-clock anchored countdown. The timer is anchored to an absolute end time, not to ticks of setInterval. Background-tab throttling, browser sleep, and OS pauses don't cause drift — when the tab regains focus, the time displayed is correct to the second.
• Browser notificationwhen each pomodoro ends, so you don't miss the bell when the tab is in the background. Permission is requested the first time you press Start.
• Remaining time shown in the browser tab title — glance at any tab strip to see progress without switching back.
• State persists across refresh. If you accidentally reload the page mid-pomodoro, the timer continues from where it was.
• Keyboard shortcuts: Space to start/pause, R to reset, M to mute.