QR sizing decides whether a QR code feels like part of your design or like an afterthought stuck onto it, and it also decides whether the code scans. This guide sets out the working rules for sizing, explains why each rule matters, and shows how to apply it on real materials. The rules are practical rather than theoretical: each one can be checked on a proof with your eyes and a phone, before you spend money on a print run. If you follow them, your code will look intentional and still read quickly in the place where it will actually be used.
The core rules for sizing
Sizing is the decision about how large a QR code should be printed or displayed for the distance people will scan it from. A code that is too small forces people to crouch, zoom, or give up; a code that is too large wastes space that could carry the message.
Size the code for the scanning distance, not for the space left over on the page. Start from where people will stand, then work backwards to a size that reads comfortably from there. A code on a business card is scanned at arm length, while a code on a poster may be scanned from several steps away.
How sizing affects scanning
Keep the modules large enough to survive printing. Long web addresses and dense payloads make modules tiny, so a short link or a higher-capacity layout keeps modules bigger at the same printed size. If the code must carry a long payload, print it larger to compensate.
Leave the code large enough that the smallest details survive the print process. Ink spread, low-resolution printing, and textured stock all blur module edges, and a code that is already small has no margin for that blur. A proof printed on the real stock is the honest check.
Setting up sizing before you print
Test the size in the real setting, at the real distance, with real phones. A size that looks generous on screen can feel small on a wall, and a size that looks fine in the studio can fail in dim light. The test is cheap; the reprint is not.
Start with the plainest version that meets the brief, then add branding step by step, testing after each addition. If a step makes scanning slower, that step is the one to simplify. This gradual approach keeps the design honest: you can see exactly which choice helped and which choice hurt. Keep a copy of the last version that scanned instantly, so you can always fall back to a known-good design if a later variation fails.
Putting this into practice
Pick one live design that uses sizing and run it through this guide today. Print a proof at the final size, check the rules against it, and fix the first problem you find. Then scan the corrected proof with two phones in the real light. Keep the passing proof as a reference, and use it as the starting point for the next design so you are not solving the same problems twice.
Common mistakes to avoid
Even when the main rules are followed, small slips still creep in. The most common ones are letting decoration drift into the quiet zone, choosing colors that look distinct but share a brightness, and approving a design from a screen preview instead of a printed proof. Another frequent slip is changing one part of a working design, such as the link or the paper, without retesting the whole thing. Treat every change as a reason to run a fresh proof, and treat any hesitation in a test scan as a signal to simplify rather than to hope the next phone will cope better.
Quick checklist
- Keep dark modules on a light, even background with strong contrast.
- Leave a clear quiet zone on all four sides of the symbol.
- Keep the finder patterns solid, undisturbed, and easy to find.
- Check the code at the real size, on the real material, in the real light.
- Confirm the call to action names the payoff and the typed alternative works.
- Recheck the code after any change to the link, design, size, or placement.
Related tools and guides
- Try the [QR size presets](/qr-size-presets) to check your choices before you commit to a design.
- Use the [QR minimum size checker](/qr-minimum-size-checker) to confirm the numbers and guardrails for this element.
- Check the [QR safety checker](/qr-safety-checker) for a practical way to verify the finished code.
- Check the [printed QR tester](/printed-qr-tester) for a practical way to verify the finished code.
- Check the [QR placement guide](/qr-placement-guide) for a practical way to verify the finished code.
- Check the [blog](/blog) for a practical way to verify the finished code.
