How to use Merge and Deduplicate Calendars
- Choose calendar files in the desired merge order.
- Select the repeated UID policy and merge.
- 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.
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.