What you are seeing
You point a phone camera at the code and nothing happens: no preview banner, no link, no vibration, no error. The same phone scans other codes normally, so the problem sits with this code, its surface, or its placement rather than with the phone. A total failure like this usually has one dominant cause, which means a short, ordered diagnosis finds it fast. Work through the causes below from most to least likely before you reprint anything, because reprinting the same broken artwork only repeats the failure.
Likely causes
1.
Damaged or covered finder patterns — The three large squares in the corners tell the scanner where the code is. If a logo, sticker, fold, scratch, or crop covers any part of one, the scanner may never lock on. Test: look at all three corners closely and compare them with the original digital file; any corner that looks different from the file is suspect.
2.
Quiet zone eaten by nearby text or trim — Scanners need a clear margin around the symbol, about four modules wide, on all four sides. Text, borders, or a page edge that crowds the code can prevent detection even when the code itself is perfect. Test: check whether any ink, rule, or edge sits close to the code on any side.
3.
Contrast too low to separate modules — A code printed in pale colours, on a coloured background, or on a reflective surface can look fine to the eye while the camera sees a grey blur. Test: photograph the code and view the photo in greyscale; if neighbouring modules blur together, contrast is the problem.
4.
Payload is malformed or empty — A code that encodes a broken link, an unsupported scheme, or nothing at all may scan without ever producing an action, which looks like a total failure. Test: decode the code with a payload inspector and read exactly what it contains.
5.
Print too small for the scan distance — A code that works at arm's length can fail completely at poster distance because the camera cannot resolve the modules. Test: walk up to the code slowly; if it starts scanning at close range, size and distance are the problem.
Step-by-step fix
1. Photograph the code in the light where it will be used and compare the photo with the original file, corner by corner.
2. Clear or restore the quiet zone on all four sides, and move any text, rule, or border away from the symbol.
3. Reprint one proof in dark modules on a plain light background and scan it before touching anything else.
4. Decode the payload and confirm it is exactly the destination or data you intended, with no stray characters.
5. Test the proof at the real viewing distance on two different phones, one iPhone and one Android if you can.
6. Only when the proof scans reliably, reprint the full run from the corrected file and spot-check the first copies off the printer.
Putting this into practice
In practice, most dead codes fail for a visible reason: a covered corner, a crowded margin, or colours that looked bolder on screen than they print. Build a habit of scanning one proof copy at the real distance before any print run, and keep that proof with the job file so the next reprint starts from a known-good sample. Keep a short note of what you tested, what failed, and what you changed, so the next person starts from evidence rather than guesswork. A fix that is written down survives staff changes and reprints; a fix that lives only in memory gets repeated.
Common mistakes to avoid
- Reprinting the full run from the same file before testing a single proof, which turns one broken code into hundreds.
- Reprinting the full run before a single proof passes, which turns one failure into many.
- Testing on one phone in ideal conditions instead of two phones in the real conditions where a code that will not scan at all will be used.
- Changing the artwork and the placement at the same time, so you cannot tell which change fixed a code that will not scan at all.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- All three finder patterns are fully visible and match the digital file
- A clear quiet zone surrounds the code on all four sides
- Dark modules sit on a plain light background with strong contrast
- The corrected proof passes on two phones in the real conditions
- The fix is recorded in the job file so the next reprint starts from a proven setup
- Every printed copy is checked against the approved proof
- The proof is retested after any later change to the link, design, or placement
Related tools and guides
- [QR payload inspector](/qr-payload-inspector)
- [QR offline verifier](/qr-offline-verifier)
- [QR scanner](/qr-scanner)
- [QR size calculator](/qr-size-calculator)
- [QR safety checker](/qr-safety-checker)
- [blog](/blog)
