
iCalendar Event
An iCalendar (.ics) file with a single event and CRLF line endings per spec — for testing calendar imports.
- File
- ICS · Calendar Contacts · UTF-8
- Use case
- Calendar parsing
iCalendar (.ics) files with events, timezones, and recurrence — for testing calendar imports and parsers.

An iCalendar (.ics) file with a single event and CRLF line endings per spec — for testing calendar imports.

A weekly five-occurrence series that provides the recurrence baseline before exclusions or additions are applied.

The same weekly series with its third occurrence excluded, for testing RRULE expansion followed by EXDATE filtering.

A recurrence set with both an exclusion and an explicit addition, useful for catching expansion engines that apply only one modifier.

A TZID-qualified event immediately after Toronto's spring-forward boundary, with an explicit VTIMEZONE definition.

The UTC representation of the Toronto event, providing an exact normalization target for calendar importers.

A floating-time variant with no TZID or Z suffix, for verifying that parsers do not silently reinterpret local wall time as UTC.

The invitation that starts a scheduling lifecycle, using stable UID and organizer/attendee identities.

An attendee acceptance for the same meeting, used to test UID correlation and PARTSTAT state updates.

The terminal cancellation for the scheduling group, checking METHOD, STATUS, UID and sequence precedence together.

A standards-conforming event with a folded content line and UTF-8 text for baseline parser and line-unfolding tests.

A complete iCalendar structure using LF-only line endings, a common recoverable export defect for tolerant parser tests.

An intentionally corrupt iCalendar file whose VEVENT is never closed, for testing fatal component-nesting errors without using a large or hostile payload.
We use Google Analytics and show ads via Adsterra. Non-essential cookies and ad scripts run only after you allow the matching categories. See our cookie policy.