Age Calculator
Find your exact age in years, months and days from any date of birth — plus totals in weeks, days, hours and minutes, the weekday you were born on, and a countdown to your next birthday. All in your browser.
Nothing leaves your browser. Your date of birth is used only on your own device with the built-in date engine. There are no network requests, no logging and no analytics on this tool — you can disconnect from the internet and it still works.
Enter your date of birth to see your exact age.
What "exact age" actually means
People usually give an age as one round number of years, but that throws away most of the information. "Exact age" here means the full calendar breakdown — years, months and days — alongside the same span expressed as running totals. The calculator reaches the breakdown the way a person would count on a calendar: it advances your date of birth one whole month at a time until one more month would overshoot the target date, then measures whatever is left as whole days. Walking the real calendar, rather than pretending every month is a flat 30 days, is what keeps the answer honest across months that are 28, 29, 30 or 31 days long, and it guarantees the month and day figures are never negative.
A worked example
Suppose you were born on 15 March 1990 and want your age on 5 July 2024. Count whole years first: 15 March 2024 has arrived but 15 March 2025 has not, so that is 34 years. From 15 March 2024, add whole months — April, May, June — reaching 15 June 2024; a fourth month would land on 15 July, past the target, so stop at three. Now count the leftover days from 15 June to 5 July: 15 days remain in June plus 5 in July, which is 20. The result is 34 years, 3 months and 20 days. The same distance in single units looks like this:
| Representation | Value |
|---|---|
| Calendar breakdown | 34 years, 3 months, 20 days |
| Total months | 411 |
| Total weeks | 1,790 |
| Total days | 12,531 |
| Total hours | 300,744 |
| Weekday of birth | Thursday |
Each total is an exact count of complete units: "total weeks" is the number of full 7-day weeks and quietly drops the leftover days already shown in the breakdown, so it will not equal the day total divided by seven rounded up. Because the inputs are calendar dates parsed at midnight UTC, the hour and minute figures are the day total multiplied out — precise to the day, not to the second.
Month-end boundaries: the part that trips people up
Months are not the same length, so "add one month" is genuinely ambiguous at the end of a long month. This tool resolves it by clamping to the last valid day: one month after 31 January is 28 February (or 29 in a leap year), because February has no 31st. A concrete consequence — someone born on 31 January 2021 is reported as exactly 1 month and 0 days old on 28 February 2021. That is the same convention most date libraries use, but it is worth knowing, because it means a "monthly" anniversary can appear to skip a day around February and the 31st of short-neighbour months.
Leap years and 29 February
Every day count uses the true length of each month, so leap days are neither dropped nor double-counted. Someone born on 1 January 2000 was exactly 7,305 days old on 1 January 2020 — a span that swallowed five 29 Februaries (2000, 2004, 2008, 2012, 2016). If your own birthday is 29 February, the next-birthday countdown falls back to 1 March in years that have no leap day: born on a leap day in 2000, your next birthday counted from mid-2025 lands on 1 March 2026, the usual way people mark the occasion in a 365-day year.
Days until your next birthday
The countdown finds the next time your birth month and day recur on or after the "age at" date, then reports the whole-day gap and the weekday it lands on. If today is your birthday it shows zero days rather than jumping a full year ahead. Because it counts from the "age at" field and not always from today, you can also ask forward-looking questions — set that field to a future wedding or exam date and read how many days of a particular age you will be on the day.
The time-zone and clock-time caveat
This is the honest limit worth reading twice. The tool works with whole calendar dates, not moments in time, and does all its arithmetic in UTC so day counts come out clean and free of daylight-saving drift. It does not know the hour you were born or the time zone you were born in versus the one you live in now. If you were born just before midnight in Sydney, the same instant was the previous calendar day in London — so an age that hinges on a single day across a large time-zone gap can be off by one. For everyday use (birthdays, milestones, form fields) the calendar-date answer is exactly what people mean; for legal or medical precision, treat the day-level result as indicative and confirm against the birth certificate's local time.
Common mistakes
Three traps catch people out. First, expecting the totals to agree — total months, weeks and days each count complete units of that size, so they describe the same span at different resolutions and will not reconcile by simple division. Second, reading "1 month" as "30 days": a calendar month is 28–31 days, so the month-and-day breakdown is more accurate than any 30-day approximation, but it also means two people the same number of "months" old can differ by a couple of days. Third, setting the "age at" date before the date of birth, which is meaningless; the tool shows a short note instead of a negative age so you notice the fields are swapped.