Sample ICS Files

Sample ICS File Download

Ten iCalendar files for testing calendar imports. Each one isolates a single behaviour, so when an import goes wrong you can tell which rule caused it.

Ten calendar files, one behaviour each

Smallest valid file: one timed event in UTC

One VEVENT with only the required properties plus a start, an end and a title. Use it to confirm an importer accepts the minimum the specification allows.

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Merge JSON Files//Sample ICS Files//EN
CALSCALE:GREGORIAN
BEGIN:VEVENT
UID:single-event-0001@samples.merge-json-files.com
DTSTAMP:20261119T090000Z
DTSTART:20270215T140000Z
DTEND:20270215T150000Z
SUMMARY:Quarterly budget review
END:VEVENT
END:VCALENDAR
UTF-8 ICS

All-day event that spans three days

Dates are written with VALUE=DATE and no time. The end date is 13 March because DTEND is not included in the event, so the calendar should show 10, 11 and 12 March.

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Merge JSON Files//Sample ICS Files//EN
CALSCALE:GREGORIAN
BEGIN:VEVENT
UID:all-day-0002@samples.merge-json-files.com
DTSTAMP:20261119T090000Z
DTSTART;VALUE=DATE:20270310
DTEND;VALUE=DATE:20270313
SUMMARY:Regional sales conference
LOCATION:Harbour Hall\, Pier 4
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR
UTF-8 ICS

Weekly series with a skipped date and a time zone

A class every Tuesday and Thursday at 18:00 New York time for ten sessions, with 11 March removed by EXDATE. The series crosses the 14 March clock change, so the local time must stay at 18:00.

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Merge JSON Files//Sample ICS Files//EN
CALSCALE:GREGORIAN
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:recurring-weekly-0003@samples.merge-json-files.com
DTSTAMP:20261119T090000Z
DTSTART;TZID=America/New_York:20270302T180000
DTEND;TZID=America/New_York:20270302T190000
RRULE:FREQ=WEEKLY;BYDAY=TU,TH;COUNT=10
EXDATE;TZID=America/New_York:20270311T180000
SUMMARY:Evening pottery class
LOCATION:Studio 2
END:VEVENT
END:VCALENDAR
UTF-8 ICS

Two events in two different time zones

One event is defined in New York time and one in Berlin time, each with its own VTIMEZONE block. Both start at 09:00 local, which is 14:00 UTC and 08:00 UTC on those dates.

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Merge JSON Files//Sample ICS Files//EN
CALSCALE:GREGORIAN
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VTIMEZONE
TZID:Europe/Berlin
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:19700329T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:19701025T030000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:tz-newyork-0004@samples.merge-json-files.com
DTSTAMP:20261119T090000Z
DTSTART;TZID=America/New_York:20270120T090000
DTEND;TZID=America/New_York:20270120T093000
SUMMARY:Stand-up with the New York office
END:VEVENT
BEGIN:VEVENT
UID:tz-berlin-0005@samples.merge-json-files.com
DTSTAMP:20261119T090000Z
DTSTART;TZID=Europe/Berlin:20270120T090000
DTEND;TZID=Europe/Berlin:20270120T093000
SUMMARY:Stand-up with the Berlin office
END:VEVENT
END:VCALENDAR
UTF-8 ICS

Event with two reminders

Two VALARM blocks sit inside the event: a pop-up 15 minutes before the start and another one day before. Use it to check whether an importer keeps, changes or drops reminders.

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Merge JSON Files//Sample ICS Files//EN
CALSCALE:GREGORIAN
BEGIN:VEVENT
UID:alarms-0006@samples.merge-json-files.com
DTSTAMP:20261119T090000Z
DTSTART:20270405T083000Z
DURATION:PT45M
SUMMARY:Dentist appointment
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:Dentist appointment in 15 minutes
TRIGGER:-PT15M
END:VALARM
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:Dentist appointment tomorrow
TRIGGER:-P1D
END:VALARM
END:VEVENT
END:VCALENDAR
UTF-8 ICS

Meeting invitation with an organizer and three attendees

METHOD:REQUEST marks the file as an invitation, not a plain export. It carries an organizer, attendees with different roles and reply states, a sequence number and a status.

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Merge JSON Files//Sample ICS Files//EN
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
UID:invite-0007@samples.merge-json-files.com
DTSTAMP:20261119T090000Z
DTSTART:20270518T130000Z
DTEND:20270518T140000Z
SUMMARY:Website redesign kickoff
DESCRIPTION:Agenda: goals\, timeline\, owners.\nPlease read the brief first
 .
LOCATION:Room Aspen / video link in the description
ORGANIZER;CN=Priya Raman:mailto:priya.raman@example.com
ATTENDEE;CN=Tomas Okafor;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED:mailto:toma
 s.okafor@example.com
