How I set up a vCard QR code for a business card

A vCard QR code puts contact details inside the QR code so a phone can offer to save the contact after scanning. I use it when the printed object is about a person or a location: business cards, appointment cards, front desk signs, technician badges, and sales sheets.

The setup is simple. Keep the contact details short, generate the vCard QR code, print it at the real size, and test the scan on more than one phone before sending the card to print.

What goes into the vCard

Use fields people will save

RFC 6350 defines vCard as a format for representing and exchanging information about people and organizations. It can hold names, structured addresses, email addresses, phone numbers, URLs, and more. For print, I do not use everything the format can hold.

• Full name, because the saved contact needs to be recognizable.
• Organization, if the business name matters more than the person.
• Phone number, with the country code when the card may travel.
• Email address, if customers should use it directly.
• Website or booking URL, if the next step belongs online.
• Street address, only when the physical location matters.

I leave out decorative fields. A vCard can carry more data, but every extra line makes the QR code denser. Dense codes are harder to print small, and business cards are already a tight format.

Business card details

The QR code is not the whole card

I still put the normal contact details on the business card. The QR code is a shortcut that sits beside readable text. If someone cannot scan because their phone camera is broken, the lighting is bad, or the card is in a photo, the card should still work.

For staff cards, I usually encode the person's direct details. For a front desk card or counter sign, I encode the business or branch contact instead. The difference matters when staff change. A card tied to a person gets reprinted when that person leaves. A card tied to a branch can last longer.

I also decide whether the website field should be the homepage, booking page, review page, or staff profile. The saved contact should match what the customer will do next. Sales reps may want a calendar link. Clinics may want the appointment page. Restaurants may only need phone, address, and menu link.

Keep the QR code printable

Short contact data scans better

DENSO WAVE documents that QR code capacity depends on the symbol version, data type, and error correction level. As the encoded data gets longer, the symbol needs more modules. That is why I keep vCard QR codes plain.

I avoid long titles, marketing copy, multiple phone numbers, and long addresses unless they are needed. If the business needs a lot of profile information, I use a URL QR code to a contact page instead. The page can hold the long biography. The QR code should stay easy to print and scan.

I keep the quiet space around the QR code clean. No logo touching the modules, no tiny caption jammed against the edge, and no patterned background behind it. A business card is small enough without making the scanner guess where the code begins.

Static or dynamic

Use static for stable contacts

A static vCard QR code is fine when the printed card belongs to a stable contact. The details are inside the QR code. There is no redirect service to maintain, and the scan can still work even if the website is down.

The tradeoff is obvious after a phone number changes. The printed QR code still contains the old number. For one person ordering 100 cards, that may be acceptable. For a service team printing badges, appointment cards, and counter displays, I check how often staff and branch details change before choosing static.

Dynamic is better when the printed asset has to survive contact changes. In that setup, the QR code points to a short link or contact page that can be edited later. It is less pure than a vCard embedded directly in the QR code, but it is easier to maintain for teams.

My print proof

Test the save-contact flow, not just the scan

I print the business card at the final size and scan it with at least two phones. I check that the phone recognizes it as a contact, that the name is readable, and that the saved phone and email fields are in the right places.

Then I save the contact and inspect it in the address book. This catches small mistakes that a scan preview hides: swapped name fields, missing country code, a website stored as a note, or an address that became one unreadable line.

After that, I keep the source contact text with the print file. If the card gets reordered six months later, I want to know exactly what data was encoded, not just where the PNG file ended up.