QR Code Size — Scans Fail on Posters Because Too Dense
A conference hallway banner carries a QR the size of a coaster. From three meters away, phone cameras hunt for focus, never lock, and attendees type the URL by hand. The generator preview looked sharp on a 27-inch monitor. Print distance and data density — not your screen zoom — decide whether a QR works.
The distance rule of thumb
A widely cited practical guide: the QR’s physical width should be at least ~10% of the scanning distance (order-of-magnitude; verify for your print). Rough examples:
| Scan distance | Start with printed size |
|---|---|
| Hand / table (20–30 cm) | ~2–3 cm |
| Poster from 1 m | ~10 cm+ |
| Window cling from sidewalk | Larger still; test outdoors |
If people must walk up to the art to scan, you have a design problem even if the code is technically decodable.
Density: quiet payload vs noisy payload
QR versions grow as you encode more:
- Short HTTPS link (ideally with a short domain) → fewer modules → larger modules at the same print size
- Full vCard, Wi-Fi string, or UTM-stuffed URL → more modules → muddier at the same centimeters
Always prefer a short redirect for print. Keep UTM parameters on the redirect target, not burned into a giant QR.
Error correction vs branding
Error correction levels (L/M/Q/H) let the code survive damage and center logos:
- Higher correction → more modules for the same payload → denser pattern
- Big logo + low correction → failed scans
- Big logo + high correction + tiny print → also failed scans
Tradeoffs are real. If brand insists on a logo punch-out, increase physical size and correction, then test.
Pre-press checklist
- Generate at high resolution (vector SVG or large PNG). Do not upscale a 200px raster to a meter-wide banner.
- Keep the quiet zone (white margin) around the code — cropping to the modules kills scanners.
- Contrast: dark modules on light ground. Avoid QR on busy photography without a solid plate behind it.
- Print one proof. Scan with iOS and Android, several apps/cameras, in the real lighting.
- Laminate/glare: glossy finishes under spotlights can flare; matte often scans more reliably.
Create and resize candidates with qr-code, export a print-ready asset, and only then send files to the printer.
Digital placements differ
On phones, on-screen QRs can be smaller because distance is small — but watch compression in social apps and video. A QR shown for one second in a Reel is a different UX problem (time), not only size.
When scans still fail
- Camera too wide / ultrawide distortion at an angle
- Code warped on fabric banners
- URL expired or typo in the redirect
- Offline venue with captive portal weirdness (the scan worked; the page did not)
Separate “did not decode” from “decoded but the landing page failed.” Put a human-readable short URL under the code as a fallback — accessibility and dead-phone-camera insurance in one line.
Color QRs (brand-colored modules) need extra contrast testing; light gray on white fails outdoors even when the desktop preview looks stylish. Stick to near-black modules on a solid light plate unless you have printed proofs that scan in sun and shade.
Print QRs for the human standing in the room, not for the designer sitting at a desk. Shorten the payload, size for distance, protect the quiet zone, and proof on real devices before the bulk run.