Processed locally
Your input stays in this browser.
Scale begins with the viewing geometry
A useful planning relationship is symbol width W about viewing distance D divided by ten: W ≈ D/10. A poster expected to be scanned from 1.5 m therefore begins near 15 cm wide, while a counter card read from 30 cm begins near 3 cm. This ratio is a framing estimate, not a scanner specification; it only says how much of the camera view the symbol is likely to occupy.
The module is the limiting unit
The outer square is made of individual modules. If a 33 by 33 module code is printed 33 mm wide, each module is 1 mm; if the same payload is printed 15 mm wide, each module is about 0.45 mm. The four-module quiet zone surrounds that matrix, so the physical panel needs 41 mm rather than 33 mm in the first example. Measuring only the dark pattern quietly removes the margin the detector needs.
Payload density changes the arithmetic
Consider two 40 mm labels. A compact web address that fits a 29 by 29 matrix gives roughly 1.38 mm modules before adding quiet space. A detailed contact record that requires 49 by 49 modules gives roughly 0.82 mm modules at the same width. The label did not become less readable because its colour changed; the camera now has to resolve substantially smaller cells. Shortening the stored text or enlarging the label addresses that particular constraint.
Distance and print resolution pull in opposite directions
A wall sign may need a wide symbol so a visitor can frame it from several metres away. A thermal printer may require larger modules because its dots soften corners. These are separate constraints: choose a width large enough for the longest realistic scan, then verify that the printer can preserve every module at that width. A screen mock-up cannot reveal dot gain, laminate glare, or a seam crossing the square.
Use a real label calculation
For a menu tent scanned from 60 cm, the D/10 starting width is 60 mm. If the payload is a 37 by 37 matrix with a four-module quiet zone on each side, the available module pitch is 60 divided by 45, or about 1.33 mm. That leaves a measurable target for the printer and makes it clear why trimming the pale border is not a harmless way to gain room.
The boundary is the final environment
This guide cannot promise a minimum pixel count or a universal millimetre size. Motion, glare, autofocus, camera quality, curvature, print method, and payload all change the result. Test the final material at the nearest and farthest expected positions. If readers must hunt for focus or step closer than the placement allows, increase the physical symbol or reduce the encoded content.
Start with a location, not a minimum size
A 25 mm code on a takeaway cup and a 250 mm code on a station poster are not smaller and larger versions of one decision. The cup is read at arm's length; the poster may be framed from two metres away while people walk past. List the nearest and farthest useful scan positions before choosing artwork. If the poster has a 2 m target distance, D/10 gives a 200 mm starting width. Then test it from the actual path, because angle, crowding and glare can require a larger symbol.
Calculate the panel around the matrix
Suppose an encoder produces a 37 by 37 matrix. A four-module quiet zone on all sides makes the full panel 45 modules wide. At a requested 54 mm outside width, the module pitch is 54/45 = 1.20 mm, not 54/37 = 1.46 mm. The second figure silently ignores the border and can cause a label supplier to shrink every module. State whether a quoted width includes the quiet zone; otherwise two people can approve apparently identical 54 mm specifications that produce different physical symbols.
Use the payload to choose which variable to move
A web address such as example.org/a may fit a smaller matrix than a contact card containing name, telephone, email, organisation and address. If both are forced into the same 40 mm panel, the contact card has smaller modules. Do not try to solve that by darkening the colour or claiming a newer phone will compensate. Shorten the data, use a stable landing URL, or allocate a wider panel. The relevant unit is the module pitch after the quiet zone, not the character count printed on the artwork brief.
A worked menu-tent case
A café wants a code on a 70 mm-wide table tent, read from about 600 mm away. The distance estimate begins at 60 mm. Its 41 by 41 matrix needs a 49-module panel, giving 60/49 = 1.22 mm modules. The remaining 5 mm each side can carry the printed menu name and a readable URL, but not graphics touching the code. If testing shows guests lean to 300 mm before focus locks, increase the code rather than reducing the adjacent text until the stated 600 mm use case is real.
Print resolution is a different calculation
A display draws square pixels; a thermal, inkjet or screen-print process deposits marks with edges and spread. A code whose pitch is mathematically 0.45 mm can still lose its light gaps on absorbent stock. Ask the printer for the effective process and inspect the proof with a magnifier as well as a phone. Do not stretch the symbol horizontally to fill a label: GS1's verification material describes axial non-uniformity as a readability problem because the grid is no longer square.
Distance can make a high-resolution proof misleading
A desktop monitor lets a camera resolve tiny cells from 200 mm under even light. That tells little about a reflective sign seen at an angle or a code behind a counter. Test the final object at the longest anticipated distance, then repeat under the bright direction that causes glare. A result that requires the tester to tilt the object, wait unusually long for focus or crop the camera frame is evidence that the planned size has no operational margin.
Use standards in their proper scope
GS1 says that a QR Code quiet zone is four X-dimensions and that smaller modules can prevent reliable scanning; it also supplies particular module ranges for its retail application. Those values are useful when the use case is a GS1 retail symbol, but they are not a magic minimum for an event poster or private Wi-Fi card. The defensible rule for a general code is to calculate the actual module pitch, preserve the quiet zone, and prove the exact object with its real audience and capture distance.