Quick Start: Inspect and repair an ICS file

CalendarLint helps you inspect an ICS file locally, repair supported problems, and export a new copy. Keep the original file until the repaired copy passes a test import.

1. Open and preview

Open the file in Workspace. Confirm the calendar name, event count, date range, and several known events. Use:

• Calendar for visual gaps and overlaps.
• Events for searchable event details.
• Source for exact ICS lines.

If the preview does not match the expected calendar, stop before repairing.

2. Investigate findings

Open each finding and connect three facts: the source line, the possible effect, and the proposed change.

• Accept mechanical repairs such as a missing VERSION:2.0 when the evidence is clear.
• Do not guess an unknown time zone, event time, UID relationship, or recurrence intent.
• Use Leave unchanged when the publisher must clarify the data.

3. Save a new version

Add confirmed fixes to the draft, then choose Apply fixes as new version. The original remains available in version history.

Compare the old and new versions. Check summary counts first, then inspect Events, Issues, and Source for unexpected changes.

4. Download and test

Download the current version with a new filename. Test it in a non-production calendar before replacing anything important.

You are done when:

• expected events, times, recurrence, and attendees are unchanged;
• intended findings are resolved and no unexplained new finding appears;
• the target calendar accepts the file.

Next: Open and review an ICS file or repair an import failure.

References

• RFC 5545: iCalendar
• Google Calendar: Import events