Age calculator

1. Start with the year difference: 2026 − 1995 = 31.
2. Check whether the birthday has actually occurred yet this year — if not, that count is one too many, so subtract one.
3. Work out the leftover months and days by comparing today's month and day to the birth month and day. This is the fiddly part: if today's day-of-month falls before the birth day-of-month, you borrow a month from the year total and add however many days that borrowed month actually has — 28, 29, 30, or 31, depending which month it is. Miss that step and the day count comes out wrong by a few days.
4. Result: 31 years, 1 months, 29 days.

The same birth date also converts cleanly into other units, if days or weeks are more useful than years for what you're doing — tracking an infant's age in weeks for a vaccination schedule, say, rather than waiting for the first full year.

The next birthday falls on 15 June 2027 — 306 days from today.

A leap year adds February 29 roughly every four years to keep the calendar lined up with Earth's orbit — any year divisible by 4 qualifies, except century years, which need to be divisible by 400 (2000 was a leap year, 1900 wasn't). For everyone born on a normal date this only affects how many days sit in February that particular year. For anyone born on the leap day itself, it means an actual calendar birthday only occurs once every four years, and every age calculator has to pick a convention — March 1 or February 28 — for the years in between.

The year/month/day figures should match exactly across any tool that uses the same today's date and the same birth date — the arithmetic isn't ambiguous. What does vary between tools is the total-day count near a date boundary: whether the current, not-yet-finished day counts as elapsed, and which time zone "today" is measured in. A one-day gap between two calculators almost always comes down to one of those two conventions rather than an actual calculation error.

It's also worth knowing that not every culture counts age the same way to begin with. Traditional East Asian age reckoning counted a newborn as already one year old, with everyone aging up together at the new year rather than on individual birthdays — a system South Korea moved away from for most official purposes in 2023. A birth date recorded in the Islamic (Hijri) or another non-Gregorian calendar needs converting to the Gregorian calendar before a tool like this one can use it at all. None of that is an error in either calculator; it's a different counting convention entirely.

One more source of apparent disagreement: some tools quietly cap or floor the month/day breakdown differently at the boundary of a calendar month with fewer days than the birth month. If you were born on the 31st and the current month only runs to 30 days, the exact borrowing behaviour at that edge case can legitimately differ between well-built calculators without either one being wrong — it's a rounding convention, not a bug, and it only ever shifts the day count by one.

Plenty of everyday eligibility rules hinge on a precise age reached on a precise date, not a rounded figure. A few illustrative examples:

These figures change periodically and vary by category, state, and specific scheme — treat the table as illustrative and check the actual notification before relying on it. The pattern worth noticing is that exam and government forms almost always specify age "as on" a fixed date rather than the application date, precisely because the gap between applying and the actual cutoff can be months — long enough for someone to age in or out of eligibility in between.

• Pin down the actual reference date first. "Today" is the default, but an exam board, HR form, or scheme eligibility check usually specifies its own cutoff — use that date, not the day you happen to be filling in the form.
• Check the February 29 convention before assuming one. Some systems treat March 1 as the observed birthday in a non-leap year, others use February 28 — the form or authority in question should say which, and it's worth confirming rather than guessing.
• Use total days or months where a few weeks could matter. A rounded year figure is fine for casual use, but pediatric dosing, developmental milestones, and some scheme cutoffs are precise enough that the month-level breakdown, not just the year, decides the answer.
• Don't confuse calendar age with gestational or corrected age. Some medical contexts, particularly for premature infants, track age from expected due date rather than actual birth date — a different number for a different purpose, not an error in either one.
• Keep the birth certificate as the record that actually counts. A calculator is a fast cross-check for everyday use; anything with legal, financial, or immigration consequences should be verified against the official document itself.

At 31 years, 1 months, and 29 days, the arithmetic itself is straightforward once the birthday-not-yet-happened check and the month-borrowing step are handled correctly — which is exactly what trips people up doing it by hand. For anything with legal, medical, or exam-eligibility consequences, treat this figure as a fast cross-check and keep the official document as the record that actually counts.

Figures are computed live from the birth date entered (or the illustrative default shown) against today's date, using the Gregorian calendar and standard leap-year rules. Date arithmetic is at calendar-day precision — time of day and time zone aren't factored into the year/month/day breakdown, though the total-day, hour, and minute figures assume a consistent reference time for both dates. None of this constitutes legal, medical, or immigration advice.