Convert JSON to VCF
Convert JSON to VCF instantly in your browser. Free, fast, and private - your files are processed locally on your device.
Drop your JSON files here
Up to 5MB per file.
Column mapping (optional)
Files never leave your browser
How to Convert
- 101
Upload your JSON files
Drag and drop or select JSON files from your device. You can upload multiple files at once.
- 202
Configure Output
Choose any available VCF output options, then start the conversion.
- 303
Download VCF files
Once conversion finishes, download your files individually or as a compressed ZIP archive.
Why convert JSON to VCF?
Convert JSON files to VCF locally, with no file upload or account required.
Clear validation protects against duplicate headers, unsupported structures and oversized files instead of quietly discarding data. See the format notes below before importing the output into another application.
Frequently Asked Questions
Which JSON contact layouts can I import?
Use an object or list of objects with fields such as Full Name and Email, or the jCard component arrays produced by VCF to JSON. A Full Name or FN value is required. Arbitrary nested address-book schemas need preparing first.
How do I preserve multiple emails and their types?
Use jCard input for structured properties and parameters. In a flat record, use separate raw headers such as EMAIL;TYPE=HOME and EMAIL;TYPE=WORK, or EMAIL and EMAIL [2] for repeated properties.
How do I convert JSON to VCF?
Select a file up to 5 MB, start the conversion, and download the result. Processing runs locally in your browser. Table conversions support up to 20,000 records, 256 columns and 200,000 cells.
Are my files uploaded?
No. This converter processes the file in a local browser worker. File contents are not sent to the conversion server, and the file is not used to train AI.
How do I map my columns?
A Full Name or FN field is required. Friendly headers include Email, Phone, Mobile, Company, Notes and Website. Open optional Column mapping to rename your source headers. Raw vCard headers retain their escaped values; repeated fields use numbered headers such as EMAIL [2]. Quote phone numbers as text in the source spreadsheet.
Are repeated contact details preserved?
vCard 3.0 and 4.0 files are supported. Repeated properties have separate numbered columns, and property parameters remain in the headers. JSON exports use jCard-compatible component arrays and can be imported again. Legacy quoted-printable or non-UTF-8 contacts must be exported as UTF-8 first.
How are data types and spreadsheet safety handled?
Table text is kept as text, including leading zeros. XLSX output uses text cells rather than executable formulas. CSV/TSV fields beginning with formula-like characters receive a leading apostrophe for spreadsheet safety; choose XLSX or JSON if you need exact literal values. Nested table values use JSON text rather than ambiguous flattened field names.