ICS Calendar File Viewer

View and parse iCalendar (.ics) files showing events, dates, locations, and recurrence rules.

Tested tool guide Tested browser tools Checked August 16, 2026

What ICS Calendar File Viewer does and how it behaves

An .ics file is structured iCalendar text, not a picture of a calendar. This viewer parses its calendar and event components, then presents event summaries, start and end values, locations, and recurrence properties for inspection. It is useful when you want to understand an invitation or export without first adding it to a calendar application. The common surprise is that RRULE is a recurrence definition, not necessarily a list of every occurrence. Calendar files can expose private schedules, so this browser-based inspection does not upload the file.

How the result is produced

Components and properties

The viewer identifies the VCALENDAR envelope and nested components, especially VEVENT. Within each event, properties such as SUMMARY, DTSTART, DTEND, LOCATION, UID, RRULE, EXDATE, and RDATE supply the information to inspect. iCalendar permits long content lines to be folded, so a logical property value can continue on a following physical line. Escaped punctuation and line breaks in TEXT values belong to the value.

Dates and recurrence

An event's DTSTART may be a whole-day DATE, a DATE-TIME with TZID, a UTC value ending in Z, or a floating date-time without a zone. RRULE defines repetition, while RDATE adds recurrence instances and EXDATE removes them. These distinctions determine whether a displayed date represents a day, a fixed instant, local time in an identified zone, or floating civil time.

Good uses

Inspect a downloaded meeting invitation before importing it, confirming the event title, scheduled start and end, location, and any recurrence instructions.
Troubleshoot a recurring event exported from a calendar by comparing RRULE, RDATE, EXDATE, and TZID values with the dates that the calendar application displays.
Review an .ics feed or a file generated by another system to confirm that VEVENT records and expected fields survived the export.

Limits and checks

A displayed RRULE is a compact definition, not an occurrence list. A VEVENT with an RRULE can represent many dates, while a VEVENT without RRULE or RDATE is a single occurrence. COUNT, UNTIL, RDATE, and EXDATE can alter the series, so checking only FREQ and INTERVAL can produce the wrong schedule.
VEVENT's DTEND is a non-inclusive end. For an all-day event, DTSTART;VALUE=DATE:20260815 and DTEND;VALUE=DATE:20260816 describe August 15 only, not a two-day event. A next-day DTEND is therefore not automatically an off-by-one error.
Time interpretation follows the source syntax. A trailing Z denotes UTC, while TZID associates a local date-time with an identified time zone. A DATE-TIME with neither Z nor TZID is floating and is not fixed to a particular zone. Do not assume every displayed time has already been converted to the device's zone.

Common questions

Does a successful parse mean every calendar application will import the file the same way?

No. This viewer reports what it can parse from the file; it does not prove identical behavior in every calendar application. Applications can vary in support for optional or extension properties, malformed content, recurrence display, and time-zone definitions. Test the original .ics file in the intended destination when import compatibility is the question.

How can I tell whether a recurring event ends?

Inspect RRULE for COUNT or UNTIL. COUNT bounds the number of occurrences and includes DTSTART as the first occurrence. UNTIL provides an inclusive upper date or date-time bound. They must not appear together in one RRULE. Also inspect RDATE and EXDATE, since added and excluded instances change the final recurrence set.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.