A QR code on your business card should save the contact, not just look clever

A business card is a small surface with a lot to prove. Name, role, company, phone, email, and website already compete for space, and a QR code can easily turn a clean card into a crowded one. The fix is to decide what the code is for before you decide where it goes. If the code only repeats the website printed in plain text beside it, it adds little. If it saves the contact, opens a booking page, or sends the reader to a page they actually need, it earns its corner of the card.

Start with the reader, not the design. Someone who meets you at a conference, a trade show, or a client meeting usually wants one of two things: your contact details saved correctly, or a clear next step. A vCard code is built for the first job. It stores structured contact fields such as name, phone, email, company, job title, and website in a standard format that phones recognise, and scanning it can prompt the phone to offer the details as a new contact. A link code is better for the second job, for example a portfolio, a booking page, a product page, or a short introduction page. Mixing the two jobs into one code rarely helps. A code that tries to save a contact and sell a product at the same time leaves the reader unsure what will happen when they scan.

The choice between a static code and a dynamic code matters more on a business card than on a flyer, because cards are printed in batches and handed out over weeks or months. A static vCard code holds the details inside the pattern itself, which means it works without an internet connection at the moment of scanning, but it cannot be changed after printing. If your phone number, email, or job title changes, the old cards become wrong in a way that is hard to fix. A dynamic link code points to a short destination that you can update later, so a new role, a new phone number, or a new landing page does not force a reprint. That flexibility is the main reason to use a dynamic code for anything that might change, and to reserve a static vCard code for details you are confident will stay stable. If you are unsure which kind of code fits, read static versus dynamic codes before you send the card to print.

What should the code link to?

For most people, the safest default is a contact save or a single, focused page. A vCard is ideal when the meeting itself is the point: the other person wants to remember you, call you, or email you later, and spelling your name or address correctly matters. Keep the vCard lean. Name, one mobile number, one email address, company, and website cover almost every real follow-up, and every extra field makes the pattern denser and harder to read at card size. Use an international phone format with a country code, so the number still works when the card travels abroad, and use an email address you expect to keep. A personal address that disappears when you change jobs is a poor choice for a card that may sit in a drawer for a year.

A link code makes sense when the card is really an invitation. A designer might link to a portfolio, a consultant to a booking page, a founder to a one-page introduction, and a salesperson to a product demo. In each case, the landing page should answer the question the card raises, not dump the reader onto a generic homepage. If the card says you design restaurant menus, the scan should land on menus, not on a homepage where menus are one item among many. Add a short label beside the code, such as “Scan to save my contact” or “Scan to book a call,” so the reader knows what to expect. A bare code with no label asks for trust without giving a reason, and many people will simply not scan it.

There are destinations to avoid on a business card. Do not link to a page that requires an account, a long form, or a download before the reader gets any value. Do not link to a social profile that you rarely update, or to a page full of competing calls to action. And do not use a code as a substitute for the essential printed details. A card should still be readable without a phone. If the phone battery is dead, the light is poor, or the reader prefers paper, your name, company, and at least one contact method should still be visible in plain text.

Layout: give the code room to breathe

Business cards are commonly 3.5 by 2 inches in the United States and Canada, and 85 by 55 millimetres in the United Kingdom and much of Europe. That difference is small, but it matters when you are fitting a code, a logo, and several lines of text onto one side. Design for the market where the cards will actually be handed out, not just for the market where they will be printed, and confirm the trim size and bleed with your printer before you finalise the layout. A code placed too close to the trim edge can be clipped, and a code squeezed into a corner can lose the clear margin it needs.

The most reliable layout puts the code on the back of the card, or in a clear zone on the front where it does not fight the name and title. The back is often the better choice because it gives the code a full, uncluttered area and leaves the front for the person. If the code must share the front, keep it to one side, align it with the text block rather than floating it in the middle, and leave the quiet zone completely clear. The quiet zone is the blank margin around the code, at least four modules wide on every side, and scanners use it to find the edges of the symbol. Text, a border, a logo, or a background pattern inside that margin can break a scan even when the code itself is perfect. For a practical guide to that margin and to print sizes in general, see the QR code print size guide.

