Short answer
vCard is the IETF standard for contact data: version 3.0 is RFC 2426 (1998)[2] and version 4.0 is RFC 6350 (2011), which requires the VERSION and FN properties in every card[1]. MECARD is a shorter, line-free format introduced by NTT DoCoMo for phone address books — a `MECARD:` prefix, key:value fields separated by semicolons and a double semicolon to end[3][4]; its original specification page no longer exists[4]. Measured: a four-field MECARD is 88 bytes and fits QR version 5 at level M; the equivalent minimal vCard 3.0 is 124 bytes and needs version 7[5].
Key takeaways
- vCard has a maintained standard with a registry of properties; MECARD has no ISO or RFC and survives through reader implementations such as ZXing[3][4].
- Most QR generators, including NexaLink's, emit vCard 3.0 rather than 4.0 because it is the version phone contact importers have handled longest; 4.0 differs in syntax (for example a mandatory FN, different parameter rules)[1].
- MECARD's N field is "family,given" separated by a comma; vCard's N is "family;given;additional;prefix;suffix" separated by semicolons[2][3].
- ZXing's documentation calls vCard "a bit verbose for use in 2D barcodes" and notes MECARD's popularity for that reason[3]; the size difference we measured is 1.4× for minimal cards and grows with fields.
- NexaLink Card's scanner parses both formats and classifies plain URLs separately; its own QR carries a vCard 3.0 at error-correction level M.
vCard: the standard
- vCard
- A text format for exchanging contact information, standardised by the IETF. Version 3.0 is defined in RFC 2426 (September 1998)[2]; version 4.0 in RFC 6350 (August 2011)[1]. A vCard is a block of lines between BEGIN:VCARD and END:VCARD, each line a property name, optional parameters and a value.
RFC 6350 states that a vCard object MUST include the VERSION and FN properties, with VERSION immediately after BEGIN:VCARD[1]. The properties a business card uses are N (structured name), FN (formatted name), ORG (organisation), TITLE, TEL (telephone), EMAIL, URL and ADR (structured address)[1][2]. Version 3.0 uses the same property names, which is why a 3.0 card remains the practical choice for QR codes: readers that predate 2011 parse it, and the 4.0 changes (parameter encoding, new properties, UTF-8 only) add nothing a business card needs.
| Minimal (124 bytes) | Typical (280 bytes) |
|---|---|
| BEGIN:VCARD · VERSION:3.0 · N:Sharma;Priya;;; · FN:Priya Sharma · TEL;TYPE=CELL:+15555550123 · EMAIL:priya@example.com · END:VCARD | BEGIN:VCARD · VERSION:3.0 · N:Sharma;Priya;;; · FN:Priya Sharma · ORG:Sharma Design Studio · TITLE:Founder · TEL;TYPE=CELL:+15555550123 · TEL;TYPE=WORK:+15555550199 · EMAIL:priya@example.com · URL:https://example.com · ADR;TYPE=WORK:;;120 Market Street;San Francisco;CA;94105;USA · END:VCARD |
MECARD: the compact format
- MECARD
- A single-line contact format originated by NTT DoCoMo for registering phone-book entries from barcodes: the literal prefix MECARD:, then fields written as KEY:value; (N, SOUND, TEL, TEL-AV, EMAIL, NOTE, BDAY, ADR, URL, NICKNAME), ending with a double semicolon[3][4]. It is not an ISO or IETF standard, and the original DoCoMo specification page is no longer online[4].
Example, 88 bytes: `MECARD:N:Sharma,Priya;TEL:+15555550123;EMAIL:priya@example.com;URL:https://example.com;;`. The ZXing project — whose reader library is embedded in many scanning apps — documents MECARD as the popular compact option, notes a slightly different variant proposed by KDDI, and says vCard, while widely understood, is "a bit verbose for use in 2D barcodes, whose information capacity is limited"[3]. Because the format is defined by its readers rather than a standard, support for the less common fields varies; ZXing's parser handles N, SOUND, TEL, EMAIL, NOTE, ADR, BDAY, URL and ORG but not TEL-AV or NICKNAME[4].
| Data | vCard 3.0 / 4.0 | MECARD | Note |
|---|---|---|---|
| Structured name | N:Family;Given;Additional;Prefix;Suffix | N:Family,Given | Different separators and fewer parts in MECARD[2][3] |
| Display name | FN (mandatory in 4.0) | — (readers build it from N) | [1] |
| Phone | TEL;TYPE=CELL: | TEL: | MECARD has TEL-AV for video phones, rarely supported[4] |
| EMAIL: | EMAIL: | ||
| Website | URL: | URL: | |
| Organisation | ORG: | ORG: (reader extension, not in the original list) | Supported by ZXing[4] |
| Job title | TITLE: | — | No MECARD field; use NOTE |
| Address | ADR;TYPE=WORK:;;Street;City;Region;Postcode;Country | ADR: | Few readers split a MECARD address into parts[4] |
| Birthday | BDAY: | BDAY:YYYYMMDD | |
| Pronunciation | — (SOUND in 3.0 is for audio) | SOUND: | Kana reading in the Japanese original[3] |
What each format costs in QR size (NexaLink measurement)
The reason the choice matters on a printed card is capacity. We encoded the examples above with the qrcode 1.5.4 encoder in byte mode on 15 November 2026[5], letting it pick the smallest QR version at each error-correction level. Modules per side are 17 + 4 × version; the standard defines versions 1 to 40, from 21 × 21 to 177 × 177 modules[6][8].
| Payload | Bytes | L | M | Q | H |
|---|---|---|---|---|---|
| Card link only (https://nexalink.co/c/a1b2c3) | 28 | v2 (25) | v3 (29) | v3 (29) | v4 (33) |
| MECARD: name, phone, email, URL | 88 | v5 (37) | v5 (37) | v7 (45) | v8 (49) |
| vCard 3.0: name, phone, email | 124 | v6 (41) | v7 (45) | v9 (53) | v11 (61) |
| vCard 3.0: + organisation, title, second phone, URL, address | 280 | v11 (61) | v12 (65) | v15 (77) | v17 (85) |
| vCard 3.0: + second email, second URL, note | 438 | v14 (73) | v16 (81) | v19 (93) | v22 (105) |
Which format to put in a QR code
- For a printed card: a link. It is the smallest payload, it opens a page you can update, and the page can offer a vCard download. NexaLink Card's printed and NFC surfaces carry a link for this reason; see NFC vs QR business cards.
- For on-screen scan-to-save: vCard 3.0. It is the format contact importers have parsed longest and it carries organisation, title and typed addresses that MECARD lacks. NexaLink Card's in-app QR encodes a vCard 3.0 at level M, and the free vCard generator produces the same format.
- MECARD when every module counts and you only need name, phone, email and URL — accepting that job title has no field and that address parsing is unreliable across readers[4].
- Test on real phones. Support for either format depends on the scanner app and OS version; the formats above are what the standards and the reference reader document, not a guarantee of any device's behaviour.
Frequently asked questions
What is the difference between vCard and MECARD?
vCard is an IETF standard (RFC 2426 for 3.0, RFC 6350 for 4.0) with many properties and a multi-line structure; MECARD is a compact single-line format from NTT DoCoMo with about ten fields and no formal standard. For the same four fields, MECARD is roughly 30% smaller.
Should I use vCard 3.0 or 4.0 in a QR code?
3.0 in practice. Its property names match 4.0 for everything a business card needs, and phone importers have parsed it since 1998. RFC 6350's 4.0 additions do not help a QR code and some readers still mis-handle them.
Is MECARD still supported?
Reader libraries such as ZXing still parse it, so most scanner apps do. There is no standard body maintaining it and the original DoCoMo specification page returns 404; support for the less common fields varies.
How many bytes is a vCard QR code?
Our examples: 124 bytes for name, phone and email (QR version 7 at level M); 280 bytes with organisation, title, two phones, URL and address (version 12); 438 bytes with extra email, URL and a note (version 16).
Can a QR code hold a photo in the vCard?
Technically a PHOTO property can embed base64 data, but a QR code holds at most 2,953 bytes at level L and 2,331 at level M, so even a tiny image will not fit alongside the contact fields. Link to a page instead.
Which format does NexaLink Card use?
Its in-app QR encodes a vCard 3.0 at error-correction level M; printed and NFC surfaces carry a link to the card page. Its scanner reads vCard, MECARD and plain URLs.
Sources
- IETF RFC 6350 — vCard Format Specification (vCard 4.0, August 2011) — checked on 2026-11-15
- IETF RFC 2426 — vCard MIME Directory Profile (vCard 3.0, September 1998) — checked on 2026-11-15
- ZXing project wiki — Barcode Contents (MECARD and vCard in QR codes) — checked on 2026-11-15
- Wikipedia — MeCard (QR code) (secondary; the original NTT DoCoMo page returns 404) — checked on 2026-11-15
- npm — qrcode 1.5.4 (QR code encoder used for the measurements) — checked on 2026-11-15
- DENSO WAVE qrcode.com — Information capacity and versions of the QR Code — checked on 2026-11-15
- DENSO WAVE qrcode.com — Error correction feature — checked on 2026-11-15
- ISO/IEC 18004:2024 — QR code bar code symbology specification (edition 4, August 2024) — checked on 2026-11-15