vCard Format Complete Guide — VCF Files & Digital Business Cards (2026)

Business cards used to be simple. You handed someone a piece of card stock with your name and number on it. They either kept it, lost it in a jacket pocket, or threw it away. The information lived on paper, and if you changed your phone number, every card you'd ever given out became obsolete. The vCard format solved this problem thirty years ago — and it's more relevant today than ever. Whether you're embedding contact details in an email signature, generating QR codes for conference badges, or programming NFC tags for tap-to-save business cards, the underlying technology is the same: a plain-text file with a .vcf extension that every contacts app on every platform can read.

This guide covers everything you need to know about vCards — from the file format specification to practical implementation. You'll learn how to create VCF files manually, embed photos using base64 encoding, generate QR codes that open contact save dialogs on smartphones, program NFC business cards, and handle the subtle differences between how Apple and Google process vCard data. If you just want a working vCard file without writing code, use Byline's vCard generator — it handles all the formatting automatically.

1. What Is a vCard (VCF File)?

A vCard — short for "virtual card" — is a standardized file format for electronic business cards. The file uses the .vcf extension (Virtual Contact File) and contains structured contact information in plain text. When someone opens a VCF file on their phone or computer, their contacts app reads the structured data and offers to create a new contact entry with all the information pre-filled.

The format was originally created by the Versit Consortium in 1995 and is now maintained by the Internet Engineering Task Force (IETF). Despite being nearly three decades old, vCard remains the universal standard for contact data exchange. Every major platform supports it: iOS, Android, macOS, Windows, Outlook, Gmail, Thunderbird, and essentially every contacts application ever built. No proprietary app installations required, no accounts to create, no APIs to integrate — just a text file that works everywhere.

At its simplest, a vCard is just a text file with a specific structure. Here's the most basic valid vCard:

BEGIN:VCARD
VERSION:3.0
FN:Jane Smith
TEL:+1-555-123-4567
EMAIL:[email protected]
END:VCARD

That's it. Save those six lines as a .vcf file, email it to someone, and when they open the attachment their phone will offer to save Jane Smith as a contact with her phone number and email address pre-populated. The format is deliberately simple — human-readable, easy to generate programmatically, and universally parseable. The RFC 6350 specification defines the current standard (vCard 4.0), but many implementations still use the older RFC 2426 (vCard 3.0) for maximum compatibility.

vCards aren't just for email attachments. They're the data format behind QR code contact sharing, NFC business cards, the "Share Contact" feature on your phone, contact export/import in every address book application, and — relevant to this site — the downloadable contact files you can attach to email signatures. When you add a "Save Contact" button to your email signature, the underlying technology is a vCard file.

2. vCard 3.0 vs 4.0 — Differences That Matter

Two versions of vCard are in active use today: version 3.0 (RFC 2426, published 1998) and version 4.0 (RFC 6350, published 2011). Understanding the differences matters because the version you choose affects compatibility, feature availability, and how contact apps parse your data.

Which Version Should You Use?

For maximum compatibility, use vCard 3.0. It's supported by every contacts app on every platform, including legacy systems and older phones. Apple Contacts, Google Contacts, Outlook, and Thunderbird all handle 3.0 flawlessly. vCard 4.0 offers more features and cleaner syntax, but support is less universal — some older Android apps and corporate exchange systems don't fully parse 4.0 properties.

If you're generating vCards for a known audience (e.g., your company's internal contacts) and you know their systems support 4.0, use it for the better structure. If you're generating vCards for public consumption — email signatures, QR codes, NFC cards — stick with 3.0. The Byline vCard generator uses 3.0 by default for this reason.

3. Complete vCard Field Reference

vCard files use property-value pairs, one per line, to store contact information. Each property has a name, optional parameters, and a value separated by colons. Here's a comprehensive reference of the most commonly used fields with practical examples.

A complete real-world vCard combining these fields looks like this:

