1. Scan the original file
Open the PNG, SVG, or PDF you plan to hand over. Scan it from a normal viewing size, not only from a zoomed-in screen preview.
A QR code can look perfect on a screen and still fail on a table tent, poster, window, or product label. Test the finished thing people will actually scan.
First, scan the code and check the entire journey. Does it open the intended page? Does that page load on mobile? Is the page current, clear, and useful for someone who has no other context? A scannable code that opens the wrong, slow, or retired page is still a failed code.
If the destination may change after the print run, decide that now. A static code locks the final information into the pattern. A dynamic code lets you update the destination later without replacing the printed QR code.
Open the PNG, SVG, or PDF you plan to hand over. Scan it from a normal viewing size, not only from a zoomed-in screen preview.
Use the same printer, stock, finish, and approximate size as the final job whenever possible. A glossy, textured, curved, or low-contrast surface changes the result.
Test a table code while seated, a poster while standing back, and a sign from the distance people will notice it. Do not test a billboard from armβs length.
Use at least two current phones and their normal camera apps. Test in good light and the least forgiving light where the code will live.
Look at the code as a scanner sees it, not as a designer sees it at 400% zoom.
| Problem | What causes it | What to do |
|---|---|---|
| The camera does not recognise the code | Low contrast, a missing quiet zone, or a code that is too small | Increase contrast, restore clear space, and enlarge the code. |
| It works on screen but not in print | The printed version has been compressed, distorted, cropped, or placed on a difficult surface | Test the final exported file and a real proof before the full run. |
| It scans only when the phone is very close | The code is too small for its viewing distance | Increase physical size or move the code where people can get closer. |
| It scans but the experience is poor | The destination is broken, outdated, or not mobile-friendly | Fix the destination, then test the complete scan-to-page journey again. |
Save the final file, the destination URL, and a photo of the approved proof. If a future print run uses a different paper, supplier, or finish, test again rather than assuming the old result transfers perfectly.
For a dynamic QR code, test again whenever you change the destination. The printed image remains the same, but the page behind it is still part of the customer experience.