From event to calendar
A calendar file you can review
An ICS file carries an event’s title, dates and optional details. Create the file here, then open or import it in your calendar app and review the event before saving.
- 1
Describe one event
Add a title and choose specific times or whole days. Location, notes and a reminder are optional.
- 2
Check dates and time zone
For timed events, use the event’s time zone. Review both the local clock time and the exact UTC time saved in the file.
- 3
Download, then import
Save the .ics file and use your calendar’s open or import action. Generating a file does not invite attendees or send a message.
Two details that matter
Clock times and whole days behave differently
A meeting in New York
On November 2, 2026, a 09:00–10:00 meeting in America/New_York is saved as 14:00–15:00 UTC. Someone viewing it in another time zone sees the same instants at their local time.
Use Load example to inspect this event. Changing the event’s time zone keeps the clock times you entered, so review the resulting UTC times.
A one-day event
For September 1, select September 1 as both the first and last day. The file uses September 2 as its exclusive end, which means the event includes September 1 only.
This also handles leap days and year boundaries. All-day dates do not shift with the selected time zone; the time-zone field is used only for timed events.
What happens when clocks change?
A spring-forward clock time may not exist. The tool asks you to choose another time instead of moving it silently. When a fall-back time occurs twice, choose its first or second occurrence; each option shows the UTC offset and exact instant.
Time-zone rules come from your browser’s time-zone data. Use a current browser and a supported IANA zone. Check far-future events again if local clock rules change.
Which calendars can use the file?
The file follows the iCalendar format used by calendar applications. Open the downloaded file or use the app’s import option, then check the title, dates, time zone and reminder before saving. Import steps and reminder handling vary by app.
This tool generates one event, not a calendar subscription. It does not connect to an account, send invitations, add attendees, create recurring events or host a public event link.
What is included in the file?
One event with a unique ID, a generation timestamp, start, end and title. Optional location and description are plain text. An optional reminder is a display alarm before the start.
Timed events are written in UTC. All-day events use dates with an exclusive end. Text is escaped and long lines are folded for the file format; these formatting characters do not change your event text.
Privacy and repeat downloads
Your event is created locally without an account, upload, analytics or automatic storage. Entries stay in page memory. Reset clears them; browser history may restore an open page. Copying or downloading creates an artifact you control.
Editing and re-exporting the same draft keeps its event ID; New event / Reset starts another ID. Calendar apps may update or duplicate an event on re-import, so review the result. Export does not transmit anything to attendees.
Format and limits
One event per file, dates from 2000 through 2100. No recurrence, calendar imports, invitations or automatic synchronization. The file format follows RFC 5545: Internet Calendaring and Scheduling Core Object Specification, including content lines, date-time values, text escaping, events and alarms.
Method reviewed September 30, 2026. Report a file or calculation issue. For a related date-planning job, the Lead Time Calculator works out delivery and order-by dates; event details do not transfer.