Age Calculator

An age calculator measures the span between a date of birth and another date — today by default, or any date you name. The result is given the way people state an age out loud: complete years first, then the months left over, then the days left over after that.

The same span can also be expressed as one number: a count of months, of weeks, of days, even of seconds. Those are useful, and this page reports all of them, but they answer a different question. Nobody answers that question with 9,131 days when asked their age.

By counting calendar boundaries, not by dividing. The calculation runs in two steps: find the largest whole number of months that fit between the two dates, which gives the years and months; then count the days from that point to the reference date.

The second step is a straight subtraction between two real dates, so it can never come out negative and never needs a correction. And because the months step lands on an actual calendar date, adding the reported years, months and days back to the birth date returns the reference date exactly — which is the property that makes an answer checkable rather than merely believable.

What it does not do is divide a day count by 365. Someone born 15 Mar 2001 has lived 9,130 days by 14 Mar 2026 — the day before their 25th birthday. Divide that by 365 and you get 25, so the shortcut declares them 25 while they are still 24. Six leap days have accumulated inside those years, and the divisor has quietly spent them.

Notice what makes the bug hard to catch: on the birthday itself the shortcut agrees with the calendar. It is only wrong on some days, and it is wrong in the direction that flatters — which is how it survives casual testing.

• Enter the date of birth. The field shows the date back to you in words, so there is nothing to misread.
• Leave the second field on today, or set it to the date you want the age measured to.
• Read the exact age in years, months and days at the top.
• Move through the tabs for the birthday, the birth details, the milestones and the date-difference calculator — all measured against the same two dates.

Each of the three parts counts something specific:

• Years — complete years lived. It only increases on a birthday.
• Months — complete months since that birthday, never more than 11.
• Days — days since that month boundary, never more than the length of the month it falls in.

A single day before the birthday, the answer is not “nearly 25” — it is 24 years, 11 months and 27 days, because February is short. That is the level of detail the three-part form exists to carry.

Enter your date of birth and leave the second field on today. The answer appears immediately, along with the total days, the next birthday and the weekday you were born on.

Your date of birth stays in your browser — it is not uploaded, not stored, and not sent to any analytics endpoint. That is worth knowing generally: a date of birth is a common identity-verification question, so it is not something to type into a page that does not say what it does with it, or to post publicly alongside your name.

The calculator counts the exact number of calendar days between the two dates, with every leap day included. For the example above that is 9,131 days over 25 years — 6 more than 25 × 365, because six leap days fell inside the span.

It is also where the hours, minutes and seconds come from. Those are the day count multiplied out, so they are exact to the day and not to the moment — no birth time was entered, and the calculator does not invent one.

Total months counts completed calendar months: years × 12 plus the leftover months. For the example, 300 months exactly.

The tempting shortcut is total days ÷ 30. It is wrong in both directions depending on which months the span covers, because a month can be 28, 29, 30 or 31 days. Over decades that drift adds up to whole months, which is enough to matter when the figure is being used for anything.

Total weeks is the exact day count divided by seven, keeping only the whole weeks and reporting the remainder separately. For the example, 1,304 weeks and 3 days.

Both parts are shown because rounding the remainder away turns an exact figure into an approximate one for no gain. A thousand days is 142 weeks and 6 days — not “about 143 weeks”.

The calculator takes your birth month and day, puts them in the reference year, and checks whether that date has already passed. If it has, it moves to the following year. Then it counts the actual calendar days.

One detail matters more than it looks: on your birthday, the next birthday is today, not the same date next year. A calculator that gets this wrong is wrong on exactly the one day anybody thinks to check.

The second field takes any date, which turns one question into many: how old you were when something happened, how old you will be when something else does, how old someone was on a historical date.

• Age at a graduation, a wedding, a first day at work.
• Age on a future date — a retirement date, a deadline, an anniversary.
• Age at a historical event, for a person born long before it.
• Age on a form’s cut-off date, where a day either side changes the answer.

The one thing a number here does not tell you is whether it makes anyone eligible for anything. Rules attach to ages in ways that vary by jurisdiction and by what is being decided, and some of them measure from a date other than a birthday. This is arithmetic; the rule is elsewhere.

The Date difference tab takes any two dates and reports the gap in years, months and days, plus the total days and weeks. Switch it to Two people and it labels which of the two is older.

The order of the two dates does not matter — the gap is the same either way and the earlier one is identified for you. It runs on the same calendar subtraction as the age above, so the two can never disagree.

They measure the same span and report it differently. A date difference is the raw gap — a count of days. An age is that gap read in calendar terms, where the answer depends on where the month boundaries fall.

So both of these are correct about the same two dates: 9,131 days, and 25 Years. The first is a measurement, the second is an interpretation, and neither converts cleanly into the other — which is precisely why dividing by 365 does not work.

