An address book is good at finding one person. It is poor at answering questions about all of them. How many contacts lack a phone number? Which contacts have no organisation listed? How many entries share the same email domain? Those are spreadsheet questions, and they need the contacts in spreadsheet shape: one row per person, one column per field. Contacts export in .vcf format, a plain-text standard where each person is a card of labelled lines. Converting that file to CSV turns each card into a row, without changing the underlying information.
The iCloud Contacts VCF to CSV Converter tool converts contacts data you paste or upload yourself into a CSV file. It never connects to an iCloud account, never logs in, never syncs, and never fetches anything from Apple. It works only on the local file or text you provide, in your browser. Your original export is not changed, and the CSV is a new file you can open in a spreadsheet application.
How the conversion works
A .vcf file is a sequence of cards, each wrapped in begin and end markers, with lines for the formatted name, telephone numbers, email addresses, and organisation, among others. The converter reads each card and extracts four fields: name, phone, email, and organisation. Those become the four columns of the CSV, in that order, with a header row naming them. A card without an organisation gets an empty cell in that column; the row is not dropped, because a contact without a company is still a contact.
A card can hold more than one phone number or email address, for example a mobile and a work number. The converter's four-column shape cannot hold an unlimited list in one cell without ambiguity, so it takes the values its design provides for and writes them in the corresponding columns. If your workflow depends on secondary numbers or addresses, keep the original .vcf file as the complete record, because the CSV is a working view of the main fields, not a full copy of every line in the card.
Text handling follows the usual CSV rules. A name or organisation containing a comma, such as "Lovelace, Ada" or a company name with a comma in it, is quoted so it stays in one cell instead of splitting across two columns. When you open the result, use your spreadsheet application's CSV import dialog and confirm comma as the delimiter, rather than double-clicking the file and letting the application guess. A wrong guess about delimiters or encoding is the most common reason a converted file looks broken when the conversion itself was fine.
A worked example
Take a single card for Ada Lovelace, with phone +1-555-0100, email ada@example.com, and no organisation. After conversion, the row reads: Ada Lovelace, +1-555-0100, ada@example.com, with the final organisation cell empty. Open that row in a spreadsheet and the audit questions become trivial: filter the phone column for empty cells to find contacts without numbers, sort by name to spot near-duplicates sitting beside each other, or filter the email column for a particular domain to list everyone at one company.
A second example shows the value for cleanup. Convert a full export of several hundred contacts and sort by email. Duplicate email addresses will sit adjacent in the sorted list, which makes them visible in a way an address book search never does. Sort by name and look for the same person spelled two ways, such as "Jon Smith" and "John Smith": they will not sit adjacent unless the spelling matches, which is itself a useful reminder that CSV sorting finds exact matches, not fuzzy ones. For fuzzy duplicates, the dedicated duplicate cleaner is the better tool, and the CSV is the better way to verify its result.
Before relying on the CSV, run three checks. First, compare the row count with the card count in the original file: every card should produce one row, plus the header. Second, look at the first and last rows and confirm they match cards you recognise. Third, find a row with a comma in a name or organisation and confirm it occupies one cell, not two. If any check fails, revisit the import settings before analysing further.
Common mistakes
The first mistake is treating the CSV as a complete backup. It holds four fields per contact; the original file may hold more, including additional numbers, addresses, birthdays, and notes. Keep the .vcf file as the record of truth. The second mistake is editing the CSV and expecting the address book to follow. The conversion is one-way: changes in the spreadsheet do not flow back into contacts, so correct important changes in the address book itself, or the next export will restore the old values.
The third mistake is letting the spreadsheet guess the import settings, which can split columns or garble characters in names. Always use the import dialog and confirm the delimiter and encoding. The fourth mistake is sharing the CSV casually. A contacts export is personal data belonging to other people as well as you: names, numbers, and emails in one portable file. Store it carefully, share it only where necessary, and delete working copies when the task is done.
Honest limitations
This tool converts .vcf contacts data you paste or upload into a CSV with four columns: name, phone, email, and organisation. It never accesses an iCloud account, never logs in, never syncs, and never downloads anything from Apple. It does not preserve fields outside those four columns, so additional numbers, addresses, birthdays, notes, and photos are not carried into the CSV. It does not write changes back to an address book, and it does not merge or deduplicate cards; that is a separate step. Cards with unusual or malformed lines may convert approximately, so compare row counts with the original export before analysing the result.
Closing
Convert to CSV when you need to sort, filter, or audit, and keep the original export as the complete record. For the surrounding workflow, preview contacts as a table with the iCloud Contacts VCF Viewer tool, split or combine contact files with the VCF Merge and Split Tool tool, and read our guide How to Clean and Transform CSV Files to handle the converted data well.