Title, date and time, time zone, location, guests, reminders, and repeats — then download the .ics file or open it straight in your calendar.
The rule inside the file
A repeat is one line: RRULE:FREQ=WEEKLY. Calendars read it and generate the occurrences themselves, which is why a repeating event stays one small file no matter how long it runs. The rule can also carry an interval (INTERVAL=2 for fortnightly), an end date (UNTIL), or a limit (COUNT).
This builder sets the frequency, and leaves the series open-ended — it repeats until you change it. Since your calendar can edit a series it has imported, the usual path is to import it here and set the end date there, where you can see it against everything else in the month.
Which frequency to pick
Weekly is anchored to the day of the week you chose for the start, monthly to the date. A monthly event on the 31st is the classic trap: months without one are skipped by most calendars rather than moved, so for “the last day of the month” pick a date every month has and adjust in your calendar afterwards.
Questions
- How do I stop a repeating event?
- Import it, then set the end date in your own calendar — every calendar app can edit the series it created. In the file itself, the properties for this are UNTIL (a final date) and COUNT (a number of occurrences).
- Can I make an event repeat every other week?
- The iCalendar format handles it with INTERVAL=2 on the repeat rule. This builder offers the four plain frequencies, so for a fortnightly series, import a weekly one and change the interval in your calendar.
- Will the repeat survive being imported into Outlook or Google?
- Yes. RRULE is part of RFC 5545 and both read it, along with Apple Calendar and Thunderbird. They expand the series on import rather than storing every occurrence.