ICS File Generator for One Downloadable Event
An ICS file generator turns an event title, start and end into an iCalendar VEVENT that a calendar app can import, with the time written in UTC so it lands at the same instant everywhere.
One event per file. Times are written in UTC, so each calendar shows one instant. Up to 200 characters for the title. Re-importing an existing .ics file is a different job and is not supported here.
This page does not check whether the file imports into your calendar. Open the downloaded file once before you send it.
Files and pasted text are read in this page; nothing is uploaded and no account is needed. This page also loads analytics scripts, so avoid confidential text. The event text is assembled in this page and is not sent anywhere; the download writes it to a file on your device.
Calendar file
Next: count days between two dates, convert a Unix timestamp, or run a countdown. None of them writes a calendar file.
Why make an .ics file instead of a link?
A file the reader keeps
An add-to-calendar link opens a service in a browser tab and depends on that service. A downloaded file belongs to the reader, imports into whichever app they already use, and survives the sender site going away.
One instant, not one clock
Times are written in UTC, so a meeting does not drift when the file crosses a time zone or a daylight saving change. The wall time you typed is converted once, and the conversion is shown.
No account, no parser
The fields are explicit, so nothing guesses a date out of prose and no sign-in stands between you and the download. What you typed is what the file contains.
How an .ics file is built
An .ics file is an iCalendar object as defined by RFC 5545. It opens with BEGIN:VCALENDAR, declares its version and product identifier, then holds one VEVENT with a start, an end, a summary and a unique identifier. Each line is one property, and the calendar app reads the properties it knows. Because the format is a plain text standard rather than one vendor export, a file that follows it is what calendar apps are built to read. This page does not record an import test, so open your own copy once before you rely on it for anyone else.
Two rules make the difference between a file that imports cleanly and one that arrives mangled. Text values escape a comma, a semicolon, a backslash and a line break with a backslash, so a title containing a comma is not read as a list. Lines longer than 75 octets are folded with a carriage return, a line feed and one space, and the app unfolds them on import. Both rules are applied to every text field here, and the generated file is shown before you download it.
Time zones, escaping and file rules
- Start and endTimed events write DTSTART and DTEND in UTC with a trailing Z. All-day events write a date only, with VALUE=DATE, and no clock time.
- Daylight saving gapA wall time that the clock skipped, such as 02:30 on a spring-forward morning, is refused with an explanation instead of being moved to a nearby hour.
- Daylight saving overlapA wall time that occurs twice, such as 01:30 on a fall-back morning, is offered as two instants with their offsets, and you choose which one the event uses.
- EscapingA comma, semicolon, backslash or line break in a text field is escaped, so punctuation in a title cannot break the property. A colon is left as written.
- FoldingLines are wrapped at 75 octets, counted in UTF-8 and never inside a character, and calendars join them again when they read the file.
- What the file holdsOne event: identifier, timestamp, start, end, title, and the description and location when you fill them in. No guests, no recurrence, no alarm, and no sending.
Common Use Cases
Send a meeting by email
Attach the file so the recipient adds the event from their own account, without a link to a scheduling service.
Publish a one-off session
Put the event on a page for a workshop, a stream or a class, where the date is fixed and recurrence is not needed.
Move an event between apps
Carry an event from one calendar application to another when the two do not sync directly.
How to create an .ics file
Fill in the event
Enter the title and the start and end, or mark it as an all-day event with dates only.
Choose the time zone
Pick the zone the wall time belongs to, which is not always the zone your device is set to.
Build the file
The generated calendar text appears so you can check the summary, the times and any escaped punctuation.
Download and import
Download the .ics file and open it in your calendar app, or attach it to a message.
Explicit fields, exact bytes
Ambiguity refused
A missing local time or a repeated one is reported with the offsets involved, so the event cannot land at a time you did not choose.
Readable before download
The calendar text is shown in full, so the escaping and the UTC conversion can be checked without importing anything.
One event, one file
The file describes exactly what the form holds. Nothing is added, nothing is sent and no account is created.
Before you send the file
- •Import it once: Open your own file in the app you use before sending it, and confirm the time matches what you typed.
- •Say the zone: Put the time zone in the title or the description when recipients are spread out, because a calendar shows the event in their own zone.
- •Check the title: A comma or semicolon in the title is escaped in the file. Read the generated text to see how it will be read back.
Make a calendar file
Fill in one event, choose its time zone and build the file.
Check the generated text, then download the .ics file and open it in your calendar app.
Related tools
Frequently Asked Questions
Which calendars can import the file?
The file follows RFC 5545, the plain text standard calendar apps read. No import test is recorded here, so open the file you download in the app you actually use before relying on it for an audience.
Why is the time written in UTC?
A UTC value is one instant everywhere, so the event does not shift when it crosses a time zone or a daylight saving change. The wall time you typed is converted once, and the offsets are shown.
What happens at a daylight saving change?
A time the clock skipped is refused with an explanation. A time that happens twice is offered as two instants with their offsets, and you pick the one the event should use.
Does the file invite anybody?
No. It describes one event. Sending it, adding guests and requesting responses all happen in your calendar application.
Can I create a repeating event?
Not on this page. One event per file, so the file holds no recurrence rule. A repeating series is easier to create in the calendar app itself.