Age Calculator

Exact Age Snapshot

Birth timestamp:

Use YYYY-MM-DD; add HH:MM only when exact birth time should affect hour/minute totals.

As-of timestamp:

Pick any target date, or use Now to fill the current local date and time.

Summary mode:

Calendar shows years/months/days; elapsed shows total days lived.

Include time-of-day:

Enable to use 24-hour HH:MM fields; leave off when only calendar dates are known.

Feb 29 handling:

Choose Feb 28 or Mar 1 before trusting birthday countdowns for a Feb 29 birth.

Year basis:

Use Gregorian mean for civil-calendar work, tropical for seasonal comparisons, or Julian for 365.25-day math.

Milestone profile:

Classic, U.S. age gates, retirement, or Every N years; choose Every N years to use the custom interval.

Custom interval:

Enter a whole number from 1 to 20 years; disabled until Milestone profile is Every N years.

years

Planning horizon:

Enter 1-120 years; longer horizons show farther future checkpoints.

years

Birthday alert window: {{ birthday_alert_days }} days

Slide from 0 to 120 days; 0 means only birthday day triggers the alert.

Round landmark set:

Practical uses common day/week/month markers; Special adds hour and second markers when time is enabled.

Reference target age:

Enter a whole age from 1 to 130; it appears only if it is after the as-of age and within the horizon.

years

Metric	Value	Copy
{{ row.label }}	{{ row.value }}

Guide item	Date / status	Timing	Notes	Copy
{{ row.label }}	{{ row.dateLabel }}	{{ row.daysAwayText }}	{{ row.note }}

Marker	Value	Note	Copy
{{ card.label }}	{{ card.value }}	{{ card.note }}

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

Age looks simple until the comparison date matters. A birthday gives a familiar yearly marker, but many real uses need a more careful answer: age on a past record date, the number of days lived, the next birthday boundary, or a future milestone that should be planned before it arrives. The same birth date can produce several correct-looking numbers, and each one answers a different question.

Civil age normally follows completed anniversaries. Someone born on May 20 has not completed the next year on May 19, even if the elapsed time is only one day short. Month and day remainders work the same way: they depend on real calendar months, not an average month length. That is why end-of-month dates and February dates can feel surprising when the comparison point sits near a short month.

Age terms and the questions they answer
Term	Question it answers	Where it is useful
Calendar age	How many birthdays, months, and days have been completed?	Forms, records, birthday wording, and most everyday age checks.
Elapsed duration	How much total time has passed between two dates or timestamps?	Total days lived, weeks lived, hours lived, and round-number landmarks.
Decimal years	What fraction of an average year has elapsed?	Comparisons that need a fractional age rather than birthday wording.
As-of date	Which date should the age be measured against?	Backdated records, future planning, current-age checks, and age gates.

Leap-day birthdays add a convention choice because most years do not contain February 29. Some organizations treat February 28 as the anniversary in ordinary years, while others wait until March 1. Neither choice changes the birth record, but it can change completed-year wording, birthday countdowns, and future checkpoint dates.

Timeline showing birth date, last birthday, as-of date, next birthday, and the parts of calendar age

Age milestones are useful reminders, not universal rules. School cutoffs, travel documents, employment forms, account policies, benefits, and medical guidance may define their own comparison date or convention. Keep the source birth date, the as-of date, and the leap-day rule with any result that another person needs to repeat.

Precision should match the record. If only a birth date is known, adding a guessed birth time makes total hours and minutes look more exact than they are. When time-of-day is genuinely important, both timestamps should use meaningful local times and the result should be read as a local-time calculation.

How to Use This Tool:

Start by choosing the two points in time. Then add convention and planning settings only when they change the answer you need to keep.

