Inspect a separate local copy of your VCF before letting a contact app save it. On Windows 11, show file name extensions, right-click the copy, choose Open with > Choose another app, and select installed Notepad to read it without editing, saving or importing.
Start with the text, even when a prettier viewer is waiting. An attachment that looks like one person's contact card can contain a second person, a second work number and details the preview never shows.
Open the copy in Notepad first
Start with a downloaded .vcf file, Windows 11 and Notepad installed. Preserve the original and make a separate copy for inspection. Microsoft documents how to show file name extensions: in File Explorer, select View > Show > File name extensions. Confirm that the copy has the .vcf extension before opening it.
Right-click that copy and choose Open with > Choose another app. Select Notepad from the installed apps. If you need to locate the installed editor, use Choose an app on your PC. Use Notepad for this inspection. Don't change the default app association or double-click the file into an address book.
Read, then stop. Leave the text alone and close without saving changes. The copy protects your original; closing without saving preserves the copy. Those are safeguards you choose. Notepad doesn't enforce them. This route doesn't promise automatic validation or successful handling of every file size or encoding.
The raw text gives you something to compare with a viewer. If you need the broader explanation of the format and its other uses, the VCF format guide covers that next question.
One file, two people, several details
The vCard 4.0 specification allows one or more vCards in one content entity. Count the contact blocks, not the attachments.
Here is a fictional sample containing Ren Ito and Amélie Martin. It illustrates the format; it isn't a tested export from a phone or contact app. The visible newlines make it readable here. An actual vCard 4.0 file uses UTF-8 and CRLF line endings.
BEGIN:VCARD
VERSION:4.0
FN:Ren Ito
N:Ito;Ren;;;
TEL;VALUE=uri;TYPE=cell:tel:+1-202-555-0147
TEL;VALUE=uri;TYPE=work:tel:+1-202-555-0161
EMAIL;TYPE=work:[email protected]
EMAIL;TYPE=home:[email protected]
NOTE:Fictional sample contact.
END:VCARD
BEGIN:VCARD
VERSION:4.0
FN:Amélie Martin
N:Martin;Amélie;;;
TEL;VALUE=uri;TYPE=cell:tel:+1-202-555-0182
EMAIL;TYPE=work:[email protected]
END:VCARDThere are two BEGIN:VCARD and END:VCARD pairs. The expected contact count is 2, with Ren first and Amélie last. BEGIN opens each record, END closes it, and VERSION:4.0 immediately follows each BEGIN. FN is the required formatted name, the name you'd expect to see on the displayed card.
N has a different job: it separates family name, given name, additional names, honorific prefixes and honorific suffixes, in that order. N:Ito;Ren;;; therefore means family name Ito and given name Ren, with the other three components empty. N:Martin;Amélie;;; follows the same pattern. Each line has four unescaped structural semicolons. The trailing empty components are part of the structure, not stray punctuation to tidy away.
TEL introduces a telephone value. VALUE=uri says that value is a URI, and tel: introduces the telephone URI itself. TYPE=cell labels the mobile number; TYPE=work labels the work number. Ren has mobile +1-202-555-0147 and work +1-202-555-0161. Those are two distinct values, not alternative spellings of one number. Amélie has one mobile number, +1-202-555-0182.
EMAIL introduces an email address. Ren's TYPE=work entry is [email protected] and the TYPE=home entry is [email protected]. Amélie's work email is [email protected]. NOTE is Ren's note, “Fictional sample contact.” It doesn't create a third contact. The accent in Amélie's name is intentional and belongs in the comparison too.
Make the viewer earn the real file
Use the fictional two-contact sample above as a separate, nonsensitive sample file before giving a candidate viewer your real address book. First inspect the local source as text so you know what you're asking the display to preserve. The comparison follows the RFC's record and field structure; it isn't a compatibility result from testing these apps.
Clear any display filter before judging the count. You should see two contacts, Ren Ito and Amélie Martin, with the family and given names intact. Then look past the headline name: Ren needs both the mobile and work numbers and both the work and home emails. Check Amélie's accent, mobile number and work email, and check Ren's note. Ren's name and one phone number make a tidy card, but an incomplete comparison.
If the viewer shows one person or drops the work number, compare the raw sample's block boundaries and VERSION lines. Also account for folded lines: under the specification, a physical line beginning with whitespace can continue the preceding content line. One visible line isn't always one complete field.
If the sample doesn't match, try another viewer with documented support using the same nonsensitive file. If the problem is in the real file, ask the sender for another export. Keep the original unchanged. A matching sample tells you how those particular fields displayed; it doesn't establish complete file validity, privacy, handling of malformed records, photos or vendor extensions.
Choose a reader by what it does with the file
A text editor shows what's present directly. A parsed viewer makes it easier to read, provided it preserves the fields you're checking. Installation and a tidy interface aren't evidence of either privacy or fidelity.
| Method | What you can inspect | What to establish before using the real file |
|---|---|---|
| Local text editor | Raw boundaries, VERSION and visible field lines, including repeated values | Read without edits or Save. Recognizable text isn't validation or a promise of a visible photo. |
| Installed parsed viewer | A more readable contact display | Check the app's documented processing, version support and save behavior. Installation alone establishes none of these. Compare the fictional sample first. |
| HiFi Toolkit browser viewer | Its advertised Cards or Table display for multiple contacts | Treat its processing and version statements as vendor claims. Compare only the nonsensitive sample before considering real contacts. |
HiFi Toolkit says its VCF Viewer processes in browser memory, doesn't upload contacts to servers, supports vCard 2.1, 3.0 and 4.0, and displays multiple contacts. These are its published statements, checked in October 2026, rather than an independent network or privacy audit or a successful version test. A hosted browser page doesn't establish that the viewer loads or works without a connection.
Its documented viewing route is Open VCF / vCard, select the fictional sample file, then use Cards or Table to compare the display. Stop there for inspection. CSV or JSON export and address book save or import are separate actions.
If a viewer's processing, supported version or save behavior is unclear, keep the file local and continue with the text copy. You don't need to settle the privacy question to read the source locally without sending it to a viewer.
Check what your own file adds or loses
After the sample comparison, return to the real file's local copy. Using the RFC's vCard field definitions, count paired BEGIN and END blocks and read the VERSION. Identify the first and last records, then inspect every repeated TEL and EMAIL value. Compare those details with the parsed display only once you're satisfied with the viewer's handling and processing.
Paired boundaries help you inspect; they don't certify the file. A truncated block, missing END, absent required FN or missing VERSION is a reason to stop and request a fresh export. Don't add guessed lines to make a preview look complete. If the file or viewer still fails, the VCF troubleshooting guide covers fuller recovery.
Your export may also contain ORG for organization, TITLE for a title, ADR for an address, URL for a web address, NOTE or PHOTO. PHOTO is a URI property, so recognizing it in text doesn't promise a visible image in the viewer. Properties beginning with X can hold extensions; seeing one in the source doesn't show that another app renders or retains it.
If a photo, note or X field matters, compare that exact field with the parsed display using a nonsensitive sample representative of the real export. The two-person example above has no photo or X field, so it can't answer those questions. If the field disappears or its treatment is undocumented, preserve the source and ask for a supported export.
A low displayed count doesn't always mean the file lost a person. Microsoft says Outlook for Microsoft 365 for Mac, Outlook 2024 for Mac and Outlook 2021 for Mac show only the first contact in the window when a VCF contains multiple contacts, while each contact is saved individually. That window isn't a reliable source count. Stop before Save & Close.
Stop at the address book boundary
Apple's Mac Contacts instructions use Add to commit the import. Google Contacts on a computer uses Import to add the VCF. Microsoft's classic Outlook instructions end with Save & Close. These are decisions to add contacts, not reader controls.
On iPhone, Apple's iOS 26 guidance puts tapping a VCF attachment in email or a message under importing contacts. Don't assume that tapping the attachment is the same inspection action as opening a text copy. Google Contacts on Android likewise documents Import from file, including choosing a destination account when several are configured. Apple says a vCard with several people produces separate iCloud contact entries when imported; Contacts on iCloud.com requires a tablet or computer.
If you've already imported into Google Contacts and can't find a detail, Google's help says to check the contact's Notes section. Compare it with your preserved source before deciding the detail has vanished.
Once you've checked the contents and chosen where the contacts should go, follow the VCF opening and import guide. For now, close the inspection copy without saving. The address book can wait.
For a later decision to share your own live profile, Zapped's public page describes sharing by link, QR code or NFC, opening in a normal browser and keeping the card current after edits. That helps with sharing your own details later. Reading or importing this VCF still belongs to the file reader and contact app you choose.
