How to use
- Enter title, start, end and time zone.
- Add location, description, reminder and repeat rule.
- Download the .ics or open the Google Calendar link.
Worked example
A weekly team meeting on Mondays at 10:00 for 8 weeks produces RRULE:FREQ=WEEKLY;BYDAY=MO;COUNT=8.
Supported formats and limits
| Input | Event details |
|---|---|
| Output | .ics, Google Calendar link |
| Engine | RFC 5545 writer (escaping, 75-octet line folding, UTC or zoned times with VTIMEZONE, RRULE, VALARM) |
Limitations
- One-off events are written in UTC, so calendars show them in each person's local time. Repeating events carry their time zone with rules from your browser covering up to 10 years.
- Some calendar apps ignore reminders in imported files and apply your own defaults.
Questions
How are time zones written in the file?
One-off events are written in UTC, so each calendar shows them in its owner's local time. Repeating events are written in local time with a TZID and a VTIMEZONE built from your browser's zone rules, so they keep the same wall-clock time across daylight-saving changes.
Will my calendar app keep the reminder?
Not always. The file includes a VALARM reminder, but some calendar apps ignore reminders in imported files and apply your own defaults. Import a test copy before sending it to others.
What does a weekly rule look like?
A meeting on Mondays for 8 weeks is written as RRULE:FREQ=WEEKLY;BYDAY=MO;COUNT=8. You can also end a series on a date instead of after a count.
Guides
Privacy
Runs on your device. Files and text are processed in this browser tab and are not uploaded.
See the privacy policy for how toolsdocks handles data.