Choose an ICS file
Open an UTF-8 iCalendar 2.0 .ics file up to 2 MB.
Make calendar files easy to inspect.
ICS to CSV
Export iCalendar events to CSV with separate date kind, TZID, start, end, duration, location, organizer and recurrence rule columns.
The CSV contains event definitions, not an expanded recurrence schedule. Formula-like calendar text is safely prefixed.
ICS Calendar ViewerYOUR WORKSPACE
Your task
Download CSV
Choose a file, then use Download CSV to save the result.
Also with this file: View events · Download Excel · Download JSON
Processed privately in your browserNo uploadNo signup
A simple workflow
Three steps. One less thing to do.
Review event definitions
Inspect titles, dates, timezone identifiers, recurrence rules and descriptions.
Save the event table
Download CSV, Excel or JSON from the same locally parsed calendar.
Made for the everyday
A useful part of your workflow.
Invite inspection
Read a calendar export before importing it into another application.
Event inventory
Create a spreadsheet of event definitions with dates and timezone context.
Calendar integration
Export structured JSON without expanding recurring events incorrectly.
Good to know
A few useful answers.
The details that matter before you use ICS Calendar Viewer.
Which calendar format is supported?
This viewer reads UTF-8 iCalendar 2.0 files with VEVENT entries. Other component types are ignored rather than presented as events.
Are recurring events expanded?
No. RRULE is preserved as metadata in the viewer and downloads. The tool does not invent an unbounded occurrence series.
Do you convert timezones?
No. Date-only, floating local and UTC values stay distinct. TZID values are retained without changing the wall time.
Will the tool load event links or attachments?
No. URL and ATTACH properties are not fetched or opened automatically.
What do CSV and Excel contain?
One row represents one event definition, including recurrence metadata. Excel stores values as text; CSV protects formula-like strings.
What are the limits?
The local parser accepts up to 2 MB, 5,000 events, 50,000 content lines and 16 nested components.
Do calendar details leave this browser?
No. Parsing and exports are local. Event text, filenames and calendar contents are excluded from analytics.