What you are seeing
This fix produces a smudge-free print by fixing the drying, the stock, and the handling. You will test the current setup, change one variable at a time, and reprint a single proof until it comes out clean. Do not approve a run while smudging is visible, because a smudged code fails unpredictably.
Likely causes
1.
Ink not dry before handling or stacking — Quick test: let a proof dry fully before touching it and compare.
2.
Wrong stock for the printer — Quick test: print the same file on the printer's recommended stock.
3.
Too much ink for the stock — Quick test: reduce the print quality setting one step and reprint.
4.
Humidity or cold slowing drying — Quick test: dry a proof in a warmer, drier spot and compare.
5.
Roller or guide smearing the sheet — Quick test: check whether the smudge appears in the same place on every copy.
Step-by-step fix
Step 1: Print one proof and set it aside to dry fully. Do not touch or stack it.
Step 2: Compare the dried proof with a proof handled immediately. If the dried one is clean, handling is the cause.
Step 3: Confirm the stock is suitable for the printer and the ink. Switch to a recommended stock if it is not.
Step 4: Reduce the print quality setting one step if the stock is overloaded with ink, then reprint.
Step 5: Improve drying conditions: warmer, drier air, and more time before stacking or trimming.
Step 6: Clean the rollers and guides if the smudge repeats in the same place on every copy.
Step 7: Reprint one proof, let it dry, and confirm it is smudge-free and scans on two phones before approving the run.
Putting this into practice
In practice, build drying time into the schedule for any QR run. A run that must be trimmed, folded, or packed the moment it leaves the printer will smudge, however good the print itself is. 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
- 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)
