Skip to content

Countdown Timer

The moment you are counting down to, in your local time. The timer ticks live, second by second.

The moment you are measuring from, in your local time. The elapsed time ticks live.

00:00:00

The stopwatch is at zero.

Start, pause, and reset a stopwatch that runs in this page. Closing or reloading the page resets it: nothing is saved or sent anywhere.

0days
0hours
0minutes
0seconds

      This tool counts time in UTC from the clock on your device, and it is for general guidance only. If your device clock is wrong, the countdown is wrong by the same amount. Check deadlines that carry legal or financial consequences against the official source that sets them.
      Quick answer: A countdown timer counts the days, hours, minutes, and seconds left until a date and time you pick. From noon on 20 November 2026, New Year 2027 is 41 days and 12 hours away: 3,585,600 seconds. Pick a target above and the timer ticks live, second by second. The same page measures time since a past moment and runs a stopwatch with pause and reset.

      Last reviewed: 20 November 2026. Reviewed every 180 days; next review due 19 May 2027.

      How to use the Countdown Timer

      A countdown timer answers one question: how much time is left until a moment you care about. This timer has three modes for three versions of that question. Countdown mode counts down to a date and time in the future. Elapsed mode measures how much time has passed since a date and time in the past. Stopwatch mode runs a live stopwatch from the moment you press Start, with pause and reset. All three modes run entirely in your browser: nothing you enter is saved or sent anywhere, and the timer reads the clock on your device, so it works with no account and no connection once the page has loaded.

      1. Count down to a moment. Pick the Countdown tab, give the event a name if you want one, and enter the target date and time. The timer starts ticking at once, second by second, and it keeps ticking as long as the page is open. From noon on 20 November 2026, New Year 2027 is 41 days and 12 hours away: 3,585,600 seconds.
      2. Use the quick chips. The chips under the target field set common targets in one tap: Next New Year, Christmas Day, 1 week from now, or 30 days from now. The New Year and Christmas chips always point at the next occurrence, so they never go stale.
      3. Measure time since a moment. Pick the Stopwatch and elapsed tab, leave the selector on Time since a date, and enter the start date and time. The timer shows how much time has passed since that moment, ticking live. Apollo 11 landed on the Moon on 20 July 1969 at 8:17 p.m. UTC: by midnight on 20 November 2026, that was 20,941 days, 3 hours, 42 minutes, and 20 seconds ago.
      4. Run the stopwatch. In the same tab, switch the selector to Live stopwatch and press Start. Press Pause to freeze the reading, press Start again to resume from the frozen reading, and press Reset to return to zero. The clock shows total hours, so a run longer than a day reads 25:00:00 and beyond.
      5. Read the results. The four boxes at the top show whole days, hours, minutes, and seconds. Below them, a plain-language sentence states the result in full, and the list underneath gives the same span as total seconds, total minutes, total hours, total days, and total weeks. The Copy result button copies the plain-language sentence to the clipboard.
      6. Watch what happens at zero. When a countdown reaches its target, the timer says so plainly instead of freezing or showing zeros forever. If the target has already passed, the timer switches to an elapsed state and shows how long ago it passed, rather than showing negative numbers.

      How it works

      The timer works on one simple idea: every moment is a number of milliseconds since 1 January 1970, and the time between two moments is the difference between their numbers. A countdown subtracts now from the target. Elapsed time subtracts the start from now. The stopwatch subtracts its start moment from now, minus any time spent paused. The difference is then split into whole days, hours, minutes, and seconds, and the same difference is shown as totals in each unit.

      Every calculation runs in UTC, which is the time scale the whole world uses as its reference. The date and time you type are read as your local time and converted to UTC before anything is calculated, so the same target entered in New York and in Los Angeles gives the same countdown: the two entries describe the same instant, only written in different local labels. The fixtures that test this tool use UTC timestamps with a Z suffix, so they give identical results on every device in every time zone. If you need to convert a target from one time zone to another before entering it, our Time Zone Converter does the conversion.

      Worked example 1: a countdown across months. From 20 November 2026 at noon UTC to 1 January 2027 at midnight UTC is 41 days and 12 hours. November has 30 days, so 10 days run from 20 November to 30 November, 31 more run through December, and 12 hours run from noon on 31 December to midnight. The total is 3,585,600 seconds, or 59,760 minutes, or 996 hours, or 5.9 weeks.

      Worked example 2: a countdown across a year boundary. From 31 December 2026 at 11:59:59 p.m. UTC to 1 January 2027 at midnight UTC is exactly 1 second. The timer says "There is 1 second left" and, one tick later, "The countdown has reached its target." From midnight on 31 December to midnight on 1 January is exactly 1 day.

      Worked example 3: time since a leap day. From 28 February 2024 at midnight UTC to 1 March 2024 at midnight UTC is 2 days, because 29 February 2024 sits between them. The same span in a common year is 1 day. The timer applies the full Gregorian leap year rule, so a span that crosses 29 February in a leap year always picks up the extra day.

      Worked example 4: the stopwatch with a pause. Start the stopwatch at noon and let it run until 12:10 p.m., with 2 minutes spent paused. The running time is 8 minutes, not 10: the engine subtracts the paused time from the wall-clock span. The clock reads 00:08:00, and the breakdown reads 0 days, 0 hours, 8 minutes, 0 seconds.

      What your result means

      A countdown has three states, and the timer names the one it is in. While the target is still ahead, the state is counting, and the boxes show the time remaining. At the exact target moment, the state is arrived, and every box reads zero. Once the target has passed, the state is elapsed, and the boxes show how long ago it passed. The distinction matters: a timer that shows negative numbers after the target has passed is reporting a state that no longer exists, and a timer that freezes at zero hides how long ago the moment went by.

      The headline number is the breakdown: whole days, then the remaining hours, then the remaining minutes, then the remaining seconds. Days remaining means whole days remaining, so 41 days and 12 hours left shows 41 in the days box, with the 12 hours in the hours box. The totals underneath give the same span in a single unit: 41 days and 12 hours is 3,585,600 seconds, 59,760 minutes, 996 hours, 41 days, or 5.9 weeks. Read the breakdown when you want to say the time out loud, and read the totals when you want one number to compare or to feed into another calculation.

      The target in words is the target written out in full: weekday, date, and time, with midnight and noon named rather than written as 00:00 or 12:00. New Year 2027 reads "Friday, the 1st of January 2027, at 12:00 midnight UTC." The plain wording exists so the target can be checked at a glance: if the weekday or the date looks wrong, the entry was wrong, and the countdown is counting toward the wrong moment. Check the target in words before trusting any countdown that matters.

      Countdown, elapsed time, and stopwatch: which mode to use

      The three modes answer three different questions, and picking the wrong one gives a correct answer to the wrong question. A countdown looks forward from now to a target. Elapsed time looks backward from now to a start. A stopwatch measures a run that starts when you press the button. The table below states what each mode needs and what it returns.

      ModeQuestion it answersWhat you enterWhat it shows
      CountdownHow long until a future moment?A target date and timeDays, hours, minutes, and seconds remaining, ticking down live
      Elapsed timeHow long since a past moment?A start date and timeDays, hours, minutes, and seconds since the start, ticking up live
      StopwatchHow long has this run lasted?Nothing: press StartA running clock with pause and reset, plus the same breakdown

      Use the countdown for anything with a date attached: a holiday, a deadline, a launch, a trip, an exam, a birthday. Use elapsed time for anything you measure from a past moment: how long since a launch, since a move, since a quit date, since a child was born. If the span you are measuring is someone's age, our Age Calculator gives the same span broken into years, months, and days from a date of birth. Use the stopwatch for anything you time as it happens: a run, a meeting, a task, a presentation rehearsal. If you need the hours between two clock times on one day, our Hours Calculator does that directly.

      Daylight saving time and your countdown

      In the United States, daylight saving time begins at 2 a.m. local time on the second Sunday in March and ends at 2 a.m. local time on the first Sunday in November. In 2026 those dates are Sunday, 8 March and Sunday, 1 November. On the spring-forward day the clock jumps from 2 a.m. to 3 a.m., so that day has 23 hours. On the fall-back day the clock returns from 2 a.m. to 1 a.m., so that day has 25 hours. Neither fact changes a countdown measured in UTC: the clock change moves local labels, not the length of the span.

      Two spans prove the point. From 1 March 2026 at noon UTC to 15 March 2026 at noon UTC is exactly 14 days, and the span crosses the spring-forward. From 25 October 2026 at noon UTC to 8 November 2026 at noon UTC is exactly 14 days, and the span crosses the fall-back. Both spans are identical to any other 14-day span, because the arithmetic runs on UTC milliseconds, which never see the local clock change at all. A tool that subtracted local midnights could return 13 days and 23 hours for the spring-forward span, or 14 days and 1 hour for the fall-back span, and a careless rounding step would turn either into the wrong day count.

      One real effect remains, and it is worth knowing about. If you set a countdown target by local time across a clock change, the local label you typed still means what it says: a target of 9 a.m. on 9 March 2026 in New York means 9 a.m. Eastern Daylight Time, which is 1 p.m. UTC, while a target of 9 a.m. on 7 March means 9 a.m. Eastern Standard Time, which is 2 p.m. UTC. The timer converts each entry to UTC at the moment you type it, so the conversion is correct for the date you entered. The countdown itself is then a plain difference in UTC, and the clock change cannot touch it.

      Leap years, leap days, and leap seconds

      The Gregorian calendar keeps the calendar year aligned with the seasons by adding a day, 29 February, to most years divisible by 4. The full rule has three tests: a year divisible by 400 is a leap year, a year divisible by 100 but not by 400 is not, and otherwise divisibility by 4 decides it. That is why 2024 is a leap year, 1900 was not, 2000 was, and 2100 will not be. The timer applies the full rule, so a countdown that crosses 29 February in a leap year is one day longer than the same countdown in a common year: from 28 February 2028 to 1 March 2028 is 2 days, because 29 February 2028, a Tuesday, sits between them.

      Leap seconds were the same idea applied to the clock rather than the calendar. Coordinated Universal Time, UTC, runs on atomic clocks, which keep steadier time than the Earth, whose rotation speeds up and slows down. Whenever UTC drifted close to 0.9 seconds from the time scale that tracks the Earth's rotation, a leap second was inserted, always at the end of June or December. Since 1972, 27 leap seconds were added, every one of them positive, and the last was on 31 December 2016, when properly set clocks ticked to 23:59:60 before rolling over to midnight. UTC now trails International Atomic Time by 37 seconds.

      Leap seconds are ending. The General Conference on Weights and Measures decided in 2022 that the maximum gap between UTC and Earth-rotation time would be increased in or before 2035, and at its 28th meeting on 15 October 2026 it adopted Resolution 5, which brings continuous UTC into effect on 20 May 2027: from that date, no leap second will ever be added or removed again, and the allowed gap widens to one hour. The decision was driven in part by the risk of a first-ever negative leap second, a minute with only 59 seconds, which no system had ever been tested against. This timer does not accept a second value of 60, and no countdown that starts after 20 May 2027 can ever span a leap second.

      What a second actually is

      Every number on this page is a count of seconds, so it is worth stating what a second is. Since 1967, the second has been defined by the cesium-133 atom: one second is the duration of exactly 9,192,631,770 periods of the radiation from the transition between two hyperfine levels of the ground state of the cesium-133 atom. The modern wording, adopted in 2018 and in effect since 2019, fixes the cesium frequency at exactly 9,192,631,770 hertz, and the second follows from that number. The length of the second did not change: the 1967 definition was chosen so the atomic second matched the older astronomical second as closely as measurement allowed at the time.

      The definition matters for a countdown timer in one practical way: the second is the same everywhere. A second measured by an atomic clock in Colorado and a second measured by an atomic clock in Paris are the same duration, which is why UTC can serve as a single world reference and why this timer can promise identical results in every time zone. Your device clock is not an atomic clock, and it can drift by seconds or minutes if it is not synchronized, so a countdown is only as accurate as the clock it reads. Before trusting a countdown that carries a real deadline, check your device clock against a trusted source.

      Common mistakes to avoid

      Counting down to the wrong day. A countdown to 1 January means midnight at the start of 1 January, not the end of it. If your event is on 1 January during the day, set the target to the actual time of the event, or the timer will read zero hours before the event starts. Check the target in words: it names the weekday and the time, so a wrong entry shows up at once.

      Reading days remaining as calendar dates remaining. Days remaining means whole 24-hour periods remaining. With 41 days and 12 hours left, 42 calendar dates still touch the countdown, but only 41 whole days remain. If a form asks how many days are left until a deadline, it usually means whole days, which is the number in the days box.

      Forgetting the leap day. Any countdown that crosses 29 February in a leap year is one day longer than the same countdown in a common year. A countdown from 20 November 2027 to 20 November 2028 is 366 days, not 365, because it crosses 29 February 2028. A countdown from 20 November 2026 to 20 November 2027 is 365 days.

      Typing a time in the wrong time zone. The timer reads your entry as your local time. If a friend in London tells you an event starts at 3 p.m., that is 3 p.m. London time, not 3 p.m. your time: convert it to your local time first, or the countdown will be off by the time zone difference. Our Time Zone Converter does the conversion.

      Trusting a countdown on a device with a wrong clock. The timer reads the clock on your device. If that clock is five minutes fast, every countdown on the page is five minutes short, and every elapsed time is five minutes long. The error is invisible on the page itself, because the timer has no other clock to check against. Check the device clock before relying on a deadline.

      Closing the page and expecting the stopwatch to keep running. The stopwatch lives in the page. Closing the tab, reloading the page, or restarting the browser resets it to zero. That is by design: nothing is saved on the device and nothing is sent anywhere. If you need a run that survives a closed tab, note the start time and use the elapsed-time mode instead, which measures from a date and time you enter.

      Expecting the timer to ring or notify you. This timer shows the time remaining and says plainly when the target arrives, but it does not play a sound or send a notification. If you need an alarm at the target moment, set one on your device as well.

      Frequently asked questions

      How many days are there until New Year 2027?

      From noon on 20 November 2026, New Year 2027 is 41 days and 12 hours away, which is 3,585,600 seconds, 59,760 minutes, or 996 hours. The answer changes every second, which is why the timer ticks live: enter 1 January 2027 at midnight as the target and the boxes show the exact time remaining right now. New Year 2027 falls on a Friday.

      What happens when the countdown reaches zero?

      At the exact target moment the timer switches to its arrived state and every box reads zero, with the message that the countdown has reached its target. One second later it switches to its elapsed state and starts showing how long ago the target passed, instead of showing negative numbers or freezing at zero. A target that is already in the past when you enter it goes straight to the elapsed state.

      Does daylight saving time change the countdown?

      No. Every calculation runs on the difference in milliseconds between two UTC instants, so the clock change never touches a result. From 1 March 2026 at noon UTC to 15 March 2026 at noon UTC is exactly 14 days, spanning the spring-forward on 8 March, and from 25 October 2026 at noon UTC to 8 November 2026 at noon UTC is exactly 14 days, spanning the fall-back on 1 November. The two spans are identical to any other 14-day span.

      How does the timer handle leap years?

      A year is a leap year if it is divisible by 4, except that a year divisible by 100 is not a leap year unless it is also divisible by 400. That is why 2024 is a leap year, 1900 was not, 2000 was, and 2100 will not be. The timer applies the full rule, so a countdown crossing 29 February in a leap year picks up the extra day: from 28 February 2028 to 1 March 2028 is 2 days, because 29 February 2028 sits between them, while the same span in 2027 is 1 day.

      What is the difference between the countdown, elapsed, and stopwatch modes?

      The countdown looks forward from now to a target date and time and shows the time remaining. Elapsed time looks backward from now to a start date and time and shows how much time has passed since it. The stopwatch measures a run that starts when you press Start, with pause and reset, and it shows a running clock in total hours, minutes, and seconds. All three modes show the same breakdown in days, hours, minutes, and seconds, plus the same totals.

      Why does the timer need my device clock?

      The timer reads the clock on your device to find the current time, and every tick re-reads it, so a slow tick never makes the timer lose time. If your device clock is wrong, the countdown is wrong by the same amount, so check it against a trusted clock before relying on a deadline. Nothing you enter leaves the page: there is no account, no saving, and no tracking.

      Can I count down to a time in another time zone?

      The timer reads your entry as your local time, so convert the target to your local time before entering it. A 3 p.m. start in London is 10 a.m. in New York during standard time, and entering 3 p.m. as your local time would make the countdown five hours too long. Our Time Zone Converter does the conversion, and the timer then converts your local entry to UTC before calculating.

      What is a leap second, and will it affect my countdown?

      A leap second was a one-second adjustment inserted into UTC, always at the end of June or December, to keep atomic-clock time aligned with the Earth's rotation. Since 1972, 27 leap seconds were added, the last on 31 December 2016, when clocks ticked to 23:59:60. The General Conference on Weights and Measures ended them: from 20 May 2027, UTC is continuous and no leap second will ever be added or removed again, so no countdown that starts after that date can be affected by one.

      Sources

      • NIST: SI Units, Time — the second is defined by fixing the cesium frequency at exactly 9,192,631,770 hertz. Page created 12 April 2010, updated 8 January 2026. Accessed 20 November 2026.
      • NIST: Time and Frequency from A to Z — one second is the duration of 9,192,631,770 periods of the radiation from the transition between two hyperfine levels of the ground state of the cesium-133 atom; the definition was added to the International System of units in 1967. Page created 12 May 2010, updated 1 March 2023. Accessed 20 November 2026.
      • BIPM: Resolution 4 of the 27th CGPM (2022) — UTC runs at the same rate as International Atomic Time and differs from it only by an integral number of seconds; when the difference between Earth-rotation time and UTC approaches 0.9 seconds a leap second is applied; the maximum difference will be increased in, or before, 2035. Accessed 20 November 2026.
      • Windows Forum: Leap Seconds End May 20, 2027 — on 15 October 2026 the 28th General Conference on Weights and Measures adopted Resolution 5, making UTC continuous from 20 May 2027; 27 leap seconds were added since 1972, the last on 31 December 2016, and UTC trails International Atomic Time by 37 seconds. Accessed 20 November 2026.
      • NIST: Local Time FAQs — daylight saving time begins at 2 a.m. on the second Sunday in March and ends at 2 a.m. on the first Sunday in November; the Uniform Time Act of 1966 set the national schedule. Page created 16 September 2024, updated 11 October 2024. Accessed 20 November 2026.
      • Wikipedia: Gregorian calendar — the leap year rule (divisible by 4, except years divisible by 100 unless divisible by 400), 1800 and 1900 not leap years and 1600 and 2000 leap years, 97 leap years and 146,097 days in every 400-year cycle. Accessed 20 November 2026.