Age Calculator
Enter a date of birth and a date to calculate on to see a calendar-aware age in years, months, and days. The tool also reports the total elapsed days and the number of days until the next birthday. It does not approximate an age by dividing by 365, so leap years and the different lengths of calendar months are handled explicitly. Dates stay inside your browser and are never uploaded.
Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.
Add to Chrome — freeWhat it does
- Calendar-aware years, months, and days
- Total elapsed day count
- Next birthday date and countdown
- Custom calculation date
- Browser-local date processing
How to use Age Calculator
- 1
Enter the birth date
Select the person's date of birth with the date field. The input uses your browser's native calendar control on supported phones and desktop browsers, which helps avoid typing the month and day in the wrong order.
- 2
Choose the calculation date
The second field starts on today's local date, but you can replace it with a past or future date. This is useful for checking an age at an event date, application deadline, policy start, or historical point in time.
- 3
Read the calendar age
The main result gives completed years followed by remaining months and days. The supporting values show all elapsed days and the next birthday countdown. A calculation date earlier than the birth date is rejected rather than shown as a misleading negative age.
- 4
Copy the result
Press Copy age to place a compact summary, including the birthday countdown, on the clipboard. Clear removes the birth date while leaving the calculation date ready for another person.
How it works
The tool parses both dates as calendar dates rather than as timestamps from a particular time zone. It first counts the difference in calendar years, then checks whether the birthday in the calculation year has happened. If it has not happened, one year is removed from the completed age.
After the completed years are known, the remaining interval is measured in months and days. The algorithm moves from the last birthday through whole calendar months, then counts the days left in the final partial month. This is why an answer such as 36 years, 3 months, 19 days can be explained in ordinary calendar language instead of being a rounded decimal such as 36.3 years.
The total day figure is calculated independently as the difference between two UTC midnights. Using UTC midnights avoids daylight-saving changes creating a spurious 23-hour or 25-hour day when a person's dates are compared. It is a duration count, not a replacement for the calendar age.
Leap days and month ends
Some birthdays do not have a matching date in every year. The calculator uses the last valid day of that month as an anniversary when it needs to compare a February 29 or another end-of-month date with a shorter month. It keeps the real February 29 when the calculation year is a leap year. This convention is predictable and is best understood as calendar arithmetic; an employer, insurer, or government form may apply a rule of its own.
Practical uses
Use the custom calculation date for age at a race, age on an application deadline, or the time between two milestones. The birthday countdown is convenient for planning, while the total days figure is useful for rough duration comparisons. For official identity, medical, financial, or legal decisions, verify the result against the rule and document requirements of the relevant authority.
A month is not a fixed length, so the answer depends on the order
Calendar arithmetic has no single correct method, and two reasonable implementations disagree.
The convention used here counts whole years first, then whole months, then the remaining days — the way people say ages out loud. From 31 January to 1 March, that is one month and one day in a non-leap year, because January is counted as complete on 28 February and the extra day follows.
Run the same calculation backwards, subtracting from the later date, and you can land on a different number, because you are now measuring against a February of 28 days rather than a January of 31. Neither answer is a bug. The months genuinely have different lengths and the result depends on which one you count through.
The place this becomes visible is the end of a month. Add one month to 31 March and there is no 31 April to arrive at, so software either clamps to 30 April or rolls to 1 May, and both behaviors exist in tools people use daily.
For anything with consequences — a contractual term, an eligibility window, a notice period — do not rely on a general-purpose calculation. Read how the rule defines the period, because the definition is part of the rule.
Leap-year birthdays and the rules that decide them
A person born on 29 February has a birthday in roughly one year out of four, and every legal system has had to decide what that means.
The two answers in use are 28 February and 1 March, and which applies depends on where you are and what the age is for. Some jurisdictions treat the day before as the completion of the year; others treat the first day of the following month. It changes an age by one day, which is normally irrelevant and occasionally decisive — a driving license, an age-restricted purchase, a deadline that falls exactly there.
The total-days figure sidesteps the question entirely, and that is its real use. Days elapsed is unambiguous: no month lengths, no leap-year convention, no disagreement between two implementations. When two systems report different ages for the same person, comparing total days usually shows which one is applying a different convention.
The countdown makes its own assumption, using 1 March in common years, which is a choice rather than a fact. If the exact day matters, check the rule that governs the decision instead.
Examples
A normal birthday calculation
The person has completed 36 full birthdays, then three complete calendar months after the 2026 birthday, plus 19 days. Counting only 365-day years would lose the useful month-and-day explanation and can be off around leap days.
Checking an age before a birthday
This example shows why calendar arithmetic is more informative than dividing elapsed days by 365. The calculation date is two days before the birthday, so the result has 23 completed years and 11 completed months rather than rounding up to 24 years.
Frequently asked questions
Why is an age not calculated by simply dividing days by 365?
Calendar years are not all the same length because leap years contain an extra day, and months range from 28 to 31 days. Dividing by 365 can be useful for a rough duration, but it cannot explain the completed months and days a person has lived. This calculator subtracts calendar components first and uses elapsed days as a separate supporting value.
Can I calculate somebody's age on a date in the past?
Yes. The second field is a calculation date rather than a permanently fixed “today” value. Set it to the date of a historical event, an exam, a contract, or a future appointment. The result describes the age on that date, while the browser-local current date is used only as the initial convenience value.
How are February 29 birthdays handled?
When a non-leap year has no February 29, the calculator clamps the birthday anniversary to the last valid day of February for its calendar arithmetic. In a leap year, February 29 remains an actual birthday date. Different legal and organizational rules can define leap-day birthdays differently, so use the displayed date as a practical calculation rather than legal advice.
Does this age calculator store dates or send them to a server?
No. The date fields are ordinary browser inputs and the arithmetic runs in the page using JavaScript. There is no submit action and no request carrying the dates. That makes the tool suitable for a quick private check, although you should still follow your organization's rules when handling sensitive personal information.