The Math Behind Age Calculation: Leap Years & Edge Cases

Typing a birth date into a calculator and getting back "27 years, 8 months, 23 days" feels instant and obvious. Under the hood, though, age calculation is one of those problems that looks trivial and turns out to be full of traps. Months have different lengths, some years have an extra day, and the very definition of "today" depends on where you are standing. This article opens up the algorithm and walks through the edge cases that separate a correct age calculator from a buggy one.

Why you cannot just subtract the years

The most common mistake is treating age as currentYear - birthYear. That formula is only right if the person has already had their birthday this year. Someone born in December 2005 is not 21 in August 2026 — their birthday has not arrived yet, so they are still 20. The correct rule is:

Getting years, months, and days all at once requires more than one subtraction, because you cannot borrow cleanly when the units are not uniform.

Date subtraction with borrowing

The standard approach mirrors the subtraction you learned in grade school, but with calendar-aware borrowing. Compute three raw differences, then fix any negatives from smallest unit to largest:

1. days = today.day - birth.day
2. months = today.month - birth.month
3. years = today.year - birth.year
4. If days < 0: add the number of days in the month before today's month, and subtract 1 from months.
5. If months < 0: add 12, and subtract 1 from years.

The tricky part is step 4. When you borrow days, you have to know how many days the previous month actually held — and that depends on which month it is, and sometimes on whether the year is a leap year. There is no single constant you can use; the calendar decides.

A fully worked example

Suppose the birth date is 1998-11-30 and today is 2026-08-22.

• Raw days: 22 - 30 = -8
• Raw months: 8 - 11 = -3
• Raw years: 2026 - 1998 = 28
• Days are negative, so borrow from the month before August, which is July (31 days): -8 + 31 = 23 days, and months become -3 - 1 = -4.
• Months are still negative, so add 12 and drop a year: months -4 + 12 = 8, years 28 - 1 = 27.

Result: 27 years, 8 months, 23 days. You can sanity-check it by walking forward from the birth date: 1998-11-30 plus 27 years is 2025-11-30, plus 8 months is 2026-07-30, plus 23 days lands exactly on 2026-08-22. The two directions agree, which is the quickest way to test any age routine.

The leap-year rule, precisely

A leap year adds February 29. The full rule, defined by the Gregorian calendar, has three clauses:

• A year divisible by 4 is a leap year…
• …except years divisible by 100, which are not leap years…
• …unless they are also divisible by 400, which are leap years.

That is why the year 2000 was a leap year but 1900 was not, even though both are divisible by 4. The 100/400 exception exists because a solar year is about 365.2425 days, not exactly 365.25, so dropping three leap days every 400 years keeps the calendar aligned with the seasons.

Year	Divisible by 4?	Divisible by 100?	Divisible by 400?	Leap year?
2023	No	—	—	No
2024	Yes	No	—	Yes
1900	Yes	Yes	No	No
2000	Yes	Yes	Yes	Yes
2100	Yes	Yes	No	No

In code this is often written as (year % 4 === 0 && year % 100 !== 0) || year % 400 === 0. Any age calculator that gets February wrong — or that assumes every fourth year is a leap year — will drift by a day around century boundaries.

The February 29 birthday problem

People born on February 29 (a "leapling") only get a true calendar birthday once every four years. In the roughly three years out of four when February 29 does not exist, when do they age up? There is genuine disagreement:

• March 1 convention: the day after February 28 is treated as the anniversary, so they turn a year older on March 1 in common years.
• February 28 convention: the last valid day of February is used, so they age up a day earlier.

Different legal systems and different software libraries pick different sides, and neither is objectively "wrong." A well-built calculator should at least be consistent and, ideally, document which convention it uses. This is the single edge case most likely to produce a one-day discrepancy between two otherwise correct tools.

Time zones and the definition of "today"

Age depends on the current date, but "the current date" is not universal. At a single instant it can already be August 22 in Tokyo while it is still August 21 in New York. If a calculator reads the clock in UTC while you are thinking in local time, your result can be off by a day right around midnight — and a birthday might technically have started in one time zone but not another.

How software actually computes it

Internally, most systems store a moment as an offset from an epoch — commonly milliseconds since 1970-01-01 UTC. Subtracting two such values gives an exact elapsed duration, but that number is in a fixed unit and cannot be divided by 365 to get whole years, because leap years make some years longer. To produce "years, months, and days" you need calendar-aware logic that walks month by month, exactly like the borrowing method above. Mature date libraries handle this for you: relativedelta in Python, Period in Java's java.time, and equivalents elsewhere all compute a calendar-based breakdown rather than a raw day count.

FAQ

Q: Why does my age in "total days" not match years times 365?
A: Because leap years add extra days. Over 28 years you accumulate roughly 7 leap days, so a plain multiply-by-365 estimate will be about a week short.

Q: Which month's length is used when borrowing days?
A: The most common convention borrows the length of the month immediately before the current date's month, accounting for leap years when that month is February. Because month lengths differ, a few date pairs are genuinely ambiguous.

Q: Do I include the birth day itself when counting?
A: Standard age counts full elapsed years, so you turn 1 on your first birthday, not the day after. The elapsed-time model handles this naturally.

Q: Can two correct calculators disagree?
A: Yes, by up to a day, usually because of the February 29 convention or a time-zone difference in what counts as "today."

Explore the free tools →