Enter Birth timestamp and As-of timestamp. Use Now when the comparison point should be the current local date and time.
Choose Summary mode. Calendar age headline highlights years, months, and days, while Elapsed days headline puts total days lived first.
Turn on Include time-of-day only when both dates have reliable HH:MM values. Leave it off for date-only records so local midnights are compared consistently.
Set Feb 29 handling before trusting completed-year wording, birthday countdowns, or future milestone dates for a leap-day birth.
A February 29 birth can use February 28 or March 1 in non-leap years. Match the rule used by the form, organization, or record you are checking.
Use Year basis for decimal-year comparisons, and use Milestone profile, Custom interval, Planning horizon, Birthday alert window, Round landmark set, and Reference target age when future age events matter.
If an error appears, fix the date order or invalid timestamp before reading results. The as-of timestamp must be the same as or later than the birth timestamp.
Review Age Ledger for audit totals, Decision Guide for upcoming checkpoints, Birthday Compass for the current birthday cycle, and Age Horizon Map for planned future events.

Interpreting Results:

The headline result is the quick answer. Use Age Ledger when the number will be copied, checked, or reused, because it separates Completed years, Months after last birthday, Days after month anchor, Total days lived, Total hours lived, and Decimal years.

A precise-looking age does not prove the source dates are precise. Guessed birth times can change hour and minute totals, short countdowns, and birthday-cycle percentages without improving the record. For date-only work, trust the calendar fields more than the timestamp-style totals.

Use Completed years for ordinary age wording and most civil records.
Use Total days lived or Approx total weeks lived for elapsed-time landmarks.
Use Birthday alert status as a reminder only; official age gates may use their own cutoff date.
Use Decision Guide and Age Horizon Map to check which future rows fall inside the selected planning horizon.

Technical Details:

Calendar age is built from anniversary anchors. The completed-year count is the largest birthday anniversary that is less than or equal to the as-of timestamp. Completed months are then counted from that anniversary by stepping through real calendar months, and the remaining days are counted from the last valid month anchor.

Elapsed duration uses the timestamp difference between the birth and as-of values. Date-only entries are treated as local midnight on the selected calendar dates. When time precision is enabled, the selected hours and minutes are included in the same local-time calculation. Decimal years divide elapsed days by the selected average year length, so the year basis affects only the fractional-year output.

Formula Core:

The formulas below show the main split: anniversary math produces calendar wording, while elapsed milliseconds produce total days and decimal years.

TotalDays = ⌊ \frac{AsOfTime - BirthTime}{86400000} ⌋

DecimalYears = \frac{TotalDays}{YearBasisDays}

CompletedCalendarMonths = 12 \times CompletedYears + MonthsAfterBirthday

Age formula symbols and their meanings
Symbol or value	Meaning	Where it appears
`BirthTime`	Birth date, plus the selected birth time when time-of-day is enabled.	All age, birthday, and milestone calculations.
`AsOfTime`	The comparison timestamp selected as the age reference.	Current age, elapsed totals, birthday countdowns, and planning rows.
`86400000`	Milliseconds in a 24-hour day.	`Total days lived`, weeks, hours, minutes, and seconds.
`YearBasisDays`	The selected average year length.	`Decimal years`.

For example, 1990-01-01 to 2026-05-17 with time precision off spans 13,285 total days. Calendar age is 36 completed years, 4 months, and 16 days. On the 365.2425-day Gregorian mean basis, decimal age is about 36.373095 years.

Year basis choices for decimal age
Year basis	Days per year	Best use
Gregorian mean	365.2425	Civil-calendar comparisons that need an average Gregorian year.
Tropical year	365.24219	Seasonal comparisons where the solar year is the intended reference.
Julian year	365.25	Legacy or approximate calculations that intentionally use a 365.25-day year.

Age calculation boundary rules
Boundary	Rule	Result affected
Invalid date or time	Dates must be real `YYYY-MM-DD` values; time values, when used, must be valid `HH:MM` values.	No age result is shown until the input is corrected.
As-of before birth	`As-of timestamp` must be equal to or later than `Birth timestamp`.	The form reports an error instead of producing a negative age.
February 29 birth	In non-leap years, the selected rule maps the anniversary to February 28 or March 1.	Completed years, birthday countdowns, birthday-cycle progress, and age-event dates can change.
Birthday alert	The alert is active when days remaining to the next birthday are less than or equal to the selected 0-120 day window.	`Birthday alert status` and planning cue wording.
Planning horizon	Future birthdays, milestone ages, day landmarks, and the reference target age appear only when they fall inside the selected horizon.	`Decision Guide` and `Age Horizon Map`.

