DaysUntilNowMake a countdown to any date
Your countdown
Pick a date to start the clock
Copy the link under this box and the countdown travels with it — the date and the name are in the address, so whoever opens it sees the same clock.
Email me before your date
Try one of these too
How do you make a countdown to your own date?
The DaysUntilNow custom countdown takes a date, an optional time of day and a name, and writes all three into the address bar — so the link you copy is the countdown. Nothing is saved on our side, no account exists to make, and whoever opens the link sees the same clock running on their own device.
That is the difference worth knowing about. Every other countdown builder in this niche stores your countdown on its servers, which is why it asks you to register first and why the countdown can later be moved, paywalled or deleted.
The trade is honest and worth stating: because the state is in the link, anyone holding the link can read it, and editing it later means editing the link. For dates you would rather be reminded about than watch, the email reminder under the clock is the better tool.
What travels in the link
Change anything above and the address bar changes with it. That is the whole storage layer: three parameters, no database, no account, no expiry.
| Part of the link | What it holds | If it is missing |
|---|---|---|
t | The name shown above the clock | The heading falls back to “Your countdown” |
d | The target date, written YYYY-MM-DD | The clock waits for a date before it starts |
h | Time of day, written HH:MM on a 24-hour clock | Midnight at the start of the date |
So a link can be written by hand as easily as it can be copied:
/custom-countdown/?t=Our+holiday&d=2027-07-04&h=09:00. Spaces in the name become + or %20,
and anything the browser cannot parse as a date is simply ignored rather than guessed at.
Two things deliberately do not travel in the link. There is no time zone, because the countdown is meant to reach zero at the local moment for each reader; and there is no identifier, because nothing was written down anywhere to identify.
What people build one for
The fixed countdowns on this site cover the dates everybody shares. This one exists for the dates only you are counting:
- Personal deadlines — a due date, a wedding, a move, a graduation, the end of a probation period, the day a passport or a warranty expires.
- Work with a hard edge — a launch, a tender deadline, a migration window, the last day of a quarter, the end of a notice period.
- Waiting with somebody else — a return date, a holiday, a match, a release, the day a course finishes. These are the ones worth sharing as a link rather than keeping in a diary.
- Counting up instead of down — put a date that has already passed into the field and the same clock measures time since, which is how people track sober days, anniversaries and how long a project has really been running.
If the thing you are counting repeats — every payday, every renewal, every month end — a single countdown is the wrong shape for it. The planners hold a list of dates rather than one.
Midnight, or a time you choose
Leave the time field alone and the countdown ends at midnight at the start of your date, which is what “days until” means everywhere else on this site. Set a time and it becomes an appointment: the clock lands on 14:30 on the day, and the days figure drops one whole day later than it otherwise would.
Use the time field whenever the hour is the point — a flight, an exam, a live stream, a deadline that closes at five. Leave it empty for birthdays, anniversaries and holidays, where the day is what matters and a specific hour would make the number look wrong to everybody else.
The switch also changes how the shared link reads. A countdown named “Exam” with no time says the day; a countdown named “Exam, 09:00” says the moment, and the reader does not have to ask which.
No account, and what that is worth
Every competitor in this niche keeps custom countdowns on a server, and each one wants an account before it will make you one. That buys three things — editing after the fact, a tidy short link, and a dashboard of your countdowns — and costs you an address, a password and a record of the date you were counting to.
This page makes the opposite trade. Nothing is stored, so nothing can be lost, leaked, migrated, paywalled or shut down; the countdown works for as long as the page exists, and the person you send it to needs nothing at all to open it. Editing means changing the fields and copying the link again, which is the honest cost of the arrangement.
The one thing worth repeating: a link is public in the way any link is public. Anyone who has it can read the name you typed, so treat the title as visible rather than as a note to yourself.
When a fixed countdown is the better tool
If your date is one everybody shares, the ready-made countdowns carry the context a blank one cannot: shopping days, weekday tables, observed days off and the rules behind the date.
- Christmas countdown — with the shopping calendar and ten years of weekdays.
- Halloween countdown — with the clock change beside it.
- Thanksgiving countdown — computed from the fourth-Thursday rule.
- Easter countdown — the moving date, with the Orthodox one alongside.
- New Year countdown — midnight, and how long the next year runs.
For date arithmetic rather than a live clock — how many days lie between two dates, what date falls 90 days from today, how many working days are left — the date calculators answer as you type, and the full list of countdowns has everything that ticks.
Frequently asked questions
Why does the countdown I shared show a different number of days for the person I sent it to?
Because a countdown to a date runs on the clock of whoever is looking at it. The link carries the date, the optional time of day and the name in the address itself, not a fixed instant in UTC, so “midnight on the 31st” means midnight where each person is standing — someone eleven hours ahead sees a smaller number, and near midnight the whole-day figure can differ by one. If everyone has to hit zero at the same instant, put the zone in the title, for example “Launch, 14:00 London”.
Can I put a live countdown in an email?
Not as a live clock. Email clients block JavaScript for security, so the only thing that can animate is an image — an animated GIF that a server regenerates at every open — and Outlook’s desktop client renders just its first frame, a still picture. A shared link is the dependable version: the recipient opens the page and the clock runs in the browser, where scripts are allowed.
Why did my countdown gain or lose an hour overnight?
Because a clock change falls between now and the target. The countdown measures real elapsed time to a moment on your local clock, so when the clocks go forward that hour is skipped and the remaining time shrinks by one hour; when they go back the hour is repeated and the remaining time grows by one. The United States changes on the second Sunday in March and the first Sunday in November, the European Union on the last Sunday in March and the last Sunday in October, so any countdown spanning one of those Sundays shifts exactly once.
Is a shared countdown link private, and does it expire?
Everything the countdown needs sits in the address you copy: the date, the optional time and the name you typed. Nothing is written to a server and no account exists, so there is no stored record to expire or delete, and the link keeps working as long as the page does. The trade is that the link is only as private as where you paste it — anyone who holds the URL sees the name you gave the countdown, and chat apps or link shorteners may keep their own copy. After the date passes the same link keeps counting, showing time since instead of time until.
Can I put the countdown on my own site?
Yes, and it is the same link doing the work. The Embed button under the clock copies an iframe that points at the countdown you have set up, so the page you paste it into shows exactly the date and name you configured, ticking on each visitor’s own clock. It loads nothing from anywhere else, needs no script tag of its own and no account at either end. Set the countdown first, then copy the embed code — the settings travel in the address inside the iframe.
How we calculate this
The clock runs entirely in your browser. It reads the date and time fields, builds a moment on your local clock, and recounts the difference every second — days as whole days, then the hours, minutes and seconds of the day in progress. Nothing is sent anywhere, and no cookie or storage is used, which is also why closing the tab loses nothing that was not already in the link.
State lives in the query string: t is the name, d is the date as YYYY-MM-DD, and h is an
optional time of day as HH:MM. The address is rewritten only after you change something, so a
clean link stays clean; a missing time is treated as midnight, and a date in the past is counted
upwards from instead of down to.
The email reminder is separate from the countdown and works the other way round: the date you give it is stored on our side so that a message can be sent, and nothing is stored until you confirm the address by clicking the link we email you.
Sources:
Good to know
Name it for the person opening it. The title is the only context that travels, so “Contract ends” reads better in six months than “Deadline”, and a time zone in the name settles arguments before they start.
Keep the link where you will find it again. There is no account to log back into, which is the point — but it also means the link is the only copy. Pin it in the chat where it belongs.
Two clocks are better than one. For anything with a hard cut-off, count to the moment you have to act rather than to the deadline itself: the flight leaves at nine, the taxi is at seven.