How to convert ICS to CSV
An ICS file is a text file that holds calendar events between BEGIN:VEVENT and END:VEVENT lines. A CSV is a table. To convert ics to csv, the tool reads every event and writes one row with the title, start, end, duration in hours, location, description, organizer, attendees, status, categories and ID.
Calendars show where you are and who you meet, so the file never leaves your computer. The conversion runs in your browser, as the Privacy Policy explains.
Total hours and billable time
The status line above the result shows the event count and the sum of all timed events in hours, such as 12 events · 19.25 hours total. The Duration (hours) column holds each event as a decimal, 1.5 for an hour and a half, so a spreadsheet can sum it. Use the date range to total one week or one month, and the keyword to total one client.
All-day events have no hours. Their Duration cell is empty and they are left out of the total. Cancelled events are still exported with their status, so filter on the Status column if you need to remove them.
Repeating events and RRULE
A weekly meeting is stored once with a rule such as FREQ=WEEKLY;BYDAY=MO,WE;COUNT=6. With Expand into rows on, the tool writes one row for each occurrence. It supports daily, weekly, monthly and yearly rules with INTERVAL, COUNT, UNTIL, BYDAY (including the second Tuesday or the last Friday), BYMONTHDAY and BYMONTH.
- Dates excluded with EXDATE are removed from the rows.
- A changed single instance of a repeating event replaces the original occurrence.
- A rule with no end stops at the end of the date range, or 12 months after today when there is no range.
- Rules that use BYSETPOS, BYWEEKNO, BYYEARDAY or time parts, yearly rules with BYDAY or BYMONTHDAY and no BYMONTH, and hourly rules, are not expanded. The first occurrence is listed and the notes say so.
List once keeps one row per event and writes the rule text in the Repeats column.
Time zones
Each time in a calendar file is one of three kinds: UTC (a Z at the end), local to a named zone (TZID) or floating, with no zone at all. As written leaves every time as it appears in the file. UTC and This browser convert the times that have a zone and apply daylight saving correctly, so a 09:00 meeting in Berlin becomes 08:00 UTC in winter and 07:00 UTC in summer.
Outlook writes Windows names such as W. Europe Standard Time. The tool knows the common ones and maps them to the standard names. A zone name it does not know is reported, and those times are used as written. Floating times and all-day events are never shifted, because they have no zone to shift from.
A worked example
A weekly Monday and Wednesday meeting in Berlin, six occurrences, with the second Wednesday excluded:
BEGIN:VEVENT
DTSTART;TZID=Europe/Berlin:20261102T090000
DTEND;TZID=Europe/Berlin:20261102T103000
RRULE:FREQ=WEEKLY;BYDAY=MO,WE;COUNT=6
EXDATE;TZID=Europe/Berlin:20261104T090000
SUMMARY:Team sync
END:VEVENTIt becomes five rows, because six occurrences minus one excluded date is five:
Summary,Start,End,Duration (hours)
Team sync,2026-11-02 09:00,2026-11-02 10:30,1.5
Team sync,2026-11-09 09:00,2026-11-09 10:30,1.5
Team sync,2026-11-11 09:00,2026-11-11 10:30,1.5
Team sync,2026-11-16 09:00,2026-11-16 10:30,1.5
Team sync,2026-11-18 09:00,2026-11-18 10:30,1.5Google Calendar, Outlook and Apple Calendar files
Google Calendar exports a .ics file under Settings, Import and export. Outlook can save a calendar as an iCalendar file, and Apple Calendar exports through File, Export. Several calendars in one pasted file are fine, and every event becomes a row. A subscription URL cannot be read here, because a web page cannot fetch it. Download the file first.
To go the other way and build calendar events from a spreadsheet, use CSV to ICS. If the CSV needs merging with others first, Merge CSV Files does that, and CSV to Markdown turns the rows into a table for a document.
Limits
Only events become rows. To-dos, journal entries and free/busy blocks are named in the notes and left out. Extra dates added with RDATE are not added. Text that begins with =, +, -, @ or a tab gets a ' in front so Excel does not run it as a formula. A very large calendar is cut at 100,000 rows, and one event never produces more than 10,000.