Getting a QR Code Onto a Business Card That Still Scans
A European business card is 85 by 55 millimetres. Take off three millimetres of safety margin on each edge and 79 by 49 is what a designer gets, with a name, a title, a phone number, an email address and a logo already in it. The code is competing for something like a 25 millimetre square on a surface the size of two postage stamps.
Making the code is the easy half, and there are pages for it: QR codes for business cards and the business card code generator cover the content side. This is the other half, the one that goes wrong at the printer, where five hundred cards come back with spot UV across the face and a code that no longer reads.
The smallest code a card can actually carry
Cards are read at arm's length, so distance is not the constraint. Print is. The number that decides everything is the width of one module, which is the printed width of the symbol divided by the module count across it.
A short redirect link of around 25 characters produces a 33 by 33 symbol at the error correction level our generator uses. At 20mm wide that is about 0.6mm per module, which card stock holds comfortably. At 15mm it is 0.45mm, the floor, and only on coated stock off a good press. Below 15mm you are gambling.
Now the same card with a full contact record encoded into the pattern. A vCard carrying a name, two numbers, an email, a company, a title and a website runs a few hundred bytes and lands above sixty modules across. At 20mm that is roughly 0.3mm per module, below what card stock and phone cameras reliably manage, and a photo field makes it worse. The vCard format and what it costs has the field sizes. The conclusion for a card is short: a link fits, a full contact record usually does not. Budget 20mm of symbol plus its margin and build the layout around that.
Bleed, safety margin and quiet zone stack up
Three margins sit in a row on a business card, and only two of them appear in the printer's template. Bleed runs three millimetres outside the trim line, the safety margin three millimetres inside it, and the code's quiet zone inside that again. Designers treat the third as slack.
It is not slack. The blank field around the symbol is how a reader finds the pattern's edges. Our generator ships with a two-module margin and a slider up to eight, while the specification asks for four, so four is what a printed card wants. At 0.6mm modules, four modules is 2.4mm on every side, which turns a 20mm symbol into a 25mm footprint. Draw that footprint as a box in the layout and keep type out of it: a phone number placed a millimetre from the pattern is inside the quiet zone whatever the visual balance says.
Trim drift finishes the argument: guillotine cutting happens in stacks, and a stack shifts by fractions of a millimetre through the lift, so keep the code five millimetres in from the trim line.
Offset, digital and the processes that bite
Toner-based digital printing is the friendly process here. Powder fused to the surface barely penetrates the sheet, so dot gain is low and a 15mm code off a decent digital press is usually fine.
Offset brings two complications. The first is ink spreading into the stock, which fattens every dark module and narrows the light gap between neighbours, and uncoated card spreads the most: how paper decides the scan covers why the same file behaves differently on two sheets. The second is registration. A deep black built from all four plates looks better across large areas and is a trap on a grid, because every plate must register perfectly for every module edge to stay sharp. Specify 100% K, single plate, and say it to the printer rather than assuming somebody catches it. The prepress detail covers the rest, including sending vector so the file has no resolution to lose.
Letterpress and thermography are worth refusing at this size: one presses the pattern into the sheet and leaves a recess that shadows under raking light, the other domes the ink so it spreads and reflects.
Finishing: what saves the scan and what ends it
Matte or soft-touch laminate is the right default. It protects the surface, and because it scatters light it stops the card throwing a highlight back at a phone held under an office ceiling. Soft-touch is the one premium finish that helps both the card and the code.
Gloss laminate or an overall UV coating turns the card into a partial mirror, and that failure is angle-dependent, so it passes at your desk and fails on a conference floor. Spot UV over the code is the worst version of it. If spot UV runs anywhere on the card, mask the code and its quiet zone out of the varnish layer and write it on the marked-up file. Why finished pieces stop scanning has the optics and the proof test.
Foil stamped as the dark modules swaps flat ink for a reflective surface, so at the angle where foil catches light the contrast inverts locally; foil elsewhere is fine. Embossing through the pattern deforms the grid.
A code on a coloured card
The format specifies dark modules on a light field, and that polarity is not a style choice. On a dark card, do not invert the code: put a light panel behind a normal dark one, as a tile, an inset shape or a band across the foot. It satisfies the quiet zone honestly and works on readers that refuse inverted symbols outright.
Coloured stock is dyed through, so the light modules are the stock colour unless you print a panel over them, and white ink on dark stock is rarely fully opaque in one pass: ask for a double hit. On a mid-tone sheet such as kraft or navy, convert the artwork to greyscale and look at it. If the modules and their background are hard to separate there, no camera will separate them either.
One note that catches people at export: our engine paints a background rectangle behind every code, so there is no transparent PNG or SVG to drop over coloured stock. Set both colours in the design step instead.
Front or back
The back, in most layouts. The front carries the name and the logo, and 25 millimetres of anything crowds something. A code squeezed between two text blocks loses its quiet zone to whichever block the designer nudged last.
The exception is a card whose whole purpose is the scan: put the code large on the front with the name underneath. Either way, label it. A bare square on a blank back reads as a printing error, and one line of type, "scan to save my details", is the difference between a card that gets scanned and one that gets filed.
Before the run goes to press
Order one card at final size, on the actual stock, with the actual finish. Scan it at arm's length under office light and again by a window, on the oldest phone you can borrow. Look at the module edges under a loupe for light gaps that have closed: if two dark modules have merged anywhere, the code is too small for that stock. Decode the physical card with a reader that shows the string, and read the string, because the wrong file reaching the press is more common than anybody admits. Then confirm the marked-up file excludes the code area from every varnish, foil and emboss layer.
