Quick answer
Work through the list: birthday passed, endpoint counting, month-length borrowing, end-of-month clamping, decimal divisor, time zone. One of them explains nearly every discrepancy.
Off by one year
The single most common discrepancy. One tool subtracted birth year from reference year; the other checked whether the birthday had actually occurred. For anyone whose birthday falls after the reference date — about half the population at any moment — those give different answers.
Diagnostic: compare the month and day of birth with the reference date. If the birthday is still ahead, the higher figure is the wrong one.
Use this guide with the right tool: Open the Age Calculator for exact chronological age in completed years, calendar months and remaining days. If the question shifts, compare it with the Date Difference Calculator or the Inclusive Date Count Calculator.
Off by one day
Inclusive versus exclusive endpoint counting. Elapsed counting measures midnights crossed; inclusive counting counts both endpoint dates. The difference is exactly one, permanently, and both are legitimate.
Time zones produce the same symptom for a different reason: a tool using local time and one using UTC can disagree about which calendar date it currently is, which shifts the reference date by a day for several hours out of every 24.
Off by one to three days in the days field
This is month-length borrowing. When the days column goes negative, a correct method borrows the actual length of the preceding month; a common shortcut borrows thirty. February borrows give the largest divergence.
End-of-month clamping produces a related symptom. From 31 January, one month forward is 28 February under clamping and 3 March under rolling. Any sequence of monthly steps built on different conventions drifts apart from the first step.
Decimal answers that nearly match
Decimal ages depend on the divisor: 365, 365.25 or 365.2425. Over a few decades those give visibly different figures for the same interval, and none of them is wrong — they are different definitions of an average year.
If two decimal ages differ in the second or third decimal place, the divisor is almost certainly the cause. Check the stated method rather than recalculating.
What to do about it
Compare stated methods before assuming one tool is broken. A calculator that documents its convention is more trustworthy than one that produces a number with no explanation, even when the undocumented one happens to agree with you.
Where a threshold or an official decision depends on the answer, the convention that matters is the one specified by the governing rule, not the one your preferred calculator uses. Find the rule, then pick the tool that matches it.
Worked example
Try it with the dates in front of you. Where the answer sits close to a threshold, treat that as a prompt to check the rule rather than to conclude.
Common mistakes to avoid
- Assuming the tool that agrees with you is correct. Check the stated methods. A documented convention beats a familiar answer.
- Recalculating instead of comparing methods. The arithmetic is rarely the problem. The convention almost always is.
- Picking a convention to match a desired outcome. Where a rule governs, its convention applies regardless of what any calculator does.
Use the right calculator
Three tools cover most of what this guide describes. Each shows its working, so a result can be checked rather than trusted.
Frequently asked questions
Which conventions does this site use?
Completed years, elapsed day counting, real month-length borrowing, end-of-month clamping, and 365.2425 for decimals. Each page states what applies.
Is one convention more correct?
Not in general. Correctness comes from matching whatever rule governs the decision the number feeds.
Why do phone and web calculators differ?
Often time zone handling. A device using local midnight and a tool using UTC disagree about today's date for part of each day.

