ICS to CSV / XLSX / PDF
Convert iCalendar (.ics) events & schedules into tables or PDF — 100% private client-side processing.
Active Converter
ICS to Excel / CSV / PDF: Extracting VEVENT Schedules from Google, Apple & Outlook Calendars
Technical Anatomy of iCalendar (.ICS) Files
The iCalendar format (.ics), defined by RFC 5545, is the backbone of cross-platform scheduling. Every .ics document is wrapped in a BEGIN:VCALENDAR ... END:VCALENDAR root container that holds timezone definitions (VTIMEZONE) and individual schedule entries (VEVENT), tasks (VTODO), or journal notes.
Inside each VEVENT block, properties follow the syntax NAME;PARAM=VALUE:CONTENT. Timestamps appear in basic ISO 8601 format—either UTC Zulu time (20261120T090000Z), local floating time, or timezone-qualified (DTSTART;TZID=America/New_York:20261120T090000). Long descriptions exceeding 75 octets are folded onto continuation lines prefixed with a single space or horizontal tab. Converting .ics to Excel flattens every VEVENT into a structured row with Title, Start, End, Location, and Description columns.
Raw RFC 5545 .ICS Input vs. Structured Spreadsheet Output
# Input: Calendar Export (q4_schedule.ics)
BEGIN:VCALENDAR
VERSION:2.0
BEGIN:VEVENT
SUMMARY:Client Architecture Review
DTSTART:20261124T140000Z
DTEND:20261124T153000Z
LOCATION:Google Meet
DESCRIPTION:Review Q4 database migration milestones.
END:VEVENT
END:VCALENDAR
# Converted Excel / CSV Output:
Summary,Start,End,Location,Description
"Client Architecture Review","20261124T140000Z","20261124T153000Z","Google Meet","Review Q4 database migration milestones."
Real-World Software & Hardware Ecosystem
Consultants, university registrars, Airbnb/Booking.com hosts, and project managers regularly export .ics feeds from Google Calendar, Microsoft Outlook / Exchange, Apple Calendar (iCal), Calendly, Airbnb, and Jira. Turning an .ics feed into Excel or PDF makes it effortless to reconcile freelance billable hours, audit vacation rental occupancy, or print semester exam timetables.
Troubleshooting & Edge Cases
- All-Day Events Using VALUE=DATE: All-day bookings omit hours and minutes (e.g.,
DTSTART;VALUE=DATE:20261201) and setDTENDto the following day as an exclusive bound per RFC 5545. - UTC vs. Local Timezone Offsets: Timestamps ending in
Zare stored in Coordinated Universal Time (UTC). Adjust for your local timezone offset in Excel if you are summing daily work shifts. - Canceled Events (STATUS:CANCELLED): Exported calendars sometimes retain declined or canceled meetings; use our Interactive Table search to filter them out before exporting your final billing spreadsheet.
RFC 5545 VEVENT Property Reference Table
| iCalendar Property | Example Value | Excel / Timesheet Mapping |
|---|---|---|
| SUMMARY | Q4 Architecture Review | Project / Client Title column |
| DTSTART / DTEND | 20261124T140000Z | Start & End timestamps for duration math |
| LOCATION | Google Meet / Room 4B | Venue or video-call link column |
| RRULE | FREQ=WEEKLY;BYDAY=MO | Recurrence rule for repeating series |
Calculating Billable Hours from Exported .ICS Timestamps in Excel
Once your Google Calendar or Outlook .ics schedule is exported to .XLSX, freelancers and agencies can parse basic ISO timestamps (YYYYMMDDTHHMMSSZ) into real Excel duration hours with one clean formula:
# Convert Start (B2) & End (C2) ISO strings to decimal hours in Excel:
=(TIME(MID(C2,10,2),MID(C2,12,2),0)-TIME(MID(B2,10,2),MID(B2,12,2),0))*24
Frequently Asked Questions
An iCalendar (.ics) file follows RFC 5545, nesting each appointment inside BEGIN:VEVENT and END:VEVENT markers. Our parser extracts SUMMARY, DTSTART, DTEND, LOCATION, and DESCRIPTION fields, unfolding RFC-wrapped 75-byte lines so long meeting notes stay intact in one Excel cell.
Yes. Export your calendar as an .ics archive from Google Calendar Settings or Outlook, convert it to .XLSX here, and use Excel formulas to subtract Start Time from End Time for client billing or timesheet audits.
In RFC 5545, a recurring series is stored as a single master VEVENT with an RRULE string (such as FREQ=WEEKLY;BYDAY=MO,WE). The exported table preserves the master event and its metadata cleanly without infinitely looping.
RFC 5545 mandates backslash-escaping commas, semicolons, and literal newlines inside TEXT properties so parsers do not confuse them with parameter delimiters. Our converter unescapes these sequences into clean, readable prose.