What you are seeing
This fix restores strong contrast to the printed code. You will judge the proof in greyscale, strengthen the module and background colours, and reprint a single proof until the scanner separates the modules cleanly. Fall back to black on white if a decorative pair will not print with enough contrast.
Likely causes
1.
Colour pair too close in lightness — Quick test: view a photo of the code in greyscale and check the separation.
2.
Background darkened in print — Quick test: compare the printed background with the design.
3.
Modules printed pale — Quick test: check the ink level, the printer settings, and the module colour.
4.
Stock reduces the contrast — Quick test: print the same file on plain white stock and compare.
5.
Background pattern behind the code — Quick test: check whether the background behind the code is plain.
Step-by-step fix
Step 1: Photograph the proof and view it in greyscale. Note how cleanly the modules separate.
Step 2: Darken the modules and lighten the background to increase the lightness difference.
Step 3: If the background pattern or stock weakens the contrast, place the code on a plain white panel.
Step 4: Check the ink or toner level and switch off any economy or toner-save mode.
Step 5: Print a black-on-white proof on the same stock as a baseline and compare it with the colour version.
Step 6: Reprint one corrected proof and test it on two phones in the real lighting.
Step 7: Approve the run only when the proof passes, and fall back to black on white if the colour pair still fails.
Putting this into practice
In practice, keep black on white as the default for any code that must work in poor light or on an unfamiliar stock. Decorative pairs are fine when a proof shows they print with strong contrast, but they should earn that trust with a proof, not with a screen preview. Record the before-and-after behaviour with the job file, so the fix is provable rather than anecdotal. When the same failure appears again, that record tells you whether the old fix held or a new cause appeared.
Common mistakes to avoid
- Choosing a QR colour pair by how it looks in colour and never checking it in greyscale.
- 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 prints with low contrast will be used.
- Changing the artwork and the placement at the same time, so you cannot tell which change fixed a code that prints with low contrast.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- Greyscale contrast is strong on the printed proof
- The background behind the code is plain and light
- The proof scans on two phones in the real lighting
- 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 minimum size checker](/qr-minimum-size-checker)
- [QR contrast checker](/qr-contrast-checker)
- [QR print proof checklist](/qr-print-proof-checklist)
- [QR DPI calculator](/qr-dpi-calculator)
- [QR quiet zone calculator](/qr-quiet-zone-calculator)
- [printed QR tester](/printed-qr-tester)
- [QR size calculator](/qr-size-calculator)
