Choose a contact file
Open a UTF-8 .vcf or .vcard export, up to 3 MB.
Read contact exports without importing them.
VCF to JSON
Parse vCard 3.0 and 4.0 contacts into structured JSON with names and arrays for phones, emails, addresses, URLs and notes.
The JSON keeps multiple values and their type labels without spreadsheet formatting.
vCard ViewerYOUR WORKSPACE
Your task
Download JSON
Choose a file, then use Download JSON to save the result.
Also with this file: View contacts · Download CSV · Download Excel
Processed privately in your browserNo uploadNo signup
A simple workflow
Three steps. One less thing to do.
Inspect the contacts
Review names and field rows, including repeated phone numbers and email addresses.
Download a structured copy
Save field-oriented CSV, a two-sheet Excel workbook or JSON.
Made for the everyday
A useful part of your workflow.
Contact backup review
Check the people and fields in a vCard export before importing it.
Spreadsheet preparation
Use a stable one-row-per-field CSV or two-sheet Excel workbook.
Structured data migration
Keep repeated values and type labels in a normalized JSON document.
Good to know
A few useful answers.
The details that matter before you use vCard Viewer.
Which vCard versions work?
This version supports UTF-8 vCard 3.0 and 4.0. Legacy vCard 2.1 and quoted-printable fields are not accepted.
Are multiple phones or emails preserved?
Yes. Each repeated value is shown and exported separately with its type and source order.
What does CSV contain?
CSV uses one row per populated contact field with a contact number, field name, index, type and value. This avoids silently dropping repeated values.
What does Excel contain?
Excel has Contact fields and Contacts sheets. All contact values are written as text cells.
Are embedded photos exported?
Photo content is not exported. JSON records only photo metadata where present.
Does the file leave my device?
No. Parsing and exports run in the browser. Contact details and filenames are excluded from analytics.
What are the limits?
Files must be UTF-8 text up to 3 MB with at most 5,000 contacts. Unsupported encodings and variants fail clearly.