Logo

VCF to CSV Converter

Pull every contact out of a .vcf file into a spreadsheet, using the column names Google Contacts or Outlook expects. Converted in this browser tab.

Drop a .vcf file here

One card or an entire exported address book.

We add a byte-order mark to the file so Excel opens accented and non-Latin names correctly instead of turning them into symbols. Building a contact file from a spreadsheet instead? The build contacts from a spreadsheet instead, with column mapping.

A .vcf export drops eight hundred contacts into one file you cannot sort, filter or clean up. Open it in Excel and each contact sprawls across a dozen rows with no columns at all. This VCF to CSV converter turns it into one tidy row per person, in your browser.

Getting a vcard to excel without the encoding mess

Drop the file in and pick a column set. The conversion happens immediately and the preview shows the first rows exactly as they will be written.

We write the file as UTF-8 with a byte-order mark. That small addition is what stops Excel turning Renée into Renée, and it is the single most common complaint about every other converter.

One honest limit: if the damage is already in your source file, we cannot undo it. Old vCard 2.1 exports store non-English text in an encoding later versions dropped, and re-exporting from the original device is the only clean fix.

Why the google contacts csv format is not just any spreadsheet

Google Contacts matches on exact column names when it imports. A column headed “Email” is ignored, because it expects “E-mail 1 - Value”.

Outlook has its own set, and they do not overlap. Pick the destination before you download and the columns come out right the first time.

The plain option exists for everything else: analysis, a mail merge, or handing a list to somebody who just wants to read it. It uses obvious names and imports nowhere in particular.

What happens when you split a multi-contact vcf into rows

A vCard can repeat a property as many times as it likes. A spreadsheet column cannot, so something has to give.

Our rule is one row per contact, always. Where a card has three numbers, we take the mobile and fall back to the first other number. A row-per-property file looks thorough and imports nowhere.

Photos are dropped entirely. A photo is thousands of characters of encoded text, and putting that in a cell produces a spreadsheet no application can open. Keep the original .vcf if the photos matter.

Using the export to merge contacts to a spreadsheet you can clean

Converting is usually step one of a bigger tidy-up. Two address books become two sheets, and pasting one under the other gives you everything in one place.

Sort by email address and the duplicates line up next to each other. Removing them by eye takes longer than an automatic merge and loses far less.

We deliberately do not offer to merge for you. Deciding that two near-matching rows are the same person is a guess, and a wrong guess deletes somebody quietly. When the sheet is clean, the CSV to VCF converter turns it back into contacts, and the steps for importing the file afterwards cover the duplicates that follow.

One practical habit for big exports: paste the notes column into the word counter before any mail merge. Notes fields hold far more than people remember writing.

Where this vcf to csv converter does the work

In this browser tab. The contact file is read with the browser's own file reader, and the spreadsheet is assembled in the same place.

An exported address book is the densest personal data most people hold. It names hundreds of other people, with their numbers and often their home addresses, and none of them chose to have it uploaded.

Watch the network panel while you convert. Nothing goes out. We serve the JavaScript, so a compromised page could always misbehave — that applies to every browser tool including this one, which is why we point at the check rather than ask for trust.

Look at the file before you convert it

Knowing what is in the file first makes this VCF to CSV converter far more useful. Contact count, vCard version and the fields that will not survive are all worth seeing before you commit to a column set.

The vcf viewer shows all three. For a single card rather than a list, build it properly with the vcard generator, and if you are deciding what to export in the first place, the structure of a vCard file makes the column choices obvious.

Questions about exporting contacts to a spreadsheet

Why does the column set matter so much?

+
Google Contacts and Outlook match on exact column names when importing. A spreadsheet headed "Email" instead of "E-mail 1 - Value" imports into Google as a list of contacts with no email addresses. Pick the destination first and the columns take care of themselves.

My contact had three phone numbers and only one came through. Why?

+
A spreadsheet has fixed columns and a vCard does not, so repeated properties have to collapse. We keep the mobile if there is one, then fall back to the first other number. The full picture is always in the original file, which is worth keeping.

Accented names turn into strange symbols when I open the file in Excel.

+
That is Excel guessing the wrong encoding, not a fault in the conversion. We add a byte-order mark to the start of the file specifically to stop it, so a fresh download should open correctly. If you are opening an older export, import it through Data then From Text and choose UTF-8.

What happens to photos in the contacts?

+
They are left out. A photo is thousands of characters of encoded text, and putting that in a spreadsheet cell produces something no application can use. Convert for the fields you need and keep the .vcf if the photos matter.

Can I convert a file that has some damaged cards in it?

+
Yes. We report the structural problems and still convert everything that parsed, because a partial list beats being told to fix the file yourself. Check the preview rows before relying on the output.

Why are some fields missing from every preset?

+
Extension properties, the ones starting with X-, were never standardised, so no spreadsheet column exists for them. Social profiles are the usual example. The tool lists which ones your file contains so nothing disappears without you knowing.

Will this let me merge two address books?

+
It gets you halfway. Convert both files, paste one sheet under the other, then sort by email and remove duplicates in the spreadsheet where you can see what is being dropped. Automatic merging guesses, and guessing wrong loses a contact quietly.

Do I get one row per contact or per phone number?

+
One row per contact, always. Some converters produce a row per property, which makes a tidy-looking file that no address book can import. If you need the property-level detail, open the file in the viewer instead.

The file came from an old phone and the names look wrong. Can that be fixed here?

+
Not reliably, and it is worth knowing why. Old vCard 2.1 exports store non-English text in an encoding later versions dropped, so the damage is in the source file rather than the conversion. Re-exporting from the original device in a newer format is the only clean fix.

Is my address book uploaded to convert it?

+
No. The .vcf is read with the browser file reader and the CSV is assembled in the same tab. You can watch the network panel while you do it — nothing goes out, and that is the reason this page exists at all.

Related Tools You Might Like

Advertisement