What you are seeing
The printed code shows smeared ink: modules that bleed into their neighbours, a smear across one corner, or a fingerprint of ink where the sheet was handled. Smudging destroys the sharp module edges the scanner needs, and a smudge over a finder pattern can kill the code outright. The cause is usually wet ink, the wrong stock, or handling before the print dried. The fix is to let the ink dry, match the stock to the printer, and handle the sheets carefully.
Likely causes
1.
Ink not dry before handling or stacking — Sheets stacked or handled while the ink is wet smear the modules. Test: let a proof dry fully before touching it and compare.
2.
Wrong stock for the printer — A stock that does not absorb the printer's ink stays wet and smears at the lightest touch. Test: print the same file on the printer's recommended stock.
3.
Too much ink for the stock — A high-coverage or high-quality setting can lay down more ink than the stock can hold. Test: reduce the print quality setting one step and reprint.
4.
Humidity or cold slowing drying — Damp or cold conditions slow drying and keep the ink wet longer. Test: dry a proof in a warmer, drier spot and compare.
5.
Roller or guide smearing the sheet — A dirty roller or a guide that touches the printed side can smear a line across the code. Test: check whether the smudge appears in the same place on every copy.
Step-by-step fix
1. Print one proof and let it dry fully before touching or stacking it.
2. Confirm the stock is suitable for the printer and the ink.
3. Reduce the print quality setting if the stock is overloaded with ink.
4. Improve drying: warmer, drier air and more time before stacking.
5. Clean the rollers and guides if the smudge repeats in the same place.
6. Reprint one proof and confirm it is smudge-free before approving the run.
Putting this into practice
In practice, smudging is a handling failure as often as a printer failure. Give printed sheets time to dry, stack them carefully, and avoid touching the code area. A code that prints cleanly and smudges in handling is still a failed code. 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
- Stacking freshly printed sheets before the ink dries and smearing every code in the pile.
- 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 smudged ink 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 smudged ink.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- The proof dries clean without smudging
- The stock suits the printer and the ink
- Sheets are handled and stacked only after drying
- 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)
