About This Tool
A calendar view helps you inspect dates; a backup helps you recover them. These are different jobs. This page lets you browse saved events, choose records for export and download files for calendar import, spreadsheet review or restoration.
The events come from Special Date Tracker. Celebration plans can travel in JSON, but they are not turned into birthday events or shopping appointments in ICS. Start by deciding whether you want a calendar snapshot, a readable date list or a restorable copy of the entire collection.
Choose the File That Matches the Job
ICS contains all-day events for importing into a calendar application. CSV is a date-record table for a spreadsheet and includes separate birthday month, day and year fields. Neither is a complete restore file for this site.
JSON is the restore format. With Export Scope set to All dates, it contains every saved date and every plan, including plans not linked to an event. Selected dates includes the checked dates and only plans linked to those dates. An unlinked plan is omitted from a selected-date backup.
How to Use
- Choose Monthly or Yearly under Calendar View. Calendar Month supplies the month for the monthly grid and the year for the yearly grid. Event Category filters the displayed calendar and upcoming list.
- Go to Export and Restore and choose Export Scope. All dates means the full event collection; Selected dates requires you to check records under Select Dates for Export.
- If you want alarms in an ICS file, check Include Calendar Alarms. Also give the relevant event a reminder preference in the tracker; an event with None has no alarm to include.
- Select Export ICS, Export CSV or Export JSON. Check the file before importing it elsewhere, especially its date scope and any notes you are sharing.
- To restore, first keep a full JSON backup of your current collection. Choose JSON Backup, select Validate and Restore, review the replacement confirmation and proceed only if replacement is intended.
Practical Examples: Inspect What the File Actually Contains
The first example is independent of today's date. For the second, the export reference is fixed at 2027-02-01 so the finite birthday series can be checked. The live exporter uses local today; Calendar Month is not an export-reference control.
Export one all-day graduation record
Inputs & conditions
| Saved Event Name | Graduation, family |
|---|---|
| Event Category | Graduation |
| Event Date | 2027-05-22 |
| Repeat | One time |
| Export Scope | Selected dates; only this record checked |
| Include Calendar Alarms | Unchecked |
Verified result
| ICS event count | 1 |
|---|---|
| DTSTART;VALUE=DATE | 20270522 |
| DTEND;VALUE=DATE | 20270523 |
| YEARLY RRULE | Absent |
An all-day event ends at the exclusive next date, so May 23 is correct for an event shown on May 22. It does not create a second celebration day.
Check a finite February 29 birthday series
Inputs & conditions
| Birthday Month | 2 |
|---|---|
| Birthday Day | 29 |
| Birth Year | Leave blank |
| Repeat | Every year |
| Leap Day Rule | March 1 in common years |
| Illustrative local today | 2027-02-01 |
| Export Scope | Selected dates; only this birthday checked |
Verified result
| Dated ICS instances | 20 |
|---|---|
| First instance | 2027-03-01 |
| Second instance | 2028-02-29 |
| Third instance | 2029-03-01 |
| YEARLY RRULE | Absent |
Explicit dates preserve the chosen common-year observance without relying on calendar software to reinterpret a February 29 recurrence. This is a finite horizon, not a promise of a recurring series forever.
How It Works: View Filters Are Not Export Scope
Event Category changes the calendar and upcoming display, but it does not restrict an All dates export. Selecting a future Calendar Month also does not move an annual export's starting point: ordinary annual series begin at the next occurrence relative to local today.
Ordinary annual records use a yearly recurrence in ICS. Annual February 29 records instead produce up to 20 individual dated events under the saved rule. One-time records keep their actual date, even if it is already past. Included alarms use the event's saved days-before preference; support and notification behavior depend on the receiving application.
A restore checks JSON syntax, version, fields, record identifiers and the size limit before replacement. Invalid files are rejected without replacing existing data. This is an atomic replacement of dates and plans, not a partial import that quietly keeps whichever rows happen to work.
Important Notes
The JSON limit is 5 MiB. A CSV or ICS file renamed with a .json extension does not become a valid backup. Clear All Local Data removes the locally saved collection after confirmation; downloaded copies remain wherever you saved them.
Exports can contain titles and notes. Review them before sharing or uploading to another service. Calendar applications may provide notifications after the exported events are imported, but this site does not send email or guarantee alerts while closed. Importing the same snapshot again can create duplicates; verify dates and alarm settings in the destination calendar.