Calendar event file builder
Download one non-recurring UTC or all-day iCalendar event.
Your inputs
Your results
Ready when you areYour results will appear here.
How it works
Create a portable iCalendar file for one non-recurring event. Text is escaped and long lines are folded at UTF-8 octet boundaries. A unique identifier and creation timestamp are generated locally.
Read the source reference ↗A few things to know
No named timezones, recurrence, attendees, RSVP, reminders or delivered invitations. Enter UTC explicitly for timed events. All-day end is exclusive. Calendar-client imports must be checked independently; no blanket compatibility guarantee.
When to use this tool
An iCalendar file describes an event that you can import into a calendar application. It is not a sent invitation or a connection to your account. Choose explicitly entered UTC timestamps for a timed event, or calendar dates for an all-day event. The all-day end is exclusive: a one-day event ends on the next date. Text is escaped and folded at UTF-8 byte boundaries, and each generation receives a local unique identifier and creation timestamp. Import the file in your actual client and inspect its dates before sharing it.
- Prepare a single workshop event download.
- Describe an all-day event with an exclusive end date.
- Create a calendar file without granting calendar-account access.
How to use calendar event file builder
Describe the event
Enter a title, description and location or meeting URL as text. The URL is not fetched and no attendee list is created.
Choose dates deliberately
Timed mode accepts YYYY-MM-DDTHH:mm:ssZ only. All-day mode accepts YYYY-MM-DD; its end date must be later and is exclusive.
Download and test the import
Save event.ics and open it in the intended calendar application. Review local display, date span and description before sending the file yourself.
One hour in explicitly entered UTC
Inputs
Small Hours workshop, 2026-10-15T14:00:00Z through 2026-10-15T15:00:00Z, location Online.
Result
The file contains one VEVENT with UTC DTSTART 20261015T140000Z, DTEND 20261015T150000Z, a generated UID and DTSTAMP.
What it means
The receiving client may display local time. No invitation has been delivered by generating this file.
Common mistakes to avoid
Using a local time without conversion
A trailing Z means UTC. This builder does not infer your timezone or resolve ambiguous local times.
Including the last all-day date as the end
The end is exclusive. A one-day event needs the following date as its end.
Assuming download means delivery
Import or distribute the file yourself. The tool does not contact calendar services or attendees.
Frequently asked questions
Definitions, edge cases, and practical next steps for this tool. Search all tool FAQs ↗
What does UTC mode accept?
An explicit UTC timestamp with seconds and Z, such as 2026-10-15T14:00:00Z. Named zones and offset timestamps are outside this version.
How do I create a one-day all-day event?
Use its date as start and the following date as exclusive end. A start of 2026-10-15 and end of 2026-10-16 describes one all-day date.
Why is the end exclusive?
That is the iCalendar end boundary convention used here. A multi-day event includes dates before the end, rather than adding the end date itself.
Are special characters safe in the file?
Commas, semicolons, backslashes and newlines are escaped as text. Long content lines are folded without splitting UTF-8 characters.
What are UID and DTSTAMP?
UID identifies this generated event; DTSTAMP records generation time. A new generation has a new UID, so repeated imports may create separate events.
Can I send invitations or collect RSVPs?
No. This creates a file only. It has no attendee tracking, email sending, invitation delivery or account connection.
Can it create recurring events or reminders?
Not in this version. It exports one non-recurring event without recurrence rules or alarms.
Is every calendar client guaranteed to import it correctly?
No blanket compatibility claim is made. Test independently in the client you will use, including its timezone display and all-day span.
Sources and method
Use the references below to check definitions and platform guidance. The model’s scope and limits are explained above. Read our editorial standards.