Age Calculator

This calculator reports age the way almost every official form, medical record and legal document does: as the number of completed years since the date of birth. A completed year is one that has actually finished. If you were born on 15 June 2000, then on 14 June 2026 you have finished twenty-five years and started your twenty-sixth, so your age is 25. The following day, on 15 June 2026, that twenty-sixth year completes and your age becomes 26. Nothing about the calculation rounds up, and nothing counts a year that is still in progress.

That boundary is where most manual age calculations go wrong. Subtracting the birth year from the current year gives the right answer only after the birthday has passed in that year; before it, the result is one year too high. It is a small error with real consequences, because eligibility rules — for a driving licence, a pension, a discounted fare, a vaccination schedule, an age-restricted contract — are almost always written against completed years. This calculator handles the boundary explicitly: the age increases on the birthday itself, not the day before and not at the start of the calendar year.

Once the completed years are settled, the remainder is split into months and then days. The months are counted as calendar months rather than fixed 30-day blocks, which is the only way the arithmetic can stay consistent across a February and a July. The leftover days are then measured from the most recent monthly anniversary of the birth date up to the reference date. So a result of "25 years, 2 months, 6 days" means: twenty-five birthdays have passed, two further calendar months have completed since the last one, and six days have elapsed since that monthly mark.

Splitting into calendar months forces a decision about the end of the month, because not every month has a matching day. Someone born on 31 January has no monthly anniversary in February at all. This calculator clamps to the last available day of the target month, so from 31 January the one-month mark falls on 28 February, or 29 February in a leap year. The alternative — letting the date spill over into 3 March — would push the month count backwards and produce a result that looks plainly wrong. Clamping keeps every month between two consecutive anniversaries exactly one month long, which is what people expect when they read the output.

The same rule settles the classic leap-year question. Someone born on 29 February 2000 has a real birthday only once every four years, so in a common year the calculator treats 28 February as the anniversary and the age increases on that day. This matches the convention used by most administrative systems, which will not leave a person a year older than the calendar allows. In a leap year the birthday falls on 29 February as normal, and the arithmetic is unchanged.

The next birthday shown in the results is always strictly after the reference date. If today happens to be your birthday, the calculator points at next year rather than at today. That choice is deliberate: a "next birthday" that has already arrived would leave zero days to count down to and would tell you nothing. Reading the results on your birthday, you will see the new age in the years line and a date twelve months out in the next birthday line — that pairing is correct, not a bug.

The total days figure counts every calendar day from the date of birth up to and including the reference date boundary, leap days included. It is genuinely useful for the things that months and years handle badly: tracking an infant in weeks, checking a residency or visa day-count, or working out how many days remain before an age threshold is reached. Because it is a plain day count with no month arithmetic in it, it is also the easiest number to verify by hand against a calendar.

Finally, a note on entering the dates. The fields use the ISO format YYYY-MM-DD to avoid the ambiguity between 03/04 meaning 3 April in most of the world and 4 March in the United States. The reference date defaults to today but is fully editable, so you can just as easily ask how old someone was on a particular day in the past, or how old they will be when a future date arrives. If the birth date is set after the reference date the calculator refuses to guess and reports an error instead.