Months Between Dates Calculator: Counting Months Correctly

Asking how many months lie between two dates sounds simple, but it hides a genuine ambiguity: months are not all the same length. A month can have 28, 29, 30, or 31 days, so "three months" can mean 89 days, 90 days, 91 days, or 92 days depending on which months you mean. That is why two people can answer the same question differently and both be following a reasonable method. The Months Between Dates Calculator removes that ambiguity by stating its method clearly: it counts whole calendar months between two dates, and reports any leftover days separately. Understanding that method is what makes the result useful, because a month count is only meaningful when you know how it was counted.

The distinction matters in real situations. Tenancy agreements, loan terms, employment probation periods, subscription billing, and project timelines are often expressed in months, and a difference of a few days can decide whether a deadline has passed or a payment is due. If a contract says "three months from 15 January", does it end on 15 April, or after 90 days, which would be 15 April in a non-leap year anyway, or 14 April in some counting conventions? The answer depends on the convention the contract uses, and a calculator cannot settle a legal question for you. What it can do is give you the calendar-month count, which is the convention most contracts and most people mean when they say "months", and show the leftover days so nothing is hidden inside a rounded number.

Whole months and leftover days

The standard method works like this. Start from the first date and step forward one calendar month at a time, keeping the same day number where possible, until the next step would pass the second date. The number of steps you completed is the number of whole months, and the days remaining to the second date are the leftover days. So from 15 January to 15 March is exactly 2 whole months with 0 leftover days, regardless of the fact that February is short, because the day number matches. From 15 January to 10 March is 1 whole month, reaching 15 February, plus 23 days from 15 February to 10 March, since February has 28 days in a non-leap year and 15 February plus 23 days reaches 10 March. The leftover days therefore depend on which month they fall in, which is another reason the method must be stated rather than assumed.

End-of-month dates need a rule of their own. If the start date is 31 January, there is no 31 February, so stepping forward one month lands on the last day of February, 28 February in a normal year or 29 February in a leap year. Different systems handle this slightly differently, and the difference only matters for end-of-month starts, but it is worth knowing the rule your tool uses before you rely on it for a contract date. As a general habit, when a deadline matters, calculate it, then check it by counting forward on a calendar, and if the two disagree, find out why before acting. A calculator is a fast way to get an answer; a calendar check is a cheap way to catch a convention mismatch.

Why not just divide days by 30

A tempting shortcut is to count the days between two dates and divide by 30, or by 30.44, the average month length. That gives a single decimal number, and it is fine for rough comparisons, such as judging whether one project lasted about twice as long as another. It is a poor method for anything that needs a calendar answer, because it erases the actual calendar. A period from 1 February to 1 March is one calendar month but only 28 days, which the divide-by-30 method reports as 0.93 months, an answer nobody would give in ordinary language. Conversely, a period spanning two long months can be 62 days, which divide-by-30 reports as 2.07 months, overstating the calendar count. Use the decimal method only when you explicitly want an average-month approximation, and say so when you report the result, so nobody mistakes it for a calendar count.

Leap years add a similar wrinkle to day counting, though not to calendar-month counting. A calendar month from 15 February 2024 to 15 March 2024 is one month, just as it is in any other year, even though February 2024 has 29 days. The leap day only changes the number of days inside the month, not the month count itself. Where leap years do matter is in the leftover days: a span that includes 29 February has one more day in it than the same span in a normal year, and a day-count method will show that difference while a month-count method will not. Both views are correct; they answer different questions. If your question is "how many monthly payments fall in this period", use months. If your question is "how many days of interest accrue", use days. Choosing the right question first prevents most month-counting arguments.

Worked example with sample values

Suppose a sample period runs from 15 January 2024 to 10 April 2026. Count whole calendar months first, stepping from the same day number. From 15 January 2024 to 15 January 2026 is 24 whole months, because two full years contain 24 months. Check: 2024 to 2025 is 12 months, and 2025 to 2026 is another 12, giving 24. Continue stepping: 15 January 2026 to 15 February 2026 is one more month, making 25, and 15 February 2026 to 15 March 2026 is one more, making 26. The next step, to 15 April 2026, would pass the end date of 10 April, so stop at 26 whole months. Now count the leftover days from 15 March 2026 to 10 April 2026. March has 31 days, so from 15 March to 31 March is 16 days, and from 31 March to 10 April is 10 more days, giving 26 leftover days. The result is therefore 26 months and 26 days.

As a check, try a simpler span with the same method. From 15 January 2024 to 15 March 2026: stepping gives 24 months to 15 January 2026, one more to 15 February 2026, and one more to 15 March 2026, totalling 26 months with 0 leftover days. That matches the first example's whole-month count, which makes sense, because the second example's end date is earlier in the month than the 15th, so it contributes leftover days rather than a whole month. If you instead divided by 30, the first example's day count would give a different-looking answer, but the calendar answer of 26 months and 26 days is the one that matches how people and contracts normally speak about months.

Common mistakes to avoid

The first mistake is counting the starting month and the ending month as full months, which overstates the result by up to two months. Count completed months, not touched months. The second mistake is assuming every month is 30 days, which fails most visibly around February. The third mistake is forgetting leap years when counting days, which throws day-based checks off by one. The fourth mistake is using the wrong date order: months between two dates are the same whichever direction you travel, but a start date after the end date can confuse tools that expect the earlier date first, so put the earlier date first unless the tool says otherwise. The fifth mistake is reporting a rounded month count as if it were exact. "About 26 months" and "26 months and 26 days" are different claims, and for deadlines, billing, and contracts, the exact form is the only safe one. Finally, remember that a calculator gives a calendar answer, not a legal interpretation: if a contract's month rule is unclear, clarify it with the other party rather than assuming the calculator's convention matches the contract's.

Try it next

Count your own span with the Months Between Dates Calculator, then cross-check the day count with the Days Between Dates and the Date Calculator. For a related read on working with date differences, see the guide at /blog/days-between-dates-guide/. State whether you mean calendar months or average months whenever the answer matters, and the confusion that usually surrounds month counts will largely disappear.