The Pause button on this page does not stop the clock. It only silences the alarm after the time is already up. The single field takes minutes, not seconds: default 5, accepted range 0.01 to 1440, so 0.5 gives you 30 seconds. Everything runs in the tab, and closing the tab ends the timer.
Where is the pause button?
Not in the settings row, and not while the clock is running. The only control labelled Pause is hidden until the alarm starts beeping, and clicking it just cuts the tone. By that point the countdown has already hit zero.
Pausing mid-run is the main button. It reads Start, then Stop while the timer runs: click Stop and the remaining time freezes, click again to carry on from the same point. Reset sends the display back to the minutes in the field.
Why does 90 mean 90 minutes?
The label is min, and the page multiplies the field by 60,000 milliseconds. I tested that multiplication and the bounds check by lifting both out of the page’s script and running them locally: 0.01 comes out as 00:01, 1.5 as 01:30, 90 as 90:00. Anything below 0.01 or above 1440 is refused with “Input format & limitations: 0.01–1440 min”.
The input accepts decimals, so seconds come from fractions rather than a second field. The clock rounds up, so 0.01 briefly shows 00:01.
| What you type | What you get | Why |
|---|---|---|
90 | 90:00 | the field is minutes, not seconds |
0.5 | 00:30 | decimals are allowed |
1441 | error | 24 hours is the ceiling |
0 | error | 0.01 min is the floor |
Does it still work in another tab?
Partly. The tab title turns into something like “04:37 · Countdown” while the clock runs, so the remaining time is readable from the tab strip. The alarm still plays, because the tones are generated in the page: five beeps at 880 Hz, 0.65 seconds apart, gone after about 4 seconds.
A desktop notification is not automatic. You have to click Enable browser notifications, grant the permission, and leave that toggle on; without it nothing pops up when the clock ends in a background tab. Close the tab and the page clears its interval and shuts the audio context, so nothing survives a reload.
Good fit: a 5 to 60 minute timer you keep an eye on in the same tab. Not a fit: counting down to a clock time, repeating intervals, several timers at once, or anything that must survive a refresh.
One number field, two buttons, free, no account: the countdown timer on ToolPug.
Written by: someone who reads a page’s script before trusting its button labels
Last updated: 15 November 2026
Sources: the tool page itself, plus its duration and bounds logic re-run locally
Features and parameters follow the version of this tool page on toolpug.com as of November 2026.