A person born on January 31 will get two different answers from two age calculators on March 1. One says "one month and a day old." The other says "twenty-nine days." Both counted correctly. They just disagree about what a month means when the month you're borrowing from has no 31st. Age looks like simple subtraction until the calendar refuses to divide evenly, and then it stops being simple.
Years, then months, then days
The standard way to express an age is years, months, and days, worked out in that order. Take someone born November 20, 1990, checking their age on September 12, 2026.
Years first: 2026 minus 1990 is 36. But November hasn't arrived yet this year, so their most recent birthday was in 2025 — that's 35 years. From that birthday (November 20, 2025) forward: nine full months lands you on August 20, 2026. From August 20 to September 12 is 23 days. Final answer: 35 years, 9 months, 23 days.
That last step hides the whole problem. The 23 comes from August having 31 days. If the arithmetic borrowed from a 30-day month you'd get 22; borrow across February and it shifts again. Date libraries resolve this differently, which is the real reason two tools can land a day apart on the same person. There is no universal borrowing rule — only the convention whoever wrote the calculator happened to choose.
The February 29 problem
Roughly 1 in 1,461 people are born on February 29, and their age is a small ongoing argument. A leap day exists only in years divisible by 4 — except century years, which must also be divisible by 400. So 2000 had a February 29 and 2024 did, but 1900 didn't and 2100 won't.
In the three years out of four with no February 29, when does a "leapling" turn a year older — February 28 or March 1? Different systems answer differently, and it's not academic. Jurisdictions have written it into law for thresholds like turning 18: some deem the birthday February 28, others March 1. A calculator has to pick one, and most roll the anniversary to March 1 in common years. If you were born on a leap day, check which side of the line a given tool falls on before you trust it for anything official.
Days, weeks, and hours
"How many days have I been alive" has a cleaner answer than months, because days don't vary in length. Someone born January 1, 2000, on September 12, 2026, has been alive 9,751 days. That number already absorbs the seven leap days between those dates (2000, 2004, 2008, 2012, 2016, 2020, 2024) — forget those and you'd be a week short.
From there the conversions are honest arithmetic: 9,751 days is exactly 1,393 weeks, and 9,751 × 24 is 234,024 hours. Months are the exception. There's no fixed number of days in a month, so "how many months old" is either a count of calendar months elapsed or a rough division by the average month length of about 30.44 days. The two methods disagree, and neither is wrong — which is worth knowing before you quote a baby's age in months to a pediatrician who's counting calendar months.
Your age depends on where you are
Until June 2023, most South Koreans carried three ages at once. Traditional Korean age started you at 1 at birth and added a year every January 1, so a baby born on December 31 turned 2 the next day. "Counting age," still used for some laws, is simply the current year minus your birth year. International age — zero at birth, plus one each birthday — is what the rest of the world uses. South Korea standardized on international age for legal and administrative purposes in 2023, but the traditional count still surfaces in conversation.
Time zones bend the number too. Age is anchored to a calendar date, and calendar dates depend on where the clock was running. Someone born at 8 a.m. in Tokyo was born the previous day by California's clock — the same instant reads as mid-afternoon on the date before. For everyday purposes only the date matters, but if you feed a calculator a full timestamp and it converts time zones, the date — and therefore the age — can quietly shift by a day. Enter the local date of birth and leave it alone.
When the exact number doesn't matter
Most of the time, none of this precision is needed. For a form, a rough "I'm 35" is fine, and the naive shortcut — this year minus birth year — is close enough as long as you remember it's wrong for anyone who hasn't had their birthday yet this year. That single off-by-one (assuming the birthday already happened) is the most common manual age mistake there is, ahead of forgetting leap years and miscounting month lengths.
The precision earns its keep in narrower places: infant ages measured in weeks, legal thresholds down to the day, milestone counting, or anything where a document has to match a definition exactly. In those cases the arithmetic is unforgiving and doing it in your head invites errors, which is the entire reason the Age Calculator exists — it runs in your browser, so your birth date, which is genuinely personal data, never leaves your device or gets uploaded to our server.
One thing no calculator can do is tell you which convention counts. It will hand you a precise number of years, months, and days; whether the institution asking wants international age, a rolled-over leap birthday, or calendar months versus average months is a definition question, not a math one. Get the number from the tool, then confirm which rule the person asking is using — that's where the real mistakes hide.