How to use VCF Contact Merger
- Choose UTF-8 vCard 3.0 or 4.0 files and inspect the match/conflict preview.
- Keep contacts separate or explicitly enable merging by email, phone or UID.
- Download reviewed-contacts.vcf and keep combined-originals.vcf as the unmerged reference.
Example: VCF Contact Merger
Review a shared email with two different formatted names.
Supported inputs and limits
- Up to 20 files, 5 MiB combined and 2,000 contacts.
- Supports UTF-8 vCard 3.0/4.0 with unfolded properties; encoded/base64 or older vCard 2.1 data is refused.
- Merging mixed-version duplicate groups is refused.
- Conflicting singleton values are retained as custom X-UFT-ALTERNATE properties; address-book support varies.
- Names alone never trigger merging.
More details
Email matching ignores case.
Phone matching retains country prefixes and extensions under the declared conservative rules.
UID contact identifiers match exactly, including case, after trimming surrounding whitespace.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
Questions about VCF Contact Merger
Can two people with the same name merge accidentally?
Name alone is not a match key. Email matching ignores case, phone matching preserves country prefixes and extensions, and UID identifiers match exactly after surrounding whitespace is trimmed. Shared household details can still require review.
Where do conflicting names or birthdays go?
The first singleton value stays in its standard field; differing values become X-UFT-ALTERNATE properties. The unmerged original records are also exported.
Can every address book read custom conflict fields?
No. Support differs, so review the conflict table and retain combined-originals.vcf before importing a merged file.