View and edit vCard (.vcf) contact files with photo display and field editing.
This page parses a vCard (.vcf) file - the interchange format for phone and email address books - and shows every stored field as an editable form: name, phones, emails, addresses, org, notes, and the contact photo. Paste the text or load the file; each BEGIN:VCARD block becomes a card you can edit and re-export. The usual surprise: one .vcf is rarely one contact - address-book exports routinely pack hundreds of cards into a single file, and long lines are folded at 75 octets with a leading space, so raw text looks mangled but parses cleanly.
A concrete input and expected output from the current implementation.
Input
BEGIN:VCARD VERSION:3.0 FN:Ada Lovelace N:Lovelace;Ada;;; TEL;TYPE=CELL:+44 20 7946 0958 EMAIL:[email protected] END:VCARD
Expected output
One card renders: name Ada Lovelace (from FN), structured name Lovelace / Ada (from N), phone +44 20 7946 0958 with type CELL, email [email protected], format VERSION 3.0, and an empty photo area.
The card has five properties and the display is a direct transcription of them: FN supplies the display name, N the split surname and given name, TEL and EMAIL their values with the TYPE parameter kept as the phone label, and no PHOTO line means no photo. VERSION tells the parser which dialect to apply.
This tool reads pasted or loaded text as a sequence of BEGIN:VCARD...END:VCARD blocks, one card each - an address-book export of 1,000 contacts becomes 1,000 cards. It unfolds folded lines (content split at 75 octets and continued with a leading space), separates each property's parameters from its value, and decodes payloads such as base64 photos and vCard 3.0 quoted-printable text.
Edits map onto the card's properties, not free text: changing the formatted name updates the FN property, a new phone number adds a TEL line with its own TYPE parameter, and removing a field deletes its line. Export re-serializes each card with its VERSION property intact, so the file keeps the dialect the address book it came from expects.
Yes - each BEGIN:VCARD block is a separate card, and you edit cards one at a time while the rest of the file is left untouched. All parsing happens locally in the browser, so nothing is uploaded. The tool hands back a file in the same multi-card form, ready to reimport where the original export came from.
Most often the file has no PHOTO property at all - the picture you remember lives in the address book, not in the card. When PHOTO exists, it is either inline base64 (which this page decodes) or a URI such as PHOTO;VALUE=URI:https://..., which needs a network fetch. Truncated base64 also fails to decode; in those cases the image simply does not render.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Convert CSV data into structured JSON arrays or objects with automatic type detection.
Transform JSON arrays and objects into downloadable CSV spreadsheet format.
Convert YAML configuration files to JSON format with validation and formatting.
Parse XML documents and convert them to equivalent JSON structure with attributes.
Convert tab-separated values to comma-separated format with proper escaping.
Convert numbers between binary, octal, decimal, and hexadecimal bases.