Timetable to Calendar
Share tool
Only this public address is included. Your files, inputs and results stay out of the link.
Create an ICS file from a photographed, scanned or tabular schedule. Review the recognized events and confirm dates and times before export.
Preparing your tool…
A visual example
Resolve the date before adding it to a calendar
A timetable can look clear while leaving an important question open: does 05/06 mean 5 June or May 6?
- Sample timetable entry
Workshop
05/06/2026
09:00–10:00
Start with what the source says
The numeric date alone does not establish its order. Check the document's convention instead of guessing.
Confirm the interpretation Confirm Example choice Date order Day / month Date 5 June 2026 Time zone Europe/Zurich Local time 09:00–10:00 Confirm the interpretation
For day/month order and Europe/Zurich, this entry means 5 June 2026, from 09:00 to 10:00 in that time zone.
Confirm dates, times and the time zone before exporting the ICS file.
Illustrative example. Review extracted entries, especially after OCR. Downloading an ICS file does not automatically add events or send invitations; import it into the intended calendar and check the result.
How to use it
- Read a printed schedule image, a PDF or a suitable CSV/XLSX table; explicitly load OCR files if needed.
- Confirm year, date format, validity dates and time zone, then check recognized cells and event-column mapping.
- Correct each event, confirm night shifts and repetitions, and enter dates to exclude; inspect the calendar and list previews.
- Confirm the complete occurrence list and create an ICS file to import yourself.
A weekly Monday lesson at 08:00 in Europe/Zurich starts at 07:00 UTC on 23 March 2026 and 06:00 UTC on 30 March. Its local start remains 08:00 across the clock change.
Details & limits
Bounded local OCR/PDF/table recognition. Confirm year, date format, time zone, repeats and exceptions. Review ambiguous times and overnight shifts. No invitations or connected-calendar changes.
How are alternating weeks and clock changes represented?
Choose Every 2 weeks with an explicit first date for each alternating rule. The finite ICS uses recurrence rules and selected exceptions; it may split a rule into several UTC series to preserve local start/end times across clock changes. Nonexistent times block export unless corrected or explicitly excluded, and repeated autumn times require a choice.