📅 Day Counter
Day Counter
Counting the days to a wedding, a deadline or a visa expiry by hand invites off-by-one errors. Pick the two dates and this counter gives the exact day count using real calendar arithmetic.
Leap years and varying month lengths are handled automatically, so the answer is always the true number of midnights between the dates.
What the Day Counter does
The Day Counter answers one question exactly: how many days are there between two dates? Pick a start date and an end date, press Calculate, and you get the count — plus the same span restated in weeks underneath. It sounds like the simplest arithmetic in the world, and it is the one people most often get wrong by hand, because the calendar refuses to use round numbers: months have 28, 29, 30 or 31 days, and roughly every fourth year February quietly gains a day. This tool counts on the real calendar, so none of that has to be held in your head.
The counting convention — read this first
Every "days between" tool has to choose whose days are in and whose are out, and the Day Counter follows the universal convention: the start day is not counted, and the end day is. From 1 January to 2 January is 1 day, not 2 — you count the days you arrive at, not the day you set off from. This is the same convention hotels, car hire and deadline arithmetic use: check in on the 1st, check out on the 2nd, and you have stayed one night and are charged for one day.
If you ever need the other convention — both endpoints included, as when you count the days of a festival that runs "from the 1st to the 2nd" — take the counter's answer and add 1. That single adjustment converts between the two conventions for any pair of dates, and knowing it exists prevents the classic off-by-one argument, in which two people with two correct methods disagree by a day and both think the other is wrong.
How the count is worked out
The calculator turns each date into a point at midnight at the start of that day, subtracts, and divides by the 86,400,000 milliseconds in a day, rounding to the nearest whole day. Working from midnights is what makes the count immune to daylight-saving changes: a day on which the clocks spring forward has only 23 hours of elapsed time, and a fall-back day has 25, but each is still exactly one calendar day, and the rounding absorbs the difference. Leap years need no special handling either — 29 February is simply a date that exists in the subtraction in the years when it occurs. Enter the span 28 February 2024 to 1 March 2024 and the answer is 2 days, because the 29th sits between them; the same dates in 2023 give 1 day.
Worked example — a long span
Take 1 January 2026 as the start and 29 September 2026 as the end:
- Days between = 271
- In weeks = 38 weeks + 5 days (38 × 7 = 266, with 5 left over)
Counted by hand, that is January's remaining 30 days after the 1st, then February 28, March 31, April 30, May 31, June 30, July 31, August 31, and 29 days of September: 30 + 28 + 31 + 30 + 31 + 30 + 31 + 31 + 29 = 271. The by-hand route is shown only so you can see nothing exotic is happening — for anything beyond a few weeks, the hand count is exactly where leap days and 31sts get dropped.
Worked example — a countdown
Counting forward to a fixed event is the same subtraction wearing a friendlier face. From 12 November 2026 to 25 December 2026 the counter gives 43 days (6 weeks + 1 day) — the length of the run-up, not counting today, counting the day itself. Event countdowns, notice periods, "90 days from signing" clauses and visa windows are all this same shape: a start, an end, and a number of midnights between them. A full 90-day window, by the way, is a useful calibration: 1 January 2026 to 1 April 2026 is exactly 90 days (12 weeks + 6 days), because January, February and March 2026 contribute 31 + 28 + 31.
Reference table — spans worth recognising
| Start | End | Days | In weeks |
|---|---|---|---|
| 28 Feb 2023 | 1 Mar 2023 | 1 | 0 weeks + 1 days |
| 28 Feb 2024 | 1 Mar 2024 | 2 | 0 weeks + 2 days |
| 1 Mar 2026 | 31 Mar 2026 | 30 | 4 weeks + 2 days |
| 12 Nov 2026 | 20 Nov 2026 | 8 | 1 weeks + 1 days |
| 12 Nov 2026 | 25 Dec 2026 | 43 | 6 weeks + 1 days |
| 1 Jan 2026 | 1 Apr 2026 | 90 | 12 weeks + 6 days |
| 1 Jan 2026 | 29 Sep 2026 | 271 | 38 weeks + 5 days |
| 1 Jan 2000 | 1 Jan 2001 | 366 | 52 weeks + 2 days |
| 31 Dec 2025 | 31 Dec 2026 | 365 | 52 weeks + 1 days |
Two rows teach the calendar faster than any rule: the February pair shows the leap day appearing and disappearing between one year and the next, and the last two rows show why "a year" is not a day count — 2000 was a leap year (366) and 2026 is not (365), so any span that crosses a February inherits that February's length.
Either direction works
The counter takes the absolute difference, so the end date may be earlier than the start date and the answer is the same positive count: 29 September 2026 back to 1 January 2026 is also 271 days. That is deliberate — "how long since" and "how long until" are the same distance measured from opposite ends. What the tool will not tell you is direction; if the sign matters to you (a deadline already passed versus one still coming), that reading has to come from the dates themselves, which you already know.
Counting days by hand, honestly
If you ever have to check a count on paper, the reliable method is the one the table above uses: count the days remaining in the start month (its length minus the start day), add whole months one at a time, then add the end day of the final month. The unreliable methods are the tempting ones — treating every month as 30 days (which loses or invents up to 3 days per quarter), counting fence-posts with both ends in (the off-by-one again), and forgetting that February 2024 had a 29th. A useful sanity check on any result: divide by 7 and confirm the weeks row, and divide by roughly 30.44 to see whether the "about N months" figure you had in your head is even in range.
Where a day count earns its keep
Deadline and notice arithmetic is the daily case: contracts, tenancy notices, refund windows and warranty periods are all written in days, and they are all counted from midnights, exactly as here. Project and course planning is the second: a 12-week course starting 5 January ends 84 days later, and the counter turns that into a date-free span you can drop into the Date Calculator's add-days card to land on the actual finish. The third is personal countdowns — days until an exam, a wedding, a flight — where the exclusive-of-today convention matches how people naturally speak: "43 days to go" never includes today.
Common mistakes
- Counting both endpoints. From the 1st to the 2nd is 1 day by the standard convention. If your document counts both ends, add 1 to the counter's answer rather than concluding the tool is wrong.
- Assuming 30-day months. Three "months" from 31 January is not 90 days later in any simple sense — February is in the way. Always let the calendar do it.
- Missing the leap day. Any span crossing February 2024 (or 2028, 2032…) contains one more day than the same span a year earlier or later. This is the single most common hand-count error.
- Mixing in times of day. The counter works in whole calendar days between midnights. "48 hours from 3 p.m. Tuesday" is a time question, not a date question — the Time Duration Calculator is the tool for spans inside a day.
- Expecting working days. Weekends count here. The counter reports calendar days; it does not skip Saturdays, Sundays or holidays.
The same span in other units
A day count is often just the first step. The 271-day span is also 6,504 hours or 390,240 minutes (×24 and ×1,440), which is the form a countdown, a rental or an hourly-billed contract wants it in; it is 19 fortnights and 5 days (a fortnight being 14 days — 271 ÷ 14 = 19 remainder 5), the form older contracts and some payrolls still use; and it is a little over three quarters of a year, the form a rough plan wants. The page answers in days and weeks because those are the units dates natively trade in — everything else is one multiplication away, and doing that multiplication from the exact day count, rather than from a rounded month figure, is what keeps the downstream numbers exact.
Key terms
- Day count (span) — the number of midnights crossed between two dates; the counter's hero figure.
- Exclusive / inclusive counting — whether the start day (exclusive) or both endpoints (inclusive) are in the count; this tool is exclusive of the start, inclusive of the end.
- Leap day — 29 February, present in years divisible by 4, except century years not divisible by 400 (2000 had one; 1900 did not).
- Calendar day — a day as dated, regardless of weekends, holidays or working hours.
Related tools
The Date Calculator does everything this page does and adds a second card that adds or subtracts days from a date; the Day of the Week Calculator names the weekday any date falls on; the Age Calculator turns a birth date and a second date into years, months and days.
Frequently asked questions
What does the Day Counter compute?
It counts the exact number of calendar days between a start date and an end date, and restates the same span in whole weeks plus leftover days. Leap years and the real lengths of months are handled automatically, so 28 February to 1 March is 2 days in 2024 and 1 day in 2023.
Is the count inclusive or exclusive?
It follows the standard convention: the start day is not counted and the end day is, so 1 January to 2 January is 1 day. If you need both endpoints counted — for example the days a festival runs from the 1st to the 2nd — add 1 to the result.
Can you give a worked example?
Yes — from 1 January 2026 to 29 September 2026 there are 271 days, shown as 38 weeks + 5 days. Counted by hand: 30 remaining days of January, then 28 + 31 + 30 + 31 + 30 + 31 + 31 for February to August, then 29 days of September.
Can the end date be before the start date?
Yes. The counter takes the absolute difference, so the count is the same positive number in either direction: "how long until" and "how long since" are the same distance. The result does not show direction, only the size of the span.
How does it handle leap years and daylight saving?
Leap days are simply dates in the subtraction, so any span crossing 29 February includes it. The count is taken between midnights and rounded to whole days, which makes it immune to daylight-saving changes — a 23-hour or 25-hour day still counts as exactly one calendar day.
Does it count only working days?
No. Every calendar day counts, including Saturdays, Sundays and holidays. If you need a working-days figure, count the calendar days first and then subtract the weekends and holidays that fall inside the span.
Why does the same span sometimes show a different total elsewhere?
Almost always because of the counting convention: tools that include both endpoints read exactly 1 higher than this counter for the same two dates. Check whether the other tool counts the start day; if it does, the two answers agree once that one day is accounted for.







































