1. Test on Real Devices
Emulators and design software previews are not enough. Scan on a recent iPhone, a mid-range Android, and an older budget Android.
2. Test Conditions
* Good indoor light (office).
* Dim light (corridor, evening).
* Bright outdoor light with glare on the surface.
* The code held at the intended scanning distance, not closer.
3. Verify the Destination
Scan the code and confirm the destination URL is correct and loads fully. A typo in a URL is impossible to see by looking at the code.
4. Print a Proof
Print the design at actual size on the actual stock and scan the proof, not a monitor rendering. Colors shift and module sharpness changes between screen and print.
5. Check the Quiet Zone
On the print proof, measure the quiet zone with a ruler. It should be at least four modules wide on all sides.
6. Document the Code
Keep a record of every code printed: the slug or campaign name, the destination URL, the date, and the location. You will need this when a destination changes.
Putting this into practice
Start with the smallest real test you can run. Generate the code, print it at the exact size you plan to use, and scan it with two different phones in the lighting where it will live. Check that the destination page loads quickly on a mobile connection and that the call to action next to the code tells people what they will get. If anything feels slow or unclear, fix it before you print a full batch, because reprints cost more than a short test. Keep a note of the size, material, and placement that worked so the next batch starts from a proven setup.
Common mistakes to avoid
The most common mistakes are easy to avoid once you know them. Long payloads make modules tiny, low contrast makes edges hard to read, and text placed too close to the border eats the quiet zone the scanner needs. Covering a corner finder pattern with a logo or a sticker breaks detection entirely, and a code placed behind glare or on a curved surface fails even when the print is perfect. Review each of these points on a proof copy, and treat any failure as a reason to adjust the design rather than a reason to blame the scanner.
Quick checklist
- Keep the payload as short as practical so modules stay large.
- Keep dark modules on a light background with strong contrast.
- Leave a clear quiet zone on all four sides of the symbol.
- Test the printed code at the real viewing distance and lighting.
- Confirm the destination page loads fast on a phone.
- Recheck the code after any change to the link, design, or placement.
Related tools and guides
- Use the [QR size calculator](/qr-size-calculator) to match the printed size to the expected scan distance before you commit to a print run.
- Check print proofs with the [printed QR tester](/printed-qr-tester) so problems show up before a full run.
- The [QR placement guide](/qr-placement-guide) covers height, lighting, glare, and surfaces that affect scan success.
- Test every code with the [QR scanner](/qr-scanner) on more than one phone before you publish or print it.
- When a one-dimensional symbol fits better, the [barcode generator](/barcode-generator) covers retail and inventory formats.
- The [blog](/blog) collects more guides on sizing, printing, security, and payments for QR codes.
