Why can exact-age sites disagree?
They may use different end-of-month conventions, time zones or inclusive counting.
Exact age is calendar arithmetic: count completed years, then completed months since the last birthday boundary, then the remaining days.
From 31 January to 28 February is not “one month because 28 days passed” under every convention. Calendar arithmetic respects real month boundaries instead of assuming every month has 30 days.
Understanding the method is useful when you need to verify an age calculator, handle a birthday near month-end or explain why a decimal-year approximation disagrees with ordinary calendar age.
Years/months/days is a calendar representation whose month component depends on real boundaries. Total elapsed days is unambiguous under a date convention. EgoTools keeps the two views separate instead of pretending months have a universal numeric length.
They may use different end-of-month conventions, time zones or inclusive counting.
Total elapsed days is straightforward; years/months/days is a calendar representation that follows date boundaries.
Suppose someone was born on 15 November 1995 and the target date is 19 August 2026. Subtracting the year numbers gives 31, but the November birthday has not happened yet, so only 30 full years are complete. Calendar age therefore has to follow the birthday boundary before months and days are counted.
This is also why “total days ÷ 365” can disagree with ordinary age language without either number being broken. Total days measures elapsed duration; years, months and days describe the same interval using real calendar boundaries.
EgoTools uses calendar dates for years/months/days and labels approximate conversions separately.
The tool logic is treated as the reference for calculations. Worked examples are checked against the same method, external facts are sourced where relevant, and wording is reviewed so exact results, estimates and entertainment are not presented as the same thing.