Business Card QR Code: Save the Contact or Open a Page?

You hand over your card at an event, the other person glances at it, and their thumb hovers over the QR code in the corner. What happens in the next three seconds decides whether the code was worth the ink. A code that saves your number straight into their phone earns its place. A code that opens a page they did not ask for gets closed before it loads. The choice is not which generator to use. It is what the code should do: store your contact, or open a link.

Should the code save your contact or open a page?

A vCard code carries your details inside the pattern itself: name, phone, email, company and title, written in the vCard format that every phone reads (defined by RFC 6350). One scan, one tap, and you sit in their contacts with everything spelled correctly. No signal needed, no account behind it, nothing to expire.

A link code carries only a short address. The scan opens a page in the browser: your site, your portfolio, your booking calendar, or a small card page with a save-contact button on it. The page can be edited after the cards are printed, and a dynamic code can count its scans. It needs a connection, and saving the contact takes one extra tap.

The two are not enemies. A practical middle ground used by many trades: a static vCard code on the card, with the website field inside the vCard pointing at a page on your own domain. The contact saves forever with no service in the path, and the link inside it goes wherever you point that page next year.

When does a vCard code win?

Pick the vCard when your details will outlast the box of cards. A consultant with one mobile number kept for a decade, a plumber whose company name and number have not changed in years, anyone who networks in basement halls and exhibition centres where the signal dies: the contact saves with no connection, no account and no provider that could change its terms later.

Keep it lean. Every field you add makes the pattern denser and harder to read at card size, which is why generator makers advise restraint. Name, title, company, one phone number, one email and a website is the full set for most cards. A second number, a street address and three social profiles turn the code into a fine grid that a phone camera struggles with across a dim table. If the card needs all of that, it needs a link code instead, or the extra facts belong on the printed card rather than inside the code.

When does a link code win?

Pick the link when something behind the code will change, or when the contact alone does not close the deal. A photographer whose portfolio wins the work, a coach who books discovery calls, a founder whose title changes with every funding round: the page carries what a contact record cannot, such as photos, a price range, a booking button and a row of social profiles. You edit the page once, and every card already sitting in drawers and wallets shows the update.

Cards live longer than almost anything else you print. Cards from a job left three years ago are still in drawers, which makes the static-versus-dynamic question sharper here than on a flyer that gets thrown away in a week. A link code also answers the one question a paper card cannot: did anyone scan it. Scan counts will not tell you who saved the contact or who became a client, but they tell you whether the box of cards you paid for is working or decorating a drawer.

One caution before you commit to a link: the code goes dead if the service behind it does. Check what still works if you cancel the subscription, and prefer a page on a domain you control over a profile locked inside one app. A phone-to-phone tap such as Apple's NameDrop (iPhone to iPhone, since iOS 17) is handy at the table but does nothing for the Android user across from you or the person who reads your card a week later. The printed code covers everyone; the tap covers one brand.

How big should the code be on the card?

A business card is scanned from a few centimetres away, so the code does not need to be large, but it cannot be jewellery either. Generator makers converge on roughly the same guidance: a short link reads comfortably from about 15 mm wide, while a full contact needs 20 to 30 mm depending on how many fields are packed in. The standard also requires a blank quiet zone four modules wide on every side, so keep text and borders out of that margin. Work it out in five steps:

1. Give the code the back of the card. The front stays clean for your name and what you do; the back gives the code room and a short label telling people what the scan does, such as "Scan to save my contact" or "Scan for my portfolio". A code with no explanation is a puzzle most people skip.
2. Size it by content, not by taste. A link code can sit at 15 to 18 mm. A vCard with five or six fields wants 20 to 25 mm; a fuller one wants 30 mm. When in doubt, encode less rather than printing bigger: drop the second email before you steal space from your name.
3. Print dark on light, matte if possible. Black on white or cream scans best. Pale ink on a coloured card and glossy laminate that glares under event lighting are the two material faults behind most "not working" complaints, as covered in the print specification guide.
4. Print one real-size proof first. Not a zoomed PDF on screen: one card, at final size, on the final stock. This is the step that saves a run of a thousand.
5. Test with three phones before approving. One recent iPhone, one mid-range Android, one older phone with a tired camera. Scan in normal room light, at arm's length, slightly angled. If all three save the contact or open the page first try, approve the run.

What must the card still carry without any scan?

• Your name and what you do, in plain words. Half the cards handed out are never scanned. "Bruno Perrot, heating engineer, Mulhouse" beats a logo with no trade on it.
• One phone number and one email, printed. The person who loses their phone, or who simply prefers typing, reaches you without any code at all.
• One code, not three. A card with a vCard code, a website code and a LinkedIn code is a card nobody scans. Pick the one job the scan does and label it.
• A call to action next to the code. Five words in the same typeface as the rest of the card: what happens when they scan. Benefit first, instruction second.

Sources and method

The vCard format is defined by RFC 6350; phone behaviour when saving a scanned contact varies by platform, so the three-phone test above is load-bearing, not decoration. The static-versus-dynamic trade-offs, the density argument (more fields, finer grid, harder scan) and the size guidance (about 15 mm for a short link, 20 to 30 mm for a contact by field count) summarise eight generator guides consulted on 1 November 2026: Digily Link, BestQR, Cardr, QRLynx (two guides), Linko, QRCodePrime and QR Scan Generator. Those figures are vendor guidance, not independent measurement. The quiet-zone rule (four modules) comes from the QR standard itself. Apple's NameDrop flow is described in Apple's iPhone User Guide for iOS 17 and later. The decision frame and the print-test procedure are the author's own method.

Decide the job first, then print. If the scan should open a page, build the page before the cards: read setting up your first page in five minutes and point the code at an address you control. If the cards go to events where portfolios matter more than phone numbers, see the digital business card page for the hosted option. And whatever the code holds, size it properly with the print specification guide before you order the run.