The half hour as a workout block
Thirty minutes is the length most home training sessions settle on, and interval work is where a visible countdown earns its place. In a circuit, the thing you need is not the total — you know the total — it is the ability to glance at a screen mid-effort and know without arithmetic whether you are a third of the way in or nearly done. The digits on this page are sized for exactly that glance, from a mat, mid-rep, without a phone in your hand.
The structure inside the half hour is yours: work and rest intervals, rounds, or a straight block with the clock simply running down. This page runs one countdown and nothing more, which is a deliberate limit — an interval timer that beeps every forty seconds needs to be configured, and configuring is the thing people do instead of training. If you want an automatic alternation, the Pomodoro timer is the structured version, and the 1 minute timer covers single rounds and rests between sets.
One honest caveat about training: this is a clock, not a coach. It knows nothing about your intervals, your fitness or your recovery, and it will happily count down while you do something unwise.
Cooking, study and the half-hour habit
Away from the mat, the half hour is the most-used slot in a kitchen after five minutes: the roasting stage, the proving, the simmer, the "check it in thirty". It is also the classic study block — long enough to get past the reluctance, short enough to promise an end — and the reason so many revision timetables are drawn in half hours.
The kitchen case has a specific requirement the others do not: you will not be looking at the screen. Everything depends on the alarm, and on the tab still being alive when it fires. Two practical rules follow. Leave the tab open, and check the sound once before you rely on it — the tab title also counts down, so you can see the remaining time in the tab strip without switching to the page.
For a longer bake or a full revision session, the 1 hour timer is the next step up; for the checkpoints inside a half hour, the 10 minute timer and 15 minute timer are the same tool at a finer grain.
What half an hour does to a sloppy timer
Thirty minutes is long enough that accumulated error becomes something you could, in principle, catch. Projected from the drift rates we measured, a naive tick-counting countdown finishes a half hour roughly 11 s late on an idle page and 20 s late on a page busy with other work — the second of those being about the length of a rest interval.
The failure that actually bites in a kitchen is different and much larger. When a tab's thread freezes, a tick counter loses the ticks outright: our measured three-second freeze cost it 3 whole seconds, which it never recovered. On a half-hour timer a single freeze like that is 0.2% of the run — small, but it stacks with every other freeze in thirty minutes of a real machine doing real work.
This page has no ticks to lose. It stores the instant your half hour ends and subtracts the clock from it on every frame, so a freeze costs a frozen picture and nothing else. The full method and the raw runs are on the online timer home page.
The numbers behind a 30 minutes timer
Every row here is worked out from the duration itself: the conversions are arithmetic on 1,800 seconds, and the accuracy rows come from the drift measurement described on the home page. The source column says which is which.
One disclosure belongs beside the table itself, where you will actually read it: those drift figures were measured in Node v22.20.0 on one Windows desktop, not in a browser (win32 10.0.26200, AMD Ryzen 9 9950X3D 16-Core Processor, on 2026-08-14). Each condition was run 5 times and the figures used here are the medians, because single runs of this kind vary by more than the difference they are being used to describe. Your machine will produce different numbers. What transfers is the shape — a counter that accumulates drifts, and a counter that subtracts from a fixed instant does not.
| 30 minutes timer | Value | Source |
|---|---|---|
| Length in seconds | 1,800 s | arithmetic |
| Length in milliseconds | 1,800,000 ms | arithmetic |
| Share of one hour | 1/2 | arithmetic |
| Ticks a naive 1-per-second counter makes | 1,800 | arithmetic |
| Finish lateness of a naive counter, idle page | 11 s | projected |
| Finish lateness of a naive counter, busy page | 20 s | projected |
| Share of the timer lost to one 3-second frozen tab | 0.2% | derived |
| Half hours in one hour | 2 | arithmetic |
| Half hours in an eight-hour day | 16 | arithmetic |
Start now, finish when?
The most common question about any fixed-length timer is what time it lets you out. These finish times are computed at build time from the start time plus 1,800 seconds, so the rows that cross midnight are right for the same reason the rest are.
| If you start | Start (24 h) | Start (12 h) | It ends | Ends (12 h) | Day |
|---|---|---|---|---|---|
| Training before work | 06:30 | 6:30 AM | 07:00 | 7:00 AM | same day |
| In the oven before lunch | 11:45 | 11:45 AM | 12:15 | 12:15 PM | same day |
| First study block of the evening | 17:00 | 5:00 PM | 17:30 | 5:30 PM | same day |
| Second block after dinner | 20:15 | 8:15 PM | 20:45 | 8:45 PM | same day |
| Half hour into the next day | 23:45 | 11:45 PM | 00:15 | 12:15 AM | next day |