1 Minute Timer

The minute is the unit of “can you actually hold this”

Almost everything a one-minute timer gets used for is a thing that is easy for forty seconds and hard for sixty. A plank. A wall sit. A held stretch. The rest between two heavy sets, which feels generous when you set it and short when you are in it. That is precisely why people reach for a clock instead of counting: counting speeds up when the thing gets uncomfortable, and a timer does not.

The minute's other job is rhythm, and has nothing to do with endurance. Teachers use it for one-minute writing sprints and speed rounds where the point is the pressure, not the volume. Tutors use it to stop a single question from eating a session. It is the standard window for counting a pulse. In kitchens it is the resting minute after the pan comes off the heat, and at a basin it is half of the two-minute brushing time dental guidance commonly suggests — we have not assessed that literature and make no claim for it — so run it twice, or set the 5 minute timer if you would rather not watch the screen at all.

None of those uses need features. They need the number to be enormous, the start button to be one click away, and the alarm to be audible from the other side of the room. That is the whole design brief for this page.

Short timers fail differently from long ones

The usual complaint about browser timers is drift — the slow accumulation of error in a counter that adds a second every time an interval fires. Over a minute that effect is small. In our 60-second runs the naive counter was 347.7 ms behind after 59 ticks on an idle page — a rate that puts a full 60-tick minute about 354 ms late — and 670 ms behind after 59 ticks on a page kept busy with other work, which projects to 681 ms. The tick count matters: a counter that has fallen a second behind has by definition not yet delivered its sixtieth tick, so the figure it ends on is the lateness at tick 59, not at tick 60. Annoying if you are timing a sprint; invisible if you are holding a stretch.

What actually ruins a one-minute timer is a stall. When the tab's single thread is blocked — a heavy script, a background sync, a laptop that has just woken up — a tick-counting timer does not fire the ticks it missed. It resumes counting from where it stopped and is permanently behind. In our stall runs a single three-second freeze cost the naive counter 3 whole seconds it never got back: it displayed 12 seconds where 15 had passed. On a sixty-second timer that is 5.1% of the entire run, gone in one hiccup.

This page never counts ticks. It stores the instant your minute is due to end and subtracts the current time from it on every frame, so a freeze costs you nothing but a frozen picture — the first frame after it re-reads the clock and shows the truth. The full measurement, method and all, is on the main countdown timer page.

Getting a clean minute

Unlock the sound first. Browsers refuse to let a page make noise until you have interacted with it, which is a rule worth having and a nasty surprise when your alarm turns out to be silent. Pressing start counts as the interaction, and the alarm is booked as soon as the browser confirms the audio is actually running — which is a moment after the click, not during it, so the code waits for that confirmation before it books anything. That is why the very first run of the session is armed and not just the second. If you want to be certain before you commit, the tool says in plain words whether sound is ready.

Go full screen for group work. The full-screen button scales the digits to the height of the display, which is the difference between a timer a class can see and a timer the front row can see. Press F for it, Space to start and pause, and R to reset — useful when your hands are chalky, wet or holding something.

For repeated rounds, reset instead of reloading. Reset returns to a full minute instantly and keeps your sound unlocked; a page reload throws both away. If your rounds need a rest between them, the honest answer is that two timers running by eye is worse than one structured cycle — try the Pomodoro timer, which alternates work and break automatically, or step up to the five-minute countdown for the longer intervals.

The numbers behind a 1 minute timer

Every row here is worked out from the duration itself: the conversions are arithmetic on 60 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.

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 60 seconds, so the rows that cross midnight are right for the same reason the rest are.