How calendar days are counted
Last updated: October 28, 2026
Two people can look at January 1 and October 28 and announce different “days between” them. One is counting elapsed time. One is counting named dates, including both ends. One is counting midnights. Days Since does the first of those, with the start fixed at local midnight. This guide is the rule the counter uses, with the sample dates worked out so you can compare a piece of paper to the screen.
The rule on this site
A date you pick is the civil date only. The page turns it into an instant by reading it as 00:00:00, midnight at the beginning of that date, in the time zone of the device. It subtracts that instant from the current time. If the result is negative, the date is still in the future and the page shows zeros. It is not a countdown.
If the result is positive, the page divides the elapsed seconds by 86,400, the number of seconds in 24 hours. The whole-number part is the day figure. The remainder is turned into hours (3,600 seconds) and minutes (60 seconds). Seconds are not shown. The display refreshes about once a second so the minute figure changes on the minute rather than lagging.
There is no separate “include the end date” switch. There is no setting for a time of day. There is no business-day mode that skips Saturdays and Sundays. If you need those, this counter will not grow them later in the calculation. You would be using a different tool.
A 300-day example
January 1, 2026 to October 28, 2026 is the sample printed on the homepage. 2026 is not a leap year, so February has 28 days. The day-of-year number of October 28 is 301: 31 + 28 + 31 + 30 + 31 + 30 + 31 + 31 + 30 + 28. January 1 is day 1 of the year. The number of midnights between day 1 and day 301 is 301 − 1 = 300. That 300 is the calendar span. The counter shows 300 days, 0 hours, 0 minutes at local midnight on October 28 only when the device’s UTC offset did not change between the two dates. UTC itself is such a clock. A U.S. zone that sprang forward on March 8, 2026 is not: that midnight reads 299 days and 23 hours, and the day figure reaches 300 at 1:00 a.m. The time-zone guide walks through the missing hour.
The homepage HTML shows 300 days, 8 hours, 15 minutes before JavaScript runs. Those figures are the elapsed time from January 1 at midnight to October 28 at 8:15 a.m. on a clock whose offset does not change. They are there so the result is not a row of zeros. Once the script runs, it replaces the snapshot with the live clock in the device’s zone. The date stays January 1, 2026 until you pick another one.
You can rebuild the 300 without a day-of-year table by adding the months and then subtracting one, because a count of dates from the 1st through the 28th that included both the start and the end would be a different question. Elapsed time does not include a full day for the starting midnight; that midnight is the zero point.
Inclusive dates versus elapsed time
From January 1 to January 3, the named dates are January 1, January 2, and January 3. Someone counting “how many dates are in this list” says 3. Someone counting elapsed midnights says 2. At midnight on January 3, Days Since shows 2 days, 0 hours, 0 minutes. At noon on January 3 it shows 2 days and 12 hours.
The same split is why “days since” and “days between” disagree in spreadsheets. Some spreadsheet functions count the end date, some do not, and some expose a basis argument for financial day-count conventions that this site does not implement. If a spreadsheet says 301 for January 1 through October 28, it is probably counting both ends or counting day-of-year. The calendar span on this site is 300. The counter prints 300 days and 0 hours at that midnight when the offset held still, and 299 days and 23 hours when a spring-forward hour is missing. Neither number is a moral correction of the other. They are different questions. Quote the question with the number.
Same day, next day, future day
On the start date, before the next midnight, the day figure stays 0. At 3:00 p.m. on the start date the page shows 0 days, 15 hours, 0 minutes, assuming the device clock is right. People who say “this is day 1” mean something real — the occasion is happening — but they do not mean 24 hours have elapsed. The page will not humor that phrasing.
The next midnight flips the day figure to 1 and the hours to 0, except when daylight saving has stretched or shrunk the civil day. That exception is the subject of the time-zone guide. In a zone that is not changing its offset, midnight-to-midnight is exactly 24 hours, so the day figure and the number of midnights match.
A future date shows 0 days, 0 hours, 0 minutes for as long as it remains in the future. The holiday menu hides holidays that have not happened yet during the current year, for that reason. The month, day, and year menus still let you pick a future date, and the zeros are the result, not a failure to calculate.
Months are a poor unit
Thirty days is not a month. From January 1, 2026, 30 elapsed days lands at midnight on January 31. “One month later” on a calendar is February 1, which is 31 elapsed days. From March 1, 30 elapsed days lands on March 31, and one calendar month lands on April 1, also 31 days. From April 1, one calendar month is May 1, which is 30 elapsed days. The counter never prints a month field, because the field would have to pick one of these meanings and then disappoint anyone who assumed the other. For anniversary language, use counting anniversary days. For a round number of days, use milestone dates.
What the remainder is for
Hours and minutes are the leftover after whole days are removed. They are not a second opinion about the day count. 300 days and 23 hours is not “almost 301” in the day box; the day box still says 300 until the next full 24 hours complete. If you are waiting for a round day number, wait for the hours and minutes to roll to zero. Rolling to zero happens at local midnight only when no daylight-saving shift is hiding inside the span. Otherwise it happens when elapsed time, not the wall clock’s date, hits the multiple of 24 hours.
Checking the page against a calendar
To audit a result, write the start date and today’s date, count the days on a calendar you trust, and decide whether you counted both ends. Then compare to the page at a known time, ideally just after midnight, so hours are a small number you can see. If the day figures differ by one, you almost certainly included an endpoint the page does not include. If they differ by an hour near a daylight-saving weekend, read the time-zone guide before you call the page wrong. If they still differ, email contact@days-since.app with both dates, the time zone of the device, and the two numbers.