Days Until Calculator
Count down the days, weeks and months until any future date.
Results are provided as is, for general information. Check anything important before relying on it. See the Terms of Use.
About this tool
Pick a target date and see a countdown: days, weeks plus days, and years/months/days until it arrives, or how long ago it was if the date has already passed. Today defaults in automatically, and four quick-pick presets — New Year's Day, next Monday, end of this month, and Christmas — fill the target date for you without typing. It shares its underlying date arithmetic with the Date Difference tool but is framed as a one-date countdown rather than a two-date span, with today implicit as the starting point.
How it works
Days until = target date − today Weeks = Days ÷ 7 (whole weeks + remainder days)
The countdown is the number of calendar days between today and the target date. A negative result means the date has already passed, and today's own date counts as zero.
| Question | Working | Answer |
|---|---|---|
| How many days from 1 December to Christmas Day (25 December)? | 25 − 1 | 24 days (3 weeks 3 days) |
When to use it
Questions
What happens if the target date has already passed?
The tool switches to a "days ago" reading instead of "days until," so a past date still gives a useful answer rather than a confusing negative number.
What are the quick-pick presets based on?
Each preset is computed from today's date in your browser: New Year's Day and Christmas jump to the next occurrence (rolling into next year once the date has passed this year), next Monday finds the coming Monday, and end of this month finds the current month's last day.
Does this handle leap years and month lengths correctly?
Yes — it reuses the same calendar-aware arithmetic as the Date Difference tool, so month and year breakdowns account for real month lengths and leap years rather than assuming 30-day months.
Does this handle time zones?
No, and it doesn't need to — like the Date Difference and Age Calculator tools, it works on plain calendar dates (YYYY-MM-DD) with no time-of-day or time-zone component.
What happens when the date has already passed?
The answer flips from 'days until' to a past reading: how long ago the deadline, anniversary or incident was, in the same days/weeks/months breakdowns. The underlying number is signed — target minus as-of — and a negative signals 'in the past'; the display translates it rather than leaving you to interpret a bare negative. The target date itself reads exactly 0.
What are the quick-pick presets?
Four of them, computed from today's date: New Year's Day and Christmas jump to the next occurrence (rolling into next year once this year's passes), next Monday finds the coming Monday, and end of this month finds the month's last day. Each only fills the target date, which you can then edit freely — they are typing shortcuts, not locked constraints.
Why show weeks and months as well as days?
Because different plans count in different units: '6 weeks and 3 days' is how a project plan or a pregnancy tracker speaks, '6 months' is how a lease or subscription speaks, raw days is how a countdown widget speaks. Every reading derives from the same date arithmetic, so the views cannot drift apart as the date nears — they are presentations of one number, not separately rounded figures.
Does the count include today?
The tool counts midnight-to-midnight calendar days from the as-of date to the target: tomorrow dates as 1, today dates as 0, and a past date goes negative. That is the standard countdown convention — how an event 'in 3 days' is understood — and the weeks-and-months breakdowns follow it exactly. Contracts that count inclusively of both endpoint days are the rare case needing a manual +1 or −1.
Can I count to a time of day rather than a date?
No — the tool is date-grained by design: no time field, no hour output. That keeps the answer unambiguous ('36 days', regardless of launch hour) and the arithmetic free of daylight-saving complications. For a deadline at a specific hour, add the hours mentally, or use the timestamp converter when that precision genuinely matters.
Does it handle leap years and month lengths?
Yes — it shares its calendar-aware arithmetic with the Date Difference tool, so February gets its real length, leap years get their day, and the months-and-weeks breakdowns count real boundaries rather than averaging 30-day months. A Feb 29 target in a non-leap year simply does not exist and cannot be entered — the same guard the underlying date parser applies everywhere.