Pick a countdown

Every named countdown on the site

The countdown hub lists every named live countdown on untl: the seven weekdays, midnight, tomorrow, and the holidays we currently support (New Year, Christmas, Easter). Each one has a dedicated page with the same live flip-clock, the same picker for setting a target time, and the same calendar-fact card.

If you're looking for a countdown that isn't in this list, the how-long-until tool accepts any date and time. Paste a target and you get a shareable URL with a live count, exactly the same flip-clock as the named pages.

Weekdays

Each weekday page targets the strictly-next occurrence of that day from now, with a picker that lets you set the hour and minute. Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday.

The segmented control above each clock switches between "this week" and "next week" so you can quickly check the imminent occurrence or the one after it. Each page also surfaces a unique calendar fact, like the next time that weekday falls on the 13th of the month.

Daily boundaries

Midnight counts down to the next local 00:00, the boundary between today and tomorrow on the calendar. Tomorrow targets the same instant but frames it as the start of the next day instead of the end of today.

Both pages handle daylight-saving transitions correctly because they use the browser's local Date object, which already accounts for the shift. The "midnight" target stays at local 00:00 on either side of a DST change.

Holidays

New Year targets January 1 in your local timezone. Christmas targets December 25. Easter uses the Anonymous Gregorian computus to compute the date each year, so it's accurate for every future Easter Sunday.

Once "now" passes any of these dates, the page rolls automatically to next year's occurrence. You don't need to do anything special at the boundary.

How the countdowns stay fast

Every countdown page renders the current value into the HTML at build time, so the first paint shows a real number rather than a placeholder. A tiny client script then takes over and starts ticking once a second. The script is around five kilobytes, with no external runtime dependencies. Once the page has loaded the countdown ticks entirely on your device's clock; the live calculation itself makes no further network calls.

The HTML is served from Cloudflare's edge, so the page lands quickly anywhere in the world. There's no server to wait for and no database to query.

Related time tools

Beyond the named countdowns, the site has a small suite of supporting tools. The stopwatch counts up with laps. The online timer counts down from a duration you set and beeps at zero. The age calculator takes a date of birth and produces your exact age and the weekday of your next birthday. The 24-hour to 12-hour converter handles the format math between military and AM/PM time. The birthday countdown targets your next birthday with the same flip-clock as the named pages.

Adding a new countdown

If you have a suggestion for a countdown that should be on the named list, the bar is: there's a meaningful body of search interest for it, and the calculation is unambiguous. Movable feasts and irregular targets are fine as long as the algorithm is reproducible. Annual events on a fixed Gregorian date are the easiest to add. Fixed-date holidays in other calendars (Lunar New Year, Diwali, Eid) take more careful handling and are on the roadmap.

Why we don't do dedicated pages for every phrasing

Search queries about countdowns come in dozens of phrasings: "how many days until Friday", "Friday countdown", "days till Friday", "how long until Friday at 4pm", "Friday in how many hours". Some sites generate a separate page for each phrasing, which creates a sprawling map of near-duplicate URLs.

We pick one canonical URL per target. The Friday page is the one page that answers every Friday phrasing. That keeps the site small, the link graph clean, and the user experience consistent: you click a link about "days till Friday" and you get the same clean live countdown you would by clicking "how many hours until Friday at 4pm".

Time zones, in one paragraph

Every clock on the site reads your browser's local timezone. There's no IP-geolocation guessing and no server-side conversion. The benefit is accuracy: the countdown is correct for wherever your device thinks it is. The cost is that you can't easily preview the countdown as another timezone would see it without changing your OS timezone. For most use cases that's the right tradeoff.

Accessibility and keyboard use

Every interactive control on the countdown pages is keyboard-reachable in tab order. The segmented "this week / next week" buttons announce their state via aria-pressed; the picker is a real <form> with proper <label> associations; the live countdown digits sit inside an aria-live polite region that screen readers can read on request. The colour contrast between digits and background meets WCAG AA at the default font sizes.

If you use a screen reader, the breadcrumb at the top of every non-home page gives you the hierarchy; the visually-hidden h1 carries the canonical question ("How long until Friday?") so the page announces meaningfully when it loads.