ATTENDEE;CN=Lena Fischer;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TR
 UE:mailto:lena.fischer@example.com
ATTENDEE;CN=Design Team;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;PARTSTAT=TENTATIV
 E:mailto:design-team@example.com
SEQUENCE:2
STATUS:CONFIRMED
URL:https://example.com/meetings/redesign-kickoff
END:VEVENT
END:VCALENDAR
UTF-8 ICS

Long text, folded lines, escaped characters and non-English text

The description is longer than 75 bytes, so it is folded across several lines. It also contains escaped commas, semicolons, a backslash, line breaks written as \n, and accented, Japanese and emoji characters in UTF-8.

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Merge JSON Files//Sample ICS Files//EN
CALSCALE:GREGORIAN
BEGIN:VEVENT
UID:folded-0008@samples.merge-json-files.com
DTSTAMP:20261119T090000Z
DTSTART:20270622T170000Z
DTEND:20270622T190000Z
SUMMARY:Team dinner: Café Zoë\, 東京 branch 🍜
DESCRIPTION:Menu choices: ramen\, gyoza\; vegetarian option on request.\nBr
 ing the booking code A\\7 and arrive ten minutes early.\nThis line is long
  on purpose so that a parser has to join several folded pieces back into o
 ne value before it reads the text.
LOCATION:Café Zoë\, 12 Rue de l'Église\; second floor
END:VEVENT
END:VCALENDAR
UTF-8 ICS

Birthday that repeats every year

An anniversary-style event: a DATE start, no end, and RRULE:FREQ=YEARLY. With no DTEND the event lasts one day, and it should appear on 9 August every year with no end date.

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Merge JSON Files//Sample ICS Files//EN
CALSCALE:GREGORIAN
BEGIN:VEVENT
UID:birthday-0009@samples.merge-json-files.com
DTSTAMP:20261119T090000Z
DTSTART;VALUE=DATE:20270809
RRULE:FREQ=YEARLY
SUMMARY:Nadia's birthday
TRANSP:TRANSPARENT
CATEGORIES:BIRTHDAY
END:VEVENT
END:VCALENDAR
UTF-8 ICS

A typical exported week: six mixed events

What a real calendar export looks like: timed UTC events, an all-day event, a cancelled event, a tentative one, and one floating event with no time zone that should stay at 07:00 wherever it is opened.

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Merge JSON Files//Sample ICS Files//EN
CALSCALE:GREGORIAN
BEGIN:VEVENT
UID:week-mon-0010@samples.merge-json-files.com
DTSTAMP:20261119T090000Z
DTSTART:20270906T080000Z
DTEND:20270906T083000Z
SUMMARY:Weekly planning
CATEGORIES:WORK
END:VEVENT
BEGIN:VEVENT
UID:week-tue-0011@samples.merge-json-files.com
DTSTAMP:20261119T090000Z
DTSTART:20270907T120000Z
DTEND:20270907T130000Z
SUMMARY:Lunch with Marco
STATUS:TENTATIVE
END:VEVENT
BEGIN:VEVENT
UID:week-wed-0012@samples.merge-json-files.com
DTSTAMP:20261119T090000Z
DTSTART;VALUE=DATE:20270908
DTEND;VALUE=DATE:20270909
SUMMARY:Rent due
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:week-thu-0013@samples.merge-json-files.com
DTSTAMP:20261119T090000Z
DTSTART:20270909T150000Z
DTEND:20270909T160000Z
SUMMARY:Vendor demo
STATUS:CANCELLED
END:VEVENT
BEGIN:VEVENT
UID:week-fri-0014@samples.merge-json-files.com
DTSTAMP:20261119T090000Z
DTSTART:20270910T070000
DTEND:20270910T074500
SUMMARY:Morning run
CATEGORIES:PERSONAL
END:VEVENT
BEGIN:VEVENT
UID:week-sat-0015@samples.merge-json-files.com
DTSTAMP:20261119T090000Z
DTSTART:20270911T180000Z
DTEND:20270911T210000Z
SUMMARY:Film night
LOCATION:Orchard Street Cinema
END:VEVENT
END:VCALENDAR
UTF-8 ICS

Invalid on purpose: event without UID or DTSTAMP

This file breaks the specification: its only event has no UID and no DTSTAMP, which are both required. A strict validator should report two errors. Use it to see how your software handles a bad file.

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Merge JSON Files//Sample ICS Files//EN
CALSCALE:GREGORIAN
BEGIN:VEVENT
DTSTART:20271004T100000Z
DTEND:20271004T110000Z
SUMMARY:Event that is missing its required fields
END:VEVENT
END:VCALENDAR
UTF-8 ICS

