How to Print Your Digital Name Card's QR Code So It Scans First Time

A QR code that scans perfectly on your screen can fail the moment it is printed. The ink spreads, the code is shrunk to fit a corner, the brand colour is too pale, or the printer trims the blank border away. Nobody notices until a prospect is standing in front of you with their phone raised and nothing happens.

This guide covers the print side only: what a phone camera needs from a printed code, how large it should be, how much contrast and blank margin it needs, where to place it, and the test routine to run before a print run. It is general good practice, not a Gotka or share2.io specification, and the sizes it mentions are rules of thumb to confirm with your own test print. For which to lead with, see NFC vs QR business cards; for what a QR code and a short link each do, see QR codes vs short links; for handing the card over in person, see how to share a digital name card.

Why a code that works on screen can fail on paper

A screen is backlit, sharp and the same size every time. Print is none of those. The paper soaks up some ink, the finish reflects light, the artwork gets resized by whoever lays out the card or flyer, and the code is read in a shop, a car park or a meeting room rather than on your desk. Four things change between the screen and the paper.

• Size. A code that was comfortable at full screen width gets shrunk to fit a corner of a card or a flyer.
• Contrast. A pale brand colour that looked fine on a monitor prints lighter and flatter, and the camera cannot tell the dark squares from the light ones.
• Sharpness. A small image enlarged for print, or a screenshot of a code, has soft edges that blur the squares together.
• Surroundings. Glare from a glossy finish, a busy photo behind the code, or a border that touches it all make the pattern harder to find.

There is also a reason to be stricter about codes than about other print details. The profile behind your card can be edited after printing (see can you edit a digital name card after printing), so a wrong phone number can be fixed. A code that does not scan cannot be fixed that way, because the code itself is what was printed.

What a phone camera needs from a printed QR code

A QR code is a grid of small dark and light squares, called modules. The three large squares in the corners tell the camera where the code is and which way up it sits; the rest of the grid carries the web address. To read it, the camera must see the whole pattern, tell dark from light reliably, and have enough pixels on each module. The more characters in the address, the more modules the code has, and the smaller each one must be at a given print size.

The next sections take these in turn. Each one is cheap to get right on the artwork and expensive to discover after the whole run is printed.

Contrast and colour: keep it dark on light

The safest code is black, or a very dark colour, on plain white. Most of the trouble comes from trying to make the code match the brand.

• Use a dark shade of your brand colour. Deep navy, dark green or charcoal on white usually scans well. Yellow, light orange, pastels and mid-greys do not.
• Avoid reversed codes. A light code on a dark background is read by many phones but not by every scanner, so if you want that look, test it on several devices or put the code on a white panel instead.
• Do not print over a photo or pattern. Place the code on a plain white or light panel, even a small one, rather than on the picture itself.
• Skip gradients and effects. A fade towards the background, shadows, outlines and rounded or dotted squares all reduce how clearly the modules stand apart.

A quick check before you send artwork to print: convert the layout to black and white. If the code looks washed out or hard to pick out in greyscale, a camera will find it hard too.

The clear margin: why a code needs empty space around it

The blank border around a QR code is often called the quiet zone, and it is the most commonly cropped part of a printed code. The camera uses it to see where the pattern starts. A commonly given guide is a border about four modules wide on every side, which in practice means leaving a visible band of plain background all the way round.

• Do not let anything touch it. Text, a frame, a logo, the edge of a coloured block or a decorative line inside the border can stop the camera locking on.
• Allow for trimming. Cards and flyers are cut after printing and the cut is never perfectly the same twice, so keep the code and its margin well inside the trim line.
• Keep it off folds, staples and perforations. A crease through the pattern is a gap in the data.
• Put any label outside the margin. A line such as "Scan to save my details" goes beside or below the clear border, not inside it.

Size and distance: how big is big enough

There is no single correct size, because it depends on how far away the phone will be. A widely quoted rule of thumb is that the code should be about one-tenth as wide as the distance it is scanned from. Someone scanning from about 50 cm away wants a code around 5 cm wide; from about a metre, around 10 cm. Treat that as a starting point, not a specification: a good camera in good light does better, an older phone in poor light does worse, and a denser code needs more room.

The practical consequence is simple. If you are putting the same code on a card and on a poster, do not scale one design to fit both. Make each at its own size and test each one.

Keep the code simple and the file sharp

Two choices made before printing decide how sharp and how forgiving the code is.

• A shorter address makes a simpler code. A long address with extra tracking parameters produces a dense grid of tiny squares that needs more size and better print. If you are creating a code yourself, point it at the shortest address that works; the difference between the two entry points is explained in QR codes vs short links.
• Use the largest, cleanest file you can get. A vector file such as SVG or PDF stays sharp at any size, while a small PNG goes soft when enlarged. Do not screenshot a code from a phone screen and place that in your artwork, and never stretch it: a QR code must stay perfectly square.
• Be careful with logos and styling. A small logo in the middle or rounded dots can still scan, but each decoration removes some of the margin for error, so test those versions harder.

Paper, finish and material

