Online Timer
A full-screen countdown timer with quick presets and an alarm, running in your browser with no account and no installation.
⏰ Time's up!
A countdown over 596 hours finishes the moment you start it
Browsers store a timeout's delay in a signed 32-bit integer, so the largest one can hold is 2,147,483,647 milliseconds — 596.52 hours, or 24.855 days. Ask for more and the value overflows, the delay reads as long past, and the callback runs at once:
| Requested | In milliseconds | What happens |
|---|---|---|
| 24 hours | 86,400,000 | works |
| 100 hours | 360,000,000 | works |
| 500 hours | 1,800,000,000 | works |
| 596 hours | 2,145,600,000 | works |
| 597 hours | 2,149,200,000 | fires immediately |
| 1000 hours | 3,600,000,000 | fires immediately |
The boundary sits at 596.5232 hours, so 596 is the largest whole number of hours that works. Nothing in the interface suggests a limit, and the failure is not an error message — it is a timer that reads 00:00 the instant it starts. For anything longer than three weeks you want a calendar reminder, not a timer.
And at the other end, rounding the right way
The display rounds the remaining milliseconds up rather than down. That sounds like a detail and it decides how the last second feels:
| Remaining | Rounding up (this page) | Rounding down |
|---|---|---|
| 3000 ms | 00:03 | 00:03 |
| 2999 ms | 00:03 | 00:02 |
| 2000 ms | 00:02 | 00:02 |
| 1000 ms | 00:01 | 00:01 |
| 999 ms | 00:01 | 00:00 |
| 1 ms | 00:01 | 00:00 |
| 0 ms | 00:00 | 00:00 |
Rounding up shows 00:00 for 1 millisecond — the instant the timer ends. Rounding down would show it for 1,000, a full second during which time still remained, so the alarm would sound a second after the screen had already reached zero.
Every number on screen gets exactly 1,000 milliseconds of airtime — measured across the whole range, the shortest and longest are identical. That is what people expect from a countdown, and it is why the choice is correct rather than arbitrary.
One thing it does not handle: the format switches from
1:00:00 to 59:59 the moment
the hour digit reaches zero, dropping from 7 characters to
5. On a large timer that is a visible jump in width partway through,
and it happens once, silently, at 59:59.
How to use
- Set a duration, or pick one of the quick presets.
- Press start, and switch to full screen if it needs to be visible across a room.
- Keep the tab open so the alarm can reliably sound when time is up.
- Allow sound if your browser has blocked audio on the page.
- Reset and reuse it as often as you like — nothing is saved or sent anywhere.
Frequently asked questions
Will the alarm sound if the tab is in the background?
Usually, but browsers throttle background tabs to save power, so the moment it fires can drift and audio may be suppressed until you have interacted with the page. Keeping the tab visible, or at minimum having pressed start yourself, makes the alarm dependable.
Why did no sound play?
Browsers block audio that begins without user interaction, to stop pages playing sound unprompted at you. Pressing start counts as that interaction, so a timer you began yourself will normally sound. A timer restored automatically when the page loaded may not, because nothing was pressed.
Does it keep time accurately while throttled?
Yes. The remaining time is calculated from the system clock rather than by counting ticks, so it stays correct even when the browser slows the page down. What can be delayed is the instant the alarm fires, not the arithmetic behind the countdown.
What are the presets for?
Common intervals — brewing tea, short exercise rounds, timed study blocks — so you can start immediately without typing a duration. The 25-minute preset is the standard focus interval popularised as the Pomodoro technique, usually paired with a short break afterwards.
Can I run more than one timer at once?
Open the tool in separate browser tabs, one timer per tab. Cramming several into a single view sounds convenient and in practice makes it harder to see at a glance which one is about to finish, which rather defeats the point.
Does this work offline?
Once the page has loaded, yes — the timer runs entirely in your browser with no server involved at any stage. Nothing about what you are timing is recorded, transmitted or stored.
Is a browser timer accurate enough for cooking?
Comfortably. The underlying accuracy is far finer than any cooking task requires, and the practical limit is how quickly you get to the kitchen rather than anything about the timer itself.
🔒 This tool runs entirely in your browser. Nothing you enter is uploaded, logged, or stored.