Map contact columns, preview the exact people, catch invalid fields and possible duplicates, then download one standards-shaped VCF - without uploading your address book.
A VCF is a vCard contact file. Load a CSV or Excel contact list, review the field mapping, choose vCard 3.0 or 4.0, and download every valid contact in one file.
Contact exports use different headers. The workspace matches header text deterministically, keeps every choice editable, validates the complete file, and serializes UTF-8 vCards with correct escaping and line folding.
Drop a contact export, paste CSV, or use the imperfect sample. Multi-sheet workbooks stay local and let you choose a sheet.
Confirm names, phones, emails, organization, address, birthday, website, and notes. A source column can feed only one contact field.
Inspect contact cards and the complete issue ledger, choose vCard 3.0 or 4.0, then download one multi-contact VCF.
A contact import can silently put a phone number in the wrong field or drop an invalid address. This workflow makes the mapping and every omission visible before the VCF reaches a contacts app.
Google-style, Outlook-style, and plain contact headers are matched from names only. Row values never drive a hidden semantic guess.
Missing names, malformed emails, incomplete URLs, invalid birthdays, and repeated email or phone signatures are reported across the full file.
Values are escaped, CRLF-delimited, and folded without splitting UTF-8 characters. vCard 3.0 and RFC 6350 vCard 4.0 are explicit choices.
Rows, headers, mappings, previews, findings, and output stay in the tab. The audience counter receives the page path only.
Google Contacts accepts CSV or vCard imports. Apple Contacts and iCloud import .vcf files, including files with multiple contacts. Microsoft documents vCard import paths for Outlook; exact bulk behavior varies by Outlook version.
The practical default for broad compatibility and Apple-style exports. Phone and email properties use the established 3.0 TYPE syntax.
The current IETF format in RFC 6350. Phone values are emitted as tel: URIs and content lines follow its UTF-8, escaping, CRLF, and folding requirements.
Every exportable row becomes its own BEGIN:VCARD / END:VCARD object inside one .vcf file. Invalid rows are listed and skipped, never silently turned into blank contacts.