A leap year birthday on 29 February is a calendar edge case with a simple core: the date exists only in leap years. In 2026 it does not exist, and the next one is 2028. That affects birthday plans, age labels and any form that expects a date, but it does not make the underlying day count ambiguous.
This guide is part of the age calculator guide. It covers the Gregorian rule, the common ways to assign a birthday in a common year, and the arithmetic that keeps age in years, months and days consistent. Use the age calculator to test a date while you read.
The Gregorian leap-year rule
The Gregorian calendar adds a leap day when the year is divisible by 4, except for century years. A century year is a leap year only when it is divisible by 400. So 2024 and 2028 are leap years; 2026 is not; 2100 is not; 2000 is. The exception matters because it keeps the average year close to the solar year: 97 leap years in every 400-year cycle.
February in a leap year has 29 days; in a common year it has 28. The extra day is inserted after 28 February, which is why 29 February is the only date that can disappear from the calendar for three years at a time. The gap can be longer around a skipped century leap year: 2096 is followed by 2104, with no 29 February in 2100.
If dates were spread evenly, a 29 February birthday would fall on about 97 out of every 146,097 calendar days, roughly 1 in 1,506. Real birth dates are not evenly spread, so treat that as a calendar fact rather than a prediction about any hospital ward or generation.
The rule applies to the proleptic Gregorian calendar, which extends the modern leap-year pattern backward before 1582. Historical dates from countries that adopted the Gregorian calendar later can be off by the local Julian calendar, so a genealogy calculation may need a manual adjustment. For dates from the twentieth century onward, the rule above is the one to use.
How often 29 February arrives
For most people the pattern is every four years. The sequence around now is 2024, 2028, 2032 and 2036. In 2026 and 2027 there is no 29 February, so a leapling's birthday falls on a date that has to be chosen by convention. The table shows how the century rule changes the answer.
| Year | Divisible by 4? | Century rule | Leap year? | Days in February |
|---|---|---|---|---|
| 2024 | Yes | Not a century year | Yes | 29 |
| 2026 | No | Not applicable | No | 28 |
| 2028 | Yes | Not a century year | Yes | 29 |
| 2100 | Yes | Divisible by 100, not by 400 | No | 28 |
| 2000 | Yes | Divisible by 400 | Yes | 29 |
Do not use "every four years" as a calculation rule without the century check. A simple four-year loop would mark 2100 as a leap year and put every date after it one day off. A date library that follows the proleptic Gregorian calendar handles this correctly; a hand-written rule needs the 100 and 400 tests.
Three ways to mark a 29 February birthday
There are three practical conventions for a common year:
- 28 February: treat the last day of February as the anniversary, so the age increments on 28 February.
- 1 March: treat the first day of March as the anniversary, so the age increments on 1 March.
- Wait for 29 February: hold the celebration until the date returns. That can mean a four-year gap and, around 2100, an eight-year gap.
None of these changes the number of days the person has lived. They change the label attached to a particular day. Legal and administrative rules are jurisdiction-specific. Some systems specify 28 February, others specify 1 March, and some laws define age by the anniversary of birth without addressing the missing date. Check the rule that applies to the form, licence or statute instead of assuming one convention is universal.
For everyday purposes, pick a convention inside the family and use it consistently. For official purposes, follow the document. Mixing the two is how a person ends up celebrating on 28 February and filing paperwork as if the birthday were 1 March.
For a child, the convention can affect school cutoff dates by a day, which matters in districts with a strict 1 March or 28 February boundary. For an adult, the practical effect is usually the celebration date, not the legal age. The day count is the stable measure; the annual label is the local rule.
Age arithmetic for a leap-day birthday
Example 1: born 29 February 2000, observed on 28 February 2026. Under the 28 February convention, the person has completed 26 years. The day count is 26 × 365 = 9,490, and the leap days from 2004 through 2024 add 6 more, for 9,496 days. That is 26 years, 0 months and 0 days under that convention. Under the 1 March convention, the same 28 February date is 25 years, 11 months and 27 days, because the 2026 anniversary has not arrived yet.
Example 2: born 29 February 2000, observed on 1 March 2026. Under the 1 March convention, the person is exactly 26 years old on that date. The day count is 9,497 days: 9,496 days to 28 February 2026, and one more day to 1 March. The one-day difference between the two conventions is the entire dispute in most birthday arguments.
Example 3: an ordinary leap-year effect. From 2024-01-01 to 2025-01-01 there are 366 days because 2024 contains 29 February. From 2025-01-01 to 2026-01-01 there are 365. Someone born on 1 January gains an extra day in the first interval, which is why multiplying age in years by 365 always undercounts.
Notice what stays fixed. The day count between two dates is a fact; the year and month breakdown depends on where you place the anniversary. If a form asks for age in years, use its convention. If you are measuring time lived, use the dates and count days.
If you need the age in months as well, count complete months first, then the leftover days. From 29 February 2000 to 28 February 2026 under the 28 February convention, the complete months are 312 (26 × 12), with 0 leftover days. Under the 1 March convention, the complete months are 311, with 27 leftover days. The month count and the day count move together; they are not independent estimates.
What this means for documents and milestones
Age in years is a legal and social label; age in days is a count. A 29 February birthday creates ambiguity only in the first. For school cutoffs, driving eligibility, retirement or visa forms, use the date of birth the document expects and apply the local rule. For a day count, use both dates and count the boundaries between them.
Time zones add a second edge. A baby born at 23:30 on 29 February in one zone may already be 1 March in UTC. If a record stores only the local date, keep that local date; if it stores an instant, convert to the zone that governs the record before deciding which calendar date applies. Do not combine a UTC timestamp with a local birthday convention.
Leap-day birthdays also affect recurring reminders. A calendar app that simply repeats "29 February every year" will skip three years at a time. A reminder set for 28 February or 1 March will fire annually, but it will not match the legal date if the governing rule uses the other convention. Decide which behavior you want before you create the event.
Checking a leap-day date in the age calculator
The age calculator takes a birth date and a comparison date and returns years, months and days, total days, and the next birthday. Enter 2000-02-29 and 2026-02-28 to see the 28 February convention in action, then change the comparison date to 2026-03-01 and compare.
- Enter the birth date exactly as recorded, including 29 February if that is the legal date.
- Choose the date you are measuring to; today is the default.
- Read the year-month-day result and the total days separately.
- Check the next-birthday line, which points to 2028 when the current year is common.
For a pure day count that ignores birthday conventions, use the age in days guide. For the difference between two arbitrary dates, the date difference tutorial covers inclusive and exclusive counting.