The Gregorian rule has three clauses, and all three are needed:

Skipping the last two clauses is the usual shortcut, and it is invisible for a lifetime — the next century that breaks it is 2100. That is exactly what makes it dangerous: code written today is right until it suddenly is not.

The cost of ignoring leap years altogether is easier to see. Eighty years from 1 Jan 1946 to 1 Jan 2026 is 29,220 days — 20 more than 80 × 365. An age built on 365-day years is nearly three weeks adrift by then, and wrong about the year on roughly a quarter of all birthdays long before.

A leap-day birthday needs no special handling in the age arithmetic. Someone born 29 Feb 2000 is 1 year old on 28 February 2001 and 4 years old on 29 February 2004, and both come straight out of the ordinary calculation.

The only decision is which day to show the birthday on in the three years out of four when 29 February does not exist. This calculator uses the common practical convention — 29 February in leap years, 28 February otherwise — and says so wherever it applies:

That is a display rule, not a legal definition. Jurisdictions and institutions differ on when a leapling’s birthday falls for official purposes, and some treat 1 March as the relevant date. The age itself is the same under either reading.

Months are not the same length, so “one month after the 31st” has to mean something in a month with 28 days. This calculator clamps to the last day of the shorter month, which produces a step worth knowing about:

The jump from 27 days to 1 month looks abrupt, and it is — but every alternative is worse. Rolling forward to 3 March puts a February anniversary in March. Refusing to clamp leaves the calculation with a negative day count it cannot resolve. Clamping is monotonic, and the result always adds back to the reference date exactly.

Chronological age is simply the time elapsed from birth to a chosen date. It is what this page calculates and all it calculates.

Other senses of the word “age” exist in medicine, developmental psychology and elsewhere, and they are assessments rather than measurements. Nothing here speaks to any of them; a number of days is not a finding about anybody.

When the age is being measured from today, the Birthday tab runs a live countdown in days, hours, minutes and seconds, using your own device’s clock — so it counts to midnight where you are, not where the birthday started. The time zone converteris the tool for the version of that question that involves somebody else’s clock.

It counts to midnight at the start of the birthday, not to a moment of birth. No birth time was asked for, and inventing one would make the seconds look meaningful when they are not. If you were born in the afternoon, the true countdown to your birth minute is longer than the one shown by however many hours that was.

The clock only runs when the reference date is genuinely today. Set the second field to a date in 2019 and the countdown becomes a plain day count, because ticking seconds towards a birthday measured from a date you picked would not be counting towards anything.

The Milestones tab lists the ages people commonly mark, with the exact date of each and the weekday it falls on. For the example birth date:

The same date-based method works at any age, and for a young child the months and days carry most of the information — which is exactly what the primary result shows. A child of two years and three months is a different answer from “two”, and both are more useful than 823 days.

Nothing entered here leaves your browser, which is worth knowing before typing anyone else’s date of birth into anything at all.

Long spans are where the calendar handling earns its keep. Over eighty years there are 20 leap days; an approximation that ignores them is nearly three weeks adrift, and one that divides by 365 gets the year wrong far sooner than that.

For adults the useful outputs tend to be the exact age, the next birthday and the age on a specific future date — a retirement date, a policy date, a deadline. All three are measured against whatever you put in the second field.

• Dividing total days by 365. It drifts by about a quarter of a day per year, so it reports the wrong year for a few days around each birthday — roughly 7 days of your 25th year and 20 of your 80th — always overstating rather than understating.
• Reading an ambiguous date format. 03/04/2001 is 3 April in most of the world and 4 March in the United States. This page writes 15 Mar 2001 for that reason.
• Swapping day and month on entry. The field echoes the date back in words underneath so the mistake is visible before the answer is read.
• Ignoring leap years, or hard-coding a list of them instead of applying the rule.
• Assuming every month is 30 days. They are 28, 29, 30 or 31, and the difference is what the months figure exists to track.
• Entering a birth date after the reference date. That produces a clear error here, not a negative age.
• Converting a date through a timestamp. Turning a calendar date into midnight UTC and reading it back locally shifts it by a day for most of the world. This calculator never converts a date into an instant at all — when you genuinely do need that conversion, the Unix timestamp converter is built for it and shows the offset it is applying.

Your date of birth is processed locally in your browser and is not uploaded to our server. It is not stored, not logged, and not sent to any analytics endpoint. There is no account to create, because there is nothing being kept — the calculation is JavaScript running on your own machine, and closing the tab is the whole of the deletion process.

The one exception is one you control. The share button puts the dates into the URL and hands you the link; they travel inside it, so you can read exactly what you are about to send. Because a date of birth is a common identity-verification question, that link is worth treating like one — and pressing Reset clears it from the address bar as well as from the fields. Downloads and printing are the same: the file is produced in the browser and saved to your own disk.