The same artwork can scan on one stock and fail on another. Ask for a proof on the material you will actually use.

Placement: where the code goes and what sits beside it

A readable code in the wrong place still fails. Think about the moment of scanning: where the person is standing, what they are holding and how long they have.

• On a card: give the code a clear panel, usually on the back, and use one code rather than several. Add a short line that says what happens, such as "Scan to save my contact", so people know why to scan.
• On a flyer: put it where the page is flat and uncluttered, often a lower corner with a generous margin, not across the fold.
• On a counter or window: place it at a height people can reach without stooping, where they wait, and out of direct glare. Many counters already carry payment codes. Keep your card code apart from them and label each one, so nobody scans one expecting the other.
• On an email signature or slide: make it large enough to scan from a screen, and remember a short link is easier to click than a code is to scan. The same profile can be reached either way.

Also remember who can see a code on a public sign. Anyone who scans it reaches whatever is on the profile, so check the details first; which personal details to put on a digital name card covers that.

The test routine to run before a print run

This is the part that saves the money. Work through it in order, and do not release the artwork until every step passes.

1. Check the screen version first. Scan the digital file with two phones. Confirm that it opens the right profile, that the name and numbers are correct and that saving to contacts works. Fix content now, while nothing is printed.
2. Print one proof on the real material at the real size. If the final run will come from a print shop, ask for a proof on the same stock. A proof from an office printer on plain paper only partly tells you how the run will behave.
3. Scan it on at least three different phones. Use an iPhone, an Android phone and an older or budget model, each with its built-in camera. If your customers commonly use a scanner built into a messaging or payment app, try that too.
4. Test in realistic conditions. Bright daylight, dim indoor light, the real distance, a slight angle and a slightly unsteady hand. A code that only scans when you hold the phone perfectly still is not ready.
5. Check what happens after the scan. Does the page load quickly on mobile data, not only on Wi-Fi? Does it read well on a small screen? Does save-to-contacts work?
6. Hand it to someone who has never seen it. Give them the proof without instructions and watch. If they hesitate, the placement or the wording beside the code needs work.
7. Check the delivered batch. When the run arrives, scan a handful of pieces from different parts of the box before you hand any out or print the same code on more material.

If it will not scan: a quick fix table

Change one thing at a time and re-test, so you know which change worked.

If your card also has an NFC chip and it is the tap that is failing, that is a different problem with different fixes; see NFC business card not tapping.

Plan your codes before you print

A print run is the wrong time to find out how many codes your plan allows. On share2.io, the platform behind Gotka's digital name cards, the number of QR codes depends on the plan.

Decide how many separate codes you actually need, for example one for cards, one for a flyer and one for a counter sign, and what each should open, before you send anything to print. If the number is close to your plan's limit, free vs Pro vs Team shows what each plan includes, and what your scan count is telling you explains how to read the results afterwards.

Common mistakes

• Testing only on your own phone. The best phone in the room is the least useful test.
• Placing a screenshot in the artwork. It is low resolution and prints soft.
• Shrinking the code to fit a corner. Size it for the distance, not for the layout.
• Matching the brand too closely. A pale or reversed code looks stylish and scans badly.
• Cropping the clear margin. Frames, text and trim lines that touch the code are a common cause of failure.
• Printing the whole run before a proof. A proof costs little; a reprint costs the whole job.
• Leaving it unlabelled. A code with no words beside it, or one sitting next to a payment code, gets ignored or mis-scanned.
• Relying on the code alone. Where a code is awkward to scan, such as a distant poster, offer a short link or an NFC tap as well.

Where Gotka Technologies fits

Gotka's Digital Name Card service runs on the share2.io platform, where subscription plans and card options are ordered at share2.io/shop. Profiles are shared by QR code or NFC tap and save to the other person's contacts, and because the profile is editable, the details behind a printed code can change without a reprint.

If you want a physical NFC card with a printed design, Design-Ready is RM118 (a ready-made design template, a physical NFC card and printing, and digital profile design) and Custom-Design is RM338 (a fully custom card design, a physical NFC card and printing, and digital profile design); Design-Ready vs Custom-Design compares them. Digital Only: Self Setup is RM0 and Digital Only: We Design is RM48, and neither includes a physical card. Whichever you choose, run the test above on the first physical card or print you receive, on several phones, before you hand it out or reuse the same code on flyers and signs. If your code leads on to a website, Gotka's web design service runs from design through ongoing maintenance.

Key terms used in this guide

• QR code: a square pattern that a phone camera scans to open a web address, here your digital profile.
• Module: one small dark or light square in the code's grid.
• Quiet zone: the empty border around a QR code that lets the camera find where the pattern starts.
• Contrast: the difference in darkness between the code's dark squares and its background.
• Vector file: a file format such as SVG or PDF that stays sharp at any size, unlike a small pixel image.
• Proof: a test print on the real material at the real size, made before the full run.
• Short link: a shortened web address that opens the same profile and can be typed or tapped instead of scanned.
• NFC card: a physical card that opens your profile when held against a compatible phone, as an alternative to scanning.