What you are seeing
This fix restores solid dark modules to the printed code. You will check the file, the printer settings, the ink or toner, and the stock, then reprint a single proof and compare it with the digital file. Approve the run only when the modules are dark and the contrast is strong.
Likely causes
1.
Low ink or toner — Quick test: check the ink or toner level and print a test page.
2.
Economy or toner-save mode — Quick test: switch the economy setting off and reprint.
3.
File with pale module colour — Quick test: check the module colour in the file.
4.
Stock that absorbs or resists ink — Quick test: print the same file on plain white stock and compare.
5.
Wrong media setting — Quick test: confirm the media setting matches the stock.
Step-by-step fix
Step 1: Check the module colour in the file. Set the modules to a solid dark colour.
Step 2: Switch off any economy, toner-save, or draft setting on the printer.
Step 3: Check the ink or toner level and replace a low cartridge.
Step 4: Confirm the media setting matches the stock you are using.
Step 5: Print one proof on the real stock and compare the modules with the digital file.
Step 6: If the modules are still pale, test the same file on plain white stock to separate a stock problem from a printer problem.
Step 7: Reprint one proof and confirm the modules are dark and the code scans on two phones before approving the run.
Putting this into practice
In practice, switch the economy mode off for every QR job and leave it off. Toner-save settings exist for internal drafts, not for codes that visitors must scan. 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
- Leaving toner-save mode on for a QR print run and wondering why the codes look pale.
- 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 faded modules 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 faded modules.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- The modules are a solid dark colour in the file
- Economy and toner-save modes are off
- The proof modules are dark with strong contrast
- 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)
