How old are you? It feels like the simplest question in the world until you try to answer it precisely. Is someone born on March 1, 2000 exactly 24 years old on February 28, 2024, or only on March 1? What about someone born on February 29? And if you were born in Tokyo but live in New York, when exactly did your birthday begin?
Age calculators handle all of this quietly, but the rules they follow are more interesting than most people expect. This article walks through how age is really computed, where the edge cases hide, and why different calculators sometimes disagree by a day.
The naive answer and why it breaks
The first instinct is subtraction: current year minus birth year. Someone born in 1990 is 36 in 2026. But if their birthday is in December and today is March, they are still 35. The year difference is only correct after the birthday has occurred this year, so any real calculation must compare month and day as well.
The standard rule: age increments on the anniversary of the birth date. If today is before this year's anniversary, subtract one from the year difference. That handles the common case. Everything interesting lives in the exceptions: months of different lengths, the extra day in leap years, and the question of what counts as the anniversary when the calendar date does not exist this year.
Leap years: the extra day problem
A leap year adds February 29 to keep the calendar aligned with the solar year. The rule: a year is a leap year if divisible by 4, except centuries, which must also be divisible by 400. So 2024 was a leap year, 2000 was one, but 1900 was not, and 2100 will not be.
For someone born on February 29, most legal systems and most calculators treat March 1 as the birthday in non-leap years, though some jurisdictions and traditions use February 28. There is no universal law of nature here; it is a convention, and conventions differ. This is also why age in total days is unambiguous while age in years and months always involves choices.
Leap years also subtly affect everyone else's day counts. A year containing a February 29 has 366 days, so two people born a year apart can differ in total days lived depending on whether a leap day fell between their birthdays. Calculators that report years, months, and days handle this by doing calendar arithmetic rather than dividing a day count.
Months are not equal, and the math knows it
Computing an age like 24 years, 3 months, 11 days requires borrowing across unequal months. The usual algorithm works from the smallest unit upward: if the current day-of-month is smaller than the birth day-of-month, borrow the length of the previous month; then do the same for months against years.
The catch is that the borrowed month's length depends on where you are in the calendar. Borrowing across February in a leap year gives 29 days; in a common year, 28. Borrowing across March gives 31. Two calculators can legitimately disagree by a day if one borrows differently or if one counts the start date inclusively and the other exclusively.
This is also why converting a day count into years by dividing by 365.25 is only an approximation. It is fine for rough figures, like the age of a geological formation, but it is not how anyone's legal age is determined.
Time zones and the international date line
Here is a genuinely strange edge case. Suppose you were born at 11:30 PM on June 1 in Tokyo and now live in New York, fourteen hours behind. In New York it is still the morning of June 1 when your birth moment's anniversary arrives in Tokyo time. So when exactly do you turn a year older?
For legal purposes, the answer is almost always the local calendar date where you are, or where the relevant authority is. Your age for a driver's license or an election is computed against local dates, not against the precise UTC instant of your birth. But a calculator working in pure UTC timestamps would give the instant-based answer, and the two can differ by a day around birthdays.
Daylight saving transitions add a smaller wrinkle: the day you spring forward has 23 hours and the day you fall back has 25. For age in years this never matters, but for age measured in hours or minutes, which some novelty calculators offer, the timezone database has to be consulted.
How age calculators do it step by step
A well-built age calculator follows a consistent recipe. First, it normalizes both dates to the same calendar system and timezone, usually the user's local dates rather than UTC instants. Then it computes the year difference and subtracts one if this year's anniversary has not yet occurred.
Next it computes months and days by borrowing, using the actual lengths of the months involved, which automatically handles leap years. Finally, if it reports totals, it counts the exact number of days between the dates, along with derived figures like weeks, hours, and the number of leap days lived through.
If you ever see two calculators disagree, the difference is almost always in one of three choices: whether the start date counts as day zero or day one, which date is used as the birthday for February 29 births in common years, and whether times are compared in local time or UTC.
Why it matters beyond curiosity
These are not just puzzles. Legal age thresholds, school enrollment cutoffs, retirement eligibility, and insurance brackets all turn on exact age computation, and the conventions vary by jurisdiction. A cutoff of midnight on a birthday versus the end of the birthday can decide eligibility, and different countries have answered the February 29 question differently in law.
Even in ordinary life the edge cases surface: milestone birthdays, anniversary reminders, and the perennial debate over when a decade or century truly begins. The underlying lesson is that age is a calendar convention laid over astronomy, and conventions have corners. Knowing where the corners are is what separates a careful calculation from a naive subtraction.
Frequently asked questions
How is age calculated for someone born on February 29?
Most calculators and legal systems treat March 1 as the birthday in non-leap years, though some use February 28. Conventions differ by jurisdiction, so for legal purposes check local rules; for fun, pick whichever your family uses.
Why do two age calculators sometimes disagree by a day?
Usually one of three choices differs: whether the birth date counts as day zero or day one, how February 29 birthdays are handled in common years, or whether times are compared in local time versus UTC.
Does my time zone change my age?
For legal purposes, no: age is computed against local calendar dates. A pure UTC-instant calculation could differ by a day around your birthday if you have moved across many time zones, but authorities use local dates.
Is dividing total days by 365.25 accurate?
It is a decent approximation but not exact, because real years alternate between 365 and 366 days in an irregular pattern. Proper calculators do calendar arithmetic with actual month lengths instead.
Conclusion
Age looks like subtraction and turns out to be calendar law: anniversaries, borrowed months of uneven length, leap-day conventions, and local dates all shape the answer. The naive year-difference gets you close enough for conversation, but whenever the exact number matters, it is worth knowing which conventions your calculator chose, because someone else's calculator may well have chosen differently.