QR Code Print Size and Scan Distance: How Big Should It Be?
If people cannot scan it from where they stand, the size is wrong — no matter how good it looks.
No sign-up, no limits, no uploads — it runs 100% in your browser.
A QR code is only useful if a phone can scan it in a few seconds, in real light, from a real distance. That depends less on the code's design than on its size, contrast, and surroundings. A code that scans perfectly on a laptop screen can fail completely on a printed poster, a product label, or a shop window, because the viewing distance and lighting are different. Getting size and contrast right before printing saves reprints and lost scans.
Size follows distance, not the page
The rule to start from is simple: the further away the scanner stands, the larger the code must be. A code on a business card is scanned from a few centimetres away, so it can be small. A code on a poster is scanned from a metre or more away, so it must be much larger. A useful rule of thumb is that the code should be roughly one tenth of the scanning distance: for a scan from one metre away, a code around ten centimetres wide is a sensible starting point. Treat that as a starting point, not a guarantee, and test at the real distance before printing in bulk.
Resolution matters as well as physical size. A code that looks large on screen but is printed at low resolution will have fuzzy edges that phones struggle to read. Generate the code at a high pixel size for print, such as 1024 pixels for posters and packaging, and a smaller size is fine for screen use. Check the printed proof with several phones, not just one, because camera quality and apps vary.
Contrast and quiet zone are not optional
A QR code needs strong contrast between the dark modules and the light background. Black on white is the safest combination. Light colours on white, or a code placed over a busy photo, can fail even if the size is right, because the phone cannot tell where one module ends and the next begins. If you must use a brand colour, keep it dark and test it in the actual light where it will be scanned, including bright sunlight and dim indoor light.
Leave a quiet zone, a clear margin, around all four sides of the code, at least as wide as a few modules. Text, logos, borders, and other graphics crowded against the code can confuse scanners. A logo in the centre of a code is possible with some generators, but it reduces the code's error tolerance, so keep any central logo small and test thoroughly. If scanning reliability matters more than branding, skip the central logo entirely.
What the code contains changes the size it needs
Short links and short text produce simpler codes with larger modules, which are easier to scan at a distance. Long URLs, long text, and codes with high error correction produce denser codes with smaller modules, which need to be larger to scan reliably. If your code is very dense, shorten the destination first, for example by using a short, stable link, rather than printing a larger and larger code to compensate. A simpler code is almost always the better fix.
Static codes are the right choice for most printed uses. A static code encodes its destination directly, so it keeps working as long as the destination exists, with no tracking service in between. Dynamic codes, which redirect through a service, can offer analytics and editable destinations, but they depend on that service staying available. For a poster, a label, or a card that will exist for months, a static code to a stable destination is the safer, simpler choice.
Test before you print in bulk
Test the code in the real setting, not just on screen. Print one copy at the intended size, place it where it will actually be used, and scan it with at least two different phones, in the light it will be seen in, from the distance people will stand at. Check that the destination opens correctly and that the page it opens is mobile-friendly, because a scan that lands on a broken or desktop-only page wastes the effort. Only after that test should you print the full run, and keep the test copy as a reference if the run looks different.
Worked example
Worked example: you need a QR code on a shop poster that people will scan from about one metre away. You generate a static code for a short link at 1024 pixels, print it about ten centimetres wide, in black on white, with a clear quiet zone around it, and no busy background behind it. You print one proof, stand one metre away in shop lighting, and scan it with two phones. Both scan in a couple of seconds and open the correct page. Only then do you print the full poster run at the same size and settings.