Calendar
Build recurring calendar events and export them to an .ics file.
| Title | When | Repeats | ||
|---|---|---|---|---|
No events yet Create one, or import an existing .ics file. | ||||
0 of 0 row(s) selected.
Runs in your browser. Nothing is uploaded.
A calendar file is a list of events, and a list is easier to fix in a table than in a month view. Import an .ics and every event becomes a row you can sort, filter, select and edit in bulk — change the time zone of forty events, tag a run of them, or delete the ones a bad sync duplicated.
Recurring events are read and written as real recurrence rules rather than expanded into hundreds of copies, so a weekly standup stays one row and exports as one event. Reminders, categories, locations, links and colours survive the round trip.
Spreadsheets come in too: pick which column is the title, which is the date, and the rows become events. Your list is kept in this browser and nowhere else, which is why it is still there when you come back and why nobody else can see it.
Step by step
- 1Import an .ics file or a CSV, or add an event by hand.
- 2Filter and edit the table until the calendar is the one you want.
- 3Export it back as .ics, CSV or JSON.
Questions
Where are my events stored?
In this browser, in local storage. Nothing is uploaded, and clearing your browser data clears the list — export an .ics if you want a copy.
Will my recurring events survive the export?
Yes. Repeats are kept as RRULE, the same thing every calendar app reads, so a weekly event exports as one recurring event rather than fifty copies.
Can I import a spreadsheet instead of an .ics?
Yes. Drop a CSV and match its columns to the event fields; the day-before-month switch settles what 03/08 means.