Online JSON to vCard Converter
Convert JSON contact data to VCF (vCard). Paste a contact object or list, or choose a JSON file, then map names, phone numbers, emails, and other supported fields. Review the generated contacts and download a .vcf file.
Conversion focus
Map JSON contact fields, preview the vCard output, and download your contact file.
Map each VCF field to a normalized table column. Use Include to choose output lines; Check all / Uncheck all sit under the mapping table. You can duplicate TEL / EMAIL / ADR to output multiple entries.
| # | VCF Field | Mapping | Include | Others |
|---|---|---|---|---|
| Provide input above to load mapping options. | ||||
What this conversion is for
Map JSON contact fields, preview the vCard output, and download your contact file.
- Choose the JSON fields to include in each contact using the mapping table.
- Multiple TEL/EMAIL lines can be duplicated when cards carry several numbers.
- Accepts a single contact object or a list of contacts.
Contact mapping: names, phones, emails
- FN (formatted name) anchors each card; ORG and TITLE are optional but common.
- TEL and EMAIL can repeat with types (work, cell) when your JSON lists multiple entries.
- ADR maps structured address lines—use separate columns when the exporter splits components.
- Photos and complex fields may be omitted from the generated vCard 4.0 output.
Use this output next
Dedupe and CRM cleanup in a grid.
Apps and directory sync.
Spreadsheet review of contacts.
Stage contacts for import.
Suggested workflow
Paste a contact object or list, or choose a JSON file.
Confirm the document parses—property names must be unique and JSON must be valid.
Map names, phone numbers, emails, and other supported fields in the mapping table.
Review the generated contacts and download a .vcf file.
Before you convert
- Use valid JSON with double-quoted property names and no trailing commas. Keep property names unique within each object so values are not overwritten or interpreted inconsistently.
- Duplicate TEL/EMAIL mapping rows add more numbers on the same card—not extra contacts. Structured N uses Family;Given;;; with unescaped semicolons.
- A blank name still exports; the card uses the placeholder “Contact.” Prefer real FN values when you can.
Choose the right output
When to use vCard
- Use vCard when your destination contact app accepts .vcf files.
- JSON from a directory API must become importable cards with FN/TEL/EMAIL.
- Each object represents one person or organization card.
- You reviewed mapped fields before downloading the .vcf.
When not to use vCard
- Bulk events belong in ICS, not contact cards.
- Data science paths want CSV/JSON, not vCard folding rules.
- When you only need printable directories, PDF may beat vCard bundles.
- Directory sync (LDAP/SCIM) beats manual vCard drops at enterprise scale.
Why use ConversionTab?
- Runs in your browser — privacy-first; sensitive JSON stays on your device until you copy or download.
- No uploads required — paste or pick a local file; nothing is sent to a conversion backend for the transform itself.
- Map, preview, download — choose fields in the mapping table, review the result, then copy or save the file.
- Built for everyone — clear steps for non-technical reviewers and power options for engineers.
Continue with other formats
Calendar files for mailbox import instead of VCF.
Typed spreadsheet review instead of VCF.
Executable load scripts instead of VCF.
Flat pipelines and spreadsheet handoffs instead of VCF.
Schema-heavy integrations instead of VCF.
Reviewed JSON → vCard notes
Long-form FAQs live below—expand a section when you need edge cases or field rules.
- Paste a contact object or list in the Text tab, or upload a JSON file. Use Load Sample if you need demo data.
- Confirm the JSON parses, then map properties to FN, TEL, EMAIL, and optional N/ADR.
- Use + on TEL/EMAIL/ADR for extra fields on the same card. Flatten or pick a repeating table when each array item should become its own contact.
- Structured N uses
Family;Given;;;with unescaped semicolons. Blank names export as Contact. - Select Convert, then copy or download the
.vcf. Use Clear to start over.
Turn JSON contact objects or lists into a downloadable .vcf file for address books.
Paste or upload JSON, map properties to FN/TEL/EMAIL (and optional N/ADR), then convert. Use + on TEL/EMAIL/ADR for extra fields on the same contact. Blank names export as Contact.
JSON 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 JSON data. Review the output before importing it into another system, especially when the destination expects strict columns, dates, or contact fields.
Help
Questions before converting
One question per row — expand only what you need.
Paste a contact object or list, or upload a JSON file. Map fields to FN/TEL/EMAIL (and optional N, ADR), select Convert, then copy or download the .vcf.
+ on TEL, EMAIL, or ADR adds another field on the same contact. It does not create extra people. − removes a duplicated mapping row.
Use the mapping table for several phones/emails on one card. When each array item should be its own person, flatten or pick the repeating table first so each item becomes a row.
Use Family;Given;;; with semicolons as separators. Those separators stay structural in the vCard.
The card still exports with the placeholder name Contact when no usable name is mapped.
Use Load Sample and Clear—there is no separate Example button on this page.
No. Conversion runs in your browser on this page.
Explore more conversions
Same goal, other inputs
SQL people data compiled into VCF for handset import.
XLSX people data compiled into VCF for handset import.
XML people data compiled into VCF for handset import.
CSV & workbook bridges
Workbook to pipeline text.
Tree to grid for review.
Spreadsheet-first path to the same shape.
Exports & delivery
Web table fragment.
Printable pack from the same source.