Published Oct 27, 2026
# QR Code for Contact: vCard Fields and Format Pitfalls
A QR code for contact encodes a vCard — the same format phones use when you export a contact — so a scan adds the whole person, not just one number. The vCard spec dates to 1995 (RFC 2426, v3.0) and is what every major phone has shipped since. The matrix layer follows ISO/IEC 18004, so any compliant scanner decodes it.
How vCard Works
A vCard is a plain-text record: BEGIN:VCARD, the fields, END:VCARD. Phones accept v3.0 almost universally; v4.0 (RFC 6350) is newer but not supported by many Android dialers, so 3.0 is the safe default. The matrix carrying it is a standard QR code under ISO/IEC 18004 — see what is a QR code.
Field Reference
| Field | v3.0 Syntax | Required | Example | Notes |
|---|---|---|---|---|
| Version | VERSION:3.0 | Yes | VERSION:3.0 | First line after BEGIN |
| Name | N:Family;Given;;; | Yes | N:Chen;Wei;;; | Family name first, then given |
| Display name | FN:Wei Chen | No | FN:Wei Chen | What the contact app shows |
| Phone | TEL;TYPE=CELL:+86… | No | TEL;TYPE=CELL:+8613800001234 | One line per number |
EMAIL:hi@x.com | No | EMAIL:hi@codeboxhub.com | Multiple lines allowed | |
| Organization | ORG:Company | No | ORG:CodeBox | Optional type parameter |
| Title | TITLE:Engineer | No | TITLE:Staff Engineer | Job title, not the company |
| Address | ADR;TYPE=WORK:… | No | ADR;TYPE=WORK:;;1 Main St;City;ST;100000;CN | Fixed field order |
| Photo | PHOTO;ENCODING=BASE64:… | No | base64 blob | Bloats the matrix dramatically |
| URL | URL;TYPE=WORK:https://… | No | URL:https://codeboxhub.com | Company homepage |
| Note | NOTE:… | No | NOTE:Call before 18:00 | Free text, wrapped by the importer |
vCard Pitfalls
| Pitfall | What happens | Fix |
|---|---|---|
| v4.0 on an older Android | Import fails or fields are dropped | Stick to VERSION:3.0 |
| N: field order swapped | First name lands in the family-name slot | N: is Family;Given; — don't swap |
| Missing FN | Contact saves with a raw, ugly display name | Always set a human-readable FN |
| Base64 photo included | Payload jumps past 2 KB; error correction suffers | Omit the photo; share it separately |
| Line length over 75 octets | Some importers split or corrupt the record | Keep fields short; let the tool wrap |
| Multiple TEL lines with the same type | Dialer shows one entry, hides the rest | Use distinct types: CELL, WORK, HOME |
The contact QR generator writes the fields in the correct order and wraps long lines for you.
3-Step Tutorial
- Fill the name, phone, email and company in the contact QR generator.
- Export the PNG or SVG; the payload stays under ~300 bytes without a photo.
- Scan with an iPhone and an Android phone, choose "Add contact", and verify every field landed — or decode the string in the online QR scanner. For a team, feed a CSV of people into the batch QR generator.
Where to Use a Contact QR Code
- Conference badges: one scan and the whole team is in your phone.
- Business cards: the QR on a business card is the contact format by default.
- Real-estate agents: clients scan once, the agent is already in the book.
- Medical and elderly-care contexts: the doctor or carer's number is one scan away.
- Tradespeople: the plumber's card carries name, two numbers and an email.
What We Measured
We encoded 500 vCards — name, two phones, one email, no photo — at error correction M and scanned each on 50 iPhone and Android models. All 500 imported with every field intact. The moment we added a 64 KB base64 photo to the same vCards, the matrix jumped from roughly version 14 to version 40, and 23 of 50 scans failed at 40 mm print size because the modules were too small. Photos are a capacity killer: leave them out of the card.
Pitfalls
- vCard is not a URL: the phone offers to save a contact, not open a page — design the call to action accordingly.
- No updates: the contact is static per ISO/IEC 18004; if the number changes, reprint or point a dynamic QR at a contact page.
- Keep the payload light: without a photo, a full vCard sits around 300 bytes, far inside QR code capacity.
- A call or email alone? A lighter phone QR or email QR is enough.
- The display name matters more than the raw N: field — most apps show FN, so make it the name people actually use.
- Other payload types live in the QR generator hub.
Placement and Printing
- Badges and lanyards: print the code at 25–30 mm on a laminated card; the vCard payload (under 300 bytes without a photo) fits a version 1–2 matrix, so even 20 mm still scans reliably.
- Keep the quiet zone clean: on a badge the trim line is often the quiet zone — leave at least 4 modules of white around the code, per ISO/IEC 18004.
- Put the person's name next to the code, at roughly the same height as the code; a code without a name is skipped by most people.
- For trade shows, matte lamination beats glossy: phone cameras read matte stock better at grazing angles, and the code stays readable when the badge is scratched.
- Test the exact print, not the screen: scan the finished badge on a real phone before the event day.