Age calculator
Your exact age in years, months and days. Or the span between any two dates.
How this works: next birthday countdown · days between two dates · born on 29 February?
Hours, minutes and seconds come from whole calendar days at 24 hours each. If a daylight saving change falls inside the span, one of those days really ran 23 or 25 hours on your clock.
How this age calculator gets your exact age
It counts calendar fields, in order: whole years first, then whole months, then the days left over. It never divides elapsed days by 365.25, because that is not how a birthday works. Someone born on 14 July turns a year older on 14 July, whether or not a 29 February happened to sit in between, and an average year length quietly loses or gains you a day.
The order matters. Take the largest whole number of months that still lands on or before your end date, split that into years and months, then measure the remainder in real days. Done that way the answer can be checked: your date of birth, plus the years, plus the months, plus the days, lands exactly on the end date every time. That is the test this page has to pass before it ships, and it passes it on three hundred thousand random date pairs.
What happens to a 29 February birthday
This page says you get older on 28 February in a common year, and it will show you a switch for 1 March if you disagree. Both are defensible and the law does not even agree with itself across borders, so the honest thing is to say which one is on screen rather than hide it. The reason 28 February is the default here is consistency: it is the same clamp the page applies to every other month end, so one rule covers both cases instead of two rules fighting.
The switch is real, and it moves more than one number. On the 1 March setting, somebody born on 29 February 2000 is 11 months and 30 days old on 28 February 2001. On the 28 February setting they are exactly 1 year old on that same day. Their next birthday moves with it too.
Why 31 January plus one month is 28 February
Because 31 February does not exist, so the result is clamped to the last day of the month it landed in: 28 February in a common year, 29 February in a leap year. 31 March plus one month clamps the same way, to 30 April. This is where a lot of date tools go quietly wrong, usually by borrowing 30 days or 31 days as a fixed number instead of the real length of the month being borrowed from.
Clamping has a side effect worth knowing. Going backwards is not the exact mirror of going forwards, so 29 January, 30 January and 31 January all sit one month before 28 February. Any calculator that claims otherwise is rounding something and not telling you.
Days between two dates, and why two tools disagree by one
Almost always because one of them counts both end dates and the other counts the gap. From 31 January to 28 February the gap is 28 days, and counting both dates gives 29. Neither is wrong, they answer different questions, which is why this page shows both and labels them. Use the gap for an age or a deadline, and the inclusive count for how many days you are booking or billing.
Working days, and which days count as the weekend
The working day count here covers both end dates and lets you say which days your weekend is, because Saturday and Sunday is not universal: much of the Gulf runs Friday and Saturday, Nepal takes only Saturday, and plenty of people work a four day week. Tap the days off and the number updates.
It does not know about public holidays. Those differ by country, by region and by year, and a tool that guesses them is worse than a tool that tells you to subtract your own. Everything else is exact, and the count is checked against a day by day tally before it ships.
Timezones, daylight saving and why none of it moves your birthday
Your birthday is a calendar date, not a moment in time, so this page never converts anything to timestamps. Every value here is a year, a month and a day, turned into a plain day number with integer arithmetic. That is the whole defence against the classic bug where someone born on the 1st reads back as born on the 31st, which happens when a date gets parsed as UTC midnight and then displayed in a timezone behind it.
It also survives the stranger cases. Clocks going forward or back inside the span changes nothing. Samoa skipped 30 December 2011 completely when it jumped the date line, and a count across that week still gives the right number of calendar days here, because calendar days are being counted and not hours.
Your age in months, weeks, days and seconds
Total months is the count of whole calendar months, so it tracks your monthly anniversary rather than dividing by 30. Total weeks is whole weeks with the spare days shown next to it. Hours, minutes and seconds are built from whole days at 24 hours each, which is right for a calendar day in every case except the two days a year a daylight saving change lands on. The page says so next to the number instead of pretending to a precision it does not have.
How far back and forward it goes
From year 1000 to year 2999, using the Gregorian calendar throughout. Leap years follow the real rule, which is every four years except century years, unless the century divides by 400: 1900 and 2100 are common years, 2000 was a leap year. Before 1582 the Gregorian calendar had not been adopted anywhere, and Britain and its colonies only switched in 1752, so very old dates here are correct arithmetic rather than correct history.
More tools
Everything here runs in your browser. Nothing you type is sent anywhere or stored.