The encyclopedia · Software & IT · Technical decision · 1996–1998
vCard's plain-text contact file became the .vcf every phone can read
The Versit Consortium's text-based business card became RFC 2426 in 1998; every phone, mail client and CRM still exchanges contacts as .vcf.
Versit Consortium
the move
In the mid-1990s electronic business cards lived inside proprietary personal information managers, so contacts could not travel between products. The Versit Consortium created vCard as a text format for representing a person's card, and transferred the rights to the Internet Mail Consortium in 1996.
The IETF made it a formal standard in September 1998 with RFC 2426, the 'vCard MIME Directory Profile', which defines how a vCard carries names, addresses, phones, email and URLs inside a MIME content type. RFC 6350 (2011) modernized it while keeping the same plain-text model: BEGIN:VCARD, a VERSION property, and one property per line.
Because the format is plain text with a stable MIME type, every major platform implemented it: smartphone contact apps, PDAs, mail clients and CRMs all exchange .vcf files, and vCards travel over email, MMS, NFC and QR codes.
why it works
- Plain text with a registered MIME type works in email, MMS, NFC and QR codes
- Every major phone and mail client ships import/export support
- Properties like FN, TEL and EMAIL map directly to a contact record
- Formal RFCs gave vendors a stable contract to rely on
what transfers
Interoperability standards win when the file is simple enough for every vendor to implement in an afternoon — and when the biggest platforms ship support by default.
what came after
RFC 6350 (2011) remains the current standard; JSON variants such as jCard (RFC 7095) and web microformats like hCard keep the same properties usable online, and .vcf is still the universal contact exchange file.
references
spotted an error? The archive wants to know.