01
Choose an ICS file
Select one calendar file up to 5 MB. It is read locally in your browser.
Convert calendar events to CSV without shifting original event times.
Up to 5 MB · Event times stay in their original local clock time
Data handling
Advertising and analytics are separate site services. We do not send selected tool input to them. Read the Privacy Policy for details.
How it works
01
Select one calendar file up to 5 MB. It is read locally in your browser.
02
Keep source events as they are, or expand supported repeating events into separate CSV rows.
03
See source records that need review before exporting readable events with their original clock times.
Example
If an ICS file contains DTSTART:20260617T090000, the CSV keeps the event's start time as 09:00. When you expand a supported repeating rule, each occurrence keeps that same local clock time instead of being shifted to another hour.
Questions
No. A floating event time such as 09:00 stays 09:00 in the CSV. Timezone, all-day, and recurrence details are exported separately instead of silently converting the event time.
Yes. Turn on recurrence expansion to create a row for each supported daily, weekly, monthly, or yearly occurrence. The original RRULE is kept in every row so the source rule remains visible.
A malformed VEVENT, EXDATE exception, or unsupported recurrence is reported with its UID when available and stays as one source event. Other readable events can still be downloaded.
Keep working
Normalize known Windows timezone labels in an ICS file without shifting event times or deleting recurrence rules.
Open tool →Validate calendar rows and download a Google Calendar-ready CSV or one-time ICS file without guessing dates.
Open tool →Convert CSV to JSON or JSON objects to CSV locally with validation and spreadsheet-safe output.
Open tool →