TL;DR: People born 29 February still age every calendar year; in non-leap years tools pick 28 February or 1 March as the effective birthday for counting. Test leaplings in Chronological Age Calculator and record which convention your process uses.

What makes leap-day births unusual

Gregorian calendars add 29 February every four years (with century rules). A birth on that rare date has no identical calendar anniversary in off years. Age calculators must choose a surrogate day for “birthday reached” when February has only 28 days.

Common policies: treat 28 February as the birthday in non-leap years, or treat 1 March as the birthday. Both are defensible; inconsistency between tools is the problem, not one policy alone.

How anniversaries move in off years

Consider birth 29 February 2012. In leap 2024, the anniversary is 29 February. In 2025, a tool using 28 February policy increments age on 28 February 2025; a 1 March policy waits until 1 March 2025. One day difference near the boundary affects same-week eligibility checks.

Legal age for drinking, voting, or contracts may follow statutory rules that override calculator defaults. When law cites “eighteenth birthday,” consult jurisdiction guidance for leaplings—calculator output informs but does not replace legal text.

Verifying leap-year logic in your tool

Run three checks in Chronological Age Calculator: as-of 28 Feb non-leap, 1 Mar non-leap, and 29 Feb leap year for the same leapling DOB. Note which as-of dates increment the year column. Document that triple for your team’s SOP.

Compare against Excel DATEDIF and manual count. Spreadsheet functions may use yet another convention—alignment matters more than which convention is “right” in abstract math.

Leap years vs leap-day birthdays

Everyone lives through leap years; only leap-day births lack a matching DOM annually. A person born 1 March never faces surrogate-day choice. Confusion arises when users assume leap-year insertion changes everyone’s age calculation—it does not, except for Feb 29 births and for month-length borrowing near February.

Century years not divisible by 400 skip leap day—2100 will not be a leap year. Long-range genealogy spanning centuries should use proleptic Gregorian rules consistently.

Forms and identity documents

Passports and birth certificates show 29 February when that was the true birth date. Do not alter DOB entry to 28 February when using a calculator unless your legal advisor says to—enter the recorded birth date and let the tool apply its leapling policy.

Some legacy systems reject 29 February in dropdowns. Workarounds (store 28 Feb internally) must be documented so age recomputation stays traceable.

Sports and school cutoffs with leaplings

Cutoff dates like 1 September compare age on that date regardless of leap quirks. A leapling still either qualifies or not based on computed age on cutoff—surrogate birthday choice rarely moves age by more than a day near cutoff unless cutoff falls exactly on 28 Feb–1 Mar window in a non-leap year.

When qualification is tight, run as-of exactly on the handbook date, not “around” the date.

Communicating age to leap-day children and families

Kids ask why they have no birthday some years. Separate celebration date from legal age counting—they can party on 28 Feb or 1 Mar while tools still increment age per software policy. Clarity reduces family arguments about “real” birthday.

Maintenance when rules change

Software updates occasionally change leapling handling. Re-run your standard leapling test vector after major site updates. A one-day shift in output is a signal to re-verify open applications pending at the time of change.

Leap-day births are rare on paper and common in confusion. A person born 29 February still ages every calendar year; the difficulty is that most years lack a February twenty-ninth, so software must pick a surrogate anniversary in off years. Two defensible conventions dominate: treat 28 February as the birthday in non-leap years, or treat 1 March as the birthday. Neither is mathematically “more true”; inconsistency between tools is what breaks workflows.

Trace one leapling through a non-leap year to see the boundary effect. Born 29 February 2012, as-of 27 February 2025 shows one age; as-of 28 February 2025 may increment the year under a 28-Feb policy; as-of 1 March 2025 increments under a 1-Mar policy. Eligibility checks scheduled in that week—sports tryouts, benefit windows—can flip on a single day if teams mix calculators with different conventions.

Statutory age thresholds may override calculator defaults. Law that cites “eighteenth birthday” or “twenty-first birthday” can include jurisdiction-specific leap-day language. Use Chronological Age Calculator to explore dates, then confirm against the governing rule text when money, licensing, or criminal liability hangs on the answer.

Verification beats assumption. Run three checks for the same leapling DOB: as-of 28 February in a non-leap year, as-of 1 March in a non-leap year, and as-of 29 February in a leap year. Record which as-of dates increment the year column and store that triple in your team’s standard operating procedure. Compare against Excel DATEDIF only after you know which convention each side uses.

Leap years themselves are not the problem for most people—everyone lives through them. End-of-February month-length changes affect borrowing for all births near February, not only the twenty-ninth. Century years not divisible by four hundred skip leap day; long genealogy spans should apply proleptic Gregorian rules consistently rather than mixing Julian and Gregorian assumptions.

When you communicate leapling age to non-technical readers, state the convention aloud: “We count your birthday on 28 February in off years.” That prevents the social myth that leaplings “only age every four years,” which is false and embarrassing on official forms. Document the convention on printouts attached to applications so reviewers recompute the same way months later.

Sports leagues and schools rarely publish leap-day policy explicitly; staff inherit defaults from whatever software the district bought. Ask vendors which surrogate day they use and mirror that in public FAQs. Parents of leaplings appreciate proactive explanation before tryout week rather than after a roster dispute.

Social media posts often joke that leaplings age every four years; clerks who laugh along without correcting the record set up false expectations. A one-sentence correction in intake materials saves hours of phone calls each leap cycle.

Birthday party planning for leaplings often lands on February twenty-eighth or March first in off years even when legal age incremented earlier in the week. Social celebration date and eligibility date diverge by design; invitations should not cite legal age unless the event gates alcohol or venue contracts. Wedding planners coordinating milestone birthdays for leaplings should confirm which calendar date the client treats as ceremonial versus which date counsel uses for contracts.