What you are seeing
This fix traces the blur from the file to the finished print and sharpens the stage that softens it. You will check the export, the printer settings, and the stock, then reprint a single proof and compare it with the digital file. Approve the run only when the proof is crisp.
Likely causes
1.
Low-resolution raster stretched to print size — Quick test: check the exported pixel size against the printed size.
2.
Printer set to draft or economy mode — Quick test: reprint the same file at the printer's normal or high-quality setting.
3.
Ink spread on absorbent stock — Quick test: compare the proof with the digital file under magnification.
4.
Scaling in the layout software — Quick test: place the code at its native size and reprint.
5.
Worn print head or low ink — Quick test: print a test page and check for banding, gaps, or faint areas.
Step-by-step fix
Step 1: Export a fresh print file as a vector, or as a raster sized for the exact printed dimensions.
Step 2: Set the printer to its normal or high-quality mode and print one proof on the real stock.
Step 3: Compare the proof with the digital file under good light, looking for soft edges, thickened modules, or gaps.
Step 4: If the image is soft, re-export at a higher resolution and reprint one proof.
Step 5: If the modules are thickened, switch to a less absorbent stock or enlarge the code.
Step 6: If the print is ragged or uneven, clean the print head and check the ink or toner level, then reprint.
Step 7: Approve the run only when the proof is crisp and scans on two phones, and check the first copies against it.
Putting this into practice
In practice, file the approved proof with the job and mark it as the reference. When a later reprint looks soft, comparing it with that proof tells you whether the file, the printer, or the stock changed. 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
- Approving a print run from a screen preview and discovering the blur only after the run is printed.
- 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 blurry will be used.
- Changing the artwork and the placement at the same time, so you cannot tell which change fixed a code that prints blurry.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- The print file is vector or high-resolution at the printed size
- The proof is crisp with clean module edges
- The proof scans on two phones
- 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)
