How to put a QR code on a business card

·6 min read

Point the code at a web page rather than raw contact details, generate it as a PNG at 512px or larger, and print it at least 0.8 inches (2 cm) square with clear white space on all four sides. The decision that matters most isn't the code itself. It's what sits behind it, because a code pointing at a live page can be changed after printing and a code holding your phone number can't.

Decide what the code opens first

This is the step people skip, and it's the one that decides whether the card is still useful in a year. A QR code is just an encoded string. What you encode is the real choice, and there are broadly three options.

  • Raw contact details (a vCard). The code holds your name, number and email directly. It works without an internet connection, which is genuinely useful at venues with bad signal. The catch is that it is permanent: change your number and every printed card is wrong.
  • A plain website URL. Simple and updatable, but it drops someone on your homepage rather than giving them a way to save you.
  • A digital card page. The code opens a mobile page holding your details and links, with a save-to-contacts button. Because the page is live, you can change what's on it after the cards are printed.

Generate the code

Any generator that outputs a PNG or SVG will do, and you should not pay for one. Two things to check before you download: that the file is at least 512 pixels square (or an SVG, which has no fixed size), and that the tool isn't routing your code through its own shortener. Free generators that wrap your link in their domain can stop working when the free tier ends, which turns every printed card into a dead end.

If your card lives on Blyn, the QR code is generated for you on the share panel once the card is published. A 512px PNG you can download and hand straight to a printer. It's on the free plan, and it encodes your card's public URL, so editing the card later updates what the code opens.

Size it for print

This is where most cards fail, and it fails after you've paid. The specs are short and worth following exactly.

  • Minimum size: 0.8 inches (2 cm) square. That is the practical floor for a phone camera at arm's length. One inch (2.5 cm) is safer and still fits comfortably on a standard card.
  • Quiet zone: leave clear white space on all four sides, roughly the width of four of the code's own small squares. Scanners use that border to find the code. Art or text pressed against the edge is one of the most common reasons a code won't read.
  • Contrast: dark code on a light background. Inverted codes (light on dark) fail on a meaningful share of scanners, and mid-tone brand colors are worse than plain black.
  • Resolution: 300 DPI at final print size. A 512px PNG covers up to about 1.7 inches at 300 DPI, so it is comfortably enough for a card.
  • Keep it out of the bleed. Anything within about 3 mm of the card edge can be trimmed off.

Where to put it

The back of the card, on its own, is the most reliable placement. The code gets the space it needs and the front stays readable. If it has to go on the front, bottom-right corner is conventional, because that's where a thumb naturally isn't.

Add a short line of text next to it saying what happens when it's scanned. “Scan to save my details” converts better than a bare code, because a QR code with no label asks someone to take a small leap of faith with their camera.

Test before you print

Print one card on ordinary paper at the exact final size and scan it with more than one phone. Ideally an older Android as well as a current iPhone, because camera quality is the variable you can't control. Scan it in poor light and at arm's length, not just under a desk lamp at 15 cm. If it hesitates at all, make the code bigger; that is nearly always the fix.

Also open the destination on a phone rather than a laptop. The whole point of the code is that someone scans it on a phone, and a page that looks fine on a desktop can be unusable on a small screen.

Mistakes that cost a print run

  • Encoding a phone number or email directly, then changing it.
  • Using a free generator that shortens the link through its own domain and later expires.
  • Printing the code smaller than 0.8 inches to fit the layout.
  • Placing artwork or text hard against the code with no quiet zone.
  • Reversing the colors for aesthetic reasons.
  • Never scanning the physical proof, only the file on screen.

The short version

Point the code at a page you control, generate it at 512px or larger, print it at 0.8 inches or bigger with clear space around it in dark-on-light, label it, and scan a physical proof on two phones before approving the run. That sequence takes about ten minutes and is the difference between a card that works and a box of cards you can't fix.

Build your free page in about a minute

Unlimited links, lead capture, click analytics and a QR code, all on the free plan.

Try it free

FAQ

Frequently asked

The questions people search alongside this one.

Generate the code as a PNG at 512px or larger, place it on the card at a minimum of 0.8 inches (2 cm) square with clear white space on all four sides, and keep it dark-on-light. Print one physical proof and scan it with two different phones before approving the full run.

At least 0.8 inches (2 cm) square, and 1 inch (2.5 cm) if the layout allows it. Below that, older phone cameras start to struggle at normal scanning distance. Leave a clear border around the code roughly four modules wide, since scanners use that space to locate it.

A web page, in nearly all cases. A code that encodes your phone number directly works offline, but it can never be changed once printed. A code pointing at a live page can be updated whenever your details, role or links change, and the printed cards keep working.

Many are, but check one thing first: whether the tool wraps your link in its own domain. If it does, your printed cards depend on that company's free tier continuing to exist. A code that encodes your own URL directly has no such dependency.

No. The camera app on any current iPhone or Android reads QR codes natively. The recipient points their camera at it and taps the link that appears. Nothing to install on either side.