vCard MIME Type
text/vcard and .vcf files contain, how vCard versions differ, and how Poly supports contact files. MIME type details for text/vcard
In active use| MIME type | text/vcard |
|---|---|
| Extensions | .vcf.vcard |
| Alternate versions | text/directorytext/directory; profile=vcardtext/x-vcard |
| First standardized | 1998 |
| Created by | Internet Engineering Task Force |
| Browser support | |
| Example applications | Apple Contacts, Google Contacts, Microsoft Outlook |
| Poly support | Partial. Poly recognizes files labeled `text/vcard` and lets you inspect their source, but it does not import them as address-book contacts. |
| Indexed by Poly | Partial. vCards remain searchable by filename, but their contact fields are not currently indexed as content. |
| Preview in Poly | Yes. A recognized vCard opens as readable text rather than as a formatted contact card. |
| Poly agent | No. The Poly agent cannot currently read or reason about vCard contents directly. |
What does text/vcard mean?
The text/vcard media type identifies vCard contact data. A vCard can describe a person, an organization, a group, or a place using fields for names, phone numbers, email addresses, postal addresses, photos, URLs, birthdays, notes, and other directory information. A single file can contain one or more cards.1
IANA registers both .vcf and .vcard as filename extensions. .vcf is the extension most applications expose. The registration lists no magic number, so a trustworthy reader checks the structure and the VERSION property instead of relying on a fixed byte prefix.2
text/vcard, not application/vcard. Older software may use text/x-vcard, text/directory, or text/directory; profile=vcard. IANA marks those forms as deprecated in favor of text/vcard.2How is a vCard file structured?
vCard is a line-oriented format. Each card begins with BEGIN:VCARD, declares its version, contains property lines, and ends with END:VCARD. In vCard 4.0, FN supplies a formatted name and is required.1
BEGIN:VCARD
VERSION:4.0
FN:Alex Rivera
N:Rivera;Alex;;;
ORG:Example Studio
TITLE:Design Director
TEL;TYPE=work;VALUE=uri:tel:+1-555-0100
EMAIL;TYPE=work:[email protected]
URL:https://example.com
END:VCARD
A property can have parameters before the colon. In EMAIL;TYPE=work:[email protected], EMAIL is the property, TYPE=work describes it, and the text after the colon is the value. Common properties include:
| Property | Represents | Example |
|---|---|---|
FN | Display-ready name | FN:Alex Rivera |
N | Structured name parts | N:Rivera;Alex;;; |
TEL | Telephone URI or number | TEL;TYPE=cell:tel:+1-555-0100 |
EMAIL | Email address | EMAIL;TYPE=work:[email protected] |
ADR | Structured postal address | ADR;TYPE=work:;;1 Main St;... |
ORG and TITLE | Organization and role | ORG:Example Studio |
PHOTO | A photo by URI or embedded data | PHOTO:https://example.com/alex.jpg |
UID | A durable identifier | UID:urn:uuid:... |
vCard 4.0 uses UTF-8. Content lines should be folded at 75 octets, and a continued physical line begins with a space or tab. Readers remove the line break and that leading whitespace before interpreting the property. Escapes also matter: a literal comma, semicolon, backslash, or newline in a text value cannot always be copied as plain punctuation.1
Which vCard version is in a .vcf file?
The MIME type does not select one vCard version. Inspect the VERSION line inside each card. IANA notes that older versions remain common and are similar but not strictly compatible.2
| Version | Standardization | Practical distinction |
|---|---|---|
| 2.1 | Industry specification, published in 1996 | Common in older phones and contact exports; permits older encodings and syntax |
| 3.0 | RFC 2426, September 1998 | Widely exchanged by desktop and web contact applications |
| 4.0 | RFC 6350, August 2011 | Current IETF standard; requires UTF-8 and defines a clearer, extensible data model |
RFC 6350 replaced RFC 2426 and brought the media-type registration and the stand-alone file format into one specification. It also added properties such as KIND, GENDER, ANNIVERSARY, and CLIENTPIDMAP, removed several older constructs, and made UTF-8 the only permitted character set.13
Do not change only VERSION:3.0 to VERSION:4.0. Property value types, parameters, escaping, and allowed fields changed too. A real conversion must parse the source version and serialize a valid destination card.
How do you open a .vcf file?
Open a vCard with a contacts or address-book application when you want to add its entries. Apple Contacts and iCloud Contacts import and export vCards. Google Contacts imports .vcf files, and Microsoft Outlook can open a .vcf as a contact.456
Current web browsers do not provide a standard native vCard viewer. A .vcf link may download, open a registered contacts application, or be handled by a website. That behavior is different from the browser rendering text/vcard itself.
Before importing a large file, consider opening a copy in a trusted text editor or vCard validator. One .vcf can hold multiple contacts, so the number of address-book entries created may be greater than one. Apple documents that a multi-contact vCard imports each contact separately and exports selected contacts together in one file.4
Support in Poly
Poly can store and recognize text/vcard files. When the file is identified with that media type, it opens as readable source text, which is useful for checking names, numbers, addresses, and the declared vCard version without importing anything into an address book.
Support is source-oriented rather than contact-aware. Poly does not turn each card into an address-book entry, render a formatted contact card, or currently index vCard properties for full-text or semantic search. You can find the file by name, but a search for a phone number or organization that exists only inside the card will not match it. The Poly agent cannot currently read the card's contents directly.
Because .vcf has no magic number and is not inferred from its filename in every Poly client, preserve the text/vcard media type when transferring or uploading the file. If a vCard arrives as generic text or binary data, its preview and classification can differ.
Converting vCard to other formats
Choose a destination based on what will consume the data:
| Destination | Useful for | Important limitation |
|---|---|---|
| Another vCard version | Moving contacts between applications with different version support | Unsupported properties or value details may be lost |
| CSV | Reviewing contacts in a spreadsheet or importing into a system with fixed columns | Repeated phone numbers, labels, photos, groups, and structured values need an explicit mapping |
| jCard JSON | JSON-based APIs that need vCard's data model | jCard has its own standardized array structure, not arbitrary key-value JSON |
| xCard XML | XML workflows and schema-aware interchange | More verbose than ordinary vCard text |
The IETF defines jCard in RFC 7095 and xCard in RFC 6351. Both preserve vCard semantics in another serialization.78 A home-grown JSON object such as { "name": "Alex" } may be useful inside one application, but it is not jCard and cannot be assumed to round-trip all vCard properties.
For CSV conversion, decide how to represent repeated properties before exporting. One contact can have several email addresses, telephone numbers, URLs, and addresses, each with labels and preference information. Flattening those into one row without a documented mapping can silently discard data.
Privacy, security, and interoperability
A vCard can contain more than a public name and work number. It may include home addresses, birthdays, personal notes, geographic coordinates, photos, relationship details, identifiers, and URLs. RFC 6350 warns that vCards have no inherent authentication or confidentiality and recommends secure transport when authenticity or privacy matters.1
.vcf as untrusted data. Review its fields before importing it, and do not assume that a familiar display name proves who created it. Contact applications should avoid fetching external PHOTO, LOGO, SOURCE, or other URIs without an appropriate trust decision.Interoperability problems often come from version differences, bad line folding, incorrect escaping, unsupported vendor properties, or character encodings used by older 2.1 and 3.0 exporters. Keep the original file until the receiving application has preserved several representative contacts, especially entries with non-ASCII names, multiple phone numbers, photos, and labeled addresses.
Contact data also becomes stale. REV can record when a card was last revised, while SOURCE can point to an authoritative source, but neither guarantees that the information is current. Confirm sensitive or operational details with the person or organization rather than treating a successfully imported vCard as verified identity.
Footnotes
- Internet Engineering Task Force. RFC 6350: vCard Format Specification. The current vCard 4.0 standard defines the format, required properties, UTF-8 encoding, line folding, versions, and security considerations. ↩ ↩2 ↩3 ↩4 ↩5
- Internet Assigned Numbers Authority.
text/vcardMedia Type Registration. The registration lists.vcfand.vcard, no magic number, deprecated media types, and the need to inspectVERSION. ↩ ↩2 ↩3 - Internet Engineering Task Force. RFC 2426: vCard MIME Directory Profile. The September 1998 specification standardized vCard 3.0 and documents its differences from vCard 2.1. ↩
- Apple Support. Import, export or print contacts on iCloud.com. Apple documents importing and exporting one or more contacts in a vCard. ↩ ↩2
- Google Contacts Help. Import your contacts into Google Contacts. Google documents importing
.vcfvCard files. ↩ - Microsoft Support. Import vCards to Outlook contacts. Microsoft documents opening
.vcffiles and adding their entries to Outlook contacts. ↩ - Internet Engineering Task Force. RFC 7095: jCard: The JSON Format for vCard. jCard is the standardized JSON representation of vCard data. ↩
- Internet Engineering Task Force. RFC 6351: xCard: vCard XML Representation. xCard is the standardized XML representation of vCard data. ↩