ICS to CSV converter for calendar records

Convert calendar event files with explicit field mapping and retained recurrence records. Your file stays in your browser.

Calendar records

Input format

UTF-8 text, up to 2 MB and 500 event records.

2 records ready

CSV file

2 calendar records converted to CSV.

Mapped event preview

Event source values
EventStartEndTime zone
Campaign day2026100420261005All-day date
Staff briefing20261003T09000020261003T093000Australia/Sydney

Preview shows the first 10 records. Downloads contain every included record.

Conversion report

  • Recurrence rules, exception dates and changed occurrences are retained as records. Rules are not expanded or evaluated.
  • Dates and stated time zones are preserved. The converter does not translate clock times or resolve daylight-saving gaps.

Map events and time zones

This ICS to CSV converter keeps each calendar event as a record with its identifier and stated start and end values. Use CSV to ICS to map spreadsheet columns back to calendar records.

For CSV input, enter one calendar field and source header per mapping line, such as summary=Event title. Remove mappings for absent optional columns. The required fields are uid, summary and start.

The complete field names are uid, summary, start, end, zone, end_zone, recurrence, duration, description, location, status and timezones. Headers are case-sensitive. Extra CSV columns appear in the report and are omitted.

Use ISO dates such as 2026-10-04, compact calendar dates such as 20261004 or date-time values such as 20261003T090000. A date-only event is all-day. Its end date is exclusive, so an end on the following day means one full day.

A time ending in Z is UTC. A local clock time with a named zone, such as Australia/Sydney, keeps that identifier in the zone column. Use end_zone for the end time’s zone.

A floating time has no fixed time zone. Write floating in its zone column to confirm that meaning. An empty zone remains unresolved until you choose how to handle it.

The converter preserves clock values without shifting them between zones. It retains embedded VTIMEZONE definitions in the timezones column. It does not calculate offsets or validate daylight-saving gaps and overlaps.

For the field definitions and exclusive end rule, read the iCalendar specification.

Handle recurrence without losing meaning

Recurring events retain their rules. The converter keeps RRULE, RDATE, EXDATE and RECURRENCE-ID content lines together in the recurrence column, including their time-zone parameters.

One record describes a repeating series. A changed occurrence remains a separate record with the same UID and its own RECURRENCE-ID. Excluded dates stay in EXDATE.

The converter never expands recurrence into individual dates. It retains rules it does not evaluate, including monthly and yearly rules. The report states that these rules remain unevaluated.

Clear Include recurring records to exclude the whole series and all records with its identifier. The report counts those exclusions. A series never becomes a single occurrence through this choice.

Event descriptions, locations and status are supported. DURATION is accepted when there is no end value. Alarms, attendees, attachments and other event properties are omitted and named in the report.

Property parameters outside the supported date and recurrence fields are also reported when omitted. The original DTSTAMP and calendar-level scheduling properties are not preserved. Keep the original file when you need a complete archive.

Check the converted file

The fictional example contains Campaign day, an all-day event starting 4 Oct 2026 and ending exclusively on 5 Oct. ICS to CSV produces start 20261004 and end 20261005.

Staff briefing starts at 9 am in Australia/Sydney on 3 Oct 2026 and lasts 30 minutes. Its daily rule requests three occurrences, with the second excluded.

The briefing’s local time stays at 9 am across Sydney’s daylight-saving change. The converter keeps the zone and exception records without calculating occurrence dates or UTC offsets.

Switch the example to CSV to ICS. The all-day event returns with VALUE=DATE, while the briefing returns with TZID=Australia/Sydney. Its recurrence rule and excluded date remain attached.

Before importing into a working calendar, review every omission in the report. Import into a separate test calendar first, then inspect the all-day span and a timed event around any daylight-saving change.

Check changed and cancelled occurrences as well as the series. Matching identifiers can update existing events in some importers. Keep a backup and confirm the destination calendar before importing.

CSV quotes protect commas and line breaks under the CSV format rules. Quoting does not prevent spreadsheet formulas. Import unfamiliar CSV columns as text to avoid evaluating their contents.

Conversion runs locally and creates a file. Calendar account access, account synchronisation and live booking updates are separate operations.