BEGIN:VCARD
VERSION:3.0
N:Smith;Jane;Marie;;
FN:Jane Smith
ORG:Acme Corp;Marketing
TITLE:Marketing Director
TEL;TYPE=WORK,VOICE:+1-555-123-4567
TEL;TYPE=CELL:+1-555-987-6543
EMAIL;TYPE=WORK:[email protected]
EMAIL;TYPE=HOME:[email protected]
ADR;TYPE=WORK:;;123 Business Ave;New York;NY;10001;United States
URL:https://acme.com
URL:https://linkedin.com/in/janesmith
NOTE:Marketing leader with 15 years experience in B2B SaaS.
REV:2026-03-10T12:00:00Z
END:VCARD

4. Creating a vCard Manually

You don't need special software to create a vCard. It's a plain text file. Open any text editor — Notepad on Windows, TextEdit on Mac (in plain text mode), VS Code, or even nano in a terminal — and start typing. The rules are straightforward but strict: each property goes on its own line, the file must start with BEGIN:VCARD and end with END:VCARD, and the VERSION property must be the first property after BEGIN.

File Encoding and Line Endings

Save the file with UTF-8 encoding. The vCard 4.0 specification explicitly requires UTF-8. vCard 3.0 technically defaults to ASCII but all modern parsers handle UTF-8 correctly, and you'll need it for international characters in names and addresses. Line endings should be CRLF (\r\n) per the specification, but most parsers also accept LF-only (\n). If you encounter import errors, CRLF line endings are the first thing to check.

Save the file with a .vcf extension. Both .vcf and .vcard extensions are recognized, but .vcf is universally supported while .vcard may not be associated with the contacts app on some systems. Always use .vcf.

Line Folding for Long Values

The vCard spec limits logical lines to 75 octets (bytes). For properties with long values — especially base64-encoded photos — you must fold lines. Folding works by inserting a CRLF followed by a single space or tab character. The parser joins folded lines back together by removing the line break and the leading whitespace character. In practice, most modern parsers handle long lines without folding, but if you're generating vCards programmatically for maximum compatibility, implement folding at the 75-byte boundary.

Special Characters

Certain characters need escaping in vCard values. Commas in property values should be escaped as \, (backslash-comma). Semicolons within a single value component should be escaped as \;. Newlines within values (like multi-line notes) should be escaped as \n. Backslashes themselves become \\. Get the escaping wrong and your vCard parser will split values at the wrong points, putting half your address in the wrong field.

If manually creating vCards sounds tedious, it is. Byline's vCard generator handles all the formatting, encoding, escaping, and line folding automatically — you just fill in the fields and download the file.

5. Embedding Base64 Photos in vCards

Adding a contact photo to a vCard makes your contact entry stand out in the recipient's address book — instead of generic initials, they see your face or your company logo. There are two approaches: linking to an external URL or embedding the image directly as base64-encoded data. Embedding is strongly recommended because it makes the vCard self-contained — the photo travels with the file regardless of network connectivity or whether the image URL remains valid.

How Base64 Photo Encoding Works

Base64 encoding converts binary image data into ASCII text characters. The image file's raw bytes are encoded into a string using only letters (A-Z, a-z), numbers (0-9), plus (+), and slash (/) characters. This encoded string is then embedded directly in the vCard text file. The contacts app decodes the base64 string back into image data when importing the contact.

The encoding adds approximately 33% overhead — a 30KB JPEG becomes roughly 40KB of base64 text. For contact photos, this is acceptable because you should be using small, optimized images anyway. Resize your photo to 256×256 pixels (or 512×512 maximum) and compress as JPEG at 70-80% quality. The resulting base64 string will be 15–40KB of text, which every contacts app handles easily.

vCard 3.0 Photo Syntax

PHOTO;ENCODING=b;TYPE=JPEG:/9j/4AAQSkZJRgABAQEASABIAAD/
 2wBDAAYEBQYFBAYGBQYHBwYIChAKCgkJChQODwwQFxQYGBcU
 FhYaHSUfGhsjHBYWICwgIyYnKSopGR8tMC0oMCUoKSj/...