Download by Size (10KB - 1MB)

Need a practical file size for load testing? Download generated dummy files near the selected size. Container formats such as XLSX and DOCX may vary slightly because of compression.

10 KB

Small sample for basic testing

100 KB

Medium sample for throughput testing

1 MB

Large sample for benchmark testing

How one calendar event is written, line by line

An ICS file is a list of lines in the form NAME:value, grouped by BEGIN and END markers. This is the smallest sample above, with what each line does. The required parts come from RFC 5545 , the iCalendar specification.

LineWhat it does
BEGIN:VCALENDAROpens the calendar. Everything else sits before the matching END:VCALENDAR.
VERSION:2.0Required. Says the file follows this version of the format.
PRODID:-//Merge JSON Files//Sample ICS Files//ENRequired. Names the product that created the file.
BEGIN:VEVENTOpens one event. A file can hold many of these blocks.
UID:single-event-0001@samples.merge-json-files.comRequired. The event's permanent identifier, which has to be globally unique.
DTSTAMP:20261119T090000ZRequired. When the event information was created or last revised, always in UTC.
DTSTART:20270215T140000ZThe start. Required unless the calendar has a METHOD line, as invitations do.
DTEND:20270215T150000ZThe end, which is not part of the event. DURATION can be used in its place, but never both.
SUMMARY:Quarterly budget reviewThe title a calendar app shows.
END:VEVENT
END:VCALENDAR
Close the event, then the calendar.

Four ways to write a time, and why events land on the wrong hour

Most import bugs are time bugs. The same event can be written four ways, and each one tells the calendar something different.

  • UTC: DTSTART:20270215T140000Z. The trailing Z fixes the moment. Every viewer sees it converted to their own zone.
  • Local time with a zone: DTSTART;TZID=America/New_York:20270302T180000. The event belongs to that zone. The file should also carry a VTIMEZONE block with the same TZID and at least one STANDARD or DAYLIGHT section that gives the offsets.
  • Floating: DTSTART:20270910T070000. No Z and no zone. The event stays at 07:00 on the clock wherever the calendar is opened, which suits a morning run and nothing that involves other people.
  • Date only: DTSTART;VALUE=DATE:20270310. An all-day event with no time at all.

A time with a numeric offset attached, such as 20270215T140000-0800, is not allowed. Test with the two-time-zone sample: both events start at 09:00 local, which is 14:00 UTC in New York and 08:00 UTC in Berlin on 20 January. If your software shows them at the same moment, it is ignoring the TZID.

Recurrence rules worth testing

A repeating event is stored once, with an RRULE line that describes the pattern. EXDATE removes single dates from the series. FREQ can be SECONDLY, MINUTELY, HOURLY, DAILY, WEEKLY, MONTHLY or YEARLY, and a rule may end with COUNT or UNTIL but never both.

RuleRepeats
RRULE:FREQ=WEEKLY;BYDAY=TU,TH;COUNT=10Tuesdays and Thursdays, ten times (the weekly sample)
RRULE:FREQ=YEARLYSame date every year, with no end (the birthday sample)
RRULE:FREQ=DAILY;UNTIL=20271231T000000ZEvery day up to the end of 2027
RRULE:FREQ=WEEKLY;INTERVAL=2Every second week on the start date's weekday
RRULE:FREQ=MONTHLY;BYMONTHDAY=1The first day of every month
RRULE:FREQ=MONTHLY;BYDAY=-1FRThe last Friday of every month

The weekly sample is the one to import first. It should produce nine sessions, from 2 March to 1 April 2027: ten from the rule, minus 11 March. The United States changes its clocks on 14 March 2027, in the middle of the series, and every session should still start at 18:00 New York time.

Folding, escaping and line endings: where importers break

Three rules of the format cause most parsing failures. The folded-lines sample exercises all of them.

Lines are folded at 75 octets

A line should not be longer than 75 octets, not counting the line break. A longer value is split by inserting a line break followed by one space or tab, and a reader joins the pieces by removing that break and the single whitespace character. The limit counts bytes, not characters, so text with accents, Japanese or emoji reaches it sooner.

Commas, semicolons and backslashes are escaped

In text values such as SUMMARY, DESCRIPTION and LOCATION, a comma is written \,, a semicolon \; and a backslash \\. A line break inside the text is written as \n. Colons are left as they are. An importer that skips this step shows stray backslashes in event titles.

Line endings are CRLF

Each line ends with a carriage return and a line feed. Files saved with Unix line endings are accepted by many apps and rejected by strict ones. Every download on this page uses CRLF, including the sized files.

What Google Calendar, Outlook and Apple Calendar do with an imported file

