induwara.lk
induwara.lkProductivity · Time

Pomodoro Timer — 25-Minute Focus Cycles, Free & No Signup

The classic 25-minute focus and 5-minute break cycle with a long break every four sessions. Customisable durations, two-tone audio chime, and a tab title that ticks down while you work — everything runs in your browser.

By Induwara AshinsanaUpdated May 11, 2026
Focus session25/5/15
Cross-checked · 2 algorithms
Focus— ready
25:00remaining focus

Session totals

Focus done
0
Focus time
0m
Break time
0m
Total elapsed
0m
Cadence presets
Daily totals match an independent algorithm. Everything runs in your browser — completed counts and settings never leave your device.

How it works

The Pomodoro Technique was developed by Francesco Cirillo in the late 1980s while he was a university student in Rome. He used a tomato-shaped kitchen timer (pomodoro in Italian) to break study sessions into fixed 25-minute blocks separated by short breaks. The cadence proved durable enough that it now ships as the default focus mode in dozens of productivity apps.

One pomodoro is 25 minutes of single-tasking followed by a 5-minute break. After four pomodoros, the short break is replaced by a longer 15 to 30 minute break to reset attention before the next set. The full sequence on this timer is:

  1. Focus block (default 25 minutes) — one task, no context-switching, interruptions are deferred.
  2. Short break (default 5 minutes) — physically step away from the screen if you can. Stretch, drink water.
  3. Repeat focus + short break four times.
  4. Long break (default 15 minutes) after the fourth focus — a genuine context switch. Walk outside, eat, or close your eyes.
  5. Reset to step 1 and continue the cycle.

The state machine is deterministic. Given the count of completed focus sessions k, the break that follows is (k mod N) === 0 long, else short, where N is the "long break every" setting (default 4). Totals are computed two independent ways — once via a closed-form arithmetic formula and once via a step-by-step walk through the sequence — and the "cross-checked · 2 algorithms" badge in the live header appears only when both agree to the second.

The countdown ticks once per second using a wall-clock difference, so the remaining time stays accurate even when your browser throttles background tabs to 1Hz. The tab title updates with the format MM:SS · Focus so a pinned tab is glance-readable. The end-of-phase chime is two short sine tones (880 Hz then 660 Hz) synthesised via the Web Audio API — no audio file is downloaded.

Worked examples

Classic 25/5, four pomodoros: how much wall-clock time?

  1. Pomodoros: 4 × 25 = 100 minutes of focus
  2. Short breaks between: 3 × 5 = 15 minutes (between sessions 1→2, 2→3, 3→4)
  3. No long break has fired yet — the long break comes AFTER session 4
  4. Total elapsed when the fourth focus ends: 100 + 15 = 115 minutes (1h 55m)
  5. summariseSessions(4, defaults) returns 6900s — confirmed by both algorithms ✓

Classic 25/5, eight pomodoros (one long break taken)

  1. Pomodoros: 8 × 25 = 200 minutes of focus (3h 20m)
  2. Breaks between 7 boundaries: 1 long (after session 4) + 6 short
  3. Long break time: 1 × 15 = 15 minutes
  4. Short break time: 6 × 5 = 30 minutes
  5. Total: 200 + 15 + 30 = 245 minutes (4h 5m) = 14,700 seconds
  6. Cross-checked: closed-form formula and step-by-step walk both report 14,700s ✓

Deep Work 50/10 preset, three pomodoros (long break every 3)

  1. Settings: focus=50, short=10, long=20, longBreakAfter=3
  2. Three focus sessions: 3 × 50 = 150 minutes of focus
  3. Breaks between sessions 1→2 and 2→3: 2 × 10 = 20 minutes short (k=1, k=2 not divisible by 3)
  4. No long break yet — would fire after session 3 only if a fourth session is started
  5. Total when third focus ends: 150 + 20 = 170 minutes (2h 50m) = 10,200 seconds
  6. Cross-checked: walking the state machine 3 times returns the same totals ✓

Frequently asked questions

Sources & references

Related tools

Rate this tool
Be the first to rate

Comments & feedback

Spotted a bug or want an improvement? Tell us — our team reviews every comment, and good ideas get built. Comments are public and anonymous.

Found a bug, edge case, or want to suggest an improvement?

Email me at [email protected] — most fixes ship within 24 hours.