Days Until Event
Countdown to any future date
Name an event, give it a date, and this panel tells you how many whole days stand between now and then. Put a date in the past instead and the heading flips from "Days Until" to "Days Since" and the number becomes a count of days elapsed — same arithmetic, opposite sign.
The number changes at your midnight. Not the event's midnight, not UTC midnight. If the wedding is in Lisbon and you are reading this in Denver, your countdown drops a day seven hours before the bride's does. That is usually what you want from a personal countdown, and occasionally the reason two people arguing about "how many days left" are both right.
The event name field is not decoration: it is written into the headline, so the panel reads "Days Until Thesis Defence" rather than a bare number. On the day itself the count is replaced by the word Today! rather than a zero.
Worked example: counting to 12 October 2026
Entered on 9 September 2026, with the event named "Conference":
- Days Until Conference: 33
- Weeks: 4.7 — 33 ÷ 7 = 4.71
- Day of Week: Monday
- Full Date: October 12, 2026
The weekday row is doing more work than it looks. A deadline that lands on a Monday means the last working opportunity is the Friday before it, so a 33-day countdown is really a 30-day countdown. Turn the same date around — enter 12 October 2026 on a day in 2027 — and the heading becomes "Days Since Conference" with the elapsed count and the note that it has passed.
What each row is for
- Days Until / Days Since — whole calendar days, with Today! substituted at zero and a "(passed)" marker on dates behind you.
- Weeks — the same figure divided by 7, to one decimal. Decimal rather than "4 weeks and 5 days" because the mixed form is exactly what you already have in the days row.
- Day of Week — the weekday the event falls on.
- Full Date — the date spelled out in full, so 03/04 cannot silently mean 3 April to you and 4 March to whoever you send it to.
That last row is a typo check more than a result. Date inputs accept a keyboard-entered year of 2062 without complaint; seeing "October 12, 2062" written out catches it before the countdown does something absurd.
What the panel reads at common checkpoints
| Days remaining | Weeks row shows | What people usually do at this point |
|---|---|---|
| 365 | 52.1 | Venue and save-the-date window for a wedding |
| 180 | 25.7 | Half-year mark; visa applications generally open no earlier |
| 100 | 14.3 | The symbolic hundred-day mark for exams and launches |
| 30 | 4.3 | Final headcount, catering numbers, freeze on scope changes |
| 7 | 1.0 | The only checkpoint where the weeks row is a whole number |
| 0 | 0.0 | Reads Today! instead of the digit |
The weeks column is worth a glance because it exposes something the days count hides: 30 days is not "a month" and not "four weeks" — it is 4.3 weeks, which is why a monthly cadence and a weekly cadence drift apart over a quarter.
How the countdown is computed
Today is read from the device clock and then reset to 00:00 local, so the count is a number of calendar days rather than a live hours-and-minutes timer. The event date is read at local midnight too. The difference in milliseconds is divided by 86,400,000 and rounded to the nearest whole number.
The rounding matters twice a year. In the United States clocks jump forward on the second Sunday of March — 8 March in 2026 — and the interval between two local midnights across that Sunday is 23 hours. A countdown that truncated instead of rounding would show 99 for a 100-day span that crossed it, and would sit on the wrong number until the autumn change put the hour back.
Because the reference point is midnight rather than now, the number does not creep down through the day. It is stable from the moment you wake up until the moment the date changes, which is the behaviour people expect from a countdown pinned to a fridge.
Countdowns that are actually decisions
Most countdowns are motivational. A few are operational, and those are the ones where the weekday row earns its place: a tax filing date, a contract auto-renewal, a domain expiry, a notice period that has to be served a fixed number of days before something else. For all of those, the question is not "how long" but "what is the last day I can act", and a deadline on a weekend silently moves that last day two days earlier.
It is equally useful backwards. Enter a launch date, a diagnosis date or a start date and read the "Days Since" figure for anniversary tracking, warranty windows, or the awkward "how long has this ticket been open" number.
If the gap you care about is measured in working days rather than calendar days, the Working Days Calculator takes a holiday list too. For two arbitrary dates that are not "now", use Date Difference.
Clocks, other people's timezones, and repeating dates
The device clock is the input. There is no server involved, so a phone with the wrong date produces a confidently wrong countdown. If the number looks a day out, check the clock before blaming the arithmetic.
Events elsewhere. The event date is treated as a date in your timezone, not in the event's. For a launch pinned to 09:00 UTC or a flight departing Tokyo, the calendar date you should enter is the one that applies where you are, which is not always the one on the ticket.
Nothing repeats. This is a countdown to one specific date, not a recurring anniversary. That is deliberate for 29 February events, where "next year" has no obvious meaning, but it does mean you re-enter the date each year.
Calendar days only. Weekends and public holidays are counted like any other day. A 30-day countdown to a deadline is typically 21 or 22 workable days — see How Many Working Days Are Really in a Year? for why that gap is wider than people plan for.
Frequently asked questions
Why does the count say Today! instead of 0?
Because zero reads as an error and Today! does not. Any date behind you shows the elapsed count with a (passed) marker and the heading switches to Days Since.
Does the countdown tick down during the day?
No. Today is snapped to local midnight, so the figure is a whole number of calendar days and stays stable until your date rolls over. It is a day counter, not an hours-minutes-seconds timer.
Whose midnight does it use — mine or the event's?
Yours. The event date is interpreted in your local timezone. For an event in a very different timezone, enter the calendar date as it will fall where you are.
Why is the weeks row a decimal?
Because the whole-weeks-plus-days form is already sitting in the days row. 33 days is 4.7 weeks; splitting it into 4 weeks and 5 days would just restate the 33.
Does daylight saving throw the count off by a day?
No. The interval across a clock change genuinely is 23 or 25 hours, but the result is rounded to the nearest day rather than truncated, so the count stays correct.
Can I count down to a date decades away?
Yes. There is no range limit worth worrying about, and leap days across the span are handled because the arithmetic works on real timestamps rather than multiplying years by 365.