Which parts of the .ics file are shown?

For each VEVENT the tool shows the SUMMARY as a title, the DTSTART and DTEND as human-formatted dates and times, the computed duration, the LOCATION, any RRULE described in plain English, and the DESCRIPTION with line breaks restored.

How are timezones handled?

Date-times ending in Z are UTC and are converted to your browser's local timezone for display. Floating times and times with a TZID are shown as local clock times. All-day events (VALUE=DATE) show only the calendar date, with no time.

Is my calendar uploaded?

No. The entire .ics file is parsed in your browser using JavaScript. Your event titles, attendees and locations never leave your machine, so it is safe for private calendars.

Does it understand recurring events?

It reads the RRULE and summarises it in plain English — for example 'Repeats weekly, 3 times' — but it does not expand every individual occurrence. The first/base event is listed with its recurrence description.

Why do long lines look correct even though .ics wraps them?

iCalendar folds long property values across multiple lines, continuing them with a leading space or tab. The parser un-folds these first (per RFC 5545) so the original value is reassembled before it is displayed.

ICS / iCal Human-Readable Summary

The ICS / iCal Human-Readable Summary turns a raw .ics (iCalendar) file into a clean, chronological list of events you can actually read. Paste the file contents and every meeting, deadline and reminder is rendered with friendly dates, durations and locations — entirely in your browser.

How it works

iCalendar is a line-based format with a few quirks the parser handles before it can make sense of your events:

Line unfolding — long values are wrapped across lines and continued with a leading space or tab. The parser rejoins them per RFC 5545 first.
Property parsing — each line is split into a name, optional parameters (like TZID or VALUE=DATE) and a value.
Date parsing — DTSTART/DTEND are read as all-day dates (VALUE=DATE), UTC date-times (...Z), or local date-times. UTC values are converted to your local timezone for display.
Text decoding — escaped sequences such as \n, \, and \; are turned back into real line breaks, commas and semicolons.

Events are then sorted by start time and rendered with a computed duration and, where present, a plain-English description of any RRULE.

Example

A VEVENT with DTSTART:20260608T093000Z and DTEND:20260608T094500Z is shown as a 15-minute event starting at your local equivalent of 09:30 UTC, with its location and description listed beneath.

Notes

The tool summarises recurrence rules rather than expanding every occurrence, and it focuses on the fields people actually read. Because parsing is local, you can safely inspect calendars that contain private meeting details.