These steps come from each vendor's own help pages.

  • Google Calendar: on a computer, open Settings, choose Import & export, select the file and pick the calendar that receives the events. Google accepts files ending in .ics or .csv, and a zip has to be extracted first. See Google's import guide .
  • Classic Outlook: go to File > Open & Export > Import/Export, choose Import an iCalendar (.ics) or vCalendar file (.vcs), select the file and pick Open as New. The file opens as a separate calendar under Other Calendars. Microsoft describes it as a static snapshot that does not update itself. See Microsoft's instructions .
  • Apple Calendar on Mac: drag the file into Calendar, or choose File > Import, then select the calendar to add the events to. Apple notes that importing removes an event's previous custom colour. See Apple's Calendar guide .

Import into a new, empty calendar when you test. Deleting that calendar afterwards removes every test event in one step.

iCalendar facts from RFC 5545

File extension.ics for calendar data, .ifb for free or busy time
Media typetext/calendar
Character setUTF-8 by default
Line endingCRLF
Line length75 octets recommended maximum, longer lines folded
Required in every calendarPRODID and VERSION, plus at least one component
Required in every eventUID and DTSTAMP, and DTSTART when the calendar has no METHOD
Event status valuesTENTATIVE, CONFIRMED, CANCELLED
Reminder placementA VALARM block must sit inside an event or a to-do
SpecificationRFC 5545, published September 2009, replacing RFC 2445

Reading a sample calendar in Python and Node.js

Both snippets were run against the files on this page. The Python one uses the icalendar package, which is also the parser used to check every sample here.

List the events in the one-week calendar (Python)

from icalendar import Calendar

with open("sample-one-week-calendar-six-events.ics", "rb") as f:
    cal = Calendar.from_ical(f.read())

for event in cal.walk("VEVENT"):
    print(event["DTSTART"].dt, "-", event["SUMMARY"], "-", event.get("STATUS", "no status"))

It prints six lines, one per event, including the cancelled and tentative ones with their status.

Unfold and unescape a long description (Node.js, no packages)

const fs = require("fs");

const text = fs.readFileSync("sample-folded-lines-and-escaped-text.ics", "utf8");

// Unfold: a line break followed by a space or tab continues the previous line.
const lines = text.replace(/\r\n[ \t]/g, "").split("\r\n").filter(Boolean);
const description = lines.find((line) => line.startsWith("DESCRIPTION:")).slice(12);

// Unescape the TEXT value: \n is a line break; \, \; and \\ are literal characters.
const plain = description.replace(/\\n/gi, "\n").replace(/\\([,;\\])/g, "$1");
console.log(plain);

The output is the description as three lines of readable text, with its commas, semicolon and backslash restored.

Questions people ask about ICS test files

What is an ICS file?

An ICS file is a plain text file in the iCalendar format defined by RFC 5545. It holds calendar data such as events, reminders and time zone rules, and its registered media type is text/calendar. Calendar apps use it to move events from one calendar to another.

Can one ICS file contain more than one event?

Yes. A file can hold any number of VEVENT blocks between BEGIN:VCALENDAR and END:VCALENDAR. The one-week sample on this page has six events, and the sized downloads hold from about 60 to about 6,000.

Why does an imported event show at the wrong time?

It depends on how the start time was written. A time ending in Z is UTC and is converted to the viewer's zone. A time with a TZID is fixed to that zone. A time with neither is floating and keeps the same clock time everywhere. An event written as floating when UTC was meant will be off by the viewer's UTC offset.

Why is my all-day event one day too long or too short?

The end of an event is not included in it. A three-day all-day event from 10 to 12 March is written with DTEND set to 13 March. Software that treats the end date as included shows an extra day, and files written with the last day as DTEND lose a day.

What makes an ICS file invalid?

The most common causes are a calendar without PRODID or VERSION, an event without UID or DTSTAMP, an event with both DTEND and DURATION, a recurrence rule with both COUNT and UNTIL, and line endings that are not CRLF. The invalid sample on this page is missing UID and DTSTAMP.

How do I import an ICS file into Google Calendar?

On a computer, open Google Calendar, go to Settings, choose Import and export, select the file and pick the calendar that should receive the events. Google accepts files ending in .ics or .csv. A zip file has to be extracted first and each .ics imported separately.

Can I open an ICS file in a text editor?

Yes. The format is UTF-8 text, one property per line. Long values are folded onto continuation lines that start with a space, so a long description can look broken in an editor even though the file is correct.

What is the difference between .ics and .ifb?

Both extensions are registered for the text/calendar media type. An .ics file carries any calendar and scheduling information, such as events. An .ifb file carries only free or busy time information.

More test files for contacts and calendars