ICS Calendar Event Generator
Make an .ics calendar file for one event — timed or all-day, time zone or UTC, location, organiser, reminder, repeat — for Google, Outlook and Apple Calendar.
A downloadable RFC 5545 file with a stable UID, escaped text and folded lines, plus the file content to copy, the duration, the recurrence rule and notes on floating times and zones.
Example: "Team sync" 5 Oct 2026 09:30–10:00 Asia/Jakarta, 15-minute reminder, every Monday and Wednesday ten times → DTSTART;TZID=Asia/Jakarta:20261005T093000 and RRULE:FREQ=WEEKLY;BYDAY=MO,WE;COUNT=10.
One VEVENT,
written the way calendars read it.
What goes into the file, how times and zones are written, and how repeats and reminders work.
The file
An iCalendar file (RFC 5545) is plain text: a VCALENDAR wrapper with a VEVENT holding a unique UID, a DTSTAMP, the start and end, and the properties you filled — SUMMARY, LOCATION, DESCRIPTION, URL, ORGANIZER. Special characters in text are escaped (\; \, \n) and lines longer than 75 octets are folded onto continuation lines, both required by the standard. Importing a file with the same UID again updates the event in most calendars instead of duplicating it — keep the UID when you edit.
Dates, times and zones
An all-day event uses DATE values with an exclusive end (the day after). A timed event with an IANA zone (Asia/Jakarta, Europe/London) is written as DTSTART;TZID=…; current calendar applications resolve the zone themselves, so no VTIMEZONE block is embedded. "UTC" writes the Z form. With no zone the time is floating — the same clock time everywhere — which is right for a local reminder and wrong for a call across zones.
Repeats and reminders
RRULE carries the frequency, an interval, BYDAY for weekly rules and either COUNT or UNTIL (an open rule repeats forever, and the page says so). The reminder is a VALARM with a DISPLAY action N minutes before the start. The generated file is built in the browser and downloaded; nothing is sent to any service. Nothing leaves the browser; the same four anonymous usage counts as the rest of the site apply.
SOURCES
- RFC 5545 iCalendar: VCALENDAR / VEVENT with UID, DTSTAMP, DTSTART/DTEND (TZID, Z or VALUE=DATE), SUMMARY, LOCATION, DESCRIPTION, URL, ORGANIZER, RRULE, VALARM; text escaping §3.3.11, line folding §3.1
Last reviewed 22 September 2026. How results are checked: How we verify.