How Many Days Until New Year?
Down to the second, counting to midnight on 1 January.
Runs entirely in your browser
Loading the tool…
- —Days total
- —Working days
- —Weeks
- —Hours
- —Minutes
The date is in the link itself, so it works for anyone who opens it.
The count above runs to midnight on 1 January in your own time zone, the moment the year changes where you are. On New Year's Eve it is the countdown to the bells, in hours, minutes and seconds.
There is no single worldwide midnight. The new year reaches the Line Islands of Kiribati first, at UTC+14, and American Samoa last, at UTC−11: a span of twenty-five hours in which it is next year in one place and still last year in another. The count here is yours, because that is the one you will hear. For the moment it arrives in another city, the world clock shows their time beside yours.
Lunar New Year is a different date every year, between 21 January and 20 February, and New Year's Eve itself is the day before this one: the count reaches zero at the end of it. For either, or any other date, use the countdown.
How to use it
- Read the count at the top: days, hours, minutes and seconds, moving as you watch.
- Look below it for the same span as whole days, weeks and working days.
- Change the date in the box to count down to anything else instead.
Questions
Whose midnight does it count to?
Yours, the midnight in the time zone your device is set to. The new year arrives at a different moment in every time zone, first in Kiribati and last in American Samoa, and a countdown to anybody else's would be wrong for where you are.
How many days until New Year's Eve?
One fewer than the count shows. New Year's Eve is 31 December and the count runs to its end, so on the Eve itself the clock reads hours rather than days: it is the countdown to midnight that night.
What does it show on New Year's Day?
It counts up from midnight, telling you how long the year has been going, until the day is over. From 2 January it counts to the next one.
Which time zone is this counting in?
Yours, the one your device is set to. The target is midnight at the start of the day in your own local time, because that is when the day arrives where you are. A holiday reaches Kiribati about a day before it reaches Hawaii, and each of them sees their own count here rather than anybody else's.
Does it keep counting while I leave the tab open?
Yes, it ticks once a second for as long as the page is open, and picks the count back up from the clock when you return to the tab. Nothing is stored between visits, so opening it again simply asks your clock what time it is now.
Is any of this sent anywhere?
No. The arithmetic runs in WebAssembly inside this tab, and the only thing it reads is your device clock. There is no account, no cookie of ours and no record of what you looked up. Load the page once and it keeps working with the network off.
The same question, other days
Each of these counts to the start of its own day, in your time zone, with the same live seconds and the same working days figure.
- How Long Until Monday
- How Long Until Tuesday
- How Long Until Wednesday
- How Long Until Thursday
- How Long Until Friday
- How Long Until Saturday
- How Long Until Sunday
- How Long Until Tomorrow
- How Long Until Morning
- How Long Until the Weekend
- How Many Days Until Christmas
- How Many Days Until Halloween
- How Many Days Until Thanksgiving
Your data stays on your device
Everything above runs inside your browser as WebAssembly compiled from Rust. Nothing you type is uploaded, logged or stored on a server. You can load this page once, go offline, and it still works.
This page makes no requests at all, to anywhere. That is not a promise in the copy: it is a Content-Security-Policy header your browser enforces, and connect-src on it is none. Open the network tab and watch nothing happen.