Sooner or later everyone who counts months meets the number 30.44. Software uses it, statistics use it, and half the month calculators on the internet quietly use it to turn a day count into a month count. It is the length of the average month - a month that does not exist on any calendar, but which is genuinely useful for some jobs and quietly wrong for others. This guide shows where the figure comes from, down to the exact fraction, and draws the line between the work it is good for and the work it should never touch.
Where 30.436875 comes from
The average month is built from the average year. The Gregorian calendar runs on a 400-year cycle with a precise leap year rule: years divisible by 4 are leap years, except century years, which are leap years only when divisible by 400. Across 400 years that produces exactly 97 leap years, so one full cycle contains 400 × 365 + 97 = 146,097 days. Divide by 400 and the average year is 365.2425 days. Divide that by 12 and the average month is 30.436875 days - usually rounded to 30.44.
Two things are worth noticing. First, the figure is not an approximation of how months behave; it is an exact property of the calendar's design, as exact as the 400-year cycle itself. Second, no real month has this length, and no real year has 365.2425 days either. The average month is a statistical unit. It describes months in bulk, the way an average family has a fractional number of children, and it should be handled with the same care.

What the average month is good for
Used on long spans and large collections, the average month earns its keep. Converting a 10-year dataset of day counts into approximate months: divide by 30.436875 and the long and short months cancel each other out almost completely. Estimating an average monthly cost from an annual figure with odd billing dates, comparing durations across hundreds of cases, sizing a rough project timeline in a planning meeting - for all of these, the average month is the right tool, and the months between dates calculator shows the average-month figure alongside the calendar count for exactly these uses. The longer the span, the smaller the error: across a full 400-year cycle the error is zero by definition, and across a decade it is a day or two at most.
Where it misleads: short, specific spans
The trouble starts when the average month is pointed at one specific span with real dates on both ends. February 1 to March 1, 2026 is 28 days. Divide by the average month and you get 0.92 months - yet the span is exactly one calendar month, a fact that matters if it is a billing period or a notice period. Run the same trick on January 15 to April 15, 2026: 90 days, which the average calls 2.96 months, while the calendar calls it exactly 3. And July 15 to October 15 is also exactly 3 calendar months, but it holds 92 days, which the average calls 3.02 months. Three spans, one true answer each, and the average month misses all three in different directions.
The pattern to remember: the average month's error on a single span can be a full day or more per month at the extremes, and it grows exactly when the span is short and the dates are specific - which is precisely when people reach for it. A deadline, an age, a due date or a contract period is always a calendar question, and calendar questions need the anniversary method from our guide on how to calculate months between two dates, not a division. If you need a decimal at all, build it honestly from full months plus leftover days, as our guide on fractional months sets out.
The 30-day shortcut is worse
If the average month is a blunt instrument, dividing by 30 is a broken one. It bakes in an error of about half a day per month, every month, always in the same direction: a year of 365 days divided by 30 gives 12.17 "months", inventing a sixth of a month out of nothing. Across a 36-month loan term the shortcut overstates the span by more than two weeks. The banking world's 30/360 convention does treat months as 30 days, but it does so as a complete, self-consistent system with its own adjustment rules, written into contracts - not as a casual division. If a figure matters enough to calculate, it matters enough to use 30.436875 rather than 30, and to prefer the real calendar count from the days between calculator and the month tools on this site whenever the dates are known.
A simple rule for choosing
Ask one question: does the answer attach to specific dates? If yes - a deadline, an anniversary, an age, a start and an end - count on the calendar, with anniversaries and leftover days, the way our guide on full months vs partial months explains. If no - if the answer is an average, an estimate or a planning figure that will be rounded before anyone uses it - the average month is honest, fast and accurate enough. Most month-counting arguments are really two people using different sides of this rule without realising it.
Frequently asked questions
Why is the average month 30.436875 days and not exactly 30.44?
30.44 is the rounded version. The exact figure is the average Gregorian year, 365.2425 days, divided by 12, which gives 30.436875. For any hand calculation 30.44 is close enough that the difference never changes a rounded answer; the long form matters mainly inside software and actuarial tables.
Where does the 365.2425-day year come from?
From the Gregorian leap year rule. In every 400-year cycle there are exactly 97 leap years, so a full cycle holds 400 times 365 plus 97, which is 146,097 days. Divide by 400 and the average year is 365.2425 days. That average, not any single real year, is what the average month is built from.
When is it safe to divide days by 30.44 to get months?
For estimates over long spans, and whenever the answer will be rounded anyway: rough project timelines, average costs per month, statistics across many cases. The longer the span, the more the long and short months cancel out. It is not safe for short spans, deadlines, ages or anything with a specific calendar date attached.
Why was my 3 months 90 days once and 92 days another time?
Because real months have different lengths and your two spans covered different sets of them. January 15 to April 15, 2026 is 3 months and 90 days; July 15 to October 15 is 3 months and 92 days, because it contains three 31-day months. Both are exactly 3 calendar months. The average month smooths this difference away, which is precisely why it cannot describe a specific span.
Do banks use the average month for interest?
Generally no. Banks use formal day-count conventions written into the product terms, most often actual days over a 365-day year, or the 30/360 convention that pretends every month has 30 days and the year has 360. The average month is an estimation tool used by statisticians, software and planners - close cousins of those conventions, but not a substitute for them in a contract.
Related guides
Fractional months - when a decimal answer is the honest one
Building a decimal month count the honest way, from real days.
How to convert months into years and days
Conversions done exactly, and done by average, side by side.
Full months vs partial months - how to read the answer
The calendar answer the average can never give you.
Months between dates for loan and interest periods
How lenders actually count, convention by convention.
