CSV to Calendar File

Turn CSV event rows into a calendar file using UTC, all-day dates or local times with an explicit zone column.

On-device No sign-up Free to use

Create calendar controls

Showing an example. Edit to see your own.

Drop your CSV file here

or choose one from your device

A chosen file replaces the pasted CSV. Up to 20 MiB, 100,000 data rows, 500 columns and 2,000,000 cells including headers.

    ?

    Required headers: summary,start,end. Local mode also requires zone. Optional: uid,location,description. At most 200 events. Blank or absent UID creates a new random identifier.

    ?

    UTC: YYYY-MM-DDTHH:mm:ssZ. Local: YYYY-MM-DDTHH:MM or AM/PM plus a zone column. All-day: YYYY-MM-DD, with the first date outside the event as its end. Years 1970–2100 only.

    ?

    Applies to local CSV mode. Clock-change gaps are refused.

    Processed in your browser. Your inputs stay on this device.

    Result

    Showing an example.

    Convert one UTC planning-meeting row into an ICS event.

    Created one calendar file with 1 finite events.
    1 calendar events
    UID | Title | Start | Exclusive end
    example-one | Planning meeting | 20260105T090000Z | 20260105T100000Z
    events.ics

    Loading the tool. Your result will appear here.

    https://usefreetools.net/csv-to-calendar · 20 November 2026

    Was this helpful?

    How to use CSV to Calendar File

    1. Paste CSV or select a UTF-8 file with summary, start and end headers. Add optional uid, location and description columns as needed.
    2. Choose the separator and event-time format. UTC uses timestamps such as 2026-01-05T09:00:00Z; all-day events use YYYY-MM-DD dates.
    3. For local times, add a zone column containing an IANA location or UTC and choose how a repeated clock time should be resolved. Local timestamps use YYYY-MM-DDTHH:MM or AM/PM form.
    4. Generate the calendar and check each title, start and exclusive end in the result table. All-day ends must name the first date outside the event.
    5. Download events.ics and review the imported events in your calendar application before saving.

    Example: CSV to Calendar File

    Convert one UTC planning-meeting row into an ICS event.

    You add
    Pasted CSV: summary,start,end,uid,location,description Planning meeting,2026-01-05T09:00:00Z,2026-01-05T10:00:00Z,example-one,Room A,Weekly plan; CSV separator: ,; Event times: utc; Repeated local clock policy: earlier
    You get
    Created one calendar file with 1 finite events. 1 calendar events UID | Title | Start | Exclusive end example-one | Planning meeting | 20260105T090000Z | 20260105T100000Z events.ics

    Options

    Time kind
    UTC rows use explicit UTC timestamps. All-day rows use dates and an exclusive end date; changing the selector alone does not convert the source strings.
    UID column
    UID identifies an event. Keep a stable supplied UID when you intend to update the same event in another application, and inspect that application’s import behavior.
    Local event CSV
    Local mode adds a required zone column. Each start and end is resolved to UTC using the selected repeated-clock policy.

    Supported inputs and limits

    • One to 200 events, with dates in years 1970 through 2100.
    • Local mode requires an IANA location or UTC in the zone column; ambiguous abbreviations and skipped local times are refused.
    • All-day end dates are exclusive.
    • No recurrence, invitations or calendar-account connection.
    • Missing or blank UIDs receive new random identifiers each run.

    Where your input is processed

    This tool does not upload your inputs. See the limits for anything saved on your device.

    Keep source rows with the generated file

    The conversion creates the supported finite event records. It does not send invitations or update an account automatically. Check the generated title, start and end values before importing, especially when a spreadsheet has reformatted a date column.

    Questions about CSV to Calendar File

    Why is an all-day end date the following day?

    Calendar end dates are exclusive. A one-day event ends at the start of the next day.

    Can I use a named time zone?

    Yes. Choose local event times and include an IANA zone in the CSV zone column, or use UTC mode for explicit UTC timestamps. The exported timed values use UTC. Repeated local times follow the selected earlier or later policy; nonexistent times are refused.

    Are recurring events created?

    No. Each CSV row creates one finite event.

    Page updated · Project managed by Tony Hines · Report a problem with CSV to Calendar File