Countdown Timer

What you get

One input and four boxes. You set a target to the minute, and the page shows the time left as whole days, then hours (0 to 23), minutes, and seconds, each padded to two digits. Days are not capped or rolled into months, so a target a year and a half away shows something like 548 days. Fractions of a second are dropped, so the display can read all zeros for up to a second before switching to the Time's up! message. If you choose a time that has already passed, you see that message straight away.

It is a single-target, on-screen countdown. It does not loop, pause, or count up after the target, and it does not keep running once the page is closed. All of the work happens in your browser: no account, and the countdown itself never contacts a server.

Example: counting down to New Year

At noon on Friday, October 23, 2026, set the target to January 1, 2027 at 00:00. On a computer set to UTC the boxes read 69 days, 12 hours, 00 minutes, 00 seconds. On a computer set to New York or London time, the same two wall-clock times give 69 days, 13 hours. Both regions turn their clocks back an hour before the end of the year (Europe on October 25, the US on November 1), so 69 days and 12 hours of calendar time takes 69 days and 13 hours of real time to pass. The countdown follows real time, which is what you want: midnight on New Year's Eve arrives exactly when the boxes hit zero.

Why the countdown does not drift

A countdown built by subtracting one from a counter every second is only as accurate as the browser's timer, and browsers deliberately slow timers down in hidden tabs to save battery. Leave such a timer in the background for an hour and it can fall behind noticeably. This one stores only the target. Once a second it reads the system clock, takes the difference, and redraws. A late tick just means a slightly delayed redraw, never a wrong number. The flip side: if your computer's clock is wrong, the countdown is wrong by the same amount. Most devices sync their clock automatically, so this is rarely a problem.

Related timers

To time something that has already started, use the stopwatch. For work-and-break rounds with an audible beep, the Pomodoro timer is the better fit. To measure the gap between two dates without a live display, including a business-day count, use the duration calculator. If you are scheduling a launch or maintenance window for people in several countries, read why future local-time events need a time zone name, not just a UTC offset, because this countdown always uses the viewer's own zone.

Frequently asked questions

Will the countdown stay accurate if I switch tabs?

Yes. Browsers slow down timers in background tabs, but each tick recalculates the remaining time from your system clock instead of subtracting one second from a stored number. When you come back to the tab, the display jumps straight to the correct value. A countdown that counts ticks would drift; this one cannot.

Does it play a sound or send a notification when time is up?

No. When the target passes, the four boxes are replaced by a Time's up! message, and that is all. There is no alarm, no notification, and no change to the tab title, so it only helps if the page is on screen. For a timer that beeps at the end of each round, use the Pomodoro timer.

If I close the page, is my countdown saved?

No. The target lives only in the open page. Reloading or reopening it resets the field to 24 hours from now. Nothing is stored in the browser or put in the URL, so a countdown cannot be shared as a link.

Which time zone does the target use?

Your device's local time zone. If you type 9:00 AM on January 1, the countdown ends when your computer's clock reads 9:00 AM on January 1. Someone in another zone who types the same time into their own browser is counting down to a different moment. For an event set in another city's time, convert it first with the time zone converter.

Why is the hours figure one more or one less than I expected?

A daylight saving change falls before the target. The countdown measures real elapsed time, so a target on the far side of a fall-back night is one hour further away than plain calendar arithmetic suggests, and a spring-forward night makes it one hour closer.