How does it name the output files?

Each file is named after the contact's FN (formatted name) property. If FN is missing, it falls back to the N structured name, then ORG, then EMAIL, and finally a generic contact number. Characters that aren't safe in file names are replaced.

What if two contacts have the same name?

Identical file names would collide, so the splitter appends a numeric suffix (for example name_1.vcf, name_2.vcf) to keep every download distinct.

Does splitting change the contact data?

No. Each output file contains the original BEGIN:VCARD … END:VCARD block exactly as it appeared, just isolated into its own file. Properties, photos and encodings are preserved byte for byte.

Why download files separately instead of a zip?

Building a zip in the browser would require a compression library, which this tool avoids. Instead it triggers each download in sequence with a brief delay so browsers reliably save every file.

Is my address book uploaded?

No. The whole split happens locally with the File API. Your contacts are never sent to a server, so the tool is safe for personal and work address books alike.

What is the vCard Splitter?

Split a single .vcf file containing many VCARD blocks into one .vcf per contact, each named automatically after the contact's FN (with N, ORG or EMAIL fallbacks). Runs entirely in your browser via the File API — no upload. It runs free in your browser on Gera Tools, with nothing uploaded.

vCard Splitter — Gera Tools

Name: vCard Splitter
Creator: Gera Tools
License: https://creativecommons.org/licenses/by/4.0/

When you export contacts from a phone or an email client you usually get a single .vcf file with every contact packed inside, one BEGIN:VCARD … END:VCARD block after another. Some systems — older CRMs, certain mail clients, smart-watch apps — want one file per contact instead. This splitter takes the combined file and produces an individual, correctly named .vcf for each contact.

How it works

The splitter scans the file for BEGIN:VCARD and END:VCARD markers and isolates each block, keeping its original lines intact (including folded continuation lines and any embedded photo data). For naming, it unfolds each block and reads the contact’s identity in priority order:

FN — the formatted display name, the preferred source.
N — the structured name (Family;Given;…), assembled into “Given Family” if FN is absent.
ORG — the organisation name, for company-only cards.
EMAIL — used as a last resort before a generic contact-N fallback.

The chosen name is sanitised into a safe file name: characters that are illegal in file names are removed, spaces become underscores, and the result is capped in length. If two contacts resolve to the same file name, a numeric suffix keeps them separate.

Where combined VCF files come from

Android: Contacts app → Import/Export → Export to .vcf → saves a single file with all contacts.

iPhone: Exporting all contacts at once requires iCloud — open iCloud.com, go to Contacts, select all, and export. This produces a single .vcf. Individual contact exports from the iOS Contacts app each produce a separate file, but exporting a large address book one at a time is impractical.

Outlook / Exchange: File → Open & Export → Import/Export → Export to a File → vCard (.vcf). Outlook exports one file per contact through this path, but some third-party plugins and migration tools bundle everything into one combined file.

macOS Contacts: File → Export → Export vCard exports selected contacts into a single combined .vcf, regardless of how many you selected.

Using the output

Each contact gets a Download and a Copy button, and a single “Download all” button triggers every file in sequence. The downloads are spaced a fraction of a second apart so browsers don’t silently drop later files in a burst — a common quirk when many downloads fire at once.

What imports an individual VCF

Once split, individual .vcf files can be imported into:

Gmail / Google Contacts: Contacts → Import → select the .vcf file.
Outlook: File → Open & Export → Import/Export → Import a vCard (.vcf) file.
iPhone: AirDrop or email the file to yourself; tapping it offers “Add to Contacts.”
CRM systems (Salesforce, HubSpot, etc.): Most accept .vcf upload via their contact import workflow, though field mapping varies by system.

Notes

The original card content is never modified — splitting only changes how the cards are packaged, not what they contain.
Cards with no recognisable name still split cleanly; they simply receive a contact-N file name.
vCard versions 2.1, 3.0, and 4.0 all use the same BEGIN:VCARD / END:VCARD structure, so the splitter handles all three.
Because everything runs in your browser, the tool is safe for large, sensitive address books — nothing is uploaded.