QR Code Print Size Guide

The short answer

A typical retail QR code with a GS1 Digital Link URL on it lands somewhere between 18 mm and 25 mm on a side. Below 15 mm, phone cameras start to struggle. Above 30 mm, you're wasting valuable label real estate.

But "typical" hides the real story. The actual answer depends on three numbers: how long your URL is, what error-correction level you picked, and what GS1 X-dimension your packaging requires. Get any of them wrong and your QR code either won't scan in the field or won't fit on the package.

What is the GS1 X-dimension?

The X-dimension is the width of one QR module — the smallest dot in the code. It's the unit everything else is measured in. The GS1 General Specifications publish two threshold values for retail packaging:

• 0.495 mm — Absolute GS1 minimum X-dimension. Below this, mobile phone cameras start failing under typical store lighting and at typical scan distances.
• 0.625 mm — GS1 recommended X-dimension. Comfortable for phone cameras, scan guns, and self-checkout imagers. This is what you should target unless space is at an absolute premium.

These thresholds are not arbitrary. They come from the resolution limits of typical CMOS imagers and the focusing distance of consumer phone cameras held at a normal arm's length. Below 0.495 mm, the imager can't reliably distinguish adjacent modules; above 0.625 mm, you're paying packaging real estate that you don't need to.

QR version vs. print size

QR codes come in 40 "versions". Each version adds 4 modules to each side of the data grid:

• Version 1 = 21 × 21 modules
• Version 2 = 25 × 25 modules
• Version 3 = 29 × 29 modules
• …
• Version 40 = 177 × 177 modules

The version your QR code lands on is determined by how much data it carries, the error-correction level, and which encoding mode the QR encoder picks (numeric, alphanumeric, byte, kanji). A short URL on a short domain might land Version 2; a long URL on a long domain might land Version 6 or 7. Each version up means more modules — and at a fixed X-dimension, more modules means a physically larger code.

The 4-module quiet zone is non-negotiable

Every QR code must have a 4-module-wide white border on all four sides. This is the "quiet zone". The decoder uses it to find the symbol on the page; without it, the locator algorithm has nothing to lock onto and the scan fails.

So the total area you need to allocate is the data-grid module count plus 8 (4 modules each side). For a Version 3 QR (29 × 29), that means 37 × 37 modules of label real estate, even though only the inner 29 × 29 carries data.

Putting it together

The math is straightforward:

minimum_mm = (modules_per_side + 8) × 0.495 mm
recommended_mm = (modules_per_side + 8) × 0.625 mm

For a typical Version 3 QR encoding a short GS1 Digital Link URL on a brand-owned resolver domain:

• Total modules: 29 + 8 = 37
• Minimum: 37 × 0.495 mm ≈ 18.3 mm (0.72 in)
• Recommended: 37 × 0.625 mm ≈ 23.1 mm (0.91 in)

Real-world failure modes

We see four recurring failure modes that send QR codes back to reprint:

1. Designer scaled the QR but ignored the version

A designer takes the QR generator's output and resizes it to fit the available space. If the source QR was Version 6 and the available space only allows ~16 mm, the resulting X-dimension drops below 0.495 mm and the code stops scanning reliably. The fix is to shorten the URL (smaller version → larger X-dimension at the same overall size) rather than scale down the symbol.

2. Quiet zone trimmed by the print layout

The packaging artwork places copy or graphics flush against the QR data grid because "the box ends here". The decoder loses the locator and the code fails. The fix is to either reserve the full 4-module quiet zone in the artwork or pass a wider quiet zone to the QR generator if the layout permits.

3. Lowercase URL silently inflates the version

QR encoders pick the smallest mode that can represent every character. Uppercase URLs (HTTPS://EXAMPLE.COM/01/...) can use alphanumeric mode (≈5.5 bits per char). Lowercase URLs (https://example.com/01/...) drop to byte mode (8 bits per char) — pushing the version up. Cloudflare and most CDNs normalise hostnames before serving, so uppercasing the scheme + domain is safe and often saves a version.

4. Long brand domain with high error-correction

A brand picks a long resolver domain ("acme.gs1resolvers.com") and sets ECC to H "for safety". Both choices push the version up. The fix is to use a short brand-owned resolver domain and pick ECC level M (the GS1 recommendation for retail packaging) — H is only worth the overhead when the print is exposed to harsh conditions like outdoor signage.

Domain length is the lever you control

Of all the factors, domain length is the easiest to act on at design time. Compare three patterns for the same GTIN:

A 12-character difference in domain length costs you 4 mm of print real estate at GS1 minimum sizing. On a 50 ml product label, that's significant.

Sunrise 2027: print-size requirements get stricter

GS1 Sunrise 2027 — the global initiative to make 2D barcodes (QR + Digital Link) scannable at retail point-of-sale by 2027 — locks in the 0.495 mm minimum X-dimension as a hard threshold. Codes printed below this won't be expected to scan reliably at checkout, and many retailers will reject suppliers that ship below-spec packaging.

If you're designing packaging today, designing to the 0.625 mm recommended X-dimension gives you headroom for the 2027 transition and for the inevitable real-world wear-and-tear that shrinks an X-dimension's effective size: ink bleed, label crinkling, low-light store conditions, and aging phone cameras.

Free tools to help you size correctly

• Print Size Calculator — paste any URL, get the exact min and recommended print size in mm and inches
• QR Code Inspector — deep technical breakdown including encoding modes, mask pattern, and concrete optimization recommendations

Further reading

• GS1 General Specifications ↗ — the authoritative source for X-dimension and quiet-zone requirements
• ISO/IEC 18004 (QR Code spec) ↗ — module-grid sizing per version, encoding modes, error correction, mask patterns
• GS1 Digital Link Resolver explained — how the resolver layer turns the URL inside your QR into a routable destination