Merge and Deduplicate Calendars

Merge finite calendar files in selected order and review which duplicate UIDs were discarded.

On-device No sign-up Free to use

Merge calendars controls

  1. 1 Add files
  2. 2 Arrange/Options
  3. 3 Download

Drop your files here

or choose them from your device

Choose 2–8 UTF-8 ICS files; at most 5 MiB combined and 200 events before deduplication. UTC or all-day events with explicit ends only. File order controls which duplicate UID survives.

    ?

    UID identity only. Equal-looking events with different UIDs remain separate; sequence numbers and dates do not select a revision.

    Result

    Showing an example.

    Combine two calendars containing different event UIDs without discarding either event.

    Merged 2 files: 2 input events, 2 kept and 0 discarded duplicate UIDs.
    first | Planning | 20260105T090000Z | 20260105T100000Z
    second | Review | 20260105T090000Z | 20260105T100000Z
    merged-calendar.ics
    deduplication-report.csv

    Loading the tool. Your result will appear here.

    https://usefreetools.net/calendar-merge-deduplicate · 20 November 2026

    Was this helpful?

    How to use Merge and Deduplicate Calendars

    1. Choose calendar files in the desired merge order.
    2. Select the repeated UID policy and merge.
    3. Review the event counts and deduplication report before importing.

    Example: Merge and Deduplicate Calendars

    Combine two calendars containing different event UIDs without discarding either event.

    You add
    Calendar files in merge order: ["first.ics (209 bytes)","second.ics (208 bytes)"] Repeated UID policy: "refuse"
    You get
    Merged 2 files: 2 input events, 2 kept and 0 discarded duplicate UIDs. first | Planning | 20260105T090000Z | 20260105T100000Z second | Review | 20260105T090000Z | 20260105T100000Z merged-calendar.ics deduplication-report.csv

    Options

    File order
    Choose two to eight files in the intended order. First or last occurrence uses that order, not event modification dates or sequence numbers.
    Repeated UID policy
    Refuse identifies duplicate identities for review. Keep first or keep last drops the other entries with that same UID; different UIDs remain separate.

    Supported inputs and limits

    • Choose two to eight files with at most 5 MiB and 200 events before deduplication.
    • Only identical UIDs match.
    • Events need explicit ends and either UTC timestamps or all-day dates.
    • Recurrence, named-zone or floating times and unsupported scheduling semantics are refused.

    Where your input is processed

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

    Equal titles do not establish duplicate events

    The tool deduplicates UID identity only. Two events that look alike can have different identities, and two versions of one UID can contain important differences. Review the discard report before importing the merged calendar.

    Questions about Merge and Deduplicate Calendars

    Are events compared by their titles?

    No. Deduplication uses event identifiers. Similar titles with different UIDs remain separate.

    Can recurring calendars be merged?

    No. Recurring events and time-zone definitions are outside the supported subset.

    Does selecting last keep the newest edit?

    It keeps the last input occurrence, without comparing edit timestamps. Order the files carefully.

    Page updated · Project managed by Tony Hines · Report a problem with Merge and Deduplicate Calendars