A countdown only pays off when something else tells you it ended.
Sauce on a back burner. A chapter you promised yourself twenty-five minutes for. A stretch between two meetings. Each one fails the same quiet way: you glance at the pot, then a message, then the document, and zero passes with nobody in the room noticing.
The timer with alerts on this page stacks a shrinking ring, a tone built in the browser, an optional system notice, and a short vibration on phones that honor it. Your label, volume, and toggles stay in local storage on this device. Toolexe never receives them.
The four tones are oscillators, not sound files
Nothing is downloaded. Web Audio builds each alert from scratch the moment the count hits zero, or when you press Test tone. A click is required first. Browsers refuse to start an audio context until you press Start or Test, so a countdown that nobody ever started will reach zero in silence.
- Beep
- Square wave. 880 Hz, then 660 Hz, about 0.6 seconds. The extra harmonics cut through a fan or a podcast. Default choice for a kitchen.
- Chime
- Sine from 523.25 Hz (C5) gliding to 1046.5 Hz (C6), then a fade near one second. Quieter in a shared office.
- Bell
- Sine at 1174.66 Hz plus a softer harmonic at 2349.32 Hz. The second oscillator is what makes it ring. Decay runs a little past a second.
- Alarm
- Sawtooth flipping between 880 Hz and 1320 Hz, five times, a tenth of a second apart. Loudest of the set. Pick it when you will not be facing the screen.
Volume is a straight gain scale. Fifty percent is the stored default. Zero mutes the tone and leaves the ring plus the notification. Repeat fires the same oscillator three times, 900 milliseconds apart. Leave the repeat on for food. Turn it off in a library.
What still reaches you in another window
The tone plays only while this tab is open and the machine is unmuted. The notification is the layer for a second app. Allow notifications for toolexe.com or the toggle does nothing. The notice title is “Timer Finished!” and the body uses your session label. It asks the system to keep it up until you click, then closes itself after twelve seconds if you do not.
Vibration follows 200 ms on, 100 off, 200 on, 100 off, 400 on. A phone browser that implements navigator.vibrate will buzz. Desktop Chrome ignores the call. iOS Safari has long ignored web vibration. Treat the buzz as a bonus.
Set the ten-minute chip, label it Sauce, press Test tone, then Start. Do that before you leave the stove, not after you smell the reduction.
A single countdown is the wrong shape for some jobs
The 25-minute chip is a duration. It does not roll into a break, and it does not count rounds. If the point is work-then-rest with a tally, use the Pomodoro timer.
HIIT and repeated work-rest pairs belong on the interval timer. Resetting this page between sets is how the rest interval gets skipped.
A launch date, a birthday, a departure clock: those are moments on a calendar, not a length you type. The countdown timer points at a target instant.
An open task with no end time is a stopwatch. Client hours you need on an invoice belong in the work time tracker after the alert fires. Two timestamps you already lived through, with breaks and a billing round, are a job for the duration calculator. This page will not reconstruct a span after the fact.
Ten minutes of sauce, then a chapter
Sauce. Chip says 10 min. Label says reduction. Alarm tone, repeat on, notification on. Keep the tab in front. A background window delays the ring. The display corrects from the wall clock on the next tick, but the tone waits until a tick runs. A tab frozen for two minutes rings two minutes late.
Chapter. 25 min, label “Chapter 4”, chime, repeat off. Space starts and pauses when focus is outside a field. Ctrl+S, or Cmd+S on a Mac, writes the hour, minute, and second boxes into the ring. Ctrl+R resets to the full duration. Ctrl+C copies the readout. If the label is still the default word Timer, the clipboard gets the clock alone. Otherwise you get the clock, a hyphen, and the label.
Roast check. Two hours, bell, notification on, tab parked beside the recipe. This is the case where the notice matters more than the ring. You are reading, not staring at the circle.
Drift, a reload, and the jobs this page refuses
While the tab stays awake, the loop reads the clock every quarter second and subtracts real elapsed time. A late tick does not drop seconds inside an active tab. Hidden tabs are a different contract. Chrome, Safari, and Firefox slow timers you cannot see, to save battery. Keep this tab visible for pasta water and for any practice block you would be annoyed to miss.
Press Apply duration and the fields, label, volume, tone, and three toggles land in localStorage under timerPrefs. The seconds still running are not stored. Refresh the page and you get the saved length, sitting at Ready, not the remainder you had left. Clear site data and the label goes with it.
The hour box stops at 23. Minutes and seconds stop at 59. Longest run from the inputs is 23 hours, 59 minutes, 59 seconds. A roast that needs a check tomorrow morning wants a hardware timer, or the countdown timer aimed at a clock time.
Study-section timing is a fair use. A proctored exam, a medication schedule, and a lab incubation are not. Those need a controlled clock with a record. A browser tab is a reminder, and a fragile one.
Notification permission is requested on load while the browser still shows the default state. Some browsers ignore that request until a click. If the toggle is on and no notice appears at zero, check the site permission in the address bar, then run the countdown again.
