Calendar Conflict Checker

Compare finite calendar events and export overlapping pairs plus the events that were checked.

On-device No sign-up Free to use

Inspect input controls

Showing an example. Edit to see your own.

Drop your files here

or choose them from your device

1 to 8 files; at most 5 MiB and 200 events combined.

    Processed in your browser. Your inputs stay on this device.

    Result

    Showing an example.

    The planning and review meetings overlap for 30 minutes.

    1 overlapping pairs among 2 blocking finite events.
    1 overlap pair
    Calendar A | UID A | Title A | Calendar B | UID B | Title B | Overlap UTC start | Overlap UTC end | Actual overlap minutes
    Calendar 1 | [email protected] | Planning meeting | Calendar 2 | [email protected] | Review meeting | 2026-01-05 09:30:00 UTC | 2026-01-05 10:00:00 UTC | 30
    calendar-conflicts.csv
    calendar-compared-events.csv

    Loading the tool. Your result will appear here.

    https://usefreetools.net/calendar-conflict-checker · 20 November 2026

    Was this helpful?

    How to use Calendar Conflict Checker

    1. Paste one or two ICS calendars, or select Upload .ics files and choose up to eight files.
    2. Set the zone for floating times and all-day dates. If a local clock repeats during a clock change, choose its earlier or later occurrence.
    3. Run the comparison and read any refusal or skipped-event notes. The check includes pairs within each calendar and across calendars.
    4. Review each overlapping pair and its actual overlap minutes. Download the conflict CSV and the list of compared events if you need to inspect them elsewhere.

    Example: Calendar Conflict Checker

    The planning and review meetings overlap for 30 minutes.

    You add
    Calendars to compare: text; First iCalendar text: BEGIN:VCALENDAR VERSION:2.0 PRODID:-//UseFreeTools//Finite calendar helper//EN BEGIN:VEVENT UID:example-one@example.invalid DTSTAMP:20260101T000000Z DTSTART:20260105T090000Z DTEND:20260105T100000Z SUMMARY:Planning meeting LOCATION:Room A END:VEVENT END:VCALENDAR ; Second iCalendar text (optional): BEGIN:VCALENDAR VERSION:2.0 PRODID:-//UseFreeTools//Finite calendar helper//EN BEGIN:VEVENT UID:example-two@example.invalid DTSTAMP:20260101T000000Z DTSTART:20260105T093000Z DTEND:20260105T103000Z SUMMARY:Review meeting LOCATION:Room A END:VEVENT END:VCALENDAR ; Zone for floating times and all-day dates: UTC; Repeated local clock policy: earlier
    You get
    1 overlapping pairs among 2 blocking finite events. 1 overlap pair Calendar A | UID A | Title A | Calendar B | UID B | Title B | Overlap UTC start | Overlap UTC end | Actual overlap minutes Calendar 1 | example-one@example.invalid | Planning meeting | Calendar 2 | example-two@example.invalid | Review meeting | 2026-01-05 09:30:00 UTC | 2026-01-05 10:00:00 UTC | 30 calendar-conflicts.csv calendar-compared-events.csv

    Options

    Comparison inputs
    Paste the two supported calendar texts or choose the intended files. Only supplied finite event intervals are compared.
    Default zone and repeated time
    These controls affect supported local-time interpretation. UTC and all-day values follow their separate conventions.

    Supported inputs and limits

    • Up to eight calendars, 5 MiB and 200 event records combined.
    • Events that meet at an endpoint do not overlap.
    • Cancelled, transparent and zero-duration events do not block time.
    • Recurrence, custom embedded timezone rules and unresolved or unsupported event semantics are refused.
    • The displayed table contains at most 200 pairs; the conflict CSV contains all reported pairs.
    More details

    The tool does not merge events or access a calendar account.

    Where your input is processed

    This tool does not upload your inputs. See the limits for anything saved on your device.

    Touching endpoints are different from overlap

    An event ending when another begins does not overlap under the stated exclusive-end interval model. A conflict report does not assess travel time, setup time, attendee availability or recurrence that the parser refuses. Add necessary buffers to the event data before using it to plan a schedule.

    Questions about Calendar Conflict Checker

    Are adjacent events conflicts?

    No. An event ending at the next event’s start does not overlap under this half-open interval model.

    Can recurring events be ignored?

    No. Unsupported recurrence prevents a complete supported conflict result. Supply an appropriate finite event export.

    Does a conflict change either calendar?

    No. The page reports pairs for review and does not edit an account or original file.

    Page updated · Project managed by Tony Hines · Report a problem with Calendar Conflict Checker