CSV to vCard Converter

Convert CSV contact lists to vCard (.vcf) files with column-to-field mapping.

Tested tool guide Tested browser tools Checked August 16, 2026

What CSV to vCard Converter does and how it behaves

This converter prepares contact records from a CSV list for applications that accept vCard (.vcf) files. You assign source columns to contact fields such as formatted name, telephone number, email address, organization, title, and address, and each data row becomes a contact record. The common mistake is treating the original column labels as sufficient. An email column left unmapped, or a phone column assigned to the wrong destination, will not produce the intended contact details. Review every mapping before converting a large list.

How the result is produced

Contact field mapping

The mapping step pairs each selected CSV column with a vCard property. Values from one CSV data row form one contact record, using properties such as FN for the formatted name, TEL for a telephone number, EMAIL for an email address, and ORG for an organization. A source column without a selected destination is not assigned to the corresponding vCard contact field.

CSV parsing and vCard records

CSV structure is resolved before contact fields are assigned. A comma inside a contact value belongs in a quoted CSV field, and a double quote inside that field is represented by two double quotes. Bad quoting can shift an email address or phone number under the wrong header. Conversion stays in the browser, so the contact data is not uploaded. Each resulting vCard record has BEGIN:VCARD and END:VCARD boundaries.

Good uses

Move an address book exported from a CRM as CSV into a phone or desktop contacts application that imports .vcf files.
Turn a spreadsheet of club members, volunteers, or event attendees into separate vCard contact records.
Restore a CSV contact backup when the destination address book offers vCard import but lacks a suitable CSV field mapper.

Limits and checks

A syntactically plausible .vcf file can still contain incorrect contact fields. Inspect the formatted name, phone, email, organization, and address mappings rather than checking only whether a file was produced.
Confirm that the source is comma-separated and consistently quoted. Semicolon-delimited exports, embedded line breaks, and unmatched quotes can make contact columns or row boundaries ambiguous.
The receiving contacts application controls the final import. It may ignore unsupported vCard properties, alter telephone labels, or handle duplicate contacts according to its own rules.

Common questions

Can I import the resulting .vcf file into any contacts application?

Often, but not universally. The destination must support vCard import, and applications differ in the vCard versions and properties they recognize. Some may discard unsupported fields or labels. Import one or two contacts first, then verify names, phone types, email addresses, organization data, addresses, and non-ASCII characters before processing the full list.

How should I map names when the CSV has one full-name column?

Map that column to the full-name or formatted-name destination used for the visible contact name. If separate given-name and family-name columns exist, map those to matching structured name fields too. Do not assume one full name can be split reliably: prefixes, suffixes, compound surnames, and differing name orders make automatic decomposition ambiguous.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.