QR Codes on Business Cards: Small Codes That Still Scan

A business card measures 85 mm by 55 mm, and most of that is already claimed by your name, your title, and three or four lines of contact detail. Whatever survives is where the QR code has to live, which makes this the smallest code most people will ever print. It can work at that size, and it works more reliably than the design forums suggest. But two things break before anything else does, and both of them are physical rather than digital.

The size floor for a card

The general sizing rule for QR codes is that the code should be roughly one tenth as wide as the distance it will be scanned from. Nobody reads a business card from across a room. It gets held 10 to 15 cm from the face, which puts the arithmetic at 10 to 15 mm, and in practice a low-density code starts scanning reliably somewhere around 15 mm square.

Treat that as a floor, not a target. Design to 18 to 20 mm and you keep a margin for everything that goes wrong after the file leaves your machine: ink spread on uncoated stock, a slightly soft print, an older camera, someone scanning in a dim bar rather than a lit office. The visual difference between a 15 mm and a 20 mm square on a card is barely noticeable, and it is the entire safety margin for the scanner.

What breaks first: module size

A QR code is a grid of squares called modules, and how many modules you get is decided by how much data you encode. A version 3 code is 29 modules across. A version 6 is 41. A version 10 is 57. Print all three at 18 mm and the individual modules measure about 0.62 mm, 0.44 mm, and 0.32 mm.

That last number is where things fall apart. A phone camera focusing at 12 cm has to resolve every one of those cells as distinctly light or dark, and once a module drops toward a third of a millimetre it is competing with paper texture, ink spread, and the limits of a small lens. The failure is not gradual either. The code scans on your phone at your desk and then refuses on a colleague's three-year-old handset in a hotel lobby.

What breaks second: the quiet zone meets the trim

Every QR code needs four modules of blank space on all sides. At 0.6 mm per module that is about 2.4 mm of clear margin, so an 18 mm code really occupies closer to 23 mm of card. Designers push codes into corners because corners look tidy, and a corner is exactly where that margin gets taken by the guillotine. Cutting tolerance of a millimetre or two is normal, and a code that loses part of its quiet zone to the trim is a code that stops being found.

Keep the payload short, or the grid gets finer

This is the most common reason a business card code fails, and it has nothing to do with print quality. The code got denser because the URL got longer.

Compare two destinations at the same printed size. A short redirect of about 15 characters fits in a version 3 code at error correction level M: 29 modules across. A tracked link carrying campaign parameters, something in the shape of https://example.com/hello?utm_source=card&utm_medium=print&utm_campaign=q3-networking, runs to roughly 100 characters and pushes the same code out to version 9 or 10: 53 to 57 modules across.

Both of those still print at 18 mm, because 18 mm is the space you have. One has 0.62 mm modules and the other has 0.32 mm modules. You did not change the design, the stock, or the printer. You roughly doubled the resolution the camera has to achieve, purely by pasting in tracking parameters that a business card never needed in the first place.

The fix is a short URL. Put campaign parameters on the redirect target instead of in the printed pattern, or drop them: a card handed to one person at a time does not need UTM attribution to tell you where the scan came from. If you want scan counts, a tracked short link gives you those without lengthening the payload at all.

What to put behind the code

Three destinations make sense on a card, and choosing between them is really a question about how stable your details are.

What you link	Updatable after printing?	Works offline?	Best for
vCard encoded in the code	No, frozen at print time	Yes	Stable role, fastest possible handoff
Short link to a page you control	Yes, repoint the redirect	No	Freelancers, anyone likely to move
LinkedIn profile URL	Profile yes, printed URL no	No	Recruiting and job-search contexts

A vCard is the fastest handoff available. The scan offers a new contact with your name, company, phone, and email already filled in, nothing is fetched from a server, and it works in a basement conference hall with no signal at all. The cost is permanence: the details are baked into the pattern, so a new title or a new number makes the entire run wrong. Which fields to include and which to leave out matters a lot at this size, and we covered that in the guide to vCard QR codes.

A short link to a page you control is the opposite trade. It needs a connection, and it depends on your redirect and your domain staying alive, but it survives a job change, a new phone number, and a rebrand. If you print in batches of 500 and expect to be in the same role in three years, the vCard is the better card. If your links move around, the redirect is.

LinkedIn sits in between and is the weakest of the three for most people. The profile updates itself, which is the appeal, but the URL is long enough to add modules, and the scan lands on an app prompt or a login wall depending on the device. You have also handed your first impression to somebody else's product decisions.

Layout: put it on the back and give it room

The back of the card is almost always right. The front is doing identity work, and a QR code is a functional object that competes badly with a logo and a name. The back is usually half empty anyway.

Centre it, keep the full four modules of quiet zone, and label it in about three words: "Save my details", "See my work", "Book a call". A centred code with a label reads as a deliberate feature. A 12 mm code jammed between the phone number and the email address loses twice: it is below the size floor, and its quiet zone is occupied by the text it is sitting against.

Keep the whole thing at least 5 mm inside the trim line so cutting drift never touches the margin, and never let the code cross a fold or run into bleed. If the layout genuinely has no room for 18 mm plus its margin, the answer is to remove a line of text, not to shrink the code.

Finish matters more here than anywhere else

People hold a card 12 cm from their face, angled toward whatever light is in the room. That is the worst possible geometry for a reflective surface, because the reflection goes straight back into the lens.

Spot UV over the code looks expensive and scans terribly. So does a full gloss laminate under a ceiling light. Matte or untreated stock is the safe answer, and if the rest of the card must be gloss, ask the printer to leave the code area matte or untreated. Soft-touch laminates are generally fine, since they scatter rather than mirror.

The colour rule is simpler: dark ink on light stock, always. Never reverse the code, and never print light ink on dark stock. Inverted codes decode on some scanners and not others, and a card is exactly the wrong place to find out which one the person in front of you is carrying. If your card is black, put the code in a light panel rather than flipping it.

Test it before you print 500

Card runs are cheap per unit and expensive per mistake, because you find out months later when someone mentions it politely. Ten minutes of testing removes the risk:

• Print at actual size on the closest paper you have. A code checked on screen proves nothing, because a backlit display flatters the pattern in a way paper never will.
• Hold it normally. One hand, 10 to 15 cm, at whatever angle you naturally hold a card. Do not lay it flat and hover over it.
• Scan in poor light. A restaurant, a corridor, an evening room with one lamp. That is where cards actually get exchanged.
• Use at least two phones, one recent and one a few years old. Camera quality varies far more than people expect.
• Try it from a lock screen, since the other person will often scan without unlocking. Confirm the vCard prompt appears or the link resolves before the phone is even open.
• Check the destination on mobile, not just that the code decodes. A code that scans into a broken page is still a failed card.

If any of those fail, the fix is almost always one of three things, in this order: shorten the payload, enlarge the code, restore the quiet zone. Work through them in that order and the last one rarely comes up.

Build the code first and lay out the card around it rather than the other way round. Generate it at the size you actually intend to print, download vector from our generator so the module edges stay crisp at 18 mm, and hand the printer a file that already has its margin built in.