Convert ICS to CSV
Convert ICS to CSV instantly in your browser. Free, fast, and private - your files are processed locally on your device.
Drop your ICS files here
Up to 5MB per file.
Files never leave your browser
How to Convert
- 101
Upload your ICS files
Drag and drop or select ICS files from your device. You can upload multiple files at once.
- 202
Configure Output
Start the conversion. Crest Convert will prepare the CSV file using the appropriate format engine.
- 303
Download CSV files
Once conversion finishes, download your files individually or as a compressed ZIP archive.
Why convert ICS to CSV?
Convert ICS files to CSV locally, with no file upload or account required.
Calendar exports retain stored events, recurrence rules and timezone information. Recurring events are not expanded; choose JSON for the complete calendar structure.
Frequently Asked Questions
Does each recurring appointment become a CSV row?
Each stored event becomes a row; recurrence rules are retained rather than expanded into all future dates. A stored exception is its own row. This avoids producing an enormous spreadsheet for an endless recurring event.
What are the __calendar and __components columns?
They preserve calendar-level settings, timezone definitions and nested alarms for round-tripping through CSV to ICS. They are not extra appointments. Keep them if you want to recreate the calendar.
How do I convert ICS to CSV?
Select a file up to 5 MB, start the conversion, and download the result. Processing runs locally in your browser. Table conversions support up to 20,000 records, 256 columns and 200,000 cells.
Are my files uploaded?
No. This converter processes the file in a local browser worker. File contents are not sent to the conversion server, and the file is not used to train AI.
What happens to recurring events and time zones?
Recurrence rules and exclusions are retained, not expanded into an unbounded list of occurrences. Table output has one row per stored event, including exceptions. Timezone parameters stay in the column headers; __calendar retains calendar and timezone definitions, and __components retains alarms. JSON retains the complete jCal structure, including tasks and journals.
How are data types and spreadsheet safety handled?
Table text is kept as text, including leading zeros. XLSX output uses text cells rather than executable formulas. CSV/TSV fields beginning with formula-like characters receive a leading apostrophe for spreadsheet safety; choose XLSX or JSON if you need exact literal values. Nested table values use JSON text rather than ambiguous flattened field names.