What Is an ICS File? Anatomy of the Calendar Format

The short answer

An ICS file is a plain-text file written in the iCalendar format. The official name of the format is iCalendar. The usual file extension is .ics. People also say "iCal file," leftover from Apple's old iCal app. Those three names — ICS, iCal, iCalendar — are the same object. The current specification is RFC 5545. The MIME type on the wire is text/calendar.

Google Calendar, Apple Calendar and Microsoft Outlook all read and write this format. That is why it became the default way to move events between apps that otherwise do not talk to each other. A meeting you accept in Gmail, a holiday calendar you subscribe to, a shift roster your workplace emails as an attachment: they are almost always the same kind of file.

You will meet an ICS file in a few everyday shapes:

• A single meeting invitation attached to an email — often named invite.ics — and often carrying METHOD:REQUEST so the calendar app can show Accept / Decline.
• A class timetable, conference agenda or public-holiday list published as a downloadable .ics that you import once or subscribe to.
• A whole calendar export — every event on one Google, Outlook or Apple calendar, packed into a single file. Google's own export is a zip that contains one .ics per calendar.

It is not a spreadsheet, not a PDF, and not a program. Open it in any text editor and you will see labeled lines: BEGIN:VCALENDAR, then one or more BEGIN:VEVENT blocks, then the matching END lines. That is the entire format: a nest of components, each made of property lines with a name, an optional parameter, a colon, and a value.

If you already know you want to write one from scratch — required fields, all-day dates, recurrence, escaping — that is a different job. Use how to create an ICS file. This page stays on the definition and the routing table: what you are looking at, how to open it, and which tool on this site matches the next step.

Anatomy of an ICS file

The file is a VCALENDAR envelope. Inside the envelope sit one or more VEVENT blocks (and, in more complete files, a VTIMEZONE block that defines daylight-saving rules). Inside each VEVENT sit property lines. Nothing is binary. Nothing is compressed. A ten-line file is a complete, legal calendar.

Here is a real, minimal example — one event, UTC times, nothing decorative:

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//csvtoics.app//ics-explained//EN
BEGIN:VEVENT
UID:pta-20260910@example.com
DTSTAMP:20260819T180000Z
DTSTART:20260910T230000Z
DTEND:20260911T000000Z
SUMMARY:Parent-teacher conference
END:VEVENT
END:VCALENDAR

That file is valid RFC 5545. The calendar itself has to declare VERSION:2.0 and a PRODID that names the software that wrote it. Each event has to carry a UID (a globally unique id so later updates can find the same event), a DTSTAMP (when this copy of the event was generated, always in UTC) and a DTSTART (when the event begins). DTEND and SUMMARY are optional in the spec, but an event without a title or an end time is rarely what anyone meant to send.

The properties you will actually care about, said in one sentence each:

A file can also carry VTODO (tasks), VJOURNAL (notes) and VFREEBUSY (availability). In the files people actually email and export, you almost never see those. VEVENT is the component that arrives as an invite or a calendar backup.

If you want to write one of these yourself — including the escaping, line-folding and exclusive-DTEND rules that break hand-typed files — go to how to create an ICS file. The example above is here so you can recognize the shape, not so you copy-paste a template.

How to open an ICS file

"Open" is the word that causes the trouble. Double-clicking an .ics file does not show you the text. On every major desktop and phone it imports the events into the default calendar app.

• Windows: Outlook, or the built-in Calendar app, swallows the file and adds the events.
• macOS: Calendar.app offers to add them to a calendar you pick.
• iPhone and iPad:tapping an attachment walks you toward adding it to Calendar. There is no built-in "just look."
• Android: the same, usually through Google Calendar.

That is convenient when you already trust the file. It is the wrong first move when you do not. An unexpected invite.ics can be one meeting or three hundred duplicated events, and reversing a calendar import is tedious on every platform.

Any text editor will show you the raw lines: Notepad, TextEdit (switch to Format → Make Plain Text first), VS Code, nano. That is enough to confirm "this is iCalendar text" and to read a title or two. It is a poor way to read a 400-event export, and a worse way to check whether the dates survived a timezone conversion.

If you want to see the events as a readable list without importing them, use the ICS viewer. It groups events by date, shows all-day and repeating badges, and never touches the calendar already on your device. The file is parsed in your browser; it is not uploaded.

If you want to change titles, dates, times or locations and then download a new .ics, use the ICS editor. That edits the file itself, not the calendar it came from and not the calendar it might go into. You only import the downloaded copy if you decide to.

ICS vs CSV — which one when

ICS is the language calendar apps speak to each other. CSV is the language spreadsheets speak. They hold overlapping facts — a title, a start, an end, a place — but they are built for different next steps.

Stay in ICS when the events still need to live in a calendar:

• you are sending a schedule to Google Calendar, Apple Calendar or Outlook
• you are publishing a timetable that people will import or subscribe to
• the events repeat, and the recurrence rule has to travel with them (CSV has no standard RRULE column)

Step into CSV when the events become data:

• you want to sort, filter, count or bulk-edit in Excel or Google Sheets
• you are cleaning a messy export before converting it back
• you are building a new calendar from a list you already keep as a table

Both directions exist here. The ICS to CSV converter turns a calendar file into a spreadsheet with one row per event. The CSV to ICS converter on the home page turns a table back into a calendar file. If the table is still an Excel workbook, use the Excel to ICS path instead of exporting to CSV first.

A practical rule: if the next person to touch the file is a calendar app, send ICS. If the next person to touch it is you, in a grid, send CSV.

Common ICS questions from real files

A few things that surprise people the first time they open a file from the wild:

• Google's export is a zip.Settings → Import & export → Export does not download a single .ics. It downloads a zip, and inside that zip is one .icsper calendar. Unzip it, then open the file that matches the calendar you actually wanted. Some Outlook "export calendar" paths wrap the result the same way.
• One file can hold thousands of events.There is no "one event per file" rule. A year of a busy work calendar is still one VCALENDAR with a long list of VEVENT blocks. The viewer and the editor on this site are built for that size; tens of thousands of events will make a page of cards sluggish, but a typical personal or team export is fine.
• METHOD:REQUEST vs METHOD:PUBLISH. REQUESTmeans "this is an invitation — please accept or decline." PUBLISHmeans "here is a published schedule, not a request for a reply." Invitation attachments from Outlook and Gmail are usually REQUEST. Consumer calendar exports are usually PUBLISH, or they omit METHOD entirely.
• The text is supposed to be UTF-8. Emoji in titles, accented names and CJK locations are all legal. If a file looks garbled in a text editor, the writer used a different encoding — the events will look garbled after import too. That is worth knowing before you add them to a calendar.

None of this requires you to write a file by hand. When you do need to produce one, convert a spreadsheet or follow the how-to.

ICS files — frequently asked questions