Add Chinese Lunar Birthdays to Your Calendar

A lunar birthday needs a date for each year in your everyday calendar. Saving this year's Gregorian date and choosing “repeat every year” keeps the Gregorian month and day; it does not keep the Chinese lunar birthday. A useful reminder starts with the original lunar date, an agreed way to handle leap months, and a checked list of future dates.

This guide uses an invented birthday on the fifth day of the fifth lunar month. It follows that date through 2027–2029, then uses a separate day-30 example to show a missing day and a year boundary. You can reproduce the examples before entering a family birthday, download an ICS calendar file, and inspect the dates before importing it.

Record the original birthday clearly

Keep the month, day and ordinary-or-leap-month status together. 五月初五 means day five of lunar month five; 闰五月初五 means day five of the leap fifth month. The extra word 闰 changes which month is meant. Neither expression means May 5 in the Gregorian calendar, even though a short numeric note might look like 5/5.

If you only have the original Gregorian birthday, enter its full year, month and day in the lunar birthday calendar tool. It converts that particular date and shows the lunar month, day and any leap-month marker. Do not convert this year's celebration date as a substitute for the original birthday: that answers a different question. You can inspect a date separately in the Chinese lunar calendar.

The original birthday and the chosen way of celebrating are separate records. For someone born in a leap month, the family may want a reminder in the ordinary month, only in a matching leap month, or in both. Confirm that choice with the person concerned. The tool can apply a selected rule; it cannot infer a family's preference from a date or decide which practice is culturally required.

Choose ordinary months, leap months or both

Enter month 5 and day 5, then select lunar years 2027 through 2029. With ordinary months selected, the preview contains three dates. Choosing both ordinary and leap months adds a fourth date because lunar year 2028 has a leap fifth month. These are different dates for the same month number, not duplicate copies of one event.

With the leap-month-only choice, this example exports just 2028-06-27. The other two years have no matching leap fifth month, so the preview shows no date for them. The tool does not silently fall back to the ordinary fifth month. If a reminder is wanted every year, select the ordinary-month rule instead of expecting the leap-only setting to provide one.

The number of exported events therefore need not equal the number of selected years. “Both” can create two events in a year with the matching leap month; “leap only” can create none in other years. Count the preview's dated rows, including any later preview pages, before importing. Rows that report no matching date are not exported as empty calendar events.

Write down the rule alongside the person's name or your reminder title. A list saying only “5/5” is insufficient when someone later rebuilds the calendar. For this practice example, a record such as “month 5, day 5; both month occurrences; lunar years 2027–2029” explains why four events are expected. Keep the date convention clear when sharing a list with relatives using another language.

Handle day 30 and the year boundary

A lunar month can have 29 or 30 days. If a birthday is on day 30, a target month with only 29 days needs a deliberate choice. The tool offers the last day of that month, the first day of the following month, or no event for that occurrence. An adjusted reminder marks when to observe the birthday; it does not establish that day 30 exists in that month.

For a concrete example, choose month 12, day 30, ordinary month, and lunar year 2026 only. That twelfth month ends on Gregorian 2027-02-05, its day 29. The earlier-day choice gives 2027-02-05; the following-day choice gives 2027-02-06, the first day of the next lunar year. Skipping gives no dated event. Check the adjusted-date status as well as the displayed Gregorian day.

This also explains the year selector. It selects lunar years, not a Gregorian January-to-December window. Dates belonging to the end of lunar year 2026 can fall in early Gregorian 2027. The birthday tool accepts complete lunar years 1901–2099. When planning a limited period, inspect the actual first and last Gregorian dates instead of assuming the year labels alone define your calendar's visible range.

Export separate all-day events

Give the reminder a clear title, such as “Practice birthday”, and download the ICS file after checking the preview. Each dated row becomes its own all-day event. The selected period is finite: exporting three years does not create an endless birthday subscription. The event description records the lunar year and month/day, a leap-month marker where relevant, and whether the date was adjusted.

An all-day birthday represents a calendar date rather than a meeting at midnight in a particular time zone. Keep it as an all-day event when importing. If you inspect the file, this pair of fields represents the single date 2027-06-09; the end date is exclusive, so it is written as the following day. It is not a two-day birthday.

DTSTART;VALUE=DATE:20270609
DTEND;VALUE=DATE:20270610

The export does not schedule a notification time. After import, check the destination calendar's all-day notification settings and a sample event. A visible event and a delivered phone alert are different outcomes. If you want to call a relative at a particular hour in China, arrange that timed call separately; moving the all-day birthday to a midnight time can introduce an unnecessary time-zone conversion.

Import into a dedicated calendar

Use a separate calendar for these birthday events when practical, and try the short example first. A distinct destination makes it easier to inspect what was added and replace a batch later. Name it clearly enough to distinguish imported birthdays from work appointments or other personal events. The ICS filename and title do not replace your choice of destination during import.

In Google Calendar on a computer, open Settings, then Import & Export. Select the downloaded .ics file and choose the intended destination calendar before importing. Check that choice: the default destination may be your primary calendar. After the import finishes, inspect the example dates in that calendar rather than judging success only from the import message.

In Outlook.com or Outlook on the web, open Calendar and Add calendar, then choose Upload from file. Select the ICS file, choose the destination calendar and import. This is a file upload, not the Subscribe from web option. The downloaded file contains a fixed set of events; changing the birthday tool's settings afterward does not change those imported events.

For the both-months example, check four events across three years. In particular, look for both 2028-05-28 and 2028-06-27. Open one event to confirm its title, all-day status and description, then check the calendar on the device you normally use. If an event is missing, check whether the correct calendar is visible and whether that row had an actual date in the preview.

1. Match the imported count to the preview's dated rows.
2. Inspect an ordinary date and any leap or adjusted date.
3. Confirm the selected calendar, all-day status and notification setting.
4. Keep the checked file with the inputs and the covered lunar years.

Update the calendar without losing track

Keep a small record for each exported birthday: the original date, month rule, missing-day rule if needed, title, covered years, filename and destination calendar. The record helps distinguish an intentional second leap-month event from an accidental repeated import. It also makes a future extension reproducible when someone else maintains the family calendar.

Do not assume that uploading an overlapping file will update old events or remove dates that no longer belong. Import behavior varies by calendar application. If you change the rule from both months to ordinary months, the new file omits the leap event, but that omission is not an instruction to delete the previously imported event. Check the old batch explicitly.

For an extension with unchanged settings, generate only the later lunar years and keep the earlier period recorded. For a correction within an existing period, identify the affected events before replacing them, or rebuild a dedicated birthday calendar after preserving anything you need. Avoid bulk changes in a mixed calendar where unrelated appointments could be included. Recheck notifications after replacing events.

The exported title helps identify the person, so use a distinct title for each birthday you maintain. Two people can share the same lunar month and day. Before sharing the calendar or file, check who can see those titles and descriptions. Set a reminder to extend the calendar before its final covered year, and revisit distant dates when they become relevant rather than treating a long export as permanent maintenance-free scheduling.