Convert VCF to JSON
Convert VCF to JSON instantly in your browser. Free, fast, and private - your files are processed locally on your device.
Drop your VCF files here
Up to 5MB per file.
Files never leave your browser
How to Convert
- 101
Upload your VCF files
Drag and drop or select VCF files from your device. You can upload multiple files at once.
- 202
Configure Output
Start the conversion. Crest Convert will prepare the JSON file using the appropriate format engine.
- 303
Download JSON files
Once conversion finishes, download your files individually or as a compressed ZIP archive.
Why convert VCF to JSON?
Convert VCF files to JSON locally, with no file upload or account required.
Contact exports preserve repeated properties and their type parameters. Choose JSON for structured contact data or a spreadsheet for reviewing fields.
Frequently Asked Questions
Is the result a simple name-and-email JSON list?
No. It is an array of jCard-style component arrays. Each property retains its name, parameters, value type and values, which preserves more information than reducing a contact to a few fixed fields.
Are contact photos downloaded from linked URLs?
No external photo or address-book resources are fetched. A photo property is retained as data or a reference in the JSON, within the file and output limits.
How do I convert VCF to JSON?
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.
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.