About this tool
Build a portable calendar event file that recipients can import without requiring access to the same calendar service or account.
Calendar Event Generator writes a single-event .ics file that Google Calendar, Outlook, Apple Calendar, and most other calendar apps can import directly. You fill in a title, a start and end, and optionally a location, a meeting URL, notes, a repeat rule, and a reminder, and the tool produces a correctly escaped and line-folded iCalendar document with a unique UID and timestamp. Timed events are tied to the IANA time zone you choose, so 9:00 in Europe/Berlin stays 9:00 there even when a recipient in another zone opens it. All-day events use the exclusive end-date convention the format requires, which is where hand-written files usually go wrong. Before downloading you can read the exact text that will be saved.
- Supports timed and all-day events with correct exclusive end dates for multi-day all-day events.
- Adds location, meeting URL, notes, daily, weekly or monthly recurrence, and display reminders.
- Escapes and folds ICS content, uses a selected IANA zone for wall-time validation, and downloads a structurally validated .ics file.
How to use Calendar Event
Type an Event title of up to 200 characters. Tick All-day event for a date-only entry, or leave it unticked and set Start date, Start time, End date, and End time, then pick the Time zone that owns those wall-clock values. Add a Location, a Meeting URL, and a Description of up to 10,000 characters if needed. Under Repeat choose Daily, Weekly, or Monthly and enter the number of Occurrences from 1 to 99, or leave it at Does not repeat. Set a Reminder if you want an alert. Press Download .ics file, then open Last generated calendar data to read it. Use Create as a separate event when you want a fresh UID so a calendar treats the next download as a new entry instead of an update.
When this tool is useful
- Event organizers adding an Add to calendar link to a webinar landing page or email invitation.
- Freelancers sending a client a kickoff meeting they can drop into whatever calendar they happen to use.
- HR teams distributing a company holiday or all-hands date to staff on mixed Google and Outlook setups.
- Course instructors publishing a weekly class schedule as one recurring event students can import.
- Anyone who needs a deadline or renewal reminder without granting a website access to their calendar account.
Practical tips
- One-time timed events are exported as UTC instants, while recurring events keep the chosen zone and wall time so every occurrence lands at the same local hour across DST changes.
- Import the file into a test calendar first. Some apps ignore reminders on imported events or display the description without line breaks.
- Re-downloading after an edit keeps the same UID, so importing again updates the existing entry in most calendars. Press Create as a separate event if you want a duplicate instead.
- A multi-day all-day event ending on Friday should have Friday as its End date; the tool adds the exclusive next-day boundary the format expects.
- Keep the Meeting URL in its own field rather than in the description so calendar apps can render it as a clickable join link.
Examples you can test
Load an example, compare the result with the expected output, then replace it with your own input.
Weekly team sync
Example input
Title Team Sync; Start 2026-09-07 10:00, End 11:00; Time zone America/New_York; Repeat Weekly, 12 occurrences; Reminder 15 minutes before
Expected output
A VEVENT with DTSTART;TZID=America/New_York, an RRULE for 12 weekly occurrences, and a VALARM 15 minutes before each meeting.
Because the zone is embedded, the 10:00 start survives the November clock change for attendees in New York.
Three-day conference
Example input
Title DevConf 2026; All-day event; Start date 2026-10-13, End date 2026-10-15; Location Berlin; Meeting URL pointing to the agenda page
Expected output
An all-day VEVENT spanning October 13 through 15, stored internally with an end of October 16 as the format requires.
The exclusive end date is handled for you, so the event shows three days rather than two after import.
Validation checklist
- Confirm Start and End are in the right order and in the intended Time zone.
- Check the recurrence type and Occurrences count before downloading.
- Read the generated text and look for the SUMMARY, DTSTART, and RRULE lines.
- Import into your own calendar and confirm the time, reminder, and link.
- Decide whether a re-export should update the existing event or become a separate one.