vCard 2.1 Format Specifications and Examples
Complete guide to the vCard 2.1 format with detailed specifications, examples, and implementation guidelines
Overview of vCard 2.1
vCard 2.1 was the first widely adopted version of the vCard specification, originally published in 1996. While it's considered legacy today, many systems still support this format due to its simplicity and widespread compatibility. Understanding vCard 2.1 is essential for maintaining backward compatibility and working with older contact management systems.
⚠️ Legacy Format Notice
vCard 2.1 is considered a legacy format. For new implementations, consider usingvCard 3.0 orvCard 4.0 instead. If you need to convert between vCard versions, use ourvCard Version Converter.
Basic Structure
Every vCard 2.1 file follows this basic structure:
Required Fields
vCard 2.1 has minimal required fields:
- BEGIN:VCARD - Indicates the start of the vCard
- VERSION:2.1 - Specifies the vCard version
- FN - Formatted name (display name)
- END:VCARD - Indicates the end of the vCard
Common Properties
Here are the most commonly used properties in vCard 2.1:
- FN: Formatted name
- N: Structured name
- NICKNAME: Casual name
- TEL: Telephone numbers
- EMAIL: Email addresses
- URL: Website URLs
- ADR: Postal address
- LABEL: Address label
- ORG: Organization name
- TITLE: Job title
- ROLE: Functional role
Complete Example
Here's a comprehensive vCard 2.1 example showing all major fields:
Property Parameters
vCard 2.1 uses parameters to provide additional context for properties:
Telephone Parameters
- WORK - Work phone number
- HOME - Home phone number
- VOICE - Voice telephone
- FAX - Fax number
- CELL - Mobile phone
- PAGER - Pager number
- PREF - Preferred number
Email Parameters
- INTERNET - Internet email
- PREF - Preferred email
- WORK - Work email
- HOME - Personal email
Address Parameters
- WORK - Work address
- HOME - Home address
- POSTAL - Postal address
- PARCEL - Parcel delivery address
- DOM - Domestic address
- INTL - International address
Field Format Details
Name Field (N)
The N field contains structured name information separated by semicolons:
Address Field (ADR)
Address fields contain seven components separated by semicolons:
Encoding and Character Set
vCard 2.1 has specific rules for character encoding:
- Default Charset: US-ASCII
- Extended Characters: Use CHARSET parameter for non-ASCII
- Line Folding: Long lines should be folded using space or tab
- Escaping: Special characters should be escaped with backslash
Character Encoding Example
Line Folding
Long lines in vCard 2.1 should be folded using a space or tab character:
Limitations of vCard 2.1
Known Limitations
- • Limited character set support (primarily ASCII)
- • No standardized support for multiple values of the same type
- • Basic date format support
- • Limited photo/logo support
- • No time zone information
- • Inconsistent parameter handling across implementations
Minimal Example
The simplest valid vCard 2.1 file:
Best Practices
Recommendations
- • Always include the FN (Formatted Name) property
- • Use CHARSET parameter for non-ASCII characters
- • Include both structured (N) and formatted (FN) names
- • Be consistent with parameter usage
- • Test compatibility with target applications
- • Consider upgrading to vCard 3.0 or 4.0 for new projects
Migration Considerations
When working with vCard 2.1 files, consider these migration strategies:
- Backward Compatibility: vCard 3.0+ readers usually support 2.1
- Forward Migration: 2.1 files can be upgraded to newer versions
- Data Loss: Some 2.1 features may not translate perfectly
- Testing: Always test migrations with target applications
Conclusion
While vCard 2.1 is a legacy format, understanding its structure and limitations is crucial for maintaining compatibility with older systems and applications. Its simplicity makes it a good starting point for understanding vCard formats, but modern applications should consider using vCard 3.0 or 4.0 for better feature support and internationalization.