A Go / No-Go Check Before You Print
Most QR failures are decided before the file ever reaches the printer, in the moment someone chooses a size that looks right on screen. On a laptop, a 25 mm code looks generous. On a poster viewed from three metres away, the same code is a speck. The checker on this page turns that judgement into arithmetic: given the distance people will actually scan from, the phones they will use, and the light they will stand in, it tells you the minimum width that stands a chance, and whether your planned size clears it. It is a go / no-go gate, and it belongs before artwork approval, not after.
Distance is the dominant factor
The rule is the standard 10:1 distance-to-size ratio: the code should be at least a tenth as wide as the distance from which it will be scanned. A code on a table tent scanned from 40 cm needs 40 mm. A code on a window scanned from 3 metres needs 300 mm. The ratio tightens when conditions worsen — 9:1 when the audience includes older or budget phones with weaker cameras, and 8:1 in dim light or glare. Those adjustments are planning rules, not laboratory measurements, and they exist because the real world is rarely the best case. The most common sizing error is measuring the distance from the nearest kerb instead of from where people actually stand, so measure the real viewing position.
What to do when the plan fails
A failing check leaves three honest options. Enlarge the code, which is the right answer whenever space allows. Shorten the payload, which drops the version and enlarges every module without changing the print size — a short redirect is the classic fix. Or move the code closer to the viewer: a code on the door at eye level beats a code high on the window, even if the window version looks more impressive. What is not an option is hoping customers will walk closer. Some will, most will not, and the ones who do not are the campaign's lost conversions. A code that fails the check should not be printed on the assumption that behaviour will save it.
The check that still matters after the maths
- Print a proof at final size on the real substrate and scan it from the real distance.
- Test on an older phone, not just the newest one in the office.
- Test in the actual light: daylight, dusk, and artificial light if the code lives outdoors.
- Check the quiet zone survived the layout — a cropped margin fails codes that the maths approved.
- Re-check after any change to payload, placement, or substrate.
The maths takes ten seconds. The proof takes ten minutes. Both are cheaper than a reprint.
