vCard 3.0 and 4.0: what you need to know (and what bloo.Cards uses)
Two common versions
The vCard format describes a contact record. Version 3.0 is defined by RFC 2426 (1998), version 4.0 by RFC 6350 (2011), which adds properties such as KIND (record type), GENDER or ANNIVERSARY and requires UTF-8 encoding.
What sets 4.0 apart
4.0 modernises the format: mandatory UTF-8 encoding (so accents and non-Latin scripts come through cleanly), new properties and a stricter structure. Better in theory; in practice, not every address book reads it perfectly yet.
What bloo.Cards uses
The “Add contact” button on your card downloads a record in vCard 3.0, the version most widely accepted by address books (iPhone, Android, Outlook). It contains your details and, if you added it, your photo.
Why 3.0 rather than 4.0
The choice is pragmatic: 3.0 imports without surprises on the widest range of devices. The point of a business card is to be saved without friction: compatibility beats novelty.
Should you worry about it?
For the user, no: you share your card, your contact saves the record, and it all works. The version is a technical detail that bloo.Cards handles for you.
Sources
Frequently asked questions
What is the difference between vCard 3.0 and 4.0?
Version 3.0 is defined by RFC 2426 (1998) and version 4.0 by RFC 6350 (2011). Version 4.0 requires UTF-8 encoding and adds properties such as KIND, GENDER and ANNIVERSARY.
Which vCard version does bloo.Cards use?
The “Add contact” button downloads a vCard 3.0, the version most widely accepted by address books (iPhone, Android, Outlook).
Why 3.0 rather than 4.0?
The choice is pragmatic: 3.0 imports without surprises on the largest number of devices, and not every address book reads 4.0 perfectly yet.
