A PRACTICAL WORKFLOW
Step 1
Paste your ICS export and download event definitions as CSV. Times retain their original ICS representation; recurrence rules are recorded without expanding them.
ICS Calendar to CSV →Step 2
For conflict checking, use a non-recurring export with UTC timestamps ending Z or all-day dates. Review each reported overlap and its duration.
Calendar Conflict Checker →
Before you finish
The conflict checker rejects recurring and named-timezone events rather than guessing. Cancelled and transparent events are excluded. An empty report only covers the supported events you supplied.
Processing runs in your browser. Save outputs before leaving. Saved setups are optional and stored on this device; avoid saving sensitive data on shared computers.
All use cases →What you need
An ICS export. For overlap checking, prepare non-recurring UTC events or all-day dates; the CSV inspection step can show other event definitions.
Check the result
Compare reported start and end times with the source calendar. Review actual overlapping intervals rather than treating every shared day as a scheduling conflict.
If the result looks wrong
Recurring or named-timezone events need a supported export before overlap analysis. A rejected event is not evidence that the schedule is free.