Diagnostic guide
Why Your QR Code Will Not Scan
Start with the symptom, change one variable at a time, and test the exact file or printed object your audience will use.
Reviewed and updated July 21, 2026 · 8 minute read
First, separate a code problem from a destination problem
Scan the code and note what happens. If the camera never recognizes a code, inspect the symbol and print conditions. If the phone recognizes it but the page fails to load, the QR code has done its job and the destination needs attention. Check the full URL, HTTPS certificate, redirect chain, mobile layout and whether the page is publicly reachable without a private network or login.
Decode the exported image before printing. Then decode one item from the production batch. This catches an old asset, a changed redirect and layout software that altered the artwork. Keep the destination visible in your job notes so another person can verify it without relying on memory.
Fast symptom table
| Symptom | Likely cause | What to try |
|---|---|---|
| Works on screen, fails in print | The printed modules are too small, the image was enlarged from a low-resolution PNG, or the printer softened the edges. | Export again at the final size or use SVG, keep the image square, and print a 100% scale proof. |
| Scans only very close | The code is too small for the intended distance or carries too much data. | Enlarge the code and shorten the encoded URL. Test at the actual viewing distance. |
| Some phones scan, others do not | Marginal contrast, an inverted design, a damaged quiet zone or aggressive logo coverage often exposes differences between camera systems. | Return to a dark-on-light design, restore the full quiet zone and reduce the logo. |
| The scan opens the wrong page | The wrong URL was encoded, a redirect changed, or the printed asset came from an older export. | Decode the production file, compare the full destination, and add versioned filenames before sending artwork to print. |
| WiFi code is rejected | The network name, password or security mode does not match the router; hidden networks also need the hidden flag. | Copy the SSID exactly, including case and spaces, select the correct security type, and regenerate. |
1. Restore the quiet zone
Remove nearby borders, text, icons and background patterns. A standard QR Code needs a clear margin around all four sides. Cropping that area is one of the easiest mistakes to make when a designer fits the code into a small badge or product label. Adding a white rectangle behind the whole symbol is often safer than assuming the page background will remain clear.
2. Increase contrast without adding effects
Temporarily switch to black modules on a white background. Remove gradients, transparency, shadows, rounded masks and photographs. If that version scans, reintroduce branding cautiously. A design that works under perfect office lighting may fail through a glossy menu cover or when a phone casts its own shadow over the label.
3. Make every module physically distinct
QR images must remain square and should not be stretched. Avoid screenshots. If the code is a PNG, place it at or below its native pixel size. If you need multiple physical sizes, use an SVG export and let the layout application rasterize it for the final device. Ask the printer to avoid image enhancement or smoothing that blurs the hard edges.
Dense codes contain smaller modules at the same outside dimensions. Shorten long URLs and remove unnecessary query parameters. If the payload itself is large, increase the printed size rather than forcing it into the same small space.
4. Reconsider the logo and error-correction setting
A center logo covers real information. Error correction may recover some obstruction, but the result depends on where the covered modules fall and how much other damage the code receives. Reduce the logo, give it a plain light backing, keep all corner markers untouched and generate a new final code. Higher error correction can help with expected dirt or a modest logo, but may increase density, so it is not a substitute for adequate size.
5. Test the use environment, not your desk
For a window sign, test through the same glass and at the time of day when reflections are strongest. For packaging, wrap the proof around the real container; curved surfaces can hide or distort part of the symbol. For a presentation screen, test from the back row. For a restaurant table, test under evening lighting and after lamination. Use several phones and their built-in camera apps.
Special case: WiFi QR codes
The SSID and password are case-sensitive. Spaces and punctuation matter. Choose the router's actual security mode rather than guessing, and mark the network as hidden only when it is configured that way. Enterprise WiFi can require identity and certificate fields that a basic WPA/WPA2 QR payload does not represent. A WiFi code is also readable by anyone who can see it, so treat a public printout as sharing the password.
Special case: codes displayed on another screen
Increase brightness, remove screen glare and avoid presenting the code too close to the edge of a display. Do not animate, rotate or resize it while someone is trying to scan. If the code is on the same phone that needs to open it, use the operating system's image or screenshot recognition feature, or provide a normal clickable link alongside it.
Before ordering the full print run
- Scan the exported production file.
- Print a proof at exactly 100% scale.
- Test the proof on at least two phones.
- Test at the real distance, angle and lighting.
- Open the destination and complete its intended action.
- Archive the verified file with a clear version name.
If it still fails after returning to black on white, restoring the quiet zone and enlarging the code, regenerate it from the original data. The production file may have been cropped or corrupted. You can also compare the result with the principles in our complete QR Code Field Guide.