The best printed QR size is the one that gives your real audience a comfortable scan on the actual material. There is no single width that suits a short website link, a detailed contact card, a curved bottle label, and a poster across a room. Physical size, pattern density, contrast, camera distance, and print quality all affect the result. Choose the dimensions after generating the real content, not before.
Separate two measurements at the start: how large the image will be on paper and how many pixels a raster file contains. A large download can be placed very small in a document. A small screenshot can also be enlarged until it looks large but has soft edges. Neither pixel count alone nor an appealing screen preview tells you whether a finished print will be easy to read.
Start with the intended scanning situation
Describe where the reader and the code will be. A hand-held business card can be moved closer to the camera, while a fixed sign behind a counter may be difficult to approach. A menu stand is seen from a seat, and a package may be curved or partly covered by a hand. Leave enough space for a person to frame the entire pattern naturally without twisting the object into an awkward position.
Use a trial size as a starting point
For a simple close-range code, a square around 25–30 mm wide can be a reasonable size to test first. Treat that as a trial layout, not a certified minimum or a guarantee. Dense content, decorative dots, a center logo, limited lighting, or a longer viewing distance may call for a larger result. When a layout has room, prefer a comfortable scan over making the code as small as technically possible.
Consider modules rather than only the outside square
The small dark and light cells in the pattern are its modules. A denser QR code places more of them within the same width, leaving less physical space for each one. Two images printed at identical dimensions can therefore have different reading demands. Generate the exact final address or payload before approving a layout, because adding data or changing error correction can change the pattern you need to reproduce.
Keep the light quiet zone around all four sides. DENSO WAVE’s code-area guidance specifies a margin at least four modules wide. Include that border in the space allocated to the image. Cropping it away to make the dark area appear larger defeats its purpose. A border drawn around the QR is not a substitute for the required clear space.
Translate raster resolution into a print requirement
When a layout requires a PNG, relate its pixel width to the planned physical width and the target print resolution. The calculation is: pixels equal width in millimetres divided by 25.4, multiplied by the chosen dots per inch. A 40 mm image at 300 dpi needs roughly 473 pixels across when rounded upward. This is a calculation about reproduction resolution, not evidence that every 40 mm QR code will scan.
Do not invent detail by enlarging a screenshot
A fresh 1024-pixel export gives a different source from a small preview stretched to 1024 pixels. Download the file rather than copying a screenshot containing browser scaling, interface controls, or compression. After importing it into a design application, inspect the export settings there too. A document tool can resample a crisp source into a lower-resolution image before the file reaches the printer.
Use vector output when your workflow supports it
SVG keeps the QR geometry scalable, while the generator’s PDF places vector shapes on a 100 mm square page. Your layout software can position that PDF at the intended final size; the PDF page size does not require printing every code at 100 mm. Check the application’s placement and scaling controls rather than relying on a thumbnail. Embedded logos still depend on their own raster resolution even when the surrounding modules are vectors.
Ask the print provider which formats it accepts and whether any conversion will rasterize the artwork. Keep proportions locked when resizing. Stretching only the width or height changes the square geometry. If JPEG is required, inspect its edges after the final conversion, since compression can introduce marks around high-contrast modules. Keep the original vector or PNG source so you can produce another file without repeatedly recompressing the same image.
Account for stock, finish, and surrounding artwork
A sharp proof on smooth office paper does not reproduce every production condition. Texture, ink spread, transparent labels, glossy varnish, and folds can change the pattern seen by a camera. Use a plain light backing for a dark code, especially on colored packaging or photographs. Leave the entire quiet zone free from neighboring text. A transparent export needs that same protection after it is placed on another surface.
Evaluate the finished object rather than only a flat print. A code wrapped tightly around a small container may not be visible as a whole square from one camera position. A crease through the center can obscure more than the design preview suggests. Moving the code to a flatter area or enlarging the available panel can solve a problem that changing resolution alone will not address.
Approve a real-size proof before the print run
Print one sample at the intended dimensions with page scaling disabled or explicitly controlled. Measure the finished square with a ruler. Try the scan at the expected distance, using ordinary lighting and more than one phone. Follow the resulting action as well: a code that opens the wrong menu is not successful merely because the camera recognized it. Record which source file and placement settings produced the approved proof.
If reading is inconsistent, work through concrete changes: increase physical size, shorten unnecessary content, simplify the pattern, remove the logo, or improve the backing surface. Compare each revision with the previous proof rather than changing everything at once. Keep a readable address or alternative instruction beside important codes. Your final dimensions should reflect this tested use case, and should be checked again if the payload or production material changes.