Note the ENCODING=b parameter — this tells the parser the value is base64-encoded. The TYPE=JPEG parameter specifies the image format. Use TYPE=PNG for PNG images. The base64 data continues on folded lines (each continuation line starts with a space).

vCard 4.0 Photo Syntax

PHOTO;MEDIATYPE=image/jpeg:data:image/jpeg;base64,/9j/4AAQ
 SkZJRgABAQEASABIAAD/2wBDAAYEBQYFBAYGBQYHBwYIChAK...

vCard 4.0 uses the MEDIATYPE parameter instead of TYPE and ENCODING. It can also reference photos by URL: PHOTO;MEDIATYPE=image/jpeg:https://example.com/photo.jpg. The URL approach keeps the file small but depends on the URL remaining accessible indefinitely.

Generating Base64 from Command Line

# macOS / Linux
base64 -i headshot.jpg | tr -d '\n'

# Windows PowerShell
[Convert]::ToBase64String([IO.File]::ReadAllBytes("headshot.jpg"))

Copy the output and paste it after the PHOTO property declaration. Remember to apply line folding if the encoded string exceeds 75 characters per line (which it always will for images). Or let Byline's vCard tool handle it — upload a photo and the base64 encoding, line folding, and property formatting happen automatically.

6. QR Codes for vCards

QR codes are the most popular way to bridge physical and digital contact sharing. Print a QR code on your business card, conference badge, or office door, and anyone with a smartphone camera can scan it to save your contact information instantly — no typing, no searching, no app required. The QR code contains your vCard data directly, so the phone's camera app decodes the QR code, recognizes it as contact data, and opens the native "Add Contact" dialog.

How vCard QR Codes Work

A QR code is simply a two-dimensional barcode that encodes text data. When that text data is a valid vCard string (starting with BEGIN:VCARD and ending with END:VCARD), smartphone cameras and QR reader apps recognize it as contact information and trigger the appropriate system action. Both iOS (since iOS 11) and Android natively support this — no third-party app needed.

The practical limitation is data capacity. A standard QR code can hold approximately 3KB of text data at the highest error correction level, or up to 7KB at the lowest. A basic vCard without a photo is typically 300–500 bytes — well within capacity. But a vCard with an embedded base64 photo can easily exceed 30KB, which is impossible to encode in a QR code. The solution: omit the PHOTO property from QR code vCards, or use a URL-based photo reference instead of embedded base64 data.

Best Practices for vCard QR Codes

An alternative to encoding the full vCard in the QR code is to encode a URL that serves the VCF file. For example, encode https://yourdomain.com/contact.vcf in the QR code. When scanned, the phone opens the URL, downloads the VCF file, and offers to save the contact. This approach lets you include photos (they're in the downloaded file, not the QR code), update your details without reprinting QR codes, and track scan analytics. The trade-off is that it requires an internet connection at scan time.

7. NFC Digital Business Cards

NFC (Near Field Communication) business cards take digital contact sharing one step further. Instead of scanning a QR code with a camera, the recipient taps their phone against a physical card, tag, or sticker, and their phone automatically receives the contact data. It feels like magic to people who haven't seen it before — and it's built on the same vCard format under the hood.

How NFC Contact Sharing Works

An NFC tag is a small chip with a tiny antenna — thin enough to embed in a standard business card, a sticker, a phone case, or a keyring. The tag stores a small amount of data (typically 144 bytes to 8KB depending on the chip type) and transmits it wirelessly when a phone is held within a few centimeters. For contact sharing, the NFC tag contains either a vCard payload directly or a URL that points to a VCF file download.

Both iPhone (XS and later) and Android phones support reading NFC tags without installing any app. The phone detects the NFC tag, reads the payload, and either opens the contact save dialog (for direct vCard data) or opens the URL in the browser (for URL-based payloads). iPhones require the screen to be on but unlocked; Android phones vary by manufacturer but generally support background NFC reading.

Direct vCard vs URL-Based NFC

