What you are seeing
The printed code looks soft: the module edges smudge together, the corners look rounded, and the scanner struggles or fails. Blurry printing comes from the file, the printer, or the stock, and the screen version usually looks sharp, which hides the problem until the proof comes off the printer. A blurry code is not a minor cosmetic fault; every blurred module edge is information the scanner has to guess. The fix is to find which stage softens the image and to correct that stage.
Likely causes
1.
Low-resolution raster stretched to print size — A small image enlarged for print spreads each pixel across several printed dots, which softens every edge. Test: check the exported pixel size against the printed size.
2.
Printer set to draft or economy mode — A draft mode lays down less ink and can leave ragged, soft edges. Test: reprint the same file at the printer's normal or high-quality setting.
3.
Ink spread on absorbent stock — Ink soaks into uncoated stock and thickens the modules until the gaps close up. Test: compare the proof with the digital file under magnification.
4.
Scaling in the layout software — A code resized inside a layout program can land on fractional pixels or be resampled, which blurs the edges. Test: place the code at its native size and reprint.
5.
Worn print head or low ink — A clogged nozzle or low toner can leave faint, uneven modules. Test: print a test page and check for banding, gaps, or faint areas.
Step-by-step fix
1. Export a fresh file for print: vector where possible, or a raster sized for the exact printed dimensions.
2. Set the printer to its normal or high-quality mode, not draft or economy.
3. Print one proof on the real stock and compare it with the digital file.
4. If the modules look thickened, switch to a less absorbent stock or enlarge the code.
5. If the edges look ragged, check the print head and the ink or toner level.
6. Approve the run only when a proof is crisp and scans on two phones.
Putting this into practice
In practice, the proof is the whole test. A screen preview cannot show ink spread, draft-mode softness, or a clogged nozzle. Print one proof on the real stock, compare it with the digital file, and scan it before you approve anything. 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
- 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)
