RandoziICS Conflict Checker
Open your calendar export in any text editor, paste it here and see every pair of events that overlap, before you import it or send it.
Conflicts
1 overlapping pair
3 events read. Times are shown in UTC.
Team meeting × Dentist
Overlap 30 min · 20 Oct 2026, 09:00 – 20 Oct 2026, 10:30 and 20 Oct 2026, 10:00 – 20 Oct 2026, 11:00
Repeating events
0
Zone-dependent times
0
How it works
- Export your calendar as an .ics file, open it in a text editor and copy everything.
- Paste it into the box. Nothing is uploaded: the file is read in your browser.
- Read the list of overlapping pairs with the length of each overlap in minutes.
- Tick “Include all-day events” if a holiday or a deadline day should also count as a conflict.
What people use it for
Before importing
Check a timetable or a conference schedule for double bookings before it lands in your calendar.
Shared rotas
Find people or rooms booked twice in a combined export.
Cleaning up
Spot events with a missing or broken date that other apps silently drop.
Questions
- When do two events count as overlapping?
- When each one starts before the other ends, so they share at least a minute. Two events that meet end to end, one finishing at 10:00 and the next starting at 10:00, do not conflict. Events without an end time follow RFC 5545: an all-day date lasts one day, but a date-time lasts 0 minutes and is never reported as a conflict. Cancelled events (STATUS:CANCELLED) are ignored.
- What about time zones?
- The tool has no time-zone database. Times ending in Z are exact UTC. Times with a TZID, and floating times, are read as if they were UTC, so two events in different zones can be shifted by the difference. The result tells you how many events are affected.
- Are repeating events expanded?
- No. A repeating event (RRULE or RDATE) is checked on its first occurrence only, and the tool counts how many such events your file contains so you know the check is partial.