Convert vCard (.vcf) to JSON
Convert phone-exported .vcf contact files to clean JSON in your browser. Folded lines, quoted-printable and multi-values decoded — never uploaded.
Drop a vCard (.vcf) file — get JSON
or click to choose · parsed on your device, never uploaded
Parsing contacts…
Decoding quoted-printable, folded lines and multi-values
Rollphy Pro lifts the file limit and unlocks batch mode.
Drop the .vcf file your phone exported and get every contact as structured JSON: name, organization, phones, emails, addresses, notes, photos' metadata — each property in a predictable array with its type parameters attached, ready for scripts, imports or deduplication.
The parser handles the messy reality of vCard files from real phones: folded lines (long properties split across lines), quoted-printable encoding (=E2=80=A6 and soft line breaks), BASE64 photos and logos, multi-value fields (itemized tel;type=cell entries), grouped Apple properties (item1.TEL), and escaped commas and semicolons in values.
Card boundaries are recovered even from slightly damaged exports — a missing END:VCARD doesn't strand the contact if it has an identity (FN or N). Output is pretty-printed JSON you can download as a file or paste into the JSON formatter. Everything is parsed locally; your address book never leaves your device.
Frequently asked questions
- My .vcf has hundreds of contacts — all of them?
- Yes. A single vCard file usually contains many BEGIN:VCARD…END:VCARD blocks (one per contact) and they all come back as an array of objects, in file order.
- Why does some text arrive garbled like =E2=80=A6?
- That's quoted-printable encoding from older phone exports. The converter decodes it automatically, so the JSON shows the real characters. If you see =XX sequences in the output JSON, the property itself wasn't flagged QP in the file.
- Are my contacts uploaded?
- No. Parsing runs entirely in your browser tab. An address book is among the most sensitive data you have — it never leaves your device here.