Practical guide
Leap-Day Birthdays: Choose an Explicit Annual Calendar Policy
An exact February 29 yearly event appears only in years with that date. A yearly reminder on February’s final day or on March 1 is a separate chosen policy. Make that choice explicit without changing the recorded birth date.
Separate the birthday from a reminder policy
A birthday date of February 29 remains February 29. A calendar reminder needs a decision about non-leap years: no occurrence, the final February date, March 1, or another personally chosen date. The recurrence rule cannot infer that preference, and a reminder does not establish a legal age, eligibility or deadline rule.
RFC 5545 requires invalid generated dates to be ignored. An exact yearly February 29 pattern therefore skips years that do not contain February 29; it does not silently substitute February 28. [1]
Exact birthday date
Keep February 29 and accept missing non-leap years.
Annual February-end reminder
Select February’s final date each year.
Annual March 1 reminder
Use a fixed March 1 date chosen for the reminder.
Encode the chosen policy directly
For the exact date, use FREQ=YEARLY;BYMONTH=2;BYMONTHDAY=29 with a valid February 29 DTSTART. For a February-end policy, use FREQ=YEARLY;BYMONTH=2;BYMONTHDAY=28,29;BYSETPOS=-1. It builds valid February 28/29 candidates, then takes the last. In a non-leap year only the 28th is valid; in a leap year the 29th is last. [1]
For March 1 every year, use BYMONTH=3;BYMONTHDAY=1 and a March 1 start. Label it “March 1 reminder” rather than silently recording a February 29 birthday as March 1. These are alternative reminders; importing all of them together would create multiple entries.
Compare the policies over six years
On a narrow screen, swipe within the table to read the remaining columns.
| Year | Exact February 29 | February-end policy | March 1 policy |
|---|---|---|---|
| 2027 | No occurrence | 28 February | 1 March |
| 2028 | 29 February | 29 February | 1 March |
| 2029 | No occurrence | 28 February | 1 March |
| 2030 | No occurrence | 28 February | 1 March |
| 2031 | No occurrence | 28 February | 1 March |
| 2032 | 29 February | 29 February | 1 March |
The February-end and exact-date policies agree in 2028 and 2032 and differ in the other four years. A short preview containing only leap years can hide that difference. These dates describe the chosen Gregorian reminder rules, not cultural or legal definitions of someone’s birthday.
Two complete February practice files
The exact-date file starts in the valid leap year 2028 and counts two occurrences: 2028 and 2032. The February-end file starts in 2027 and counts six annual reminders through 2032. Their counts cover different numbers of years because invalid February 29 dates do not consume COUNT. [2]
Download practice exact leap birthday (.ics)
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Fictional Examples 1.0//EN
BEGIN:VEVENT
UID:2d78e80daadb384032196f18@daymooncalendar.com
DTSTAMP:20261108T000000Z
DTSTART;VALUE=DATE:20280229
SUMMARY:Practice - Exact leap birthday
RRULE:FREQ=YEARLY;COUNT=2;BYMONTH=2;BYMONTHDAY=29
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDARDownload practice february end birthday (.ics)
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Fictional Examples 1.0//EN
BEGIN:VEVENT
UID:5f76474e5dcd86c314387ded@daymooncalendar.com
DTSTAMP:20261108T000000Z
DTSTART;VALUE=DATE:20270228
SUMMARY:Practice - February end reminder
RRULE:FREQ=YEARLY;COUNT=6;BYMONTH=2;BYMONTHDAY=28,29;BYSETPOS=-1
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDARPreserve the original date when changing reminders
Keep a separate factual birth-date field if the contact system supports it. Use a reminder title that states the chosen non-leap-year policy. Do not change the person’s stored birth date merely to make a yearly calendar event appear.
Some contact or birthday features may apply their own fallback behavior. Inspect the actual exported event or documented feature and compare a leap and a non-leap year. These files explain standard rule meanings; they do not prove how a specific contact-birthday feature behaves.
If a deadline or age calculation matters, obtain the controlling jurisdiction’s rule for that task. A personal February-end reminder is not evidence for when eligibility starts. The practical calendar decision here is only when to display your reminder.
Two complete decisions
My February 29 event skips 2029. Is the stored birth date broken?
Not necessarily. The exact-date recurrence has no valid February 29 in 2029.
Check the rule and the contact record separately. If you want an annual reminder, choose and label an explicit fallback policy. Do not rewrite the person’s actual birth date as February 28 just to make the event visible.
I set COUNT=2 for exact February 29 starting in 2028. Is the second event in 2029?
No. The second valid occurrence is February 29, 2032.
The invalid dates in 2029–2031 are ignored and do not count. A February-end policy instead creates an entry every year. The intended reminder frequency, not only the numeric count, determines the correct choice.
Check both years before replacing a birthday series
Verify one non-leap year and the following leap year, then inspect the final counted occurrence if the series is bounded. Keep only the chosen reminder policy in an isolated test calendar. If the event shifts between time zones, use the existing all-day guide to check DATE versus DATE-TIME; that is a separate issue from a missing February 29.
Sources and further reading
- RFC 5545 §3.3.10 — Recurrence valueFrequency, intervals, ordinal weekdays, set positions, count/cutoff and invalid generated dates.
- RFC 5545 §3.8.5.3 — Recurrence setDTSTART synchronization, inclusion/exclusion precedence and documented examples.