To create a VCF file for multiple contacts, you build a list of contacts and export them together, either as one combined .vcf or one file per contact. You can do it by hand in a text editor by typing each contact between a BEGIN:VCARD and END:VCARD line, but that is slow and easy to break once you pass a couple of contacts. A vCard generator like the Univik VCF Generator does it from a form. You add each person, pick a vCard version and export the whole group in one step, with the correct format written for you.
Why Creating Many vCards by Hand is Painful
One vCard is easy. Twenty is a different story. A VCF file is plain text, so in theory you can type a contact in Notepad and save it with a .vcf extension. In practice, every field has a strict format, long lines have to be wrapped a specific way and a single misplaced character can stop the whole card importing.
Now multiply that by a team, a class list or a set of event contacts. You are repeating the same fiddly structure for every person, fixing up every comma in every address by hand and hoping you did not fumble a line somewhere in the middle. Online generators do not really solve this either, because most build one card at a time and send your contact details to a server to do it.
The task people actually have is simple to describe. You want to make multiple vCards at once from a list of people and end up with either one file that holds them all or one vCard file per contact. The trick is doing that without hand-writing vCard code, which is exactly the problem when you bulk create vCards for a whole team.
Three ways to Create a VCF file for Multiple Contacts
The right way to create a VCF file for multiple contacts depends on where your contacts start. There are three real approaches, and they suit different starting points. Here is how they compare.
| Method | Best when | Catch |
|---|---|---|
| Desktop vCard tool | You are building cards from contact details you have in hand | Needs an app, free demo is capped |
| Manual text editor | You only have a couple of simple contacts | Slow and easy to corrupt at scale |
| Online generator | A single quick card | One at a time, your data leaves your PC |
If your contacts already sit in a spreadsheet, none of these is the right path, you want a converter instead, which we cover near the end. For building cards from a list of people, a desktop generator is the direct route. Let me walk through it.
The Direct way: Build a Contact List in a Desktop Tool
A desktop tool turns a plain form into valid vCards, which is the simplest way to create a vCard for multiple contacts at speed. You type each contact into clear fields, the app writes the correct vCard property behind every one and you export the lot together. No BEGIN:VCARD blocks to type, no long lines to wrap, no special characters to fix by hand.
The Univik VCF Generator works this way on Windows, fully offline, so your contact details never leave your PC. Here is the full process in three steps.
Step 1: Add Each Contact to the List
Fill in the form for the first person, the name, phone numbers, email, postal address, company, job title and anything else you need, then add them to the list. The form covers the fields a real contact uses, including photo, birthday, website, nickname, categories and notes, and a live preview shows the finished vCard building as you type.
Repeat for each person. You are not saving a file yet, you are building a list inside the app, so you can add as many contacts as you need before you export anything.
Step 2: Pick a vCard Version
Choose the vCard version your target app expects. This matters more than people realise, because the version controls the format, and the wrong one is a common reason an import fails.
One practical note worth knowing. Android’s built-in contact export often produces vCard 2.1, which can fail to import on a modern iPhone, so 3.0 is the safer choice when a file has to work across both. A good tool writes the correct format for whichever version you choose, from the phone type tags to the photo encoding. For the full background on the differences, see our guide to vCard 2.1, 3.0 and 4.0.
Step 3: Export the Whole Group
Once your list is complete, export it. This is where the bulk job is won or lost, and where a desktop tool pulls ahead of anything that works one card at a time. You get two output choices, and the right one depends on what you are doing next.
contacts.vcf.vcf for each person in one folderBuild a whole list of vCards without touching vCard code. The Univik VCF Generator creates clean .vcf files from a simple form, single or bulk, in vCard 2.1, 3.0 and 4.0, with photo and QR code support. The free demo creates up to 5 contacts so you can test it first.
One Combined file or One file Per Contact
This choice trips people up, so it is worth a moment. Both are valid VCF files, the difference is how the contacts are packaged.
A combined file holds every contact placed one after another, each in its own BEGIN:VCARD to END:VCARD block. It is the right pick when the goal is to move a whole address book at once, import everyone into a new phone or keep one tidy backup. The catch worth knowing is that a few apps and some webmail services import only the first contact from a multi-contact file, or cap how many they will read in one go, so a very large combined file does not always import cleanly everywhere.
One file per contact sidesteps that entirely. Each person becomes a standalone card, which is what you want when you are handing out individual contacts, importing into a CRM that takes one record at a time or deploying cards across a team. It is also the safer choice when you are not sure how the receiving app handles large multi-contact files.
A simple rule
If the contacts are going into one place all at once, use the combined file. If the contacts are going to different places or people, use one file per contact. A generator that offers both, like the Univik VCF Generator, lets you create the list once and export it either way without rebuilding anything.
Avoiding Import Problems with a Multi-Contact file
A file that holds many contacts can hit a few snags on import. All three are easy to avoid once you know them, and they are the reason the export choice above matters.
Only the first contact imports. A few apps, including some older Outlook versions and certain webmail services, read only the first card in a multi-contact file. If that happens, export one file per contact instead, or import into an app that reads them all, like Google Contacts. Our guide to VCF file errors covers more import failures.
Accented or non-Latin names come through garbled. This is an encoding problem. Save the file as UTF-8, which is what handles names outside the basic Latin set. See VCF encoding errors if names still look wrong.
The whole file is rejected. Usually the vCard version does not match the target app. Rebuild the file in the version the app expects, vCard 3.0 for most, 2.1 for very old devices, and try again.
None of these are problems with the contacts themselves, they are about how the file is saved. A tool that lets you re-export the same list in a different version or as one file per contact, without rebuilding it, turns each of these into a one-click fix.
The Manual Way: Building the file by Hand in Notepad
Because a VCF is plain text, you can create a multi-contact file by hand. It is free, and for two or three simple contacts it is fine. The idea is to write each contact as its own block and place them one after another in one file.
A single contact looks like this in vCard 3.0.
BEGIN:VCARD
VERSION:3.0
N:Rogers;Nick;;;
FN:Nick Rogers
TEL;TYPE=CELL:+1-555-0100
EMAIL;TYPE=WORK:nick@example.com
END:VCARDTo add more people, you paste another full block underneath, from its BEGIN:VCARD to its END:VCARD, for each contact. Save the file with a .vcf extension and UTF-8 encoding so accented names are not garbled.
Where the manual route falls apart
Every comma, semicolon and backslash inside a field has to be written a special way, or it splits the value. Long lines have to be wrapped a set way, and the limit is counted in bytes not letters, so a non-Latin name is not cut in the middle. Photos must be turned into Base64 text by hand. One wrong line and the card, or the whole file, fails to import. For more than a handful of plain contacts, this stops being worth it fast.
If you want to understand exactly how the format is put together, our explainer on VCF file structure breaks down every part of a vCard.
Already Have a CSV or Separate files?
Creating vCards from scratch is one job. If your contacts already exist in another form, a different Univik tool is the better fit, and using the right one saves you a lot of effort.
Contacts in a CSV or Excel sheet? You do not need to retype them. The VCF Converter turns a spreadsheet of contacts into vCards directly.
Many separate .vcf files to combine? The VCF Joiner merges them into one file without retyping anything.
One big file to break into singles? The vCard Splitter turns a multi-contact file into one card per contact.
Need to change contacts in an existing file? The VCF Editor opens any .vcf and lets you edit every field.
Already have the contacts in your phone or a Google or iCloud account? You do not need to rebuild them. Export them straight to VCF, see export Google contacts or export iPhone contacts.
The Univik VCF Generator is for the case those tools do not cover, building brand new vCards from contact details you have in hand, when there is no spreadsheet or existing file to start from.
Frequently Asked Questions
Can a single VCF file contain multiple contacts?
Yes. A VCF file can hold many contacts, each stored as its own block between a BEGIN:VCARD and END:VCARD line, placed one after another in the same file. Most phones and contact apps import every contact in the file. A few apps or webmail services read only the first contact or limit how many they accept at once, so for very large lists, one file per contact can be more reliable.
How do I create a VCF file with multiple contacts at once?
Build a list of contacts in a desktop tool, then export the list in one step. In the Univik VCF Generator you fill in a form for each person, add them to a list, pick a vCard version and save the group as either one combined .vcf file or one file per contact. You can also do it by hand in a text editor by typing each contact block, but that is slow and error-prone beyond a few contacts.
Should I save one combined file or one file per contact?
Use one combined file when you are moving a whole address book into a single place, like a new phone, Outlook or Google Contacts or keeping a backup. Use one file per contact when you are handing out individual cards, importing into a CRM record by record or deploying cards across a team. One file per contact is also safer if the receiving app struggles with large multi-contact files.
Do I need to know vCard code to create multiple contacts?
No. The right desktop tool writes the code for you. You fill in plain fields like name, phone and email, and the app maps each one to the correct vCard property in the background, then writes it in the correct format for the version you chose. You only need to type raw vCard code if you create the file by hand in a text editor, which is where most import errors come from.
Will a multi-contact VCF file import into iPhone and Android?
Yes, as long as the vCard version is right. vCard 3.0 imports cleanly into iPhone, Android, Google Contacts, Outlook and most other apps, so it is the safe default for a shared file. Very old devices may need 2.1. If an import drops contacts, try one file per contact or check that the file is saved as UTF-8 with the correct version.
Can I add a photo to each contact when creating multiple vCards?
Yes. A desktop tool can embed a photo in each vCard. The Univik VCF Generator accepts JPEG, PNG, GIF or BMP, resizes large images so the file stays small and writes the photo into the card with the correct encoding for your chosen version. Doing this by hand means converting each image to Base64 text yourself, which is impractical for more than one contact.
How many contacts can one VCF file hold?
There is no fixed limit in the format itself. A single VCF file can hold thousands of contacts, each in its own block, and the file stays small because it is plain text. The real limit comes from the app you import into, not the file, since some apps slow down or cap how many contacts they read at once. For very large lists, one file per contact is the safer route. Our guide to VCF file size goes deeper on this.
Why does only the first contact import from my VCF file?
Some apps read only the first card in a multi-contact file. Older versions of Outlook are the classic example, and a few webmail services behave the same way. The file is fine, the app is the limit. The fix is to export one .vcf file per contact instead of one combined file, or to import into an app that reads every card in the file, such as Google Contacts.
Can Outlook create one VCF file with multiple contacts?
Not directly. Outlook saves contacts as one .vcf file per contact and has no built-in option to bundle several into a single file. To get one combined file from Outlook contacts, export them to CSV first and convert the CSV to vCard, or build the cards from scratch in a desktop tool. This Outlook limit is a common reason people reach for a generator or converter instead of the built-in export.
Conclusion
Creating a VCF file for multiple contacts comes down to two things, building the list and choosing how to package it. Writing BEGIN:VCARD blocks by hand works for two or three simple contacts, but it gets slow and fragile fast, and online tools build one card at a time. A desktop generator lets you enter each person in a form, pick the right vCard version once and export the whole group as one combined file or one file per contact.
Match the export to the destination. Send everyone to one place, use the combined file. Send cards to different people or systems, use one per contact. Either way, the work is the same, you build the list once and let the tool write clean, valid vCards that import without errors.