ICS to CSV
Convert iCalendar events to CSV or JSON. DTSTART and DTEND retain their raw values alongside best-effort ISO text; TZID values are labels only, with no timezone database conversion. RRULE values are preserved but recurrences are not expanded.
About ICS to CSV
ICS to CSV turns a calendar export — the .ics file you get from Google Calendar, Outlook, or Apple Calendar — into a spreadsheet-ready CSV or JSON table of events with start, end, title, location, and description columns. It's the missing step between 'my calendar has the data' and 'I need it in Excel'. Parsing happens in your browser, so your schedule stays private.
- Category
- convert
- Input
- Accepts: text/calendar.
- Output
- Outputs: text/csv.
- Cost
- Free, runs in your browser
- Memory
- low
Common uses
- Export Google Calendar events into Excel for timesheet or billing reconciliation
- Turn a shared team calendar into a spreadsheet for planning
- Archive a year of appointments as a readable table
- Analyze meeting load by converting your calendar to CSV and sorting it
- Migrate events into a system that imports CSV
Frequently asked questions
What columns does the CSV have?
start, end, summary (title), location, description, status, all_day, rrule (the raw recurrence rule), and uid — one row per event.
How are recurring events handled?
The recurrence rule is included as its raw RRULE text in its own column, but occurrences are not expanded into separate rows. You get one row per defined event.
How are time zones handled?
Times are output with a best-effort ISO form alongside the raw calendar value. Complex time-zone rules aren't recalculated — for cross-timezone precision, check the raw value.
Can I get JSON instead of CSV?
Yes — switch the format parameter to JSON for the same event fields as structured data.
Is my calendar uploaded?
No. The .ics file is parsed entirely in your browser.
Keywords
- ics
- icalendar
- calendar
- event
- csv
- json
- convert
- export
- rrule