Guide
ICS vs iCal: what is inside the file
An ICS file is plain text that almost every calendar app understands. Knowing its few moving parts helps you publish events that update cleanly instead of duplicating.

Are ICS and iCal the same?
iCalendar is an open standard for exchanging calendar data, defined in RFC 5545. Files usually end in .ics and are served with the media type text/calendar. People often say iCal for the format, although iCal is also the name of one Apple application.
A file is a list of lines in the form NAME:value. Events sit inside a calendar wrapper, between BEGIN:VEVENT and END:VEVENT lines.
How to create an ICS file: a minimal event
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Date Sheet//Example//EN
BEGIN:VEVENT
UID:[email protected]
DTSTAMP:20260105T090000Z
DTSTART;TZID=Europe/London:20260113T190000
DTEND;TZID=Europe/London:20260113T203000
SUMMARY:Choir rehearsal
LOCATION:Community hall
END:VEVENT
END:VCALENDAR
The example is made up. The fields that matter are these.
- UID: a unique, permanent identifier for the event. It must never change for the same event.
- DTSTAMP: when this version of the record was created, in UTC.
- DTSTART and DTEND: start and end, with a time zone.
- SUMMARY and LOCATION: what people read in their calendar.
Three ways to write a time
- Local time with a zone, such as DTSTART;TZID=Europe/London:20260113T190000. Best for events in one place, because it follows daylight saving time.
- UTC, marked by a trailing Z, such as 20260113T190000Z. A fixed instant, good for online events.
- Floating time with no zone. It means the same wall-clock time wherever the viewer is, and is rarely what a public event wants.
All-day events
An all-day event uses a date without a time: DTSTART;VALUE=DATE:20260113. The end date is exclusive, so a one-day event ends on the next day and a two-day event ends on the day after its last day. Getting this off by one is a common reason an all-day event appears to run a day too long.
ICS feed URL or download: do ICS calendars update automatically?
The same file can be used in two ways, and the difference matters for the people who rely on it.
- Download and import: a one-time copy. Later changes on your site do not reach the person.
- Subscribe to a feed: the calendar app keeps the address and fetches it again from time to time. Changes you publish arrive on their own.
Feeds are often offered with a webcal:// link, which opens the subscription dialog in many apps and maps to the normal web address underneath. How often an app refreshes a subscribed feed is decided by the app, not by you, so a change may take hours to appear. Say so near the subscribe button.
Updating and cancelling
To change an event, keep its UID and raise its SEQUENCE number. A new UID looks like a different event and leaves the old one behind, which is the usual cause of duplicates after an update.
To cancel, keep the event in the feed with STATUS:CANCELLED instead of deleting it. Apps then show it as cancelled, and people who saw the original learn what happened. The habit fits the advice in keeping an event calendar updated.
Recurring rules in the file
A recurring event adds one RRULE line, for example RRULE:FREQ=WEEKLY;BYDAY=TU. Skipped dates are listed with EXDATE, and a single moved date is a second event with the same UID and a RECURRENCE-ID that names the original slot. The patterns themselves are covered in recurring events.
Text, line breaks and escaping
Lines end with a carriage return and a line feed. Long lines are folded: the line is broken and the next line starts with a space or a tab. Commas, semicolons and backslashes inside text values are escaped with a backslash, and a line break inside a value is written as \n. Most libraries do this for you, and generating the file with one is safer than assembling strings by hand.
Test before you publish
Open your feed in at least two or three different calendar apps and check start times, the time zone, an all-day event, a recurring event and a cancelled one. A feed that looks right in one app can be read differently in another.