Open and review an ICS file

Use Open an ICS file for a saved export, Paste ICS text for a trusted snippet, or Try sample calendar to learn the interface. Processing stays in the current browser.

Check the header

Before inspecting individual events, confirm the filename, event count, date range, version badge, and issue count. A surprising count or range usually means the wrong file or a parsing problem.

Choose the right preview

• Calendar: spot missing dates, overlaps, all-day events, and recurrence patterns.
• Events: search events and read normalized details without parsing raw text.
• Source: verify exact properties such as UID, DTSTART, TZID, RRULE, and EXDATE.

Switch views; they describe the same current version.

Read an event card

Select a representative event and verify its time, location, time zone, recurrence, reminders, organizer and attendee status. Also check privacy, priority, availability, categories, links, attachments, and UID when present.

Treat meeting links and confidential descriptions as sensitive. CalendarLint displays them so you can verify the file; it does not make them safe to share.

Know what opening means

Opening previews a local file. Importing copies events into a calendar. Subscribing follows a published URL for later updates. Opening in CalendarLint does neither import nor subscribe.

If the file does not open, use Fix an ICS file that will not import.

References

• RFC 5545: Calendar components and properties
• Microsoft Outlook: Import or subscribe