Convert CSV contact lists to VCF (vCard) files. Paste CSV or choose a file, map columns to contact fields, and download your .vcf file. Conversion runs locally in your browser, without sending your contact list to a conversion server.
Next: paste your list in the tool below, then convert—everything stays in your browser until you save the file.
Built for address books
No installation is needed; the converter runs in modern browsers.
Contacts: paste your list from Excel or a CRM export (or Load sample), adjust input options if needed, then set vCard mapping so name, phone, and email line up. Convert sits right under the mapping table. Save the .vcf for Google Contacts, Outlook, or your phone’s import screen.
Use NULL for empty field: prevents SQL errors when inserting missing values into nullable columns.
NOTE - you can change the column names below by overwriting the Field Name value.
Key: the first column is checked automatically. Confirm it matches your table’s primary key before generating UPDATE or DELETE (composite keys: check every key column).
| # | Field Name | Data Type | Max Size | Key | Include | Trim | Use NULL for Empty Field |
|---|---|---|---|---|---|---|---|
| Paste CSV above to load columns. | |||||||
Map each vCard field to a CSV column. Include is checked automatically when a column is mapped; uncheck to skip that field in the file, or set Mapping to — none — to clear it. Use Check all / Uncheck all under the mapping table for every row at once. You can duplicate TEL / EMAIL / ADR rows to emit multiple values.
| # | VCF Field | Mapping | Include | Others |
|---|---|---|---|---|
| Paste CSV above to load mapping options. | ||||
Run this after you are happy with column mapping—output opens further down the page.
Each row in your sheet becomes one person in the file—same idea your phone already uses for name, dial, and email.
Create a vCard contact file from CSV rows. Use the mapping table to choose which columns supply names, phone numbers, emails, and other supported fields. Review the generated VCF, then copy it or download a .vcf file.
Stage contacts before a controlled database import.
Feed directories and sync jobs with structured objects.
Review TEL/EMAIL columns with spreadsheet filters.
Normalize cards into a grid for dedupe and CRM cleanup.
Use VCF when the destination contact app accepts vCard or you want to share contacts as a .vcf file. Google Contacts accepts both CSV and vCard, so conversion is not always necessary. Check your destination app’s supported formats and import instructions before exporting.
Export CRM or help-desk contacts and load them onto sales reps’ phones before a trip. Move a shared Excel “clients” tab into Google Contacts for the office line. Email a single .vcf bundle so a colleague can tap Import without seeing your whole sheet. Shift a household mailing list from CSV into iCloud for family devices.
Business owners updating handsets, sales teams reorganizing territories, freelancers sharing client lists with clients, and everyday users who just want their grid of people to land in an address book.
Problem
Spreadsheet apps can strip leading zeros or a leading +, and numbers without a country code may dial incorrectly after import.
Fix
Keep phone numbers as text so leading zeros and a leading + are preserved. Include international country codes where appropriate. This converter maps your values; it does not verify that a number is valid or automatically determine its country.
Problem
Incorrect mapping can put a name, phone number, or email in the wrong field.
Fix
Review the mapping table and generated contacts before downloading.
Problem
Some devices reject files when lines are broken, fields are empty, or the app does not recognize the mix of columns.
Fix
Preview the generated vCard in the output panel, fix odd characters or blanks, then save a clean .vcf and import again.
Problem
Re-importing the same sheet or overlapping CRM exports can create twins in Google or on the handset.
Fix
Deduplicate in your sheet first, or merge carefully inside Google Contacts / Outlook after import.
Use the Text or File tab. Your sheet can come from Excel, Google Sheets, or a CRM export—one row per person is ideal.
Open mapping options and point each vCard field at the right column so each value appears in the correct contact field.
Tap Convert, then copy or download the vCard bundle from the output area when it looks right.
Import the downloaded .vcf using your destination app’s supported workflow; steps vary by app and device.
Open Contacts, use Import (wording varies by phone), and choose your .vcf file.
Use the Contacts app or iCloud import—pick the vCard bundle you saved from this page.
Google Contacts can import CSV or vCard. Use Import and choose your .vcf when that is the format you prepared—or keep CSV if that fits your account’s import options.
On Outlook for desktop, use File → Open & Export → Import/Export (wording varies by version) and follow the prompts for a vCard or contacts file. Outlook on the web uses a different import path—check Microsoft’s current help for your account type rather than assuming desktop menus.
You do not need to edit this by hand—just a quick read so imports feel less mysterious.
BEGIN:VCARD
VERSION:4.0
FN:John Doe
TEL;TYPE=CELL:+1234567890
EMAIL;TYPE=INTERNET:john@example.com
END:VCARDUse this path when the destination accepts vCard, when you are moving a list between systems that prefer .vcf, or when you want to share a contact pack without sending the full spreadsheet.
Skip browser vCard when your company already pushes contacts through full directory sync (SCIM/LDAP), or when relationships are messy enough that cleanup belongs in the CRM before any export.
CSV → vCard
People, phones, and inboxes—share a .vcf and import into Contacts.
CSV → JSON
Apps, scripts, and APIs—great when a program will read the data next.
CSV → XLSX
Filters, pivots, and printouts—when the audience lives in Excel.
Keep phone numbers as text so leading zeros and a leading + are preserved. Include international country codes where appropriate. This converter maps your values; it does not verify that a number is valid or automatically determine its country.
Conversion runs in the browser—no upload to a conversion server—so you can map columns, review the generated contacts, then download or copy the .vcf when you are ready to import.
Use when the web or a CMS needs a pasteable table fragment.
Export to calendar apps when rows represent meetings or shifts.
Use when the next hop is INSERT-ready text for a database load.
Use when Git, Helm, or CI expects indentation-first config.
Use when APIs, fixtures, or mobile clients need structured objects.
Strip workbook binaries when loaders only accept UTF-8 CSV.
Materialize config lists into a grid ops can annotate before merge.
Spread VEVENT fields across columns for spreadsheet-based planning.
Freeze tables for legal, procurement, or print-room workflows.
Package typed workbooks when humans—not parsers—must sign off.
Serialize rows to elements when XSD or SOAP is the contract.
YAML config blocks compiled into runtime JSON.
JSON payloads promoted into INSERT-ready relational text.
Format notes first; FAQs below are grouped so you can skim on a phone.
Turn CSV contact rows into a downloadable .vcf file for address books.
Paste or upload CSV, map columns to FN/TEL/EMAIL (and optional N/ADR), then convert. Use + on TEL/EMAIL/ADR for extra numbers on the same contact. Blank names export as Contact.
CSV is parsed as structured input for this page. Use complete rows, valid syntax, and consistent field names so the converter can preserve the important data when creating vCard.
vCard is generated from the parsed CSV data. Review the output before importing it into another system, especially when the destination expects strict columns, dates, or contact fields.
.csv file. Use Load Sample to try demo contacts.Family;Given;;;—semicolons stay structural. A blank name still exports as Contact..vcf.CSV to vCard FAQs
Start with the three answers people need before import; open a topic below for everything else.
Paste CSV in the Text tab or upload a file, map columns to FN/TEL/EMAIL (and optional N, ADR, ORG), select Convert, then copy or download the .vcf.
On TEL, EMAIL, or ADR, + duplicates a mapping row so one contact can have more phones or emails. That does not create extra people. Use − only on those duplicated mapping rows.
Keep phone values as text in your CSV (quoted if needed). Digits already stored without zeros cannot be restored here.
Open one section at a time.
The row still exports. The card uses the placeholder name Contact when no usable name is mapped.
Use Load Sample for demo rows, and Clear to reset input, mappings, and output.
Use Family;Given;Additional;Prefix;Suffix—for example García;José;;;. Semicolons stay structural so apps can split first and last names.
No. Conversion runs in your browser on this page.
Names and numbers stay in your browser tab while you map columns—nothing is sent to a converter server just to build the file.
Built for bulk contact lists: map once, preview, then import many people into Google Contacts, Outlook, or a handset.
You get standard .vcf text—easy to sanity-check, email to yourself, or hand off before anyone imports.
Map FN, TEL, and EMAIL to the right columns, preview the bundle, then import through Google Contacts, Outlook, or your phone’s Contacts app.