Countdown Timer

How this countdown works

A countdown looks like the simplest tool on this site and contains its hardest problem. The difficulty is not the arithmetic — subtracting two instants is trivial — it is decidingwhich instant you meant, and that turns out to be genuinely ambiguous on two nights of the year in most of the world.

What is stored is a reading on a clock, not a moment in time

When you set a countdown to 23:59 on 31 December in London, you mean the reading on a London clock. Almost every countdown tool stores that as an instant — a single number of milliseconds — and from then on the reading is gone and only the number remains.

That difference is invisible until a government changes the rules. If the United Kingdom abolished daylight saving tomorrow, a countdown stored as an instant would still fire at the old moment, which would now read 22:59 on a London clock. The countdown would be an hour wrong, permanently, and nothing on the page would say so. This one storesthe wall clock and the time zone — 2026-12-31T23:59 plusEurope/London — and resolves them to an instant fresh on every load. When the rules change, the answer changes with them, which is what you meant in the first place.

The two nights when a clock reading is not a single moment

Storing a reading has a cost, and rather than hide it this tool shows it to you.

On the night clocks go back, a reading happens twice. In New York on 1 November 2026, 01:30 occurs once at UTC−04:00 and again, an hour later, at UTC−05:00. Both are real. Both are correctly described as "half past one". If you set a countdown to that reading, this page tells you it happens twice, says which one it is using, and offers a button to switch to the other. Whichever you choose is saved with the countdown, so it resolves to the same moment on every reload — and so that a link you share shows the recipient the same moment you are looking at, rather than re-deciding on their machine.

On the night clocks go forward, a reading never happens at all. In New York on 8 March 2026, clocks jump from 02:00 straight to 03:00, so02:30 is not a time that exists. Rather than refuse the date or silently move it, the page says the reading does not exist, says what the clocks did, and shows you which time it used instead.

Both messages are written from the transition the time zone database actually reports, not from a template — which is why they are correct for the places whose clocks do not move by an hour. Lord Howe Island shifts by thirty minutes and Antarctica's Troll station by two, and a tool that has "one hour" written into its copy is simply wrong for both.

Why the figures are days, hours and minutes rather than years

A year is not a fixed length. Deriving "3 years" from an average year of 365.2425 days produces a number that is quietly wrong by hours or days depending on which leap years fall inside the span, and this site does not put approximations in a headline. Days, hours, minutes and seconds are exact: every day in a browser is precisely 86,400,000 milliseconds, because civil time as browsers expose it contains no leap seconds at all. So the readout counts in units that are genuinely fixed, and a distant date reads as a large number of days rather than a rounded number of years.

Three worked examples

• New Year in London, watched from anywhere. Target2026-12-31T23:59 in Europe/London. Open it in Los Angeles and the countdown reads the same remaining time as it does in London, because it counts to the same moment. Only the local clock differs, not the target.
• A reading that happens twice. Target 2026-11-01T01:30 inAmerica/New_York. The page reports the overlap and names both offsets. Choosing the second occurrence puts a=l in the share link, so the recipient's browser resolves the same instant rather than defaulting to the first.
• A reading that does not exist. Target 2026-03-08T02:30 inAmerica/New_York. Clocks jump from 02:00 to 03:00 that morning, so the page says so and counts to 03:30 instead — while offering01:30, the same reading interpreted with the pre-change offset.

The share link never reaches a server

Everything a shared countdown needs travels in the part of the address after the#. Per RFC 3986 §3.5 a fragment is separated from the rest of the address before the request is made, so it is never transmitted. Your event's name and date therefore do not reach this site's host, do not appear in its logs, and are not sent in the Referer header to anything the page later contacts. A query string would have put all three in every one of those places.

Links are capped at 512 characters and refused in both directions — we will not mint one longer, and we will not parse one either. A truncated time zone identifier decodes to adifferent real place, which is the failure worth designing out rather than detecting.

Sources

• IANA Time Zone Database — the rules that decide when a clock reading is ambiguous, read from your own device.
• Temporal: time zones— the disambiguation convention this tool matches, so its answers agree with a calendar app.
• RFC 3986 §3.5 — why the share link uses a fragment.
• WCAG 2.2.2 Pause, Stop, Hide — why this page, alone among the timers here, ships a pause control.
• GOV.UK: asking for dates— why the date field is your device's own control and not a custom calendar.

Limitations, stated plainly

• Your device carries the time zone rules, and this page cannot tell if they are old.If a country changed its rules recently and your device has not been updated, the countdown inherits that quietly. There is more on time zone changes.
• This is not an alarm. Nothing sounds, nothing notifies, and a browser tab is not a dependable way to be told about a moment. For anything where missing it matters, use something built for that.
• Fifty countdowns. Past that, saving is declined rather than something older being quietly deleted.
• Names are capped at 60 characters and stripped of the invisible characters that can make a shared link display text it does not contain. Ordinary punctuation, accents, non-Latin scripts and emoji all survive untouched.
• Saved in this browser only. Clearing site data or switching devices will erase it.

Questions

Will the countdown be right for someone in another country?

Yes, and that is the point of choosing a time zone. The countdown targets a moment, not a local reading, so everyone opening it sees the same remaining time no matter where they are. If you set it to midnight in Sydney, someone in Berlin counts down to the same instant — which is a different reading on their own clock, correctly.

What happens if the date has already passed?

It counts up instead, and says so. A date in the past is not an error — checking how long ago something happened is a normal thing to want, and roughly half the traffic to tools like this one is people doing exactly that.

Why does it only update once a minute?

Because a value that changes every second, on a page you did not ask to start moving, is a genuine accessibility problem — it can make a screen reader or a magnifier unusable. Minute granularity is the default for that reason. Show seconds turns the finer readout on, andPause countdowns stops them entirely; both settings are yours to make.

Does the link work if I share it with someone who has never used this site?

Yes. The link carries the whole countdown — the date, the time, the time zone, the name, and which occurrence you chose if the reading was ambiguous. Nothing is looked up and nothing is stored on our side, so there is no link that can expire or break later.

What if their browser does not know the time zone in the link?

Time zones are occasionally added to the database, so a link naming a new one can reach a browser that predates it. The page falls back to the reader's own zone and tells them it has done so, rather than failing outright or silently showing a different moment.

Can I set a countdown to the year 9999?

Yes. It computes, and reads as a large number of days rather than erroring or overflowing. Dates run from 1900 to 2200 in the picker; the arithmetic itself goes considerably further.

Are my countdowns uploaded anywhere?

No. They are saved in this browser's local storage, which is never transmitted anywhere, and the share link puts its state in the part of the address that browsers do not send to servers. There is no account and nothing to sign in to. Saved in this browser only. Clearing site data or switching devices will erase it.

Why is there no custom calendar picker?

Because your device already has one, it works with whatever assistive technology you use, and hand-built calendar widgets are among the most reliably broken controls on the web. GOV.UK's guidance is blunt about it, and we follow it: the date field is a real date input.