The most common NFC tags (NTAG213) hold only 144 bytes of usable data. A minimal vCard with just a name, phone number, and email is about 150-200 bytes — already tight. This means direct vCard storage only works on larger tags (NTAG215 with 504 bytes, or NTAG216 with 888 bytes) and requires stripping the vCard to absolute essentials.

The more practical approach is to store a URL on the NFC tag that points to a hosted VCF file or a contact landing page. A URL like https://byline.email/v/abc123 fits easily in any NFC tag and lets you include full contact details, a photo, multiple phone numbers, social links, and a company logo — all in the downloaded VCF file. You can also update your contact details without reprogramming the NFC tag, since the tag just contains the URL and the content lives on the server.

Programming NFC Tags

You need an NFC-capable phone and a free NFC writing app. On Android, apps like NFC Tools or NXP TagWriter let you write NDEF records to blank NFC tags. On iPhone, apps like NFC Tools or Simply NFC work similarly. Write the URL as an NDEF URI record — this is the most compatible format and ensures every phone that reads the tag opens the URL automatically. Blank NTAG213 tags cost about $0.30–0.50 each when purchased in bulk, making NFC business cards extremely cost-effective.

Create a professional digital business card with a hosted VCF file using Byline's vCard generator — then write the download URL to an NFC tag for tap-to-save functionality. Pair it with a printed email banner for a complete professional branding package.

8. Apple Contacts vs Google Contacts Handling

Both Apple Contacts and Google Contacts import VCF files, but they interpret certain vCard properties differently. If you're creating vCards that will be imported by a mixed audience of iPhone and Android users, understanding these differences helps you write vCards that work well on both platforms.

For reference, Apple's documentation on importing contacts and Google's documentation on importing contacts to Google Contacts cover the import process from the user's perspective. When testing your vCards, import them on both platforms and verify every field is displayed correctly. Fields that don't import cleanly on one platform may need to be restructured or duplicated using platform-specific properties.

9. Privacy Considerations

vCards are designed to share personal information — that's their entire purpose. But the ease of sharing creates privacy risks worth considering, especially when your vCard is encoded in a QR code on a public-facing business card, embedded in every email you send, or written to an NFC tag that anyone can read.

What to Include and What to Omit

Just because vCard supports a field doesn't mean you should populate it. Your business vCard should include your professional name, work phone, work email, company name, title, and website. It should not include your home address, personal phone number, birthday, or private social media accounts unless you have a specific reason. A vCard shared via QR code at a conference reaches an unknown audience — treat it like any public-facing professional profile.

QR Code and NFC Exposure

QR codes on printed materials can be scanned by anyone — not just the intended recipient. If your business card is photographed (increasingly common at events), the QR code in the photo can be scanned later. Similarly, NFC tags can be read by any NFC-capable phone within range. Consider what information you're comfortable making accessible to anyone who encounters your card, not just the people you hand it to intentionally.

URL-Based vCards and Tracking

If you use a URL in your QR code or NFC tag that points to a hosted VCF file, be aware that the hosting server can track access. This can be useful (knowing how many people saved your contact) but also raises privacy considerations. Server logs record IP addresses, timestamps, and device information for every download. If you're offering the vCard download from your own domain, your privacy policy should mention this. If you're using a third-party vCard hosting service, review their privacy policy to understand what data they collect about your contacts.

GDPR and Contact Data

Under GDPR, a vCard is personal data. If you collect other people's vCards (e.g., scanning attendee badges at events), you're collecting personal data and must process it lawfully. Sharing your own vCard is generally fine — you're consenting to share your own information. But if your company distributes vCards containing employee information, the employees should know their data is being shared and the vCard content should align with what's necessary for the business purpose. The email disclaimer legal guide covers GDPR requirements for email communications in more detail.

For professional email signatures, vCards are powerful additions. Use Byline's signature generator to create a signature with a "Save Contact" vCard link, and validate your signature's metadata with Clarity to ensure your links preview correctly. Choose your signature colors with Hue for a cohesive brand palette.

Frequently Asked Questions