Sample ICS calendar file
An iCalendar file with 14 fictional events in December 2026: 12 one-hour meetings, one weekly event that repeats 8 times and one all-day event. Free, no sign-up. Updated 19 November 2026.
What these files are
An iCalendar file with 14 fictional events in December 2026: 12 one-hour meetings, one weekly event that repeats 8 times and one all-day event. Lines end with CRLF as the standard requires.
Every file was generated by our own code, so nothing in them is copied from anyone, and we release them under CC0: use them for anything. The facts in the table were read back from each file after it was written, not typed in by hand.
About the format
iCalendar is defined in RFC 5545. A file starts with BEGIN:VCALENDAR, each event is a VEVENT with a unique UID, and times ending in Z are in UTC. Lines must end with CRLF, and lines longer than 75 bytes are folded by starting the continuation line with a space. RRULE describes a repeating event, for example FREQ=WEEKLY;COUNT=8.
These files open in Google Calendar, Outlook and Apple Calendar. A web server should send them with the header Content-Type: text/calendar.
1 file to download
| File | Size | What it is |
|---|---|---|
| sample-calendar.ics | 3 KB | 14 events in December 2026: 12 one-hour meetings, one weekly repeating event (RRULE, 8 times) and one all-day event events: 14; recurring: 1; crlf: yes |
MIME type: text/calendar. Total 3 KB.
Good for testing
- Calendar import in Google Calendar, Outlook and Apple Calendar
- Recurrence rule (RRULE) expansion
- Time zone handling: times are in UTC
Check a file
grep -c BEGIN:VEVENT sample-calendar.icsCompare the SHA-256 checksum to make sure the download is complete and unchanged (sha256sum file on Linux, shasum -a 256 file on macOS, certutil -hashfile file SHA256 on Windows):
| File | SHA-256 |
|---|---|
| sample-calendar.ics | 9f68dd4e9f9de62fd46187e305c71d45306be5fac15edb677c585d8389444bf5 |