Contrast and background matter as much as position. Dark modules on a light background remain the safest choice, and a white or very light patch behind the code is worth the space even on a dark or colourful card. Reversing the code, printing it in a pale colour on a dark card, or placing it over a photograph may look striking, but it asks the camera to work harder in exactly the conditions where cards are scanned: dim event halls, bright sunlight, and hurried hands. If your brand colour is essential, use it in the surrounding design and in the call to action, and keep the code itself high contrast. A logo in the centre of the code is possible, but it covers part of the pattern, so use a higher error correction level and keep the logo small and clear of the three large corner squares that scanners use to orient the symbol.

Size: small card, firm minimum

Business cards are scanned from close range, usually with the phone held about 15 to 25 centimetres away, and that sets the size. A widely used rule of thumb is that the code should be about one tenth of the scanning distance, which points to roughly 2 centimetres for a card held at close range. Treat that as a floor, not a target. A short link code can work at about 2 centimetres, but a fuller vCard code, or a code with a logo, should be at least 2.5 to 3 centimetres wide, because the extra data makes the pattern denser and the individual modules smaller at the same physical size. One comparison makes the point clearly: a short link may produce a code about 29 modules across, while a longer contact record can produce a code of 61 modules or more at the same error correction level, so its modules are roughly half the size when both codes are printed at the same width.

That density effect is why a lean destination pays off twice on a business card. A short link or a lean vCard keeps the modules larger, which helps older phones, poor light, and textured card stock. If you must encode a lot of detail, compensate by printing the code larger, by shortening the link behind a dynamic code, or by moving the extra detail to the landing page instead of into the code itself. Do not compensate by shrinking the quiet zone, lowering the print resolution, or stretching the code to fit a gap. A distorted code is not a smaller version of a good code; it is a different, less readable pattern. Export the code as a vector file or as a high-resolution image at the final print size, and check that the printer has not resampled it, recolored it, or cropped its margin when placing it in the card file.

Proof before you print the whole batch

The cheapest scan test is also the most convincing: print one card at final size, on the final stock, and scan it with more than one phone. Test it in the light where it will actually be used, at the distance where it will actually be held, and with the card slightly tilted, as people really hold cards. Test the destination too, not just the scan. Does the contact save with the right name and number? Does the landing page load quickly and read well on a phone? Does the call to action on that page match the label beside the code? A code that scans to the wrong page, a page that asks for too much, or a contact that saves with a misspelled name all undo the benefit of an otherwise perfect card.

Check the details that are easy to miss in a design file. Confirm that the phone number includes a country code, that the email address is spelled correctly, and that the website address uses the current domain. Confirm that the code still scans after the card is handled, because gloss, embossing, foil, and heavy texture can all change how a camera reads the pattern. If you use a special finish, proof it on that finish, not on plain paper. If the card will be printed in two sizes or two regional formats, proof each version separately, because a code that works at one size may fail at the other. For a structured run-through, use the pre-print QR code checklist alongside your printer proof.

When a card fails, work through the usual causes in order: size, quiet zone, contrast, density, and distortion. Enlarge the code before you redesign the card, clear the margin before you change the colour, and shorten the destination before you add more data. If the problem persists, simplify. A card with one clear code and one clear label will outperform a card with two competing codes, a tiny code, and no explanation, however clever the design looks on screen. If a scan still fails after those fixes, see why a QR code may not be working and why a QR code may look blurry for the wider troubleshooting steps.

When to reprint, and when not to

A dynamic link code buys you time when details change. Update the destination, test the new page from a printed card, and keep handing out the batch. A static vCard code does not offer that escape: when the details inside it change, the honest fix is a reprint, because handing out cards you know are wrong costs more in missed follow-ups than a new batch costs in print. That is a practical reason to keep a small reserve of cards rather than printing a very large batch at once when your role, company, or contact details are likely to change soon. It is also a reason to put the most stable details in print and the most changeable details behind a dynamic link, so the card stays useful even as your work changes.

Finally, remember that the card is still a human object. The code should support the conversation, not replace it. Introduce yourself, write a note on the card if the moment calls for it, and let the scan handle the part humans get wrong: spelling, dialling codes, and long web addresses. A business card with a well-placed, well-sized, clearly labelled code does exactly that. It turns a brief meeting into a saved contact or a booked next step, without asking the other person to type anything, remember anything, or guess what you wanted them to do.