Accuracy Notes:

Age results are informational date calculations. They do not decide legal age, benefits, medical age bands, school enrollment, travel eligibility, or account policy by themselves.

Time-of-day results use the browser's local timezone for the selected timestamps.
Daylight-saving changes can affect timestamp-duration totals near transition dates.
Leap seconds are not modeled.
End-of-month dates use real calendar months, so shorter destination months can change the month-and-day remainder.
Milestone profiles are reminder sets, not personalized legal, medical, retirement, or benefit rules.
The age calculation runs in the browser after the page loads; copied rows, downloaded files, and shared results contain the dates and settings you choose to include.

Advanced Tips:

Use Gregorian mean for most civil date comparisons; switch year basis only when the decimal-year number itself is the output you need.
Set Birthday alert window to 0 when only birthday day should trigger the alert.
Choose Every N years in Milestone profile when you need a regular custom interval from 1 to 20 years.
Increase Planning horizon when a future checkpoint is missing from Decision Guide.
Keep Feb 29 handling, Year basis, and Include time-of-day with copied results so another person can repeat the same calculation.

Worked Examples:

Record age on a fixed date

With Birth timestamp set to 1990-01-01 and As-of timestamp set to 2026-05-17, Primary age readout shows 36y 4m 16d. Age Ledger also shows 13,285 in Total days lived and 436 in Completed calendar months lived.

Leap-day birthday check

A 2000-02-29 birth with an as-of date of 2026-02-28 depends on Feb 29 handling. The February 28 rule treats the 2026 anniversary as reached. The March 1 rule leaves the next birthday one day away, so completed-year wording and milestone dates differ.

Round-number landmark planning

For someone approaching 15,000 days lived, Round landmark set can add that checkpoint to Decision Guide when it falls inside Planning horizon. Switching Summary mode to Elapsed days headline keeps the day count prominent while the ledger still preserves calendar-age fields.

Date-order correction

If the as-of date is earlier than the birth date, the result area reports that the as-of timestamp must be the same as or later than the birth timestamp. Correct the date order before using Age Ledger, Decision Guide, or copied exports.

FAQ:

Why do calendar age and total days lived differ?

Calendar age follows birthday anniversaries and real month lengths. Total days lived is an elapsed-duration count, so it can answer a different question from the same two dates.

Should I include time-of-day?

Use Include time-of-day only when both timestamps have reliable hours and minutes. Leave it off when the source record gives only dates.

Which February 29 rule is correct?

Use the rule required by the organization, jurisdiction, form, or record that will rely on the result. Both February 28 and March 1 are supported because real workflows use both conventions.

Why are some future milestones missing?

Future rows appear only when they are after the as-of age and inside Planning horizon. Increase the horizon, change Milestone profile, or choose a different Round landmark set.

Are entered dates sent away for calculation?

The calculation runs in the browser after the page loads. Copied rows, downloaded reports, and shared results can still contain the date information visible in them.

Glossary:

As-of date: The comparison date used to calculate age at a specific point in time.
Calendar age: Completed years, months, and days since birth, anchored to birthday anniversaries.
Decimal years: Elapsed days divided by the selected average year length.
Elapsed duration: The total time between the birth timestamp and as-of timestamp.
Leap-day handling: The convention used for February 29 birthdays in years without February 29.
Planning horizon: The future range searched for birthdays, milestones, landmarks, and reference target ages.

References:

Leap Year, Hong Kong Observatory.
Leap Seconds FAQs, National Institute of Standards and Technology, updated October 11, 2024.
See your Full Retirement Age (FRA), Social Security Administration.
Use Social Security retirement calculators to estimate your benefits, USA.gov, last updated January 16, 2026.