QR codes on business cards: a complete guide

A QR code turns a paper card into a one-tap contact transfer. Done well it’s genuinely useful; done badly it’s a dense, unscannable square that makes the card look cluttered. The difference is a few specific choices.

Choose the right code type

For a business card, a vCard code is almost always the right answer. It encodes your contact details in a standard format, so one scan offers to save you as a new contact — no app, no website, no retyping. Alternatives and when they make sense:

• vCard — the default. Best for getting saved into someone’s phone instantly.
• URL to a personal or company page — better if you’d rather drive people to a portfolio, booking page or LinkedIn than hand over raw details.
• Both, on different cards — some people carry a networking card (vCard) and a sales card (URL to a landing page).

Keep the data lean

A vCard’s density depends on how much you encode. Name, mobile, email and company make a clean, coarse code that scans easily at small sizes. Add a second phone number, a full postal address, a website and a job title and the grid becomes noticeably busier — and a busy code printed at 2cm is exactly the kind that won’t scan. Encode the essentials; let the printed card carry the rest. Our troubleshooting guide explains why over-stuffed vCards are a common failure.

Size and placement

• Size: 2cm × 2cm for a simple code; 2.5cm if your vCard carries a few fields. Below 2cm, scanning gets unreliable on older phones.
• Placement: the back of the card is ideal — it gives the code room and keeps the front clean. A bottom corner works well, with the code’s quiet zone naturally protected by the card edge.
• Quiet zone: leave a clear margin of at least four modules (roughly the width of a corner square) on all sides. Don’t butt the code against text, a logo or the trim edge.

Print quality matters more on small codes

At business-card size, every module is tiny, so print precision counts. Use a 300 DPI or higher file — our Medium (256px) export covers a 2cm code. Never enlarge a small PNG to fit; regenerate at a larger size instead. Watch out for cheap card stock with heavy ink spread, which can blur module edges, and avoid glossy finishes directly over the code where overhead light causes glare. The full sizing and resolution detail is in our print size guide.

Contrast and brand colour

It’s fine to colour the code in your brand shade, but it must stay clearly dark on a light background. A pale or low-contrast colour scheme that looks elegant in the proof can fail under a phone camera. If you customise the colour, test-scan a printout before ordering the run, and oversize slightly to claw back the margin a non-black code gives up.

Always test before the print run

Order a single proof, or print one card on similar stock, and scan it with more than one phone — including the oldest you can find — under ordinary indoor light, held at a natural distance. If it saves your contact first time on a five-year-old handset, the run is safe. Testing on screen only is the classic mistake: backlit screens are far more forgiving than printed card.

Static, not dynamic

Use a static code. Your contact details rarely change, the card should keep working for years, and there’s no reason to tie it to a subscription that could lapse and kill every card you’ve handed out. If your number does change, you reprint — which you’d do anyway. See static vs dynamic for the reasoning.