QR Code on a Business Card: What to Encode, How Big, and Where It Goes
The best QR code on a business card is a vCard code printed at least 2 x 2 cm on the back of the card with a clear white margin around it. One scan saves your name, phone, and email straight into the other person's contacts, with no app to install and no internet connection needed. The details below decide whether that scan happens: payload, placement math, finish, and the test you run before the print shop makes 500 copies.
What to encode: vCard, LinkedIn URL, or website
The payload matters more than the design. A business card scan is a one-shot moment: the person is standing in front of you, phone in hand, and whatever the code does in the next three seconds is all you get. Here is what each common payload actually does on scan.
| Payload | What happens on scan | Works offline | Typical size | QR version at level M |
|---|---|---|---|---|
| vCard (contact file) | Contact preview opens, one tap saves name, phone, email | Yes | 120 to 180 bytes | 7 to 9 |
| LinkedIn profile URL | Profile opens in browser or app, they tap Connect | No | 35 to 45 characters | 3 to 4 |
| Website URL | Homepage opens, nothing is saved | No | 20 to 40 characters | 2 to 3 |
| tel: phone link | Dialer opens with your number filled in | Yes | 15 to 20 characters | 1 to 2 |
| mailto: email link | Blank email draft opens, addressed to you | No | 25 to 35 characters | 2 to 3 |
Conference halls and basement meeting rooms are exactly where mobile signal dies, and only the vCard and the phone link still work there. A URL that cannot load is a dead scan, and nobody tries again later.
Why a vCard wins the handshake moment
A vCard QR stores the contact data inside the code itself, not on a server. The native camera on iPhone (iOS 11 and later) and on nearly every current Android phone decodes it and shows a contact preview with a save button. There is no hosted profile to pay for, no redirect that can break, and nothing that expires. Five years from now the same printed card still saves the same contact.
The one rule: keep the vCard lean. Name, phone, email, plus company and job title if you want them, lands around 120 to 180 bytes and produces a version 7 to 9 code at level M, which is 45 to 53 modules per side. Add a postal address, a second phone, and a note field and you push past 300 bytes, and the tighter grid gets hard to read at 2 cm. The vCard QR code generator builds the code in vCard 3.0 format in your browser, so you can watch the density change as you add or drop fields.
Two audiences justify a different payload. If you are job hunting or your value lives in your work history, a profile link converts better than a saved contact, and the LinkedIn QR code generator makes a code any camera opens straight to your Connect button, no LinkedIn in-app scanner needed. And if you run a trade or sales role where the only outcome that counts is a call, a tel: code from the phone number QR generator opens the dialer with your number already filled in, so nobody retypes digits wrong.
Size and placement on a 3.5 x 2 inch card
A standard US business card is 3.5 x 2 inches, which is 88.9 x 50.8 mm. The working floor for a vCard code is 2 x 2 cm. The math behind that floor: a version 8 code is 49 modules across, so at 20 mm each module is about 0.41 mm wide, and a phone camera held 10 to 15 cm away resolves that comfortably. Shrink the same code to 15 mm and each module drops to 0.31 mm, which starts failing on textured stock and older cameras.
| Print width (version 8 vCard) | Module size | Verdict |
|---|---|---|
| 15 mm | 0.31 mm | Fails often, especially on textured or dark stock |
| 20 mm | 0.41 mm | Minimum safe size |
| 25 mm | 0.51 mm | Comfortable, scans first try for most phones |
| 30 mm | 0.61 mm | Very easy scan, but dominates the card back |
Placement rules that survive real print runs:
- Put the code on the back of the card. The front carries your name and role; the back carries one code and a short caption like "Scan to save my contact", which tells people what the reward is.
- Respect the quiet zone. ISO/IEC 18004 requires a margin of 4 modules of background color on all four sides. On a 25 mm code that is about 2 mm of clear space, but give it 3 to 4 mm so nearby text and logos never bleed into it.
- Keep the code at least 5 mm from every trim edge. Guillotine trim on short runs commonly shifts 1 to 2 mm, and a shaved quiet zone kills scans.
- Print dark modules on a light background. Inverted codes, light on dark, fail in many default camera apps.
- Pick error correction level M for a clean code, or H if you overlay a small logo. Level H can restore roughly 30 percent of the code's codewords under ISO/IEC 18004, but it also adds modules, so do not combine H with a bloated vCard.
Matte or glossy: the finish changes scan reliability
Glossy coating is the quiet killer of business card QR codes. A gloss or UV coated surface reflects overhead lighting as a hard white hotspot, and when that hotspot lands on the code the camera's exposure blows out a patch of modules. The person tilts the card, the hotspot moves, and the scan drags or never lands. Matte, uncoated, and soft-touch finishes scatter light instead of mirroring it, so they scan at far wider angles.
Practical calls: order matte or uncoated stock if the card exists mainly to get scanned. If you love a glossy front, keep the back matte and put the code there. Never place spot UV gloss or foil stamping over the code area, both create mirror reflections that cameras cannot punch through. Dark navy or charcoal modules on cream stock are fine as long as contrast stays strong; pastel modules are not.
Test before you print 500
A typical short run is 250 to 500 cards, and a broken code turns all of them into scrap. The full test costs one sheet of paper and five minutes:
- Print the design at home at 100 percent scale on plain paper. Screen tests lie, paper does not.
- Scan with an iPhone camera and with an Android camera or Google Lens. The platforms use different decoders; passing on one does not guarantee the other.
- Test at 15 cm and at 30 cm, in dim light, and with the card tilted about 30 degrees to simulate glare.
- Open the saved result and check every field. A digit typo in the phone number survives the scan test and then ships on 500 cards.
- Ask the print shop for a printed proof of the final stock and finish before the full run.
If the code hesitates on any phone, run through the checklist in why a QR code will not scan and how to fix it before blaming the printer. If the proof itself comes back soft or smudged, the causes and fixes for blurred QR codes cover resolution and export settings.
What not to encode
Some payloads technically work and still waste the moment:
- An email-only mailto: code. It opens a blank draft the other person is supposed to write on the spot, with nothing saved to contacts, and most of those drafts die unsent. If email matters, put it inside the vCard.
- A bare homepage URL when your goal is contact capture. They glance at your site, close the tab, and your number is nowhere on their phone.
- A vCard with an embedded photo. Even a tiny base64 photo adds 2,000 or more characters and pushes the code toward version 40, the largest grid at 177 modules per side, which will never scan at card size.
- A free third-party short link in front of your real destination. When that service changes plans or shuts down, every printed card breaks, and the guide on whether QR codes expire explains exactly which setups die and which do not. If you genuinely need an editable destination, build the dynamic redirect on your own domain so nobody else holds the switch.
The short version: encode a lean vCard, print it at 20 to 25 mm on a matte back with a protected quiet zone, and test on both platforms from a paper proof before committing to the run. Every generator here runs free in the browser, and the rest of the lineup, from label and asset tag codes to Wi-Fi and payment codes, lives in the QR tools collection, with deeper how-tos in the guides library.