Pomodoro Timer

Runs focus and break cycles with a notification, a session log and configurable interval lengths.

Twenty-five minutes of work, five off, a longer break every fourth round — with the lengths adjustable, because the useful interval is the one you will actually sit through. Each finished block is logged with whatever you named it, so the session ends with a list of what the time went on.

🔒 Runs entirely in your browsertimerpomodorofocus

Focus · round 1

25:00

Settings

Focus (min)Short break (min)Long break (min)Rounds before long break

Start the next phase automatically

Chime when a phase ends

Browsers throttle timers in a background tab — Chrome slows them to once a second when hidden, and to about once a minute after a few minutes. The countdown above is computed from the clock, so it stays correct; the chime is not, and can arrive late. A system notification is the reliable signal, so turn it on if you switch tabs while a block runs.

The technique as Francesco Cirillo describes it: 25 minutes of work, 5 minutes off, and a longer break after four rounds. Those are the defaults; the useful length is the one you will actually sit through.

How to use it

Name what you are about to do
The label under the clock goes into the session log with the block. Leaving it empty works; the log is then just durations.
Set the intervals once
Focus, short break, long break and how many rounds before the long one. The settings are remembered in this browser, so this is a one-time step.
Turn notifications on if you switch tabs
The chime is played by a callback the browser throttles when the tab is hidden. A system notification is not throttled, and is the only alert that will reliably reach you in another tab.
Read the log at the end
Rounds, focus time and a per-label breakdown, with a copy button for pasting into a standup note or a timesheet.

Common questions

The countdown is right but the chime came late. Why?

The number is computed from the system clock on every repaint, so it is correct the moment you look at it. The chime is a scheduled callback, and Chrome slows those to about once a minute in a tab that has been hidden for a while. This is a browser rule, not a bug here — use the notification.

Does the timer keep running if I close the tab?

No. Closing the tab ends it. Switching to another tab or another application is fine — the clock and the wake lock survive that.

Where does the session log go?

Into this browser, capped at the most recent 500 entries. Nothing is uploaded and there is no account, so copy the summary out if you need it beyond this machine.

Why 25 minutes?

It is the interval Francesco Cirillo described, and it is a default rather than a finding. If 50/10 fits the work better, change it — the technique is the structure, not the number.