QR Code Print Rules: Size, Error Correction and Contrast That Actually Scan

Minimum physical size: think in modules, not millimetres

A QR code is a grid of modules. The rule of thumb for reliable phone scanning is a module size of at least 0.25 mm for close-range print and 0.4 mm or more for codes people scan from a distance, plus a quiet zone of at least four clear modules on every side.

The physical size that results depends on how much data you encode - a short URL produces a small grid (21x21 modules at version 1) while a long vCard or Wi-Fi string pushes the grid much larger, so the same printed width gives you smaller modules and a harder scan.

The pattern is honest: the further away the viewer stands, the bigger the code must be, and the less data you should pack into it. A long URL that forces a dense grid is the most common reason a large poster still scans badly.

Error-correction levels: L, M, Q and H

QR codes deliberately waste some capacity to store redundancy so a damaged code still reads. The generator exposes the four standard levels: Low (7%), Medium (15%), Quartile (25%) and High (30%) recovery of codewords.

Pick by how rough the code's life will be. M is the sensible default. Use Q or H when the code may be scratched, folded, printed small, or partly covered - and crucially when you plan to put a logo in the middle, because the logo destroys modules that only higher error correction can survive.

The trade-off is density: higher error correction means a larger grid for the same data, so a long payload at level H can get big fast. Do not default to H out of caution; raise it deliberately when redundancy buys you something real.

Contrast, colour and the quiet zone

Scanners read the difference between dark modules and light background. Keep it high: near-black on white is safest. Reversing it (white on black) works on many cameras but not all, and coloured codes fail when the two colours are too close in brightness - a red-on-green code is unreadable to most phones even though you can see it.

If you tint a code, tint the modules and keep the background light, and check that a greyscale version still shows clear separation. The four-module quiet zone is not decoration: it is the border the decoder uses to find where the code starts, and cropping it against an edge or pattern is a top cause of no-scan.

Print quality and finish: DPI and matte vs gloss

Print at 300 DPI or better so module edges stay crisp; a blurry or dithered print softens the squares and defeats detection. For a code you will enlarge a lot, generate a large PNG and upscale it with the image upscaler rather than stretching a small file in a document editor, which produces jagged edges.

Choose a matte finish where the code will be lit from the front or photographed under lights: gloss creates specular glare that washes out modules on camera. Gloss is fine for controlled indoor posters viewed at an angle. If the printed piece will get handled, laminating under matte film protects contrast without adding shine.

The test routine before you print a run

Never trust a single on-screen check. Scan the actual printed proof, at the real distance, with more than one phone - iOS Camera and at least one Android scanner - because camera quality and decode libraries differ. Test in the lighting where it will live (a storefront code at dusk is a different code at noon).

Verify the payload too: a short link is easier to carry than a long raw URL, so route a dense vCard through a clean short link built with the URL shortener before you print, then re-encode. For product codes rather than URLs, the barcode generator covers the linear formats that QR is not meant to replace.

When you must hand the file to a print shop, convert the PNG to a crisp JPEG with PNG to JPG only if they ask for it; otherwise keep the lossless PNG so edges do not degrade.