Leap-day birthdays fall on 29 February in leap years. This guide explains the 28 February and 1 March conventions, the 2100 exception and why legal age thresholds can differ.
If you were born on 29 February, your birthday exists on the calendar roughly once every four years. Every other year, something has to decide what to do about it, and the decisions do not agree with each other.
This is not a trivia question. It determines when a leap-day baby legally becomes an adult, when a warranty expires, and when a policy renews. Different systems answer it differently, and most people affected have never been told which rule applies to them.
Why 29 February exists at all
The Earth takes about 365.2422 days to orbit the sun. A 365-day calendar therefore drifts by nearly a quarter of a day per year, which accumulates to a full day every four years and a full month every 128 years or so. Left uncorrected, the seasons detach from the calendar.
The Julian calendar’s fix was a leap day every four years, adding 0.25 days per year on average. That slightly overcorrects, the real figure is 0.2422, leaving a residual error of about 11 minutes annually, or one day every 128 years.
By the sixteenth century that residual had pushed the vernal equinox roughly ten days away from where the ecclesiastical calendar assumed it was, which mattered because Easter’s date depends on it. The Gregorian reform of 1582 dropped ten days and refined the leap rule:
| Rule | Condition | Example |
|---|---|---|
| Leap year | Divisible by 4 | 2024, 2028, 2032 |
| Not a leap year | Divisible by 100 | 1700, 1800, 1900 |
| Leap year after all | Divisible by 400 | 1600, 2000, 2400 |
This gives 97 leap years per 400 years, an average year of 365.2425 days, within half a minute of the true figure. The residual error is now about one day in 3,200 years.
The consequence nobody expects: an eight-year wait
Because 2100 is divisible by 100 but not by 400, it will not be a leap year. Neither will 2200 or 2300.
For anyone born on 29 February, this creates a gap. The last leap day before the break is 29 February 2096. The next is 29 February 2104. Eight years between birthdays.
Anyone born on 29 February 2096 will therefore have their first real birthday at the age of eight. It is a small piece of calendar arithmetic that produces a genuinely unusual human experience, and the last time it happened was 1896 to 1904.
The two conventions
In a non-leap year, a 29 February birthday has to be mapped onto a date that exists. There are exactly two candidates.
The case for 28 February
- It is the last day of the same month, so the birthday stays in February
- It is what essentially all software does, clamping to the last valid day of the target month
- Databases, spreadsheets and date libraries behave this way by default
- It means a threshold is reached at the earliest defensible moment, which favours the person
- Consistent with how 31 January + 1 month is handled everywhere
The case for 1 March
- A full year has not elapsed until the day after 28 February
- Several legal systems specify it explicitly for exactly that reason
- It is the strictly correct reading of "one year after 29 February"
- It avoids the oddity of a birthday arriving 365 days after the previous one in some years and 366 in others
- Consistent with the principle that a period ends when it is complete, not before
Both arguments are sound. That is precisely the problem: neither can be dismissed, so different systems have picked different answers, and the answer that applies to you depends on which system is asking.
Where each convention shows up
Software almost universally clamps to 28 February. If you add one year to 29 February 2024 in a database, a spreadsheet or any mainstream programming language, you get 28 February 2025. This is the same clamping behaviour that turns 31 January plus one month into 28 February, and it is deeply embedded, changing it would break far more than it fixed.
Legal systems vary, and they vary by jurisdiction rather than by any general principle. Some statutes address leap-day birthdays explicitly; many do not, leaving the question to general rules on how periods of time are computed. Those general rules differ between countries and sometimes between areas of law within a country.
The practical upshot: if an age threshold matters to you and you were born on 29 February, find out the specific rule that applies in your jurisdiction. Do not assume, and do not rely on any calculator, including ours, to tell you. This is one of the few places where a one-day difference has real legal consequence, and the answer is genuinely local.
What this calculator does
Our tools clamp to 28 February in non-leap years, and we say so on every page where it matters. The reason is consistency: it is the same rule we apply to every other month-end date, and applying one rule everywhere is more predictable than special-casing a single date.
That means the Age Calculator will show a leap-day baby reaching a new age on 28 February in non-leap years. If your jurisdiction uses 1 March, add one day.
The Birthday Countdown does the same, and the Date Add & Subtract Calculator flags clamping explicitly when it occurs, so you can see that the result was adjusted rather than wondering whether it was.
The one thing that gets easier
There is a genuine consolation. Six months from 29 February is 29 August, which exists every single year without exception. A leap-day baby has the most reliable half birthday of anyone, no clamping, no ambiguity, no competing convention.
Contrast that with someone born on 31 August, whose half birthday requires clamping to 28 or 29 February every year. The Half Birthday Calculator handles both, and it is one of the few situations where a leap-day birthday is the easy case.
Practical advice for leap-day families
On official forms, always write 29/02 as the date of birth. Never substitute 28 February or 1 March to make a form accept it, a mismatch between your documents causes far more trouble than an awkward date field.
For celebrations, do what you like. Many families mark both 28 February and 1 March in common years, which has the advantage of settling the argument by ignoring it.
For anything with a legal threshold, a driving licence, a pension, an alcohol purchase, a contract, check the rule that applies where you live, in advance, rather than discovering it at a counter.
For the eight-year gap, if you are planning a birth around late February 2096, this is admittedly a long way off. But anyone born then will have a genuinely rare story, and the arithmetic behind it is worth knowing.
The wider point
Leap-day birthdays are a good illustration of something true of date arithmetic generally: the calendar is a human construction with irregularities baked in, and every irregularity forces a convention. Month lengths force clamping. The 0.2422 remainder forces leap years. The 400-year rule forces an eight-year gap once a century.
None of these are bugs. They are the price of keeping a whole number of days aligned with an orbit that does not cooperate. The tools that handle dates well are the ones that tell you which convention they picked, which is why every calculator on this site names its own. For the other traps in the same family, see seven mistakes people